Guide

Template craft: prompts, not prose

Summary

Build templates as prompts that force a different answer each visit, not prose that reads the same every time. A template should ask 'what changed since last visit' and 'what's the plan today,' with free-text fields wherever the answer is supposed to vary — not pre-write the sentence and let the clinician click through it unedited. Cloned documentation, where two encounters read identically, is one of the most consistent audit findings across payers, and templates are usually the cause.

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

Prompts, not prose

A template built as prose pre-writes the sentence and asks the clinician to click through it; a template built as prompts asks a question and leaves the answer blank until you fill it in for this specific visit. The difference sounds small and isn't — prose templates are what payer reviewers mean when they flag cloned documentation, because a pre-written sentence looks identical whether or not anything about the patient actually changed.

The fix isn't fewer templates, it's a different kind of field. Replace "patient reports feeling well, no new complaints" with a blank field labeled change since last visit and force yourself to type something into it every time — even "none reported" is a real answer, typed fresh, instead of a sentence that was already sitting there before the patient walked in. The result should read closer to the defensible note than to a form letter.

Why cloning is a specific, named audit target

Documentation that looks copy-pasted across encounters draws attention for a concrete reason: Medicare's signature and authentication expectations assume each note reflects the clinician's independent judgment about that specific visit, and an attestation exists to cure a missing signature, not to vouch for content that was never actually reviewed 1Ref 1Centers for Medicare & Medicaid Services (2023).Complying with Medicare Signature Requirements.Establishes that signature and attestation authenticate independent clinical judgment for a specific visit, supporting why identical content across visits draws review scrutiny..

A reviewer comparing two visit notes word-for-word isn't just checking a box — identical assessment-and-plan language across unrelated visit dates is one of the more common triggers for a documentation-integrity referral, because it suggests the note was generated by the template rather than by the encounter. Templates that pre-populate the assessment or plan section with static language are the highest-risk design choice you can make, even when every word in them happens to be true.

The 2021 E/M shift changed what a good template should even ask

The AMA's 2021 revisions removed history and exam from the elements that set an office visit's code level, replacing them with medical decision making or total time — which means a template still built around exhaustive review-of-systems checkboxes is documenting something that no longer determines what you can bill 2Ref 2American Medical Association (2023).CPT evaluation and management (E/M) revisions.Establishes that the 2021 E/M revisions removed history/exam as level-setting elements in favor of MDM or time, changing what a template should be built to capture..

CMS's E/M guide walks through what actually needs documenting under the current framework: the number and complexity of problems addressed, the data reviewed, and the risk of the management chosen — three things that are different at essentially every visit for a given patient, which makes them naturally resistant to cloning if your template asks about them directly instead of burying them under a checkbox exam 3Ref 3Centers for Medicare & Medicaid Services (2023).Evaluation and Management Services Guide.Supports describing what MDM-based documentation (problems addressed, data reviewed, risk) requires, as the content a clone-resistant template should prompt for.. If your templates still lead with a lengthy review of systems, that's usually legacy structure from before 2021, not a current documentation requirement.

Coverage-specific documentation still needs its own field

Some services carry documentation conditions beyond E/M leveling — psychiatric services and incident-to billing both have their own requirements in Medicare's Benefit Policy Manual, and a generic template built for a routine visit will miss them unless you build a specific field for them 4Ref 4Centers for Medicare & Medicaid Services (2026).Medicare Benefit Policy Manual (Pub. 100-02).Supports that psychiatric-service and incident-to billing carry their own documentation conditions beyond E/M leveling, requiring dedicated template fields..

Keep the problem list and med rec as their own structured sections rather than folding them into free text — both are places where a template's job is to remind you to update something, not to generate prose, and both are exactly what a payer or a subsequent treater actually needs to find fast.

Designing the prompt: field types that force differentiation

Three field types resist cloning better than a single open text box: a forced-choice field that still requires a second free-text line ("stable / worsening / improved — describe"), a date-anchored field that references the last visit by name, and a checklist that expires — one you have to re-answer rather than one that remembers last visit's answer as the default.

Avoid designing a field that defaults to "unchanged" or pre-fills the prior visit's answer; that single design choice is responsible for more accidental cloning than deliberate copy-paste ever is, because it makes the path of least resistance identical documentation. If your EHR's template builder can't stop a field from auto-populating with the prior encounter's value, that's worth flagging as a real limitation, not a minor annoyance.

