The CDI Module: Clinical Documentation Integrity as Its Own Workflow

A well-run CDI programme pays for itself many times over. Industry studies report denial reductions of 25 percent or more, stronger case mix index accuracy, and millions in additional appropriate reimbursement each year. The reason is simple: payers adjudicate the documented record, not the care that was delivered. When the record is complete and specific, claims are paid the first time, audits are survivable, and quality reporting reflects the true acuity of the patients treated.

Those benefits only materialise when CDI runs consistently on every encounter. The Medical Copilot CDI Module is a standalone product built for that: it reviews the full encounter, finds the gaps, manages the query conversation with the physician, tracks every query to closure, and marks the record ready for coding. It never generates or alters final codes, so the separation between review and coding that auditors expect is preserved by design.

Reviewing the encounter the way a specialist would

The module begins by reading the full clinical context together: demographics, history, chief complaint, history of present illness, assessment and plan, recorded diagnoses, and the services delivered. A documentation gap is only visible when the whole encounter is read at once, so nothing is assessed in isolation.

From that complete reading, the review covers four questions:

  • Is the chart complete? Conditions that were treated but never stated, findings that support a diagnosis that was never carried into the assessment, and services with no documented indication are all surfaced.
  • Is the documentation specific enough? The module checks each documented condition against the coding guidelines for the detail its code requires: type, stage, acuity, laterality, and the clinical relationships between conditions. If the record stops short of that detail, the gap is flagged.
  • Does the encounter hold together? A coherence assessment surfaces material documentation issues and coding gaps, such as an assessment that does not match the findings, or a plan that treats a condition the note never establishes.
  • Does it meet the applicable standard? The review is aligned with the documentation standards of the market it is deployed in, so it reflects what the payers and regulators adjudicating the claim actually expect, not a generic checklist.

The review covers both outpatient and inpatient encounters, and the inpatient side is being extended further as the product develops.

Throughout, the module assesses and asks. It does not write codes, and it does not decide what the clinician meant.

Compliant provider queries, generated automatically

When the review finds a gap, the module prepares a physician query that follows the AHIMA documentation standards for compliant query practice. Each query is non-leading, tied to the specific evidence in the record, and presented in whichever of three formats fits the question: multiple choice, yes or no, or open-ended.

Because the query is generated from the encounter itself, the physician sees exactly which part of the record prompted the question and can answer quickly, either by selecting an option or by adding a free-text comment. The answer belongs to the physician; the module never fills it in.

A full query lifecycle, tracked end to end

A query is not an email that disappears into an inbox. The module tracks every query through a full lifecycle: Draft, Open, Answered, and Closed. The CDI specialist reviews a draft before it is sent, the physician's response is captured with both the selected choice and any comments, and the resolution is recorded against the encounter. Nothing is left in an ambiguous state, and nothing depends on memory or spreadsheets.

An inbox built for the CDI team

Day-to-day work runs through a dedicated CDI review inbox. The team sees status breakdowns at a glance, including draft, open, answered, closed, and expired queries, and can filter the query list by encounter or by status. Each item opens into a detail view with the full query, the evidence behind it, and the response history, so a specialist can pick up any case without reconstructing its context.

Finalise, hand over, and prove it

When the queries on an encounter are resolved, one click finalises the review: open queries are closed and the encounter is marked ready for the next stage. Where the team needs to release an encounter earlier, partial finalise is supported, with the count of still-open queries reported so nothing is silently dropped.

Everything the module does is persisted. Timestamps, responses, resolutions, and every lifecycle event are kept in a full audit trail, so when a payer or an auditor asks why the documentation says what it says, the answer is already on record. Access is secured per user session, data is isolated at the organisation level, and every action is attributed to its role, whether CDI specialist or physician.

For organisations that want the module inside their own systems, a REST API covers the complete workflow: review, query management, the inbox, and finalise.

Where it fits

The CDI Module is for teams whose product is the integrity of the record itself: hospital CDI programmes, provider groups building a documentation review function, and RCM companies offering CDI as a service. It runs alongside whatever coding process the organisation already has, and because it never touches the final codes, it slots in without disturbing that process.

The takeaway

Clinical documentation integrity is the discipline of making the record prove the care before anyone codes or bills it. The CDI Module gives that discipline a complete workflow of its own: a full-context review, compliant AHIMA-aligned queries, a tracked lifecycle from draft to closure, an inbox the team can run the day from, and an audit trail that stands behind every decision.

To see it on your own encounters, book a demo.