4.3 CDI-Coding Reconciliation & Annual Regulatory Updates
Key Takeaways
Define reconciliation selection, holds, escalation, and release authority in local policy; a matching DRG does not prove that all inputs are correct.
Route coding and clinical-documentation questions to appropriate expertise while preserving provider responsibility and current query standards.
Distinguish proposals, rule display/publication, corrections, and actual effective periods; April 1 code implementation is not limited to emergencies.
Coordinate code, grouper, weight, benchmark, and payment updates using versioned sources and focused education.
Transfer payment uses qualifying circumstances, the applicable graduated calculation, caps, and special rules; a new PCS code alone does not establish NTAP payment.
4.3 CDI-Coding Reconciliation & Annual Regulatory Updates
Reconciliation makes coding decisions explainable. It connects the record, the applicable rules, the grouping inputs, and the people responsible for resolving an issue. Update management keeps those same decisions consistent when codes, grouping definitions, or payment policies change. Both activities require a defined local process; neither is accomplished by always selecting the higher-weighted result.
Build a reconciliation process with clear ownership
An organization can compare concurrent and coding results before billing and select cases for additional review. The ACDIS reconciliation practice example describes variation in program design, including mismatch review and broader review approaches. It supports collaboration, not a universal requirement to hold every mismatch or to release every matching case.
A local policy should define the cases selected, the reason for any hold, the responsible reviewer, response windows, escalation, release authority, and the disposition of unresolved questions. Its review queue can include:
- Different principal diagnoses, even when both inputs happen to produce the same DRG.
- Differences in secondary reportability, code specificity, POA, or procedure representation.
- Open queries, contradictory responses, or newly available documentation.
- An unexpected grouping route or mismatch between the release used and the discharge date.
- Selected quality-related cases requiring verification under the particular measure or payment rule.
These are useful selection criteria. The organization must identify which are mandatory under its policy and which are subject to risk-based review. A DRG match alone does not prove that every code is correct. Conversely, a mismatch caused by a properly documented change after the concurrent review is not automatically a defect.
Route the question to the expertise it needs
Begin with a shared problem statement: identify the exact disputed input, the documentation, the source, and the practical consequence being evaluated. A source-based discussion is more useful than competing assertions that CDI or coding always has the final word.
The following is an illustrative local escalation design, not a nationally prescribed four-tier hierarchy:
| Question or stage | Possible responsible participants | Required product |
|---|---|---|
| Initial discrepancy | Reviewing CDI practitioner and coding professional | A comparison of the record, inputs, and cited provision |
| Unresolved coding interpretation | Coding lead, CDI lead, or designated subject-matter expert | A documented interpretation consistent with applicable rules |
| Conflicting diagnoses or clinical-validation concern | Responsible provider, with physician-advisor assistance when appropriate | Necessary provider clarification through a compliant process |
| Repeated, systemic, or compliance concern | Designated CDI, HIM, clinical, and compliance leadership | A corrective policy, education, or further investigation with assigned ownership |
A physician advisor can help discuss clinical evidence and communicate with a treating provider. That role does not authorize inventing a diagnosis in the record or overruling a classification instruction. Likewise, CDI and coding reviewers can identify clinical-validation concerns and seek clarification; they should not simply replace a documented diagnosis with their own interpretation of test results.
The 2026 query practice brief supplies the standards for the clarification itself, including neutrality, relevant clinical information, response incorporation, and management of unanswered queries. A committee's preference for a financial result does not replace those standards.
Record the resolution as a reasoned decision: for example, a corrected procedure input, a clarified diagnosis, a specific guideline application, or an unresolved query closed under policy using the existing documentation. Do not promise that a fixed percentage of disagreements will resolve at the peer stage. Measure the local process before using such a statistic.
Distinguish proposal, publication, and effective date
The federal fiscal year runs October 1 through September 30. October 1 is the central annual implementation date for the relevant inpatient code and payment releases, but a rule's display date, Federal Register publication date, and effective provisions are separate facts.
Use the FY2027 IPPS final-rule page as a concrete example: it lists July 31, 2026 display, August 4 publication, and a September correction notice. Thus, August 1 is not an invariant publication date. Read the final rule, applicable corrections, tables, and implementation files rather than treating a proposed change as operative or assuming every provision shares one date.
The CMS ICD-10 release page identifies the applicable code files and periods. On this guide's October 2026 review date, the posted FY2027 CM files cover October 2026–September 2027, while the posted October 2026 PCS files cover October 2026–March 2027. The page also provides prior April 1 releases. Follow each file's stated applicability and any subsequent update; do not extend one release beyond its period because the fiscal-year number matches.
April 1 code implementation is not simply synonymous with an emergency release. CMS's PCS request process allows requests for April 1 or October 1 consideration, with the committee determining which requests to consider for each date. The release actually approved and published controls code use.
Translate an update into operational changes
Assign an owner and evidence of completion for each affected area:
| Area | What to compare | Operational follow-through |
|---|---|---|
| CM/PCS classification | Addenda, tables, index, guidelines, errata, and effective periods | Update reference access, coding tools, and affected teaching cases |
| Grouping | Current definitions, OR attributes, hierarchy, CC/MCC classifications and exclusions | Validate representative cases against the correct grouper version |
| Weights and benchmarks | Applicable final weights and LOS data | Separate classification changes from weight changes in reports and forecasts |
| Payment rules | Applicable transfer, technology, and other payment policies | Coordinate with billing, finance, and case management on claim-specific requirements |
| Queries and education | Documentation needs and current query standards | Remove obsolete or directional prompts; teach accurate clinical documentation rather than desired reimbursement answers |
For severity changes, distinguish the final-rule tables from the Definitions Manual's Appendix C and its linked exclusions. A baseline label alone does not establish a code's impact on a particular claim. For trend reports, record whether a comparison uses each year's native grouping or holds a release constant; otherwise a release change can be mistaken for a change in patient mix or CDI performance.
Apply transfer rules without a GMLOS shortcut
42 CFR 412.4 addresses both qualifying transfer circumstances and payment. Postacute transfer circumstances include qualifying DRGs with discharge to the specified excluded hospital/unit settings, SNFs, home with a written HHA plan and services beginning within three days, or hospice under the applicable provision. The destination and actual service circumstances must be verified; home discharge alone is not enough.
The general graduated-per-diem calculation divides the appropriate prospective payment by the group's GMLOS, pays twice that daily amount for the first day and once for each subsequent day, and caps payment at the applicable full amount. Special rules must be checked. Therefore, a stay shorter than GMLOS does not universally guarantee a reduction.
Illustrative arithmetic: Assume a verified qualifying transfer uses the general rule, the appropriate payment is $12,000, GMLOS is five days, the stay has two payable days, and no special rule or other adjustment affects this illustration. The daily amount is $12,000 / 5 = $2,400. The first day contributes $4,800 and the second $2,400, totaling $7,200, below the $12,000 cap. Under those same assumptions, four days yield five daily amounts, reaching the $12,000 cap even though four is below GMLOS five. These are hypothetical inputs, not a prediction for an unspecified real discharge.
Verify technology payment separately from code creation
CMS's NTAP page directs users to the fiscal-year implementation file for newly approved, continued, and discontinued technologies. Its code-request process is separate from NTAP approval. A new PCS code does not by itself establish an approved add-on payment.
For an actual case, verify the technology, approval period, required identification and documentation, and the applicable payment conditions. 42 CFR 412.88 includes cost comparisons and limits; capturing a detailed code alone does not guarantee an add-on amount. CDI supports an accurate account of what was performed, while the billing and payment review applies the eligibility and calculation rules.
Close the update cycle with focused joint education and review of selected cases. Keep the source version and resolved interpretation available so that a later disagreement can be traced to the same facts and rules, rather than to an obsolete worksheet or an unsupported local custom.
CDI and coding reviewers have compared the same record and applicable coding rules. A remaining disagreement concerns conflicting provider descriptions of the patient’s condition. Under a local policy that provides physician-advisor support, which next step best addresses the unresolved issue?
Ask the coding supervisor to select between the conflicting diagnoses solely from test results, without further provider clarification.
Seek appropriate provider clarification, using physician-advisor assistance for the clinical discussion and a compliant documentation process.
Ask the physician advisor to choose a diagnosis for the coding worksheet without obtaining appropriate documentation from a responsible provider.
Accept the last chronological diagnostic statement without evaluating the unresolved provider conflict or following the local clarification policy.
An update team reviews the current CMS release notices. They show one applicability period for CM files, another for PCS files, and a correction notice to the annual final rule. Which implementation approach is sound?
Apply the proposed rule as final because its publication occurs before operational planning begins.
Assume every file with the same fiscal-year number applies unchanged through the entire fiscal year.
Use each final file’s stated effective period and applicable corrections, and check later releases before extending code use beyond that period.
Ignore any April 1 release unless the hospital has separately declared a public-health emergency.
A hypothetical verified transfer is subject to the general graduated-per-diem rule, with no special rule or other adjustment affecting this calculation. The appropriate full payment is $12,000, GMLOS is 5 days, and the stay has 2 payable days. What is the illustrated transfer payment?
$4,800, applying one $2,400 daily amount to each of the two days.
$12,000, because the full amount is paid for every qualifying transfer regardless of the stay.
$9,600, applying twice the $2,400 daily amount to both days.
$7,200, applying $4,800 for the first day plus $2,400 for the second, below the full-payment cap.
Sections you finish are checked off in the contents.