How to define and organize your abbreviations
As your template library grows, remembering every abbreviation is becoming harder.
Without a clear pattern, abbreviations become inconsistent, duplicated, or hard to guess.
A good strategy keeps templates easy to find.
Some ideas to address this are: use short prefixes, organize templates into groups, let SmartComplete — PhraseExpander's built-in suggestion pop-up — and Quick Find — PhraseExpander's template search tool — help you narrow the list.
This article walks through a practical prefix system, a starter map built around common medical workflows, and a step-by-step rollout plan you can apply to any size template library.
The examples here use medical workflows. The same prefix logic applies to any domain — customer support, legal, administration, or any team managing a large template library.
Related: Learn more about SmartComplete in the SmartComplete article.
Recommended pattern
Choosing a consistent pattern before adding templates is the most important step. It determines whether users can guess or discover abbreviations they have not memorized.
| Pattern | Use it for | Examples |
|---|---|---|
| note section + topic | HPI, exam, assessment/plan, and other note-writing templates | hpi-knee, hpi-uti, ap-dm, ap-htn |
| workflow + topic | Tasks that cut across specialties or conditions | rx-htn, ref-cv, msg-lab, lab-a1c |
| condition/specialty + action | Large libraries where users often start from a disease area or specialty | dm-fu, htn-fu, cv-ref, hem-ref |
Starter prefix map
Medical users usually retrieve templates by workflow, specialty, condition, or communication type. The map below is a starting point — adapt the prefixes to match the terms your practice already uses.
| Category | Prefix | Examples |
|---|---|---|
| History/HPI | hpi | hpi-knee (knee pain HPI), hpi-uti (urinary symptoms HPI), hpi-uri (upper respiratory infection HPI) |
| Assessment/plan | ap | ap-dm (diabetes A/P), ap-htn (hypertension A/P), ap-afib (atrial fibrillation A/P) |
| Exam | ex | ex-cv (cardiovascular exam), ex-resp (respiratory exam), ex-neuro (neurological exam) |
| Prescriptions | rx | rx-htn (hypertension medication instructions), rx-abx (antibiotic instructions), rx-refill (refill wording) |
| Referrals | ref | ref-cv (cardiology referral), ref-gi (gastroenterology referral), ref-hem (hematology referral) |
| Patient messages | msg | msg-lab (lab results message), msg-rx (medication instructions), msg-fu (follow-up message) |
| Labs/results | lab | lab-a1c (HbA1c result wording), lab-cbc (CBC result wording), lab-lipid (lipid panel result wording) |
| Common conditions | dm, htn, afib, copd | dm-fu (diabetes follow-up), htn-fu (hypertension follow-up), afib-ap (atrial fibrillation A/P) |
| Specialties | cv, gi, hem, pulm, neuro | cv-ref (cardiology referral), gi-ref (GI referral), hem-ref (hematology referral) |
You can add the . prefix to each template if you used to it but it’s not necessary as PhraseExpander displays the suggestions as you type and you can confirm them by pressing the SHIFT key.
Examples
Here is how the pattern plays out across realistic clinical text-expander examples. These are not intended to be universal medical abbreviations. They are example naming patterns based on common clinical documentation workflows, so each abbreviation is predictable from the prefix map above.
| Abbreviation | Meaning | Why it works |
|---|---|---|
| hpi-knee | Knee pain history of present illness | Note section plus complaint |
| hpi-uti | Urinary symptoms history of present illness | Note section plus presenting problem |
| ap-dm | Diabetes assessment/plan | Note section plus condition |
| ap-htn | Hypertension assessment/plan | Note section plus condition |
| ex-cv | Cardiovascular exam | Exam section plus body system |
| rx-htn | Hypertension medication instructions | Prescribing workflow plus condition |
| rx-abx | Antibiotic instructions | Prescribing workflow plus medication type |
| ref-cv | Cardiology referral | Referral workflow plus specialty |
| ref-hem | Hematology referral | Referral workflow plus specialty |
| msg-lab | Patient message about lab results | Message workflow plus topic |
| lab-a1c | HbA1c result wording | Results workflow plus test |
SmartComplete makes this easier
Users do not need to memorize every full abbreviation. Typing the first few characters is enough — SmartComplete shows matching templates as they type and narrows the list with each keystroke.
Abbreviations can include a hyphen to improve readability — hpi-knee instead of hpiknee, for example. SmartComplete matches what you type regardless of the hyphen, so users never need to type it.
| User types | What happens |
|---|---|
| hpi | Shows HPI templates |
| hpik | Narrows toward knee pain HPI templates |
| hpiknee | Finds the hpi-knee template — users type hpiknee without the hyphen and SmartComplete matches it |
| ref | Shows referral templates |
| refc | Narrows toward cardiology referral templates |
| msgl | Narrows toward lab result message templates |
Groups should match your prefixes
In PhraseExpander, groups are folders inside a glossary. They help you organize related templates so users can browse the library by clinical area or workflow, rather than relying solely on memory.
For example, a medical glossary might include groups such as HPI, Assessment/Plan, Prescriptions, Referrals, Patient Messages, and Labs/Results.
Groups and abbreviations work best when they follow the same logic. If your abbreviations use prefixes such as hpi, ap, rx, ref, msg, and lab, your groups should mirror those categories.
That way, users can either browse to the right group or start typing the prefix in SmartComplete to reach the same set of templates.
| Group | Possible prefixes | Contains |
|---|---|---|
| History/HPI | hpi | HPI templates for common presenting complaints |
| Assessment/Plan | ap | Problem-based assessment and plan wording |
| Exam | ex | Physical exam wording by body system |
| Prescriptions | rx | Medication instructions, refill text, and counseling |
| Referrals | ref | Referral letters and consult requests |
| Patient messages | msg | Portal replies, result messages, follow-up text |
| Labs/results | lab | Result comments and patient-facing result explanations |
| Common conditions | dm, htn, afib, copd | Follow-up, plans, monitoring, and education for common chronic conditions |
| Specialties | cv, gi, hem, pulm, neuro | Specialty-specific notes, referrals, and plans |
Changing your prefixes
You do not need to get every prefix right on the first attempt. If your library grows and you realize that a prefix is too broad, unclear, or inconsistent, you can change it later.
In PhraseExpander, you can change the abbreviation prefix from the context menu:
- Select a template, multiple templates, a group, or an entire glossary.
- Right-click the selection.
- Choose Abbreviation > Change prefix.
- Add a new prefix, replace the existing one, or remove a prefix.
This is useful when you need to course correct. For example, if you started with cd for cardiology but later decide that cv is clearer for your users, you can update the affected templates in bulk instead of renaming each abbreviation one by one.
When you don't remember: Quick Find
QuickFind searches template names, abbreviations, and content — so users can find a template by describing the clinical idea when they do not remember the abbreviation.
- Search cardiology referral to find ref-cv, cv-ref, or related referral templates.
- Search the lab result message to find msg-lab or lab-result templates.
- Search diabetes follow-up to find dm-fu or related diabetes templates.
Rollout playbook
- Audit the current library and identify duplicate, unclear, or regular-word abbreviations.
- Choose a small starter set of 2-3 character prefixes.
- Use a two-part pattern: specialty/topic plus action.
- Rename the most-used templates first.
- Organize groups to match the same structure.
- Train users to type the first few characters and rely on SmartComplete.
- Use Quick Find when users remember the concept but not the abbreviation.
- Review after a few weeks and adjust prefixes that are too broad or confusing.
Mistakes to avoid
- Using regular words as abbreviations, such as pain, note, plan, or refill. They can work at the beginning, but things can get messy as you add more and more abbreviations
- Creating unrelated abbreviations one template at a time.
- Making prefixes so long that users stop typing them.
- Making prefixes so cryptic that only the creator understands them.
- Using one structure for abbreviations and a different structure for groups.
- Expecting users to memorize the library instead of using SmartComplete and Quick Find.
Start small
Pick three or four prefixes from the starter map above and rename your most-used templates to match. You do not need to rebuild the whole library at once. Once a few templates follow the pattern, the logic becomes obvious, and the rest falls into place faster. Try typing a prefix in SmartComplete to see the system in action, and use Quick Find whenever you cannot recall the full abbreviation.