Copy-Forward in Therapy Notes and Cloned Documentation

“Cloned documentation” is a Medicare term, not a software term. When a Medicare Administrative Contractor’s reviewer finds two visit notes that read the same, from the subjective line down to the plan, the record is treated as cloned, whether the sameness came from a keyboard shortcut, a saved template, or an EHR default. CGS, the Jurisdiction 15 Part B contractor, puts the definition in two sentences in its electronic medical record guidance: “Cloning occurs when medical documentation is exactly the same from beneficiary to beneficiary. It would not be expected that every patient had the exact same problem, symptoms, and required the exact same treatment.”

That definition is judged by outcome, not mechanism, so the real question for a therapy practice is not “is copy and paste allowed” but which fields in today’s note are allowed to carry forward, and which have to be entered fresh at every visit. Medicare’s own therapy manual does not require a daily note to repeat the plan of care or re-argue medical necessity, so some carry-forward is expected, not just permitted. The fields that must never repeat are the ones describing what happened today: the interventions provided, the minutes, and the signature.

There is also a mirror-image risk the top search results don’t mention: an EHR that defaults every field to blank rather than carrying anything forward can cause underbilling if staff assume the fields were prefilled. This guide works through the primary sources on cloning, what a therapy daily note has to contain, a field-by-field carry-forward matrix, and that underbilling trap. Current as of September 2026.

What is cloned documentation under Medicare?

The same CGS guidance, dated September 6, 2012 and still posted, names the EHR feature directly: “Electronic Health Records allow providers to copy forward clinical documentation. This process of copying existing text in the record and pasting it in a new destination is often used by clinicians to save time when updating notes on an existing patient, it is also known as copy and paste, cloning, and carry forward, among other terms.” The contractor’s objection is to the result, not the feature: “All documentation in the medical record must be specific to the patient and her/his situation at the time of the encounter.” Noridian, the Jurisdiction E Part B contractor, states the same idea in its low-tech form, in guidance last updated July 30, 2025: providers should “Not use statements such as ‘same as above’ or ditto marks (“). This is not acceptable documentation that service was provided on that date.”

AHIMA, the professional body for health information management, collapses all of this into one term. Its Copy Functionality Toolkit defines copy as “any one of the following synonyms: copy and paste, cloning, copy forward, re-use, carry forward, and save note as a template and any intent to move documentation from one part of the record to another.” Copy forward and cloning are the same behavior under AHIMA’s vocabulary, and its 2014 position statement, quoted in the toolkit, sets the bar practices are held to: “The use of copy/paste functionality in EHRs should be permitted only in the presence of strong technical and administrative controls which include organizational policies and procedures, requirements for participation in user training and education, and ongoing monitoring.” The MAC articles that dominate the search results for “cloned documentation medicare” were written for evaluation and management coding, not therapy daily notes, which the manual treats differently, covered below.

What happens when a reviewer finds cloned notes?

CGS is direct about the consequence: “Cloning of documentation is considered a misrepresentation of the medical necessity requirement for coverage of services. Identification of this type of documentation will lead to denial of services for lack of medical necessity and recoupment of all overpayments made.” The same page adds a practical instruction: “Providers using electronic records should conduct regular self-audits to be sure your documentation meets the above mentioned criteria.”

CMS’s own guidance to providers, MLN909160, “Complying with Medical Record Documentation Requirements,” explains why insufficient documentation becomes a repayment demand: “If there’s no or insufficient documentation, then there’s no justification for the services or level of care billed,” and an already-paid claim “we may consider… an overpayment, which we can partially or fully recover.” CERT reviewers flag claims when “the reviewer couldn’t determine whether some of the allowed services were actually provided, were provided at the level billed, or were medically necessary,” citing examples like “Incomplete progress notes (for example, unsigned, undated, insufficient detail)” and cases where “the documentation submitted by the physician or NPP didn’t support certification of the plan of care (POC).”

This is not a hypothetical for the CPT codes therapists bill every day. First Coast Service Options publishes Targeted Probe and Educate round results for rehabilitation services outpatient with review rounds for 97110, 97112, and 97140 running as recently as 2026. Top denial reasons include documentation that “does not support medical necessity as listed in coverage requirements” and that “did not support the number of therapy minutes/units billed,” alongside missing certifications, evaluations, and progress reports. A minutes field carried forward instead of entered fresh produces exactly that finding, a different failure mode than the other reasons therapy claims get denied.

