Clinical Documentation Integrity Review

It covers the documentation elements that affect coding accuracy and risk capture: encounter identification, diagnostic specificity, clinical support, consistency across notes, HCC capture, and plan alignment. The template is built to surface deficiencies that may require a provider query or CDI follow-up. It is not a coding cheat sheet; it is a review tool for determining whether the record supports the documented diagnoses. Use it to compare what was assessed, what was treated, and what was actually written.

Use it during concurrent CDI review, pre-bill review, retrospective audit, or targeted chart sampling for high-risk service lines. It is especially useful when the record includes multiple diagnoses, changing acuity, or conditions that may affect CC/MCC, SOI/ROM, or HCC capture. It can also be used after denials or coding audits to identify recurring documentation gaps. If the encounter is simple and fully self-evident, a lighter review may be enough.

A CDI specialist, coding auditor, compliance reviewer, or trained clinical documentation reviewer should complete it. In some organizations, a nurse auditor or HIM professional may use it first, then route findings to the provider or coding team. The reviewer should understand clinical terminology, documentation standards, and how payer-facing coding decisions are supported by the chart. The template is not meant to replace provider judgment or coder assignment rules.

It prompts the reviewer to confirm that the condition is not only named, but also clinically supported, current, and relevant to the encounter. That matters because CC/MCC and HCC capture depend on documentation that shows acuity, significance, and linkage to care. The template also helps identify when a chronic condition is mentioned in history but not addressed, which can weaken risk adjustment support. If the chart is vague, the template flags where a query may be needed.

Common issues include unspecified diagnoses, inconsistent problem lists, missing laterality or episode details, and secondary conditions that are listed but not supported by assessment or treatment. Reviewers also often find that chronic conditions are carried forward without current evidence, or that the plan does not match the stated diagnosis. Another frequent gap is unclear terminology such as 'rule out,' 'possible,' or 'history of' used where a definitive status would be more appropriate. These are the kinds of issues that can trigger coding delays or queries.

The cadence depends on volume and risk, but many teams use it concurrently for high-impact encounters and periodically for retrospective sampling. You may review every inpatient discharge, selected ED visits, or a rotating sample of outpatient charts with HCC relevance. If your organization is rolling out a new CDI workflow, a short-term higher-frequency review can help stabilize documentation habits. After that, a steady audit schedule is usually enough to track trends.

Yes. The core structure works across inpatient, outpatient, emergency, and specialty clinics, but the examples and query triggers should be tailored to the setting. For example, an inpatient version may emphasize acuity, discharge status, and CC/MCC support, while an outpatient version may emphasize chronic condition assessment and HCC capture. Specialty-specific terms, common diagnoses, and local query standards can be added without changing the overall review flow.

An ad hoc review often catches obvious issues but misses repeatable patterns because each reviewer uses a different standard. This template gives the team a consistent walk-through so findings are easier to compare, trend, and act on. It also creates a cleaner record of what was reviewed, what was deficient, and what follow-up was recommended. That makes it easier to support education, queries, and compliance oversight.

No. It supports documentation review, but it does not replace coding guidelines, payer policy, or your organization’s compliance procedures. The reviewer still needs to apply official coding rules, medical necessity standards, and internal escalation paths. Use the template as a structured audit tool, then route findings through the appropriate CDI, coding, or compliance workflow. If a case is ambiguous, the template should help document why a query or escalation is needed.