Medical Record Signature Requirements for AI Notes

CMS added artificial intelligence to its scribe-signature guidance in July 2025. The practical rule is short: the treating practitioner signs an AI-transcribed entry when Medicare signature requirements apply, and the scribe does not need to sign or date it (CMS MLN905364, July 2025).

That sentence settles who acts. It does not tell a practice which version was reviewed, what to do with a missing signature, or how to keep an electronic signature from becoming a shared button. Those are the policy and system questions that decide whether concurrence can be proved later.

Key takeaways

• Treat every AI note as a draft until the responsible clinician reviews and authenticates it.
• Keep authorship, transcription provenance, and clinical concurrence as separate facts.
• Route missing, illegible, late, and post-signature corrections through different exception paths.
• Test six synthetic failure cases before measuring how fast clinicians can clear the queue.

This article is an operational reading of current federal sources, not legal or billing advice. Medicare policy, a hospital condition of participation, state law, payer rules, service-specific requirements, medical-staff bylaws, and local policy can set different or stricter conditions. Name the source behind each rule in your own policy.

CMS added AI to the scribe rule

CMS does not describe a signature as decoration at the bottom of a note. Its July 2025 fact sheet says reviewers look for signed and dated documentation from the people responsible for providing care. It also says reviewers use signatures for two purposes: meeting an explicit rule and resolving concern about whether documentation is authentic (CMS MLN905364, July 2025).

That distinction matters. A missing signature does not have one universal consequence across every record. The relevant statute, regulation, national coverage determination, local coverage determination, order requirement, and authenticity evidence determine the path. A clinic policy that says “all unsigned notes fail” is too blunt. A policy that says “sign whenever convenient” is worse.

Hospital records have a separate federal baseline. 42 CFR 482.24 requires hospital medical-record entries to be legible, complete, dated, timed, and authenticated by the person responsible for providing or evaluating the service, consistent with hospital policy. The same section requires final completion of hospital records within 30 days after discharge. That 30-day condition is hospital-specific. Do not paste it into an office policy and call it a universal Medicare deadline.

One signature carries three facts

The current Medicare Program Integrity Manual names AI directly. When a scribe documents a medical-record entry, CMS does not require the scribe to sign or date it. The treating practitioner signs to affirm that the note adequately documents the care. CMS says the same practitioner concurrence is required when artificial intelligence captures the transcription (Medicare Program Integrity Manual, section 3.3.2.4).

So the useful record has three separate facts:

Fact	The question it answers	Evidence to preserve
Clinical author	Who provided or evaluated the service?	Practitioner identity and role
Draft provenance	How did the words enter the draft?	Approved workflow metadata under local policy
Concurrence	Who reviewed and accepted this entry?	Signature, date or time evidence, and record version

Do not make the AI tool the clinical author. Do not make a generic “AI generated” badge substitute for the clinician’s action. And do not hide the draft source if local policy requires provenance. These are different controls.

Give each signature exception its own lane

A queue labeled “unsigned” usually mixes problems that should not share a fix. Use the matrix below before anyone starts clearing old charts.

Exception	First question	Safe operational path
Ordinary unsigned draft	Has the clinician reviewed the actual final draft?	Review, correct, then sign under the normal policy
Wrong clinician assigned	Who provided or evaluated the service?	Reassign through an approved path; never sign for a colleague
Material error before signature	Does the draft match the encounter evidence?	Correct the draft, preserve necessary provenance, then review again
Missing required signature found later	Does the controlling rule permit attestation?	Use the author-created attestation path only when allowed
Illegible handwritten signature	Can the author be identified?	Attach the approved signature log or other allowed evidence
Correction after signature	Does the record need an addendum or correction?	Preserve the signed entry and use the approved amendment path
Order missing a signature	Is the order subject to a distinct timing rule?	Stop and apply the order-specific rule; do not reuse the note-attestation lane

CMS accepts an attestation for some missing signatures in medical records other than orders. The record’s author must create it, it must identify the beneficiary and entry, and it cannot repair a rule that required the signature before a specific event or date. CMS gives the plan of care as an example: an attestation cannot backdate it (CMS MLN905364, July 2025).

For an illegible signature, CMS permits a signature log or an attestation that identifies the signer. A signature log may be created later. That does not turn it into a universal repair for missing authorship, a wrong signer, or a missing order. It answers an identity problem.

Break the version chain on purpose

Use synthetic records. No real patient information belongs in an acceptance test.

1. Send a correct draft to the responsible clinician and confirm that the signed version is the version reviewed.
2. Put the wrong patient in a draft and confirm that it cannot be signed into the intended chart.
3. Change a medication or assessment sentence before signature and confirm that the clinician sees the changed version.
4. Leave a required signature missing and confirm that the exception remains visible to its owner.
5. Submit an illegible handwritten signature and confirm that the approved signature-log path identifies the author.
6. Request a correction after signing and confirm that the original stays intact while the approved addendum carries its own author and time.

Time the ordinary case only after all six pass. Fast review of the wrong version is still wrong.

Only then build the worklist

The worklist should show more than a red badge. At minimum, capture the encounter identifier, responsible clinician, draft-created time, current version, review state, exception type, signature time, and final disposition. Limit the worklist to the information needed for the job, and keep access consistent with the practice’s security controls.

One clean state model is enough:

DRAFT CREATED
  -> CLINICIAN REVIEW
      -> CORRECTION NEEDED -> CLINICIAN REVIEW
      -> READY TO SIGN
          -> SIGNED AND LOCKED
              -> APPROVED CORRECTION OR ADDENDUM, IF NEEDED

EXCEPTION PATHS
  wrong clinician | missing signature | illegible signature | order rule

Measure the queue by age and reason, not only by total count. “18 unsigned” tells you there is work. “Seven awaiting first review, three returned for material correction, six ready to sign, two assigned to the wrong clinician” tells you what to fix.

The medical-chart audit checklist helps test a sample after rollout. If signed content needs a later change, use the separate correction and addendum workflow instead of overwriting the original entry.

The button is not the evidence

CMS tells providers using electronic signatures to protect the system against modification and to apply administrative safeguards that fit recognized standards and laws. The signer and provider remain responsible for authenticity. CMS also directs physicians to check with counsel and malpractice insurers about alternative signature methods (CMS MLN905364, July 2025).

A vendor demo should therefore answer concrete questions:

• Can one user apply another user’s signature?
• Does the record show which version the clinician reviewed?
• What happens when the note changes after review but before signature?
• Can an administrator see the signature time without changing the record?
• Does an addendum preserve the original signed content?
• What evidence leaves with the practice during an export or vendor exit?

We think the version question is the most revealing. A polished signature screen is not useful if a late edit can slip into the note without a fresh review.

The software should stop before authorship

AI Scribe by Patient Square is an ambient AI medical scribe. It listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft, ready to review and sign about two minutes after the visit.

The clinician owns the review and signature. The scribe does not decide whether a Medicare signature requirement is satisfied, invent a concurrence statement, apply a colleague’s identity, or choose an attestation route. Those decisions stay with the practice’s clinicians, compliance owners, billing owners, and counsel.

Use the clinical documentation audit to compare source evidence with a finished note, then run the six signature cases above. The product question comes after the record-control question: can your team show who reviewed which version and what happened when the normal path broke?