What belongs in free text vs a structured field

APA's record-keeping guidelines describe the content a behavioral health note is expected to carry — presenting problem, intervention, response, plan — without prescribing a specific template format, which leaves the free-text-versus-structured-field decision to you 5Ref 5American Psychological Association (2007).Record Keeping Guidelines.Supports describing the content a behavioral health note is expected to carry, informing the free-text-vs-structured-field design decision.. That decision is where most solo-practice templates go wrong: everything gets forced into the same kind of field, either all rigid checkboxes or all open paragraphs, when the two genuinely different content types call for two different designs.

As a rule, put anything that's supposed to vary session to session — the clinical narrative, the patient's own words, your interpretation of a symptom — in free text, and reserve structured fields for things that are genuinely checklist-shaped: medication names, screening scores, safety-plan status. When a patient hands you patient-supplied paper, outside records, a symptom log, a specialist's letter, summarize it into the note in your own words rather than scanning it into a template field verbatim; a scanned attachment isn't documentation of your review, a summary is.

Testing the template before you rely on it

Before a new template goes live, run it against two different patients on two different days and read the outputs side by side — if you can't tell which note belongs to which encounter without checking the header, the template is still prose, not prompts.

Apply the same test to any template touching the referral log or the inbound pile of outside records — both are high-volume, repetitive workflows where a badly designed template clones fastest, precisely because the underlying task really does look similar from case to case. Revisit every template on the same schedule you review anything else in the EHR; templates drift toward convenience over time, and a good one two years ago can be exactly the cloned-documentation risk you're trying to avoid today.

Common questions

Two or more notes, usually for the same patient on different dates, that share substantially identical assessment or plan language with nothing to show the clinician actually reconsidered the case. It's a template-design problem more often than a shortcut a clinician takes deliberately — a field that defaults to the prior answer produces the same result as copy-pasting, just automatically.

Only the parts built around history and exam as level-setting checkboxes — those elements no longer determine your code level under the current medical-decision-making or time framework. Keep templates that prompt for the problems addressed, data reviewed, and risk of the plan; those are still exactly what needs documenting, and cloning them is harder because the answer genuinely differs by visit.

Yes — the problem list is meant to persist and be updated, not rewritten from scratch each time; that's different from cloning the assessment and plan narrative. Keep it as its own structured field you actively edit, adding, resolving, or reprioritizing entries, rather than letting it sit untouched, which is its own kind of quiet inaccuracy.

No — summarize what's clinically relevant in your own words instead. A scanned attachment shows the paper exists; it doesn't show you reviewed and incorporated it, which is what the documentation is actually supposed to demonstrate. Save the original as an attachment if you want a record of it, and use the template field for your summary.

Whenever you update a template's content, and at least once a year even if nothing prompted it — templates drift toward convenience over time as clinicians, including you, find ways to click through them faster. Test any template against two different real encounters and see whether the outputs actually read differently before trusting it again.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

1.Centers for Medicare & Medicaid Services (2023). Complying with Medicare Signature Requirements. CMS Medicare Learning Network (MLN905364). link ✓Establishes that signature and attestation authenticate independent clinical judgment for a specific visit, supporting why identical content across visits draws review scrutiny.
2.American Medical Association (2023). CPT evaluation and management (E/M) revisions. American Medical Association (AMA). link ✓Establishes that the 2021 E/M revisions removed history/exam as level-setting elements in favor of MDM or time, changing what a template should be built to capture.
3.Centers for Medicare & Medicaid Services (2023). Evaluation and Management Services Guide. CMS Medicare Learning Network (MLN006764). link ✓Supports describing what MDM-based documentation (problems addressed, data reviewed, risk) requires, as the content a clone-resistant template should prompt for.
4.Centers for Medicare & Medicaid Services (2026). Medicare Benefit Policy Manual (Pub. 100-02). Centers for Medicare & Medicaid Services (CMS). linkSupports that psychiatric-service and incident-to billing carry their own documentation conditions beyond E/M leveling, requiring dedicated template fields.
5.American Psychological Association (2007). Record Keeping Guidelines. American Psychological Association. link ✓Supports describing the content a behavioral health note is expected to carry, informing the free-text-vs-structured-field design decision.

https://www.gale.care/for-providers/cde-building-templates · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

← Back to for providers