Skip to main content
This template editor allows you to create reusable clinical documentation templates. Use the special syntax below to create dynamic content that can be customized for each patient encounter. The preview panel shows you exactly how your template will appear to other clinicians.

How It Works

Templates define the structure and sections of your clinical documentation. They ensure consistency across similar encounters and align with your specialty, setting, and workflow. Learn the syntax below to create powerful, dynamic templates.

# Section Headings

Structure your template with clear section headers using # for major sections and ## for subsections. Major section heading:
# History of Present Illness
Subsection heading:
## Physical Examination

Patient Variables

Use curly braces to create placeholders that will be filled with patient-specific data during each encounter.
VariableDescription
{patient_name}Patient’s full name
{chief_complaint}Primary reason for visit
{vital_signs}Current vital measurements
{age}Patient’s age
{date_of_birth}Patient’s date of birth
{physical_exam_findings}Physical examination results
{assessment}Clinical assessment
{treatment_plan}Treatment plan details
Variables are automatically populated from patient data and the transcription content.

Verbatim Text

Text enclosed in quotation marks appears exactly as written in every case. Use this for standard clinical phrases and terminology. Examples:
"Findings on auscultation include"
"Current presentation is suggestive of"
"Physical examination reveals"

Instructions to AI

Use parentheses to guide the AI assistant on how to structure and format content in your documents. Examples:
(List out the chief complaints in bullets if more than one)
(Summarize the patient's symptoms, including onset, duration, and severity in bullet points)
(Do not include relevant family history and risk factors in this section)
Instructions to AI help ensure consistent formatting and content structure across all generated documents.

Complete Example Template

Here’s a full example of a cardiology SOAP note template using all the syntax elements:
# SOAP Note - Cardiology

## Subjective
Patient: {patient_name}
Age: {age} | DOB: {date_of_birth}

Chief Complaint: {chief_complaint}
(Summarize the patient's symptoms, including onset, duration, and severity in bullet points)

## Objective
Vitals: {vital_signs}

"Physical examination reveals" {physical_exam_findings}

## Assessment & Plan
{assessment}

{treatment_plan}

Clinical Documentation Best Practices

Follow these guidelines when creating templates to ensure quality and consistency:

Use Consistent Variable Names

  • Use the same variable names across all templates (e.g., {patient_name} not {name})
  • Maintain a standard set of variables for common data points
  • Document custom variables for team reference

Include Clear Instructions

  • Provide AI instructions to guide content generation and formatting
  • Be specific about desired output format (bullets, paragraphs, etc.)
  • Specify what information to include or exclude in each section

Use Verbatim Text Strategically

  • Apply verbatim text for standard medical terminology and phrases
  • Use it to maintain consistent language across documentation
  • Ensure phrases meet clinical and regulatory standards

Structure for Clinical Standards

  • Follow established documentation standards (SOAP, APSO, etc.)
  • Organize sections in a logical clinical flow
  • Include all required sections for your specialty and setting

Test and Preview

  • Use the preview panel to verify template formatting
  • Test templates with sample data before sharing with team
  • Iterate based on clinician feedback and real-world use

Consider Compliance Requirements

  • Ensure templates meet regulatory documentation requirements
  • Include necessary elements for billing and coding compliance
  • Review templates with compliance team when appropriate
Always review generated documentation for completeness and accuracy. Templates guide structure, but clinical judgment is required to verify content.

Choosing the Right Template

Select a template that matches your clinical context before starting a session.

Common Template Types

Template typeUse case
Problem-focused visitBrief consultations addressing specific complaints
Comprehensive reviewAnnual exams, new patient visits, complex cases
Procedural noteMinor procedures, injections, wound care
Counseling visitMental health, behavioral health, care planning
Specialty-specificTemplates aligned with cardiology, pediatrics, etc.
Match your template to the encounter type before you start. Switching templates mid-session isn’t supported.

How Templates Work with Transcription

When you end a session, Quiver Transcribe:
  1. Analyzes the conversation transcript
  2. Maps content to the sections defined in your selected template
  3. Generates a structured summary with appropriate headings
  4. Populates each section based on what was discussed and patient variables
Templates guide structure, not content. If a section wasn’t discussed during the consultation, it may appear empty or minimal in the summary. This is expected behavior.

Managing Your Templates

Creating Templates

Define templates that reflect your documentation standards:
  1. Identify the sections you need for a specific encounter type
  2. Use the syntax guide above to structure your template
  3. Add patient variables, verbatim text, and AI instructions as needed
  4. Preview your template to verify formatting
  5. Save the template with a clear, descriptive name

Editing Templates

Update templates as your documentation needs evolve:
  • Add or remove sections to match new workflows
  • Adjust AI instructions for better content generation
  • Update variable names for consistency
  • Refine verbatim text based on clinical feedback
  • Rename templates for clarity

Organizing Templates

Keep your template library manageable:
  • Use clear naming conventions (e.g., “Pediatric Well Visit”, “Adult Problem Visit - Cardiology”)
  • Archive templates you no longer use
  • Share templates with team members when appropriate
  • Review and update templates periodically
Changes to a template only affect future sessions. Past notes generated with an older version of the template remain unchanged.