Does Medicare prohibit templates or copy-forward?

No, and this is where the articles that rank for this query stop short. The Medicare Program Integrity Manual (Chapter 3, §3.3.2.1.1, Rev. 13008, issued December 18, 2024, effective January 17, 2025; chapter table of contents Rev. 13821, issued June 9, 2026) is explicit: “The CMS does not prohibit the use of templates to facilitate record-keeping. CMS also does not endorse or approve any particular templates except for the clinical templates it publishes on its website.” It adds that “Contractors shall consider information captured in templates when conducting medical review.”

What the manual discourages is narrower than templates in general: templates using “‘check boxes,’ predefined answers, limited space to enter information,” because such templates “often fail to capture sufficient detailed clinical information to demonstrate that all coverage and coding requirements are met.” A carried-forward note nobody edits becomes exactly that kind of template: it captures the plan, not the visit. The same chapter’s signature requirements section (§3.3.2.4) adds that authorship is a separate concern from content: Medicare requires the responsible clinician “be identifiable as such in accordance with Medicare billing and coverage policies,” to “resolve authenticity concerns related to legitimacy or falsity of the documentation.” A signature on a carried-forward note asserts that today’s clinician observed what the note describes.

The mechanism is visible to reviewers even when the wording has been edited. Two Office of Inspector General reports found Medicare’s contractors poorly equipped to catch it. In 2013, OIG reported that “only about one quarter of hospitals had policies regarding the use of the copy-paste feature in EHR technology” and recommended “audit logs be operational whenever EHR technology is available for updates or viewing.” In 2014, OIG found that “few contractors were reviewing EHRs differently from paper medical records” and “not all contractors reported being able to determine whether a provider had copied language or overdocumented in a medical record,” noting that “Audit log data distinguish EHRs from paper medical records and could be valuable to CMS’s contractors when reviewing medical records.” An EHR’s audit trail shows whether an entry was typed today or carried forward, evidence these reports found contractors were not consistently using.

What a therapy daily note must contain, and what it doesn’t have to repeat

Section 220.3 of the Medicare Benefit Policy Manual, Chapter 15 (Rev. 255, issued January 25, 2019; chapter current revision Rev. 13889, issued July 30, 2026) sets the baseline: “Documentation must be legible, relevant and sufficient to justify the services billed,” and reviewers must read the whole record rather than any single entry in isolation, “so that the absence of an individual item of documentation does not negate the medical necessity of a service when the documentation as a whole indicates the service is necessary.”

For the treatment note specifically (§220.3.E), the manual is direct about purpose: it exists “simply to create a record of all treatments and skilled interventions that are provided and to record the time of the services in order to justify the use of billing codes on the claim,” required “for every treatment day, and every therapy service,” but “not required to document the medical necessity or appropriateness of the ongoing therapy services.” And it says outright what may repeat: “Specifics such as number of repetitions of an exercise and other details included in the plan of care need not be repeated in the treatment notes unless they are changed from the plan.”

What must be entered fresh every visit, per the same section, is a short list: “Date of treatment”; “Identification of each specific intervention/modality provided and billed, for both timed and untimed codes, in language that can be compared with the billing on the claim to verify correct coding”; “Total timed code treatment minutes and total treatment time in minutes,” with the rule that “the billing and the total timed code treatment minutes must be consistent”; and “Signature and professional identification of the qualified professional who furnished or supervised the services and a list of each person who contributed to that treatment.”

The skilled-care language is what turns an unedited exercise list into a red flag: a clinician “must apply the skills of a therapist by actively participating in the treatment of the patient during each progress report period,” shown through “the changes made to the treatment due to a clinician’s assessment of the patient’s needs on a particular treatment day.” The manual also expects a note when progress stalls: “the reasons for lack of progress be noted and the justification for continued treatment be documented if treatment continues after regression or plateaus,” an expectation sharpest around maintenance therapy and plateaus, where reusing last visit’s language is most tempting.

Progress reports, by contrast, run on a longer clock: they provide “justification for the medical necessity of treatment” and are due “at least once every 10 treatment days.” Necessity gets re-argued there, and at plan of care certification, not in every daily entry. See the five required documents and four treatment-note elements for how the daily note fits the rest of the chart.

Which fields can carry forward in a therapy note?

Medicare’s rules on templates, signatures, and daily-note content add up to a field-by-field answer rather than a blanket rule. The table below sorts a typical therapy note by what may safely carry forward from the prior visit.

Field Carry forward? Why
Diagnosis, referral, precautions, contraindications Yes, edit if changed Plan-level content; “need not be repeated … unless they are changed”
Long-term goals, plan of care Yes, edit if changed Same rule; changes at progress reports and recertification, not daily
Exercise list and parameters (sets, reps, resistance) Carry, then edit every visit May stand unless changed, but skilled care expects visible “changes … on a particular treatment day”; unchanged for weeks reads as unskilled
Subjective / patient report Never A statement about today; identical text across dates is the textbook cloning example
Objective measures (ROM, strength, pain, functional tests) Never as values; measurement list may carry as a prompt Record must show “progress toward goals,” which yesterday’s numbers cannot do
Assessment and clinical reasoning Never Where “changes due to progress the clinician judged sufficient” get documented
Interventions provided and billed today Never Required daily; must match the claim “in language that can be compared with the billing”
Timed minutes and total treatment time Never Required daily element; “the billing and the total timed code treatment minutes must be consistent”; TPE rounds flag minutes/units not supported
CPT codes and units Never prefilled Units derive from today’s minutes; see the 8-minute rule
Signature and signer Never Signer attests to today’s authenticity

The top two rows are plan-level content the manual says need not repeat unless it changes. The exercise row may carry but needs a visible edit every visit. Everything below documents something specific to today’s encounter, so none of it belongs prefilled.

The other failure: carry-forward defaults that cause underbilling

Everything above treats carry-forward as the risk to guard against. There’s a mirror-image risk none of the articles ranking for this topic mention: a system that refuses to carry anything forward can cost a practice money if staff assume otherwise. Rehabilitation Health builds PrismEHR, and the product deliberately does not prefill CPT units from the prior visit: units default to zero on every new note, so a note can’t silently inherit yesterday’s billing. In practice, some users expected the units field to already reflect the visit the way other fields did, and left it at zero without checking, which produced underbilling until the workflow was retrained.

The lesson generalizes: an anti-cloning default only works if the workflow makes the empty or zero field impossible to miss, ideally through a check that runs automatically, such as a claim-creation rule flagging a note with timed minutes and zero units, rather than relying on every clinician remembering to look.

Do AI-drafted notes count as cloning?

The same test applies regardless of what produced the text. AHIMA’s definition of copy already includes “save note as a template” and “re-use,” so a note assembled from a stored template or a prior note, whether by a macro, a smart phrase, or a language model, reads the same to a reviewer if the output reads the same across dates. The MAC rule doesn’t carve out an exception for the tool behind the draft: documentation “must be specific to the patient and her/his situation at the time of the encounter.” Whatever produced it, the fields in the matrix above still have to be true for today’s visit before the note is signed. A closer look at AI-generated documentation is planned for a future post.

A carry-forward policy checklist for a therapy practice

AHIMA’s 2014 position statement names the three controls a practice needs around any copy functionality: “organizational policies and procedures, requirements for participation in user training and education, and ongoing monitoring.” Translated into an EHR setup:

Control In practice
Written policy Field-by-field carry-forward policy matching the table above, not a blanket “always” or “never” rule
Field-level defaults Plan-level fields open for edit; minutes and units default to zero or blank, never to the prior visit
Staff training Covers both failure modes: notes that repeat too much, and blank fields left unfilled because staff assumed a default was prefilled
Claim-creation check Flags a note with timed minutes and zero units, or the reverse, before the claim goes out
Ongoing monitoring Periodic audit-log review of whether entries are authored fresh or carried forward

PrismEHR does not prefill CPT units from the prior visit: units default to zero on every new note. Organizations can define their own billing rules, including minute and unit restrictions, that are enforced at the point of documentation and reinforced again at claim creation. See how this fits physical therapy practices, and pair the carry-forward rules above with how therapy claims actually get denied.