Dot phrases have a discoverability problem. Even if a great template is ready to go in order for it to be useful it needs to be easy to access in the moment. If a clinician cannot find it quickly then they are more likely to just write it out by hand instead of wasting more time looking for it.
Treating template discovery as its own design discipline helps prevent a large clinical template library from becoming a memory test.
Repertoire is for patient-independent template management, not patient documentation. Do not enter PHI, identifiers, or patient-specific information. Complete encounter-specific documentation in the organization-approved EMR and obtain appropriate organizational approval before use.
Start with a canonical title
Every managed template needs one clear title that acts as its stable identity.
A good canonical title should be:
- specific enough to distinguish nearby templates
- written in language familiar to the intended users
- consistent with the library’s naming conventions
- stable even if aliases change
- free from local shorthand that outsiders cannot interpret
Avoid generic titles such as “follow-up,” “plan,” or “screen.” If several templates need the same leading phrase, add the distinguishing context in a consistent place.
Test titles as a group. A title that looks clear by itself may become ambiguous beside ten related templates.
Use aliases as deliberate routes, not extra titles
An alias is another phrase that intentionally leads to the canonical template. It may be an abbreviation, a common synonym, or a remembered local term.
A useful alias is:
- specific to one template
- likely to be used intentionally
- long enough to avoid accidental recognition
- reviewed for collisions
- easy to remove or revise when usage changes
Do not add every possible wording variation. A large uncontrolled alias list recreates the maintenance problem under another name.
Start with one or two high-confidence aliases. Add more only when failed searches show a recurring need.
Keep automatic recognition conservative
Search and automatic insertion have different risk profiles.
Search can return several candidates and let the user choose. Automatic recognition changes the document, so it should require stronger confidence.
Repertoire’s automatic matching is exact by design. A supported template title, alias, or eligible Building Block name or alias must occupy the complete line, apart from capitalization and trailing punctuation. Templates are checked first. Reusable statements and narratives can insert directly; reusable choices need a saved default. Conflicting reusable recognition phrases and all other ambiguous phrases are left untouched.
This may feel less magical than fuzzy insertion, but it is also easier to understand, test, and trust.
Design categories for browsing
Categories are not merely metadata. They are a fallback when the user does not know the title or trigger.
A useful category system has:
- a manageable number of choices
- labels familiar to the target audience
- consistent rules for where a template belongs
- a way to handle cross-category concepts without duplicating content
Review the “Other” category periodically. It can reveal missing taxonomy or templates whose scope is unclear.
For example in the default pediatric library, users may search by diagnosis, complaint, organ system, visit type, age-specific workflow, or follow-up context. The library does not need to force all of those into categories if title and alias search can carry part of the load.
Protect the namespace
As a library grows, template titles and aliases become a namespace. Treat it as shared infrastructure.
Before approving a new name:
- Normalize capitalization and punctuation.
- Check for an exact existing title or alias.
- Review common abbreviations.
- Flag unusually short terms.
- Test the phrase as ordinary text.
- Decide whether it belongs to one template unambiguously.
Repertoire performs normalized collision checks for custom templates and workspace imports. That protects exact recognition, but human review is still needed for near-overlaps and confusing concepts.
Discoverability is part of template quality
Coverage asks whether the right reusable structure exists.
Discoverability asks whether a person can reach it with the language they actually use.
Measure both. Fix titles, aliases, taxonomy, and search behavior before adding duplicate content. Keep automatic recognition conservative, and let ambiguity remain visible rather than guessing.
A template that cannot be found has not completed its job.
Next: put these principles into practice by customizing and reusing clinical note templates.