13.2 Coder Roles Working with a CDI Department
Key Takeaways
- After discharge, the inpatient coder assigns official ICD-10-CM/PCS codes, present-on-admission indicators, discharge disposition, and the final MS-DRG from the complete record plus Official Guidelines and AHA Coding Clinic.
- CDI owns concurrent and retrospective clinical review, compliant queries, education, and the working DRG; a working DRG does not override a guideline-supported coding decision.
- A physician advisor is a clinical peer bridge for contested cases, education credibility, and escalation—not a substitute coder and not a person who silently enters billed codes.
- An advisor who did not treat the patient should not answer a query or add a diagnosis in place of the treating provider; the treating provider documents, then coding codes.
- When a query is still open at coding time, coordinate so the response reaches the permanent record before final code assignment; do not code from query wording alone or add an undocumented MCC to force a match.
13.2 Coder Roles Working with a CDI Department
Quick Answer: After discharge, the inpatient coder assigns the official ICD-10-CM/PCS codes, present-on-admission indicators, and the final MS-DRG from the completed record and coding authorities. CDI owns concurrent and retrospective clinical review, queries, and the working DRG. A physician advisor is a clinical peer bridge, not a substitute coder.
Domain V asks you to describe the coder’s job in a hospital that already has CDI. The trap is treating the two roles as duplicates or as a hierarchy in which whoever spoke last wins. They are parallel crafts that share one record and one claim.
Final Code Assignment After Discharge
The inpatient coder (often a Registered Health Information Technician (RHIT), Registered Health Information Administrator (RHIA), or Certified Coding Specialist (CCS) working in HIM) assigns the codes that will be billed. That assignment happens against the complete discharge record: history and physical, progress notes, consults, operative notes, diagnostic reports the provider has addressed, the discharge summary, and any query responses that made it into the permanent record.
The coder applies the ICD-10-CM Official Guidelines for Coding and Reporting, ICD-10-PCS guidelines for procedures, UHDDS definitions of principal and secondary diagnoses, and AHA Coding Clinic advice. From that work come the principal diagnosis, reportable secondaries, procedure codes, present-on-admission (POA) indicators, discharge disposition, and the final MS-DRG. Some hospitals also run All Patient Refined DRG (APR-DRG) grouping for severity and mortality analysis; that too is a coding product from the coded record, not a CDI override.
A few programs practice concurrent coding—a coder abstracts while the patient is still in house. Even then, official finalization waits until the record is complete after discharge. Concurrent coding does not move final code ownership to CDI, and it does not let anyone code a diagnosis that exists only as a hint in a nursing row.
Coding does not allow assumption. A nurse’s up-arrow next to sodium is not hypernatremia. A dietitian’s impression is not a provider diagnosis. An echo report sitting unacknowledged is not attending confirmation. The coder’s lane is: report what the record states under the rules, and query when the record is incomplete for code assignment.
Two Lanes, One Record
CDI reviews for integrity: missing specificity, conflict, clinical validation concerns, and the educational pattern behind repeat gaps. CDI’s grouping output is a working DRG—an estimate from documentation on hand, often updated several times during the stay.
Coding reviews for reportability and official assignment. Coding’s grouping output is the final DRG on the claim.
Those outputs will not always match, and a mismatch is not automatically a CDI failure. The working DRG may have been built mid-stay before pathology resulted, before a query was answered, or before a guideline or CC exclusion (IPPS Table 6K) neutralized a secondary diagnosis. Reconciliation—comparing working versus final and classifying why—is the next Domain V chapter. Collaboration in this chapter is the everyday handoff that makes that reconciliation possible.
| Task | CDI lane | Coding lane | Physician advisor |
|---|---|---|---|
| When the work happens | Concurrent daily and/or retrospective pre-bill | After discharge from the complete record (some concurrent abstracting, then finalization) | On escalated clinical or validation questions |
| Primary output | Queries, education, working DRG | Official codes, POA, disposition, final MS-DRG | Peer conversation and clinical second look |
| Governing references | Clinical indicators plus compliant query practice | Official Guidelines, Coding Clinic, UHDDS | Clinical judgment in discussion with the treating provider |
| May add a diagnosis to the note? | No | No | Not as a substitute for the treating provider |
| May assign the billed codes? | No (working DRG is an estimate) | Yes | No |
Coders in a CDI shop should see the CDI work before they release a bill: open queries, query responses, working-DRG rationale, and any clinical-validation flag. Ignoring CDI and coding in a silo wastes the review. The opposite error is equally expensive: a coder who copies the working DRG without applying guidelines, or a CDI specialist who tells the coder to just add the MCC.
Both roles may query. Concurrent programs often have CDI carrying the in-house query load; coding carries many retrospective or post-discharge queries (procedure specificity, pathology confirmation, conflicting discharge diagnoses). Facility policy should say who queries for what so the provider is not hit twice for the same gap. Policy does not erase the coder’s duty to query when the record cannot support a code the claim needs.
Dual-Skilled People, One Hat at a Time
Some staff hold both a CDI credential and a coding credential. That is useful. It is also a role-blur risk. When the person is doing a CDI review, they query and estimate; they do not silently recode the account as if the review were final coding. When the same person is assigned as the discharge coder, they apply guidelines to the complete record, including any CDI queries, and they own the final codes. The hat in use—not the résumé—determines the action.
Organizational design matters. Programs that treat CDI and coding as independent, equally voiced departments (each with its own lead) tend to collaborate better than programs that use CDI as a pre-coder whose worth is a 100 percent working-to-final match rate. ACDIS commentary on DRG match metrics has long warned that scoring specialists on whether they predicted the coder’s final DRG pushes them to act like junior coders and to take guideline decisions personally. Domain V is testing whether you can describe a coder who works with CDI, not a coder who is replaced by CDI.
The Physician Advisor Is a Clinical Bridge, Not a Coder
A physician advisor (sometimes called a physician champion) is a clinician with credibility among the medical staff. Typical uses: peer-to-peer discussion when a treating provider disagrees with a query; second-level clinical validation when a documented diagnosis lacks indicators; help designing service education; and, in some programs, denials or utilization review conversations that touch the same record.
The advisor is not:
- The person who assigns ICD-10-CM/PCS codes or the final MS-DRG
- A substitute attending who may enter diagnoses on patients they did not treat just to close a query
- An override button when coding cites a guideline the advisor finds inconvenient
- Someone who edits the treating provider’s note
If a query needs a clinical answer, the treating provider answers it in the permanent record. An advisor who was not involved in the care can talk with that provider; the advisor generally should not be the query respondent. Coding Clinic’s description of clinical validation is a clinical review of whether the patient possesses the documented condition—not a license for a non-treating advisor to rewrite the coded claim.
Escalation that stays in lane looks like this: CDI and coding talk, each citing record facts and, on the coding side, a guideline or Coding Clinic reference; if the dispute is clinical truth (does this picture support acute respiratory failure?), a physician advisor joins the treating provider; if the dispute is code selection or sequencing, coding leadership and the Official Guidelines decide. Nobody “wins” by seniority.
Worked Handoff: Malnutrition MCC That Coding Cannot See
CDI’s working DRG includes severe protein-calorie malnutrition as an MCC after a dietitian note describes poor intake and weight loss. No treating provider has documented the diagnosis or linked it to the stay. At discharge the coder correctly refuses to assign the MCC from the dietitian note alone. Collaboration is not an argument about who is right about nutrition. It is a retrospective query to the treating provider (or a held claim while that query is answered), a physician-advisor peer call if the provider wants a clinical second look, and a final code set that follows whatever the provider then documents—or does not document. Forcing the MCC into the claim to match the working DRG is not teamwork. It is an integrity failure.
A second common handoff: CDI sequenced community-acquired pneumonia as the working principal diagnosis; the coder, after study of the complete record, applies guideline-driven sequencing and selects sepsis as principal because that condition occasioned the admission. The working DRG and final DRG will differ. The coder still owns the official assignment. The useful conversation is whether documentation of the linkage is clear—not whether CDI can instruct the coder to keep pneumonia first so the match rate looks better.
What Each Role Must Refuse
- CDI must not instruct a coder to assign a code that is not in the record.
- A coder must not add an undocumented complication or comorbidity (CC) or MCC to agree with a working DRG.
- A coder must not treat a query’s suggested options as a diagnosis if the provider never responded in the record.
- A physician advisor must not replace guideline application with a hallway opinion that never enters the record.
- Nobody should release a bill while a material query is still unanswered if the unanswered issue would change reportable codes; coordinate, hold, or escalate.
Healthy collaboration is visible: shared query software, a comment that the working DRG assumed a pending culture, and mutual respect that coding’s final pass is a professional act, not a rebuke of CDI.
On an IPPS inpatient account, who assigns the official ICD-10-CM/PCS codes and the final MS-DRG that will be billed?
A treating hospitalist disputes a clinical-validation query on documented severe malnutrition. What is the physician advisor’s correct role?
CDI’s working DRG includes an MCC. The coder cites an Official Guideline and a Coding Clinic note that keep that condition from being reported as the CDI specialist expected. What is the correct collaboration rule?
Coding opens a discharged account and finds a CDI query still unanswered. The queried condition would change the MS-DRG if confirmed. What should happen next?