Hospital Readmission Coding: Impact on Reimbursement 2026
Two hospitals can deliver nearly identical clinical care for heart failure patients and still land on opposite sides of the Hospital Readmissions Reduction Program penalty line. The difference often has nothing to do with what happened at the bedside. It has everything to do with how accurately the coding and documentation team captured planned procedure status, comorbidity severity, and transfer relationships before the record was finalized.
Understanding the mechanics of HRRP, and where documentation gaps create penalty exposure, is now a core revenue cycle competency, not an optional compliance exercise.
How HRRP Works Mechanically
Under the Hospital Readmissions Reduction Program, CMS reduces the Medicare base operating DRG payment for every Medicare discharge at hospitals whose risk-adjusted readmission rates exceed expected rates for tracked conditions. The statutory cap on that payment reduction is 3% of base operating DRG payments. The penalty applies across all Medicare discharges at a penalized hospital, not just discharges related to the tracked conditions, which makes the financial reach of the program much broader than it first appears.
The six conditions CMS currently tracks are acute myocardial infarction, heart failure, pneumonia, chronic obstructive pulmonary disease, coronary artery bypass graft surgery, and elective total hip or total knee arthroplasty. Each has its own readmission measure, its own denominator definition, and its own risk-adjustment model.
Because the penalty methodology and exact penalty rates are updated through the annual IPPS rulemaking cycle, hospitals should review the current program details directly on the CMS HRRP program page rather than relying on prior-year figures. The core structure of payment reduction tied to excess readmission ratios has remained consistent, but the specifics shift year to year.
Planned vs. Unplanned: The Classification That Changes Everything
CMS's readmission measures count only unplanned readmissions. A return to an acute care hospital within 30 days of discharge for a scheduled or typically-scheduled procedure does not count against a hospital's readmission rate if it is correctly identified as planned.
Here is where the coding and documentation gap becomes consequential.
CMS uses an algorithm to classify readmissions as planned or unplanned. A readmission qualifies as planned when it involves a procedure that is either always considered planned (such as a kidney transplant or certain cancer therapies) or when the clinical record makes clear that the return was a scheduled continuation of a previously established care plan. Without documentation in the discharge summary or associated records that explicitly connects a return visit to a previously planned procedure, CMS's algorithm defaults the case to unplanned.
That default costs hospitals penalty points they may not deserve. A patient discharged after AMI who returns 18 days later for an elective cardiac catheterization that was scheduled at discharge should not count as a readmission, but it will if the original discharge summary does not clearly state that the follow-up procedure was scheduled before the patient left the hospital.
The Most Common Documentation Failures
Three failure patterns appear repeatedly in readmission miscoding situations.
- Discharge summaries that omit planned-procedure language. Physicians frequently arrange follow-up procedures before discharge without documenting the scheduled nature of that return in the summary itself. A generic "follow up with cardiology" note does not satisfy the specificity CMS's algorithm requires to classify a subsequent admission as planned.
- Incomplete comorbidity documentation that understates patient severity. When conditions like CKD stage, diabetes with complications, morbid obesity, or chronic respiratory failure are present but not explicitly documented and coded, the patient's record signals lower clinical complexity than actually existed. CMS uses that coded complexity to set expected readmission rates. An artificially healthy-looking patient population means the hospital's expected readmission rate is set lower than it should be, increasing the likelihood of a penalty even when readmissions were clinically appropriate and unavoidable.
- Transfer-coding errors that create phantom readmissions. When a patient is transferred from one acute care facility to another as part of a coordinated episode of care, coding that transfer as a new independent admission rather than a transfer inflates the readmission count. The two stays should link through accurate transfer codes, not stand as separate admissions.
Why Risk Adjustment Makes Coding Accuracy a Direct Financial Variable
CMS does not compare raw readmission rates between hospitals. It compares actual readmission rates to expected rates, where expected rates are calculated based on the clinical complexity of each hospital's patient population as reflected in diagnosis coding.
This means that accurate risk adjustment and HCC coding during the index admission is not just a billing function. It is a direct input into the denominator that determines whether a hospital receives a penalty. Undercoding a secondary diagnosis of CKD stage 3 or failing to document and capture diabetes with peripheral neuropathy as a distinct condition makes the patient look less sick than they are. Multiply that effect across hundreds of discharges in the three-year lookback period and a hospital's expected readmission rate can be materially understated, creating penalty exposure for clinical outcomes that were actually within the range of what should be expected for that patient population.
HCC capture during both the index admission and any readmission reinforces this effect. Both encounters require capturing the full clinical picture rather than just the presenting problem, because both contribute to the coded complexity profile that CMS uses to evaluate performance.
The Three-Year Lookback and Why Timing Matters
CMS calculates HRRP penalties using a three-year rolling lookback period. This means that documentation and coding improvements made today will not fully appear in penalty calculations for the next annual determination. The effect of better planned-procedure documentation, more accurate comorbidity coding, and corrected transfer classifications accumulates over time before it is fully reflected in the excess readmission ratio that determines penalty status.
That lag has a practical implication: hospitals that wait until they are already penalized to address documentation gaps are paying penalties on a lookback window that includes years of data they can no longer fix. Starting documentation improvement now reduces the penalty risk across the next several annual determinations, not just the current year.
Building a Readmission-Specific Coding Protocol
A structured protocol focused specifically on HRRP-tracked conditions can prevent the most common miscoding patterns before records are finalized. The elements of such a protocol include the following.
CDI Review Triggers for the Six HRRP Conditions
Identify every admission for AMI, heart failure, pneumonia, COPD, CABG, or elective hip and knee arthroplasty as a CDI priority at the time of admission, not at discharge. Early concurrent review creates the opportunity to query for comorbidity specificity and planned-procedure documentation while the physician is still actively involved in the case. Strong CDI program support ensures these triggers are applied consistently rather than relying on individual coder judgment.
Mandatory Discharge Summary Elements for Scheduled Follow-Up Procedures
Any patient being discharged with a follow-up procedure already scheduled should have that fact stated explicitly in the discharge summary. The summary should name the procedure, confirm it was arranged prior to or at the time of discharge, and note the anticipated timeframe. This is the documentation CMS's algorithm requires to classify a subsequent admission as planned.
Secondary Coding Review When a Patient Returns Within 30 Days
A 30-day return trigger should automatically initiate a secondary review of both the original index stay and the readmission record. The review should assess whether the return qualifies as planned, whether transfer coding is accurate, and whether any comorbidities present at the index admission were inadequately captured in the original coding.
Pre-Discharge Query Prompts
Structured pre-discharge queries for HRRP-tracked conditions should cover three specific areas: confirmation of planned-procedure status for any scheduled return, specificity of comorbidity documentation (including chronic conditions, stages, and complications), and transfer documentation when the patient is moving to another facility. These queries are most effective when they are part of a systematic physician query management program rather than ad hoc requests.
Holding High-Risk Cases for Final Coding
Some hospitals build a brief hold into their workflow for high-risk HRRP cases, allowing coders to finalize the index stay record with knowledge of whether a 30-day return occurred and what that return involved. The tradeoff is slower billing against more accurate planned-status classification. That tradeoff is a real one and each facility must weigh it based on its own cash flow priorities and coding capacity, but the approach reflects a recognition that finalizing coding in isolation from return-visit context can produce preventable miscoding.
Frequently Asked Questions
What is the difference between a planned and unplanned readmission for CMS purposes?
CMS classifies a readmission as planned when the return involves a procedure that is always considered planned under the measure's algorithm, or when the clinical record clearly establishes that the return was a scheduled continuation of a previously arranged care plan. Any return that does not meet those criteria is classified as unplanned by default and counts against the hospital's readmission rate. The key word is "default." Absent specific documentation, CMS counts it as unplanned.
How does diagnosis coding accuracy affect HRRP penalty risk?
CMS risk-adjusts expected readmission rates using the diagnosis codes submitted on claims. When comorbidities are undercoded, the patient population appears clinically less complex than it actually is, which lowers the expected readmission rate CMS assigns to the hospital. A lower expected rate makes it easier for actual readmissions to exceed expectations, increasing the chance of a penalty even when the clinical outcomes were appropriate for the true patient population.
Can improving coding reduce HRRP penalties without changing clinical care?
Yes. Because the penalty calculation depends on the accuracy of coded data, hospitals with genuine documentation and coding gaps may be penalized for readmissions that should have been classified as planned, or may be compared against an expected rate that understates their patient complexity. Correcting those gaps can reduce penalty exposure without any change in clinical practice, because the clinical quality was never the underlying problem.
Where can hospitals find the current HRRP penalty methodology and rates?
The authoritative source is the CMS Hospital Readmissions Reduction Program page on CMS.gov. CMS updates the methodology and applicable payment adjustment factors through the annual IPPS final rule, and the program page links to the current technical specifications, measure information, and hospital-specific data files used in each payment year determination.
The Bottom Line
The HRRP penalty is a coding and documentation problem as much as it is a clinical quality problem, and hospitals that treat it only as the latter will keep paying penalties the former could prevent.
To identify where your current coding is creating readmission penalty exposure, schedule a coding quality audit with the team at MedCodex Health.