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
Input group | Purpose |
Current source material | Transcript, written context, uploads, and attached patient details provide facts for the current note. |
Historical context | Reference Notes can provide prior documentation when enabled; review whether it is still relevant. |
Reusable output preferences | Applicable Memory, the selected template (including changes saved by Learn), and Note Settings guide presentation and wording. |
The priority order
Vero separates clinical source accuracy from reusable output preferences.
Clinical content: Current source material and explicit instructions for this encounter take priority. Reference Notes remain background context and do not prove that older information is still current.
Output preferences: Applicable clinician preference Memory applies first, followed by the active template, then broad Note Settings where the higher-priority source is silent. Learn changes are part of the template; separate learned examples are no longer a note-generation input.
Required template content: Fixed visible text, triggered conditional blocks, and specific required template instructions are still preserved when they are clinically safe and source-supported.
A few practical consequences:
Vero should not invent content to satisfy a template or preference.
Current transcript, written text, and uploaded files override conflicting historical context.
The active template controls section order, headings, grouping, and presentation where applicable Memory is silent.
Write required headings as fixed visible text. Review the active version after Learn saves a change, just as you would after editing the template directly.
Specific template rules can override broad Note Settings when the rule is clinically safe.
How each input is used
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 up to five recent notes from earlier encounters for the same attached patient, selected by note creation date.
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 Learn updates a template
Generate a note, make a reusable style or structure edit, and click Learn in the note toolbar. Vero compares the edits and saves an accepted reusable improvement directly into a new template version. Simply editing a note does not update the template.
Changes can include headings, grouping, bullets or prose, equivalent phrasing, and reusable closing text.
Patient-specific corrections belong in the encounter. Learn should not turn patient facts into fixed template content.
If no reusable change is found, the template stays unchanged.
When someone else owns the template, Learn asks before using a personal copy. If you own the template, it updates that template directly, even if you have shared it.
Review learned versions in the template’s Version menu. To restore an earlier version, select its number, review the content, and click Save. Version selection alone is a preview. See Vero Learn for the changeover Q&A and full workflow.
Memory and preferences
Use templates for reusable rules about note headings, wording, structure, dates, signatures, or patient instructions. In Vero Chat, specify that the change should apply to the template or future notes. Use Note Settings for a broad default detail level.
Memory is for durable preferences about how Vero communicates with you or non-document workflows. For example: “Remember to keep your explanations to me brief.” Do not save patient information as Memory.
Previously saved note-formatting memories can still influence generated notes and take priority over templates. If a note keeps following an old preference, review Settings → Memory and remove the conflicting memory after putting the desired rule in the template. See Memory.
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.
Text replacements - 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 Learn to improve the template from edits. Demonstrate a reusable change in a generated note, select Learn, and review the saved template version.
Use Text replacements for repeated spelling or terminology fixes. One text replacement can affect every template.
Keep reusable note rules in the template. Reserve new Memory preferences for Vero's communication or non-document workflows.
Test with edge cases. A good template should still produce clean output when some fields are missing.
Frequently asked questions
How do I keep a required heading?
How do I keep a required heading?
Write it as fixed visible text in the active template. If it is still missing from generated notes, ask Fin in your existing support chat to check the active version, source information, and saved rule with you. If the issue remains unresolved after those checks, a teammate can investigate the template and an affected encounter. A generic placeholder alone does not reliably require a visible heading. See Template Fields & Rules.