Does Use of a Hospital-wide Readmission Measure Versus Condition-specific Readmission Measures Make a Difference for Hospital Profiling and Payment Penalties?
Bibliographic record
Abstract
BACKGROUND: The Centers for Medicare and Medicaid Services (CMS) use public reporting and payment penalties as incentives for hospitals to reduce readmission rates. In contrast to the current condition-specific readmission measures, CMS recently developed an all-condition, 30-day all-cause hospital-wide readmission measure (HWR) to provide a more comprehensive view of hospital performance. OBJECTIVES: We examined whether assessment of hospital performance and payment penalties depends on the readmission measure used. RESEARCH DESIGN: We used inpatient data to examine readmissions for patients discharged from VA acute-care hospitals from Fiscal Years 2007-2010. We calculated risk-standardized 30-day readmission rates for 3 condition-specific measures (heart failure, acute myocardial infarction, and pneumonia) and the HWR measure, and examined agreement between the HWR measure and each of the condition-specific measures on hospital performance. We also assessed the effect of using different readmission measures on hospitals' payment penalties. RESULTS: We found poor agreement between the condition-specific measures and the HWR measure on those hospitals identified as low or high performers (eg, among those hospitals classified as poor performers by the heart failure readmission measure, only 28.6% were similarly classified by the HWR measure). We also found differences in whether a hospital would experience payment penalties. The HWR measure penalized only 60% of those hospitals that would have received penalties based on at least 1 of the condition-specific measures. CONCLUSIONS: The condition-specific measures and the HWR measure provide a different picture of hospital performance. Future research is needed to determine which measure aligns best with CMS's overall goals to reduce hospital readmissions and improve quality.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.113 | 0.338 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.004 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".