13.1 Roles and Responsibilities of the CDI Specialist

13.1 Roles and Responsibilities of the CDI Specialist

Quick Answer: An inpatient CDI specialist reviews records concurrently while the patient is still hospitalized or retrospectively after discharge (typically before the bill), uses clinical knowledge to judge how the record will translate into coded data, queries for missing or conflicting documentation, maintains a working DRG, and educates providers. The specialist never independently adds a diagnosis to the health record or edits another clinician’s note.

The clinical documentation integrity (CDI) specialist sits between the bedside story and the coded claim. On an inpatient stay paid under the Inpatient Prospective Payment System (IPPS), that position is a defined communication role: review the record, recognize what the documentation can and cannot support, close gaps through conversation or query, and teach so the next record is clearer. It is not a license to rewrite the chart, and it is not a silent second coding shift during the stay.

This independent OpenExamPrep chapter teaches the job description Domain V tests: what the specialist does every day, what a working diagnosis-related group (working DRG) is for, and which actions are out of bounds. Later Domain V sections cover non-confrontational style and working-versus-final DRG reconciliation. Domain III covers query formats. Keep those lanes separate while you study the role itself.

Concurrent Review and Retrospective Review

Concurrent review happens while the patient is still an inpatient. ACDIS describes the concurrent specialist as performing daily reviews of records for patients who are currently hospitalized. In a working program that usually means a first review shortly after admission—or after a case-selection screen flags the account—and follow-up reviews as new notes, results, and treatments appear. Concurrent work is the setting where a working DRG is most useful: the specialist estimates the Medicare Severity Diagnosis-Related Group (MS-DRG) that today’s documentation would support and updates that estimate when a query is answered or a new condition is documented.

Retrospective review happens after discharge, typically in the pre-bill window—after the stay ends and before the claim is released. The retrospective specialist still uses clinical knowledge, still queries, and still educates. Timing and leverage change. The care team is no longer rounding on that patient; memory fades; some results (pathology, send-out cultures, finalized operative reports) may only now be complete. The advantage is a fuller record. The risk is a late query that delays billing or a missed conversation that would have been easier at the bedside.

Many hospitals run a hybrid model: concurrent coverage on high-priority units or payers, with a retrospective sweep of accounts concurrent staff never reached. The role does not change with the calendar. Both concurrent and retrospective specialists collaborate with physicians and the rest of the care team; evaluate how provider notes, nursing and allied documentation, laboratory results, imaging, and treatment plans will translate into coded data; communicate—verbally or by query—when documentation is missing, unclear, or conflicting; and educate providers so severity of illness, complexity, and acuity are described in language coding can report.

What does change is the usual channel. Concurrent work favors a short unit conversation plus a documented query when the issue must live in the permanent record. Retrospective work is more often a written query in the electronic health record or query software, with physician-advisor escalation if the case is clinically contested. Choosing verbal versus written communication is its own Domain V skill; here the point is that both timings are legitimate inpatient CDI practice, and ACDIS eligibility counts concurrent or retrospective inpatient work.

From Clinical Knowledge to Coded Data

The specialist is not assigning the official codes that will appear on the institutional claim. That is the coder’s post-discharge job. The CDI task is a clinical-to-coded question: if a coder applied the Official Guidelines for Coding and Reporting and Uniform Hospital Discharge Data Set (UHDDS) definitions to this record tomorrow, what would be reportable—and what is only implied?

That question requires bedside literacy. A rising creatinine and a fluid bolus are not a diagnosis of acute kidney injury (AKI). Crackles, an elevated B-type natriuretic peptide (BNP), and intravenous diuretics are not a coded type of heart failure until a provider states the type and acuity. A positive blood culture is not sepsis, severe sepsis, or bacteremia until the provider links infection and organ dysfunction or states an alternative. The specialist reads the treatment and the indicators to see whether the words match.

The same skill supports clinical validation. If the record says severe malnutrition but there is no recognized nutritional assessment, no supporting intake or anthropometric story, and no treatment beyond a standard diet, the issue is not add the major complication or comorbidity (MCC). The issue is whether the documented diagnosis is clinically supported. A compliant query can ask the provider to confirm, revise, or offer an alternative. Silently leaving an unsupported MCC in the working DRG trains the program to fail an auditor and teaches physicians that CDI is a payment shop.

CDI specialists are not members of the treatment team. They do not render a bedside diagnosis. They collect indicators from the record and ask the people who are accountable for the diagnosis to make the clinical statement complete and consistent.

Queries, Education, and the Working DRG

A query is the formal tool when the record is incomplete, conflicting, or clinically inconsistent. The 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice require a nonleading question, sourced clinical indicators, and no reimbursement or quality-outcome language. Multiple-choice queries need clinically relevant options plus an open-ended path such as Other, please specify. Yes/no queries may not introduce a new diagnosis. Those format rules belong to Domain III. The role rule is simpler: the CDI specialist requests clarification. The provider decides what is true for the patient and documents it in the permanent record before coding relies on it.

Provider education is the other half of the same job. A query fixes one encounter. A five-minute service huddle on acute-on-chronic systolic heart failure versus unspecified heart failure can prevent the next month of repeat queries on that service. ACDIS lists education among the daily functions of both concurrent and retrospective specialists. If your only output is a query rate, you are doing half the role Domain V tests.

The working DRG is the specialist’s running estimate of the MS-DRG the current documentation would group to. It is a communication and analysis tool—used for case-mix conversations, expected-length-of-stay context, and later comparison with the final DRG coding assigns after discharge. It is not a second official grouper result, and it does not authorize the specialist to drop a diagnosis into the coder’s queue that no provider wrote. A working DRG that assumes an undocumented MCC is a planning fiction, not CDI.

Hard Boundaries: What the Specialist Must Never Do

Three prohibitions show up on exams and in compliance reviews.

1. Do not independently add a diagnosis to the health record. The specialist may not enter acute respiratory failure as if it were a provider diagnosis, even when the arterial blood gas is classic and the patient is on a high-flow device.
2. Do not edit another clinician’s note. Fixing a typo in an attending progress note, inserting a missing MCC, or cleaning up a copy-forwarded problem list is record alteration, not CDI.
3. Do not lead. Suggesting the one diagnosis that raises reimbursement, offering only the MCC option, or putting quality-score language in the query violates compliant query practice.

The specialist may collect indicators from any part of the record, talk with the team, issue a compliant query, update the working DRG, and teach. Those actions leave the diagnostic decision with the provider and the final code assignment with coding.

Worked Encounter: Implied Heart Failure

A 78-year-old is admitted from the emergency department with dyspnea. The history and physical says CHF. The echocardiogram shows a left-ventricular ejection fraction of 30 percent. Intravenous furosemide is infusing. BNP is 1,400 pg/mL. The concurrent specialist’s job is not to type acute-on-chronic systolic heart failure into the history and physical. The job is to recognize that coded data cannot report a specific heart-failure type from CHF plus an echo, to place a nonleading query that cites those indicators, to update the working DRG only after the provider documents the type and acuity, and to note if this service repeats unspecified heart failure—because that pattern is an education topic, not a reason to start editing notes.

A Day-in-Role Picture

A typical concurrent specialist opens a worklist (all Medicare inpatients, a high-risk service, or a software-priority score), reads the history and physical, the latest progress notes, relevant results, and the medication administration record, then asks whether the principal diagnosis—the condition, after study, that occasioned the admission—is stated specifically enough and whether secondary diagnoses that meet UHDDS reporting criteria (clinical evaluation, therapeutic treatment, diagnostic procedures, extended length of stay, or increased nursing care or monitoring) are actually named. If the gap is real, the specialist queries. If the gap is a pattern on that service, the specialist plans education. If the clinical story is disputed, the specialist may involve a physician advisor. If the stay has ended, a retrospective colleague does the same work against a closed record and a ticking bill-hold clock.

None of those steps includes writing a diagnosis the provider did not document or changing a note the provider already signed.