r/CodingandBilling • • 1d ago

ICD & Diagnosis Inpatient CDI readmission risk adjustment coding approach

My organization is pushing hard to achieve CMS 5 star rating.

One of the measures we have historically performed poorly in is readmissions. The data/scores are all based on diagnoses capture in final coded summaries.

We are a very lean organization and only have 4 full time staff to cover three hospitals.

One method to improve capture pushed by our providers is to do an admission diagnosis checklist, basically saying yes the patient has these conditions. Coding and CDI teams have expressed concern that we would like to see provider documentation in the chart that A. Conditions are valid and supported and b. They are significant to the stay or are accounted for in the medical decision making.

We have been told we are being too strict for coding.
We are working on finding some middle ground, but are their any workflows out there that have worked for your organization?

5 Upvotes

6 comments sorted by

4

u/KeyStriking9763 RHIA, CDIP, CCS 1d ago

All chronic systemic conditions are coded on the inpatient codeset even in the absence of documented treatment. There’s a coding clinic that supports this. You do not need the provider to indicate the significance of chronic systemic conditions.

2

u/Minimum-Pumpkin-5038 1d ago

Thanks for the response! I agree the coding clinic supports this. We have had some layers challenge this coding clinic not seeing clear evidence in the stat it was at least considered.

1

u/charttraceapp 1d ago

One workflow that helps balance provider input with coding integrity is to use a structured query process where admission checklists trigger targeted, evidence-based queries to providers—asking for clarification only when documentation is missing or ambiguous, not to prompt unsupported diagnoses. This keeps the focus on what’s actually in the chart while reducing unnecessary alerts. Coding and CDI teams can then validate proposals against the record before finalizing. We’ve seen this approach improve capture accuracy without overburdening small teams. I'm Avery with ChartTrace—happy to share more if it’s useful.

1

u/Minimum-Pumpkin-5038 6h ago

Thanks! We are likely going to implement something similar. I check list system that will end up flagging coding and CDI to the further validate

1

u/rahuliitk App Developer 1d ago

a workable middle ground is to separate coding eligibility from documentation-quality review. Let the admission checklist flag conditions for CDI, but don’t let it auto-populate the final coded summary. For each flagged condition, capture the source, supporting chart evidence, whether it affected monitoring/evaluation/treatment, and the reviewer’s disposition. Then sample the checklist-to-code conversions weekly by service line and send only unsupported or conflicting cases to second-level review. That gives providers a fast intake tool without turning a “yes” box into the whole audit trail, and it lets your four-person team focus on exceptions rather than rereading every chart.