CCA (AHIMA): The Template That Wrote Its Own Review of Systems

The risks:

• Auto-populated ROS. Text the clinician did not generate is not evidence that a review occurred. If the record is used to support an E/M level or an ED facility level, the level rests on work that may never have been performed. This is a documentation-integrity problem first and a coding problem second.
• Contradicted records (5). These are the dangerous ones. "Denies diaphoresis" sitting beside "diaphoretic on arrival" means the record cannot be trusted on its face, and a reviewer, attorney, or payer will find it. Resolve these first.
• Copy-forward (2). Carrying an eight-month-old HPI forward produces a clinically false history - wrong onset date, possibly wrong symptoms. Cloned documentation has been flagged by CMS, the OIG, and accreditors as a fraud and quality risk, and it is indefensible in litigation.
• Downstream coding. Severity of illness, risk of mortality, and any level driven by history/exam elements become unsupportable once the text is known to be boilerplate.

Immediate steps:

1. Sequence by risk: the 5 contradictions, then the 2 cloned HPIs, then the boilerplate ROS.
2. Issue compliant queries to the responsible physicians asking them to confirm what was actually performed and documented, and to correct the record by dated, timed, signed addendum where inaccurate. The coder does not delete or rewrite the entries.
3. Suspend code assignment for the affected encounters until the documentation is resolved - do not code the auto-text as though it were performed.
4. Notify the compliance officer and open a documentation-integrity log.
5. Open an IT ticket to remove the default-checked template content and to require active clinician entry, and confirm the mechanism for identifying templated text in the record.

The problem: a time-of-service stamp of April 13, 08:00 on care delivered April 12 is a factual error. Timing drives order validity, medication administration, restraint and seclusion limits, and the clinical picture used for code selection (for example, whether a condition was present on admission).

Handling:

1. Label every re-entered entry as a late entry, showing both the actual date and time the care occurred and the date and time the entry was made. The author must be identified and the entry authenticated.
2. Retain the original paper documents per retention policy and state law, and cross-reference them to the EHR entry. The paper is the contemporaneous source; it is not discarded after back-entry.
3. Correct the time-of-service fields through IT, using the audit trail, not by asking staff to re-key or overwrite. The correction itself must be traceable - who changed what, when, and why.
4. Verify orders placed on paper were authenticated within the required window and that any order whose validity depends on timing (restraints, medications, blood products) is reviewed individually.
5. Re-check any code assignment that depended on timing - present-on-admission determination and any time-sensitive clinical criteria - after the timestamps are corrected.
6. Debrief the downtime procedure afterward: pre-printed downtime forms with fields for time of occurrence and time of entry prevent this entirely and cost almost nothing.

System design controls:

• No default-checked or auto-inserted clinical findings in any template. A blank field is honest; a pre-filled "denies" is not.
• Restrict or require attestation for copy-forward of HPI and review-of-systems content, and require the clinician to confirm each carried-forward element.
• Make cloned and templated text identifiable to auditors through the system's metadata rather than by manual reading.
• Preserve robust audit logs of who viewed, entered, and amended each note.

Process controls:

• A documentation-integrity committee with medical staff representation, meeting on a defined cadence.
• Targeted audits: a monthly random sample plus a focused review of high-risk templates (ED chest pain, sepsis, observation conversions).
• Physician and APP education on what makes documentation defensible, tied to the audit findings - not generic training.
• A clear route for any staff member to report a documentation concern without retaliation.

Measures that tell you it is working:

• Proportion of records with unmodified template text, tracked monthly and trending down.
• Number of contradiction queries and the percent answered.
• Query agreement rate, which reveals whether the templates or the clinicians are driving the problem.
• A spot re-audit of the same 30-record population after the template fix; if the identical ROS still appears in more than a trace number of records, the fix did not take.