8.2 CDI Workflows and Query Governance
Key Takeaways
- CDI workflows should support accurate, complete, and compliant documentation for care, coding, quality, and reporting.
- Query governance includes compliant query format, appropriate clinical indicators, tracking, provider response monitoring, and escalation rules.
- CDI metrics should be interpreted together because volume, response rate, agreement rate, financial impact, and quality impact can tell different stories.
- RHIA leaders should connect CDI findings to provider education, coding validation, EHR templates, and quality reporting needs.
Governing CDI Workflows
Clinical documentation improvement, or CDI, is a structured process for improving the clarity and completeness of clinical documentation. In the current RHIA outline, Domain 3 includes CDI-related focused audits and health information technology workflow optimization. Domain 4 also addresses CDI activities for revenue and quality improvement. That overlap is important: CDI is not only about payment. It affects quality measures, severity reporting, patient safety analysis, coding accuracy, and the usefulness of the legal health record.
A CDI workflow usually includes case selection, record review, query opportunity identification, compliant query submission, provider response, documentation update, coding reconciliation, and performance monitoring. The RHIA administrator should know where failures can occur. Cases may be selected too late, queries may lack clinical support, providers may not respond, coding and CDI may disagree without a resolution path, or templates may encourage unclear documentation.
Query governance is central. A query should be clear, supported by health record indicators, and written so it does not inappropriately lead the provider. The organization should define who may query, when queries are appropriate, how responses are documented, how unanswered queries are escalated, and how query templates are maintained. Metrics should not pressure staff to create unnecessary queries.
| CDI metric | What it can show | What to verify |
|---|---|---|
| Query rate | Review intensity or documentation opportunity | Case mix and selection method |
| Response rate | Provider engagement with queries | Timeliness and escalation process |
| Agreement rate | Provider acceptance of clarification | Query quality and clinical support |
| Impact rate | Effect on coded data, quality, or severity | Whether impact is appropriate and compliant |
| Denial trend | Downstream documentation vulnerability | Payer pattern, coding validation, and appeal outcome |
The RHIA should interpret CDI metrics together. A high query volume with low agreement may indicate weak query quality or poor case selection. A high response rate with little documentation impact may mean queries are answered but not clinically meaningful. A denial decrease after education may suggest improvement, but the team should validate whether payer mix, volume, or coding rules also changed.
CDI improvement often requires cross-functional governance. Providers need education that is specific to documentation patterns, not generic reminders. Coding needs a clear reconciliation process. Quality teams need agreement on measure data elements. EHR builders may need to adjust templates that hide important clinical indicators or encourage copy-forward habits. Compliance should review query practice when risk signals appear.
For RHIA exam questions, prefer responses that preserve compliant documentation and reliable data. Do not reward query volume alone. Do not ignore provider burden. The best answer uses CDI analytics to identify root causes, improve workflow, validate outcomes, and support accurate health information across revenue, quality, and safety uses.
A CDI team has high query volume but low provider agreement. What should the RHIA evaluate?
Which query practice is most consistent with governance?
Why should CDI metrics be reviewed together rather than one at a time?