A template is not just a document. It is a set of instructions Vero combines with source material, patient context, saved preferences, and your note style to produce a finished note.
This article explains how those pieces fit together so you can predict what Vero will produce and design templates that stay consistent.
What Vero Uses When Generating a Note
When you click Create or regenerate a note, Vero can combine several inputs:
Transcript - the recording or uploaded audio transcript from the current encounter.
Written text - anything typed into the encounter context area.
Uploaded documents - PDFs, Word files, text files, images, referral letters, lab results, or other supported context files.
Attached patient profile - name, pronouns, date of birth, sex, past medical history, medications, allergies, social history, and family history when present.
Reference Notes - saved notes from the same encounter or the most recent previous note for the same attached patient, when those settings are enabled.
Your template - the plain text,
[fields],(rules), and rich text formatting in the selected template.Learnings - previous notes you have taught Vero for this template, used as style examples.
User settings - detail level, quotes, abbreviations, bullets, paragraphs, output language, and Replace terms.
Clinician preference memory - durable preferences you explicitly asked Vero to remember, such as formatting or communication style. This is not for patient facts.
The Priority Order
When inputs conflict, Vero resolves the conflict by using the most reliable and most current information first.
Highest priority: clinical accuracy and current source material.
Middle priority: the selected template, explicit current instructions, and Reference Notes as background.
Style layer: Learnings, clinician preference memory, and user settings shape wording and formatting when they do not conflict with clinical accuracy or current source material.
A few practical consequences:
Clinical accuracy beats everything. Vero should not invent content just to satisfy a template rule.
Current transcript, written text, and uploaded files should override older notes when they conflict.
Reference Notes are historical context, not proof that older information is still current.
Learnings and memory are style/preference signals, not patient-specific source material.
Template rules can override broad user settings when the rule is specific and clinically safe.
Source Material: Transcript, Written Text, Uploads
Vero treats the main source types differently.
Source | Role |
Transcript | Primary current-visit source when a recording or audio upload is used. |
Written text | Intentional clinician-provided context, corrections, pasted details, or note-specific instructions. |
Uploaded documents | Historical context, outside records, referral letters, forms, reports, or source material that should inform the note. |
Patient profile | Stable chart details such as demographics, pronouns, PMH, medications, allergies, social history, and family history. |
If you want to override a template for one encounter without editing the template, type the instruction into the encounter's written text before generating or regenerating.
Reference Notes
Reference Notes add saved notes as context when the relevant preference is enabled.
Reference Current Encounter Notes uses other saved notes from the same encounter.
Reference Previous Patient Notes uses the most recently updated usable note from the most recent previous encounter for the same attached patient.
Use Reference Notes when a follow-up document should account for prior documentation. Do not use it as a substitute for reviewing the current note or confirming that older information still applies.
How Learnings Interact With Templates
Learnings are style examples. They teach Vero how you write when using a specific template.
What Learnings can shape:
Section headers and abbreviations, such as
S:vsSubjective:.List style, line breaks, and spacing patterns.
Clinical phrasing preferences, such as "denies chest pain" vs "no chest pain".
Capitalization, punctuation, and signature/footer style.
What Learnings should not do:
They should not add patient facts that are not in the current source material.
They should not override a template's content placement rules when the template is clear.
They should not replace clinician review.
Key idea: Templates teach Vero what goes where. Learnings teach Vero how you write. Detail level tells Vero how much to include.
Memory and Preferences
Clinician preference memory can help Vero remember durable, non-patient-specific preferences that you explicitly ask it to remember.
Good memory examples:
"Remember that I prefer concise assessment and plan sections."
"Remember that my clinic uses DD/MM/YYYY dates."
"Remember that I prefer patient instructions in plain language."
Do not use memory for:
Patient facts.
Encounter-specific diagnoses or plans.
Identifiers, demographics, contact details, or other patient information.
For details, see Memory: Saved Clinician Preferences.
User Settings
User settings are the broad preference layer.
Detail level - controls how concise or thorough the note is.
Quotes - includes direct patient quotes when clinically relevant.
Abbreviations - uses standard medical abbreviations when appropriate.
Bullets - favors list-style output.
Paragraphs - favors prose output.
Replace terms - applies your spelling, abbreviation, and terminology replacements.
Template-specific rules are usually better for preferences that apply only to one template. User settings are better for preferences that should apply broadly.
Design Principles for Strong Templates
Use the template for content placement. Decide which sections get which facts.
Use rules for constraints. Examples: only include if mentioned, keep to one line, place pending tests under Plan.
Use Learnings for style. Teach Vero examples when you like the final shape of the note.
Use Replace for repeated spelling or terminology fixes. One Replace entry can affect every template.
Use Memory for durable clinician preferences. Keep it about your workflow, not patient information.
Test with edge cases. A good template should still produce clean output when some fields are missing.