6.2 Reviewing Clinical Documentation for Completeness & Accuracy
Key Takeaways
- Documentation review checks completeness (is everything present and authenticated) and accuracy (is it internally consistent and clinically plausible).
- NHA names five common documentation errors: wrong directional terms, misspelled names, conflicting information, duplicate charting, and missing entries.
- Self-review is performed by the author before signing; peer-to-peer review is performed by a colleague or reviewer against defined criteria.
- Charting requirements include the primary diagnosis and any secondary diagnoses, with each order and service supported by documentation.
- The reviewer queries the author to resolve gaps and never edits another clinician's documentation.
Test plan task 2.C — "review and monitor clinical documentation to ensure completeness and accuracy (e.g., self-review, peer-to-peer)" — is a Domain 2 duty distinct from the formal HIM audits in Section 3.4. Those audits are scheduled and sampled; this is the ongoing, day-to-day quality check that catches problems before the chart closes. Knowledge statements 2.K9 and 2.K10 supply the error list and the charting requirements.
Two Review Modes
| Mode | Who Performs It | When | Purpose |
|---|---|---|---|
| Self-review | The author, before signing | At the end of documentation | Catch the author's own omissions and errors while memory is fresh |
| Peer-to-peer review | A colleague, informatics specialist, or CDI reviewer | Concurrently or shortly after | Catch what the author cannot see, and normalize practice across a group |
Neither replaces the formal quantitative and qualitative analysis described in Section 3.4; they feed it. Consistent findings from day-to-day review become the audit focus for the quarter.
The Completeness Checklist
Completeness asks whether everything required is present and properly authenticated:
- Two patient identifiers on every page or screen, and the correct patient and encounter selected
- Date and time of service, and of the entry itself
- Reason for visit and a documented chief complaint
- All required sections for the visit type present (history, exam, assessment, plan; operative note elements; discharge summary elements)
- Primary diagnosis documented, plus any secondary diagnoses relevant to the encounter (knowledge statement 2.K10)
- Every order placed has a documented indication
- Every service billed has supporting documentation
- Required consents and forms scanned and indexed
- Provider electronic signature present, with cosignature where policy or supervision requires it
- Allergy list addressed (including an explicit NKDA when applicable) and medication reconciliation completed at transitions
The Accuracy Checklist and NHA's Named Error Types
Accuracy asks whether the documentation is internally consistent and clinically plausible. Knowledge statement 2.K9 names the common errors explicitly:
| Error | What It Looks Like | Why It Is Dangerous |
|---|---|---|
| Directional term errors | "Left knee" in the HPI, "right knee" in the exam and order | Wrong-site procedure risk; the single highest-severity documentation error |
| Misspelling of names | "Jon Smyth" versus "John Smith" on a specimen label | Breaks matching at the interface and the clearinghouse; can cause a filing error |
| Conflicting information | Note says the patient is afebrile; the flowsheet shows 102.1°F | Undermines clinical decisions and legal defensibility |
| Duplicate charting | The same vitals entered twice with different values; the same problem listed twice under different terms | Reports and decision support cannot tell which entry is authoritative |
| Missing entries | A medication administered with no MAR entry; an order with no result | Creates a gap that reads as care not delivered |
Additional patterns worth catching: copy-forward content that contradicts the current visit (Section 5.3), anatomy documented on a patient who no longer has that anatomy, timestamps that make the sequence impossible, and unresolved template placeholders such as an unedited asterisk or bracketed prompt left in the signed note.
The Query Process
When a reviewer finds a gap, the response is a query — a formal request to the author for clarification. Compliant queries follow strict rules:
- Never edit another clinician's documentation. The author corrects the record through an addendum or erratum (Section 3.4).
- Never lead. A compliant query presents the clinical indicators and asks the author to clarify. "The note documents an infiltrate on chest x-ray, a WBC of 18.2, and IV antibiotics; can the associated condition be clarified?" is compliant. "Please document pneumonia so we can bill a higher DRG" is not — it is a leading query and a compliance violation.
- Offer multiple reasonable options plus "other" and "unable to determine" when a multiple-choice query format is used.
- Document the query — the question asked, who asked it, when, the author's response, and the resulting record entry. The query record is retained per policy.
- Escalate unanswered queries through the defined chain rather than assuming or dropping them.
Monitoring Over Time
"Monitor" in task 2.C means watching trends, not just individual charts:
- Delinquent record reports — unsigned notes, unsigned verbal orders, missing cosignatures by provider and by age
- Unbilled/held encounter reports — completed visits with no charges, usually pointing to unsigned documentation (Section 8.2)
- Query volume and response time by provider and by query type
- Repeat error patterns — one clinician consistently omitting laterality, one template consistently leaving a section blank
Trends are what justify a fix. A single missing laterality is a query; forty of them from the same template is a template defect, and the remedy is the change process in Section 6.1 plus targeted training from Section 4.5.
A reviewer notices that a progress note describes the patient as afebrile while the vitals flowsheet for the same encounter records a temperature of 102.1°F. Which documentation error category is this?
A coding reviewer sends a provider the message: 'Please document pneumonia so this encounter can be coded at a higher level.' Why is this improper?
What distinguishes self-review from peer-to-peer review of clinical documentation?