- Late entries, addenda, corrections and patient-requested amendments are four different things, and your policy should name each one.
- A legitimate correction brings the note into line with something else that existed at the time: the schedule, attendance, the eMAR, the clinician's own contemporaneous record.
- No correction can add medical necessity that was never documented, reconstruct a session from memory months later, or let someone else finish a departed clinician's note.
- Reviewers line up the date of every edit against the date of service, the claim, the payment and the records request, and clinical content added after a request is likely to carry little weight.
- When a request arrives, freeze editing on the requested records and route any real errors to compliance rather than cleaning up the chart.
A clinician opens a signed progress note from April, sees that the session end time is wrong, and fixes it. Another clinician, in August, adds two paragraphs of risk assessment to a note for an IOP day that was billed and paid months earlier, the week after the payer asked for the chart. In most EHRs both actions look the same: someone opened a signed note and changed it. A reviewer will not treat them the same way, and neither should your documentation policy.
Four things that get called a correction
Most programs use one word for several different acts. The differences matter because reviewers distinguish them, and because each one has a different legitimate use.
- Late entry. Documentation of something that happened but was not recorded at the time. It is dated when it is written, refers clearly to the date of service, and says it is late.
- Addendum. New information added to a note that was complete when signed, such as a toxicology result that came back the next day or a collateral call returned after the session. The original note stands untouched; the addendum sits beside it with its own date and author.
- Correction. A fix to an error in the original: a wrong date, a wrong time, text that landed in the wrong patient's template field. The original wording stays visible, with who changed it, when and why.
- Patient-requested amendment. Under the HIPAA Privacy Rule, a patient can ask a covered entity to amend health information in the designated record set, and the rule sets out how those requests are accepted or denied. It is the patient's right, not a clinician's editing tool, and it has its own procedure. Read the regulation directly when one arrives.
If your templates have a single "edit" button and no way to say which of these is happening, your record cannot tell a reviewer either.
What a correction can legitimately fix
The useful test is simple: a legitimate correction is supported by something else that existed at the time of service. It brings the note into line with the rest of the record.
- Clerical errors the record contradicts. A typed date of service that does not match the schedule, a start and end time that disagree with the attendance record, a diagnosis transposed in a field when the rest of the note plainly describes another.
- Misplaced content. Text that belongs to a different patient's note, removed from this one and corrected openly, with the error and the fix both visible. Misfiled content in a substance use disorder record may also raise a disclosure question under 42 CFR Part 2, so involve compliance.
- Information that arrived later. A lab result, a returned call, a pharmacy confirmation. Recorded as an addendum dated when it was added, not folded into the original as if it had always been there.
- A missing element where the act is documented elsewhere. For example, a signature the clinician genuinely omitted. Whether and how a signature can be supplied after the fact varies by payer; some accept a signature attestation process and some do not, so confirm before relying on one.
What a correction cannot fix
These are the edits that turn a documentation gap into a credibility problem.
- Memory doing the work of documentation. A late entry written long after the service, reconstructed from recollection, carries less weight the further it sits from the date of care. No single rule sets how long is too long across all payers, so check the payer policy, your state rules and your own policy, and set an internal limit beyond which a late entry goes to compliance review.
- Medical necessity that was never written down. If the note did not show why the patient needed this level of care that day, adding the justification after a denial or a records request looks like exactly what it is.
- Changing the service to match the claim. If attendance shows the patient left after forty minutes and the claim was billed as a full session, the note gets corrected toward the attendance record and the claim gets dealt with by billing. Never the reverse.
- A departed clinician's note. The unsigned note from a clinician who left in March cannot be completed by a supervisor writing it in their name. A supervisor can document their own knowledge and involvement, signed as themselves. What the departed clinician observed is not theirs to record.
- Overwriting. Any edit that removes the original text, rather than preserving it with the change, makes every other entry in that chart harder to trust.
How a reviewer reads a note edited after payment
A reviewer does not read a corrected note on its own. They build a timeline: date of service, original signature, claim submission, payment, records request, and the date of each edit. Medicare's Program Integrity Manual addresses amendments, corrections and delayed entries in medical documentation, and the principles it sets out are the ones most reviewers apply in some form: the change is clearly identified as a change, it shows who made it and when, and the original content remains readable. Entries that do not follow those principles may simply be disregarded. Medicaid programs and commercial payers have their own policies, so confirm the rules in each contract and manual that applies to you.
With the timeline in front of them, reviewers tend to ask the same questions:
- When was the edit made relative to the claim, the payment and the records request?
- Who made it, and were they the person who delivered the service?
- What did the original say, and can it still be read?
- Does the change fix a clerical detail, or does it add support for payment?
- Is there a pattern: a cluster of notes edited in the same week, across several charts, by the same people?
A May correction to an April end time that matches the attendance record is unremarkable. Clinical content added in August, after the request arrived, will probably be given little or no weight, and it gives the reviewer a reason to look harder at every other note in the chart. A pattern of edits across many charts in the days before a response is due reads as remediation of the record, not of the care.
A correction brings the note into line with what happened. It should never bring the note into line with the claim.
The week the records request arrives
The instinct when a request lands is to tidy the charts before they go out. Resist it. The cleanest response is the record as it actually stands, including its amendment history, compiled honestly.
- Freeze editing on the requested records. Tell clinicians the charts are under request and route any proposed change through the compliance lead.
- Separate errors from gaps. A genuine clerical error found during assembly can be corrected openly, dated and explained. A gap in documentation is not an editing task.
- Treat unsupported paid claims as a compliance question. If assembly reveals services that the record does not support, that is a conversation with compliance and counsel about potential overpayment obligations under Medicare, Medicaid and your payer contracts.
- Send the history with the note. A packet that shows an honest correction and its date reads better than one where the reviewer discovers the change later in the audit trail.
Write the policy before you need it
Most programs have a sentence about corrections in a documentation policy and nothing operational behind it. This is the minimum worth writing down this month:
- Define late entry, addendum, correction and patient-requested amendment, and give each a label in your note templates.
- State who may edit a signed note: the author, for their own content. Supervisors add their own signed addenda; they do not edit someone else's clinical observations.
- Require every correction to carry a reason, a date and an author, with the original content preserved.
- Require late entries to say they are late, name the date of service and state the source of the information. Set an internal threshold beyond which a late entry needs compliance review.
- Route any edit to a billed note to billing. If the change affects time, units, the service, the provider or the date, the claim may need a corrected claim or a refund, and billing makes that call.
- Freeze edits on records under request until compliance releases them.
- Review post-signature edits monthly, by clinician and by program, and look for patterns before a reviewer does.
The principles here are general. Your payer manuals, state Medicaid rules, accreditor standards and contracts set the specifics, including signature requirements and any limits on late documentation. Check each one that applies before you finalize the policy.
Where the system should carry the weight
A correction policy only works if the EHR makes the right edit easy and every edit visible. Ask of whatever system you run: can you see the original text after a change, who changed it and when, and can you produce that history on request without an engineer?
In Unisona Health, the activity log records every view, edit, signature and export with the user and timestamp, entries cannot be edited or deleted by anyone, and they are retained for seven years, so the edit history a reviewer asks about is a report rather than a reconstruction. Upstream, the documentation clock makes unsigned notes visible from the end of the session and escalates them to supervisors before they go overdue, which is the most reliable way to need fewer late entries in the first place.
Frequently asked questions
What is the difference between a late entry and an addendum in a progress note?
A late entry documents something that happened but was not recorded at the time; it is dated when written, refers to the date of service and says it is late. An addendum adds new information, such as a lab result received later, to a note that was complete when signed, leaving the original untouched.
Can you edit a progress note after the claim has been paid?
You can correct genuine errors, openly, with the original preserved and the date, author and reason recorded. A reviewer will compare the edit date to the claim, payment and any records request, and clinical content added after a request is likely to carry little weight. Any edit that changes time, units, service or provider should go to billing, which may need to submit a corrected claim or a refund.
Can a supervisor finish an unsigned note for a clinician who left?
Not in the departed clinician's name. A supervisor can write their own signed addendum describing their own knowledge and involvement, but what the departed clinician observed is not theirs to record.
Should we fix chart errors before responding to a payer records request?
No. Freeze editing on the requested records and route proposed changes through compliance. Genuine clerical errors can be corrected openly with a date and reason; documentation gaps are a compliance question, not an editing task, and the amendment history should go out with the record.
Can a patient make us change a clinical note under HIPAA?
A patient can request an amendment to information in the designated record set under the HIPAA Privacy Rule, and the rule sets out how such requests are accepted or denied. It is a separate procedure from a clinician's own corrections, so read the regulation directly when a request arrives.
