12.3 Payer Prioritization, Length of Stay & Re-Review Cadence
Key Takeaways
Set review intervals and milestones from local needs, coverage, and information rather than treating 24–48/48–72 hours as national requirements.
Distinguish clinical urgency, legal record-completion requirements, query-response windows, and chart-review scheduling.
Verify actual payer arrangements and model versions; hospital reimbursement, CMS-HCC plan risk adjustment, APR SOI, and APR ROM are different concepts.
GMLOS is a benchmark with specified payment uses, not proof of an undocumented complication or an automatic outlier threshold.
Plan all assigned work, count activities and encounters accurately, and reconcile the supported final record without forcing an earlier working DRG.
Planning Review Timing, Follow-Up, and Reconciliation
Review timing should fit the program’s scope, available information, patient flow, coverage, and the significance of unresolved issues. A local policy may set initial and follow-up expectations, but the often-quoted 24–48-hour initial and 48–72-hour follow-up intervals are not universal national CDI requirements. A short-stay record may need earlier attention; another review may reasonably await a relevant report.
ACDIS’s published practitioner examples illustrate substantial differences in how organizations count work, staff services, and schedule reviews. Those examples are not a national productivity study or a mandatory target. Use local evidence to choose a workable process and measure whether it produces accurate, timely results.
Establish a Review State and a Next Action
For each reviewed encounter, distinguish the initial review, a subsequent review of new information, query work, reconciliation, and final handoff. These activities can involve the same patient more than once. Counting each work item as another unique encounter misrepresents coverage and productivity.
| Review state | Useful next action | Example reason to return |
|---|---|---|
| Initial information reviewed | Record established facts and unresolved needs | A relevant report or assessment is pending |
| Clarification sent | Track actual delivery and the local response window | Response received, approaching deadline, or escalation needed |
| New clinical or procedural information | Assess whether it changes the documentation question | New provider conclusion, actual support change, or operative detail |
| Discharge approaching | Review significant open items and handoff needs | Final assessments or disposition become available |
| Coding reconciliation | Explain differences using the complete record and applicable rules | A genuine conflict, coding question, or authorized correction remains |
The purpose is continuity and ownership, not repeated full-chart reading without a reason. Record what has changed since the last review and focus effort on that change while preserving the broader context.
Distinguish Three Kinds of Timing
Clinical events, record-completion requirements, and local CDI workflow clocks serve different purposes. A new urgent care issue uses the appropriate clinical route. H&P and record-completion requirements have their own legal scope. A query response window and an initial-review target are separate local operational expectations.
The 2026 query brief assigns specific response timeframes to organizational policy and supports defined escalation and closure. It does not prescribe a universal schedule for all CDI chart reviews. Do not infer that every record should wait for an H&P deadline, or that every review after a chosen local interval is professionally noncompliant.
Milestone-based follow-up can complement a schedule. A significant final report, a meaningful contradiction, a change in documented clinical assessment, or impending discharge may warrant earlier attention. None automatically establishes a complication or a higher severity tier. Check what actually changed before sending another query.
Identify the Actual Payment and Data Context
The payer name is a starting point for identifying applicable arrangements, not a complete description of the contract or model. Clinical accuracy and appropriate reporting remain necessary regardless of payer. Verify the actual hospital payment method, applicable code-set and grouper versions, population, service, and any special terms before explaining a financial effect.
Traditional Medicare IPPS uses MS-DRG classification together with other payment rules. Many families have severity splits, but grouping uses the complete relevant inputs rather than merely finding the first CC or MCC. A maximum tier is not permission to stop reviewing accuracy or other reportable conditions.
Medicare Advantage plan risk adjustment and hospital facility reimbursement are distinct. A hospital’s contract may use a DRG, per diem, or another arrangement; do not assume its terms from the insurance label. CMS-HCC modeling concerns risk-adjusted plan payments and uses specified data and model rules. It is not an automatic dollar amount added to the hospital claim for every chronic diagnosis.
CMS’s technical report describes prospective risk modeling, diagnostic hierarchies, and the principle that more closely related codes should not automatically increase predicted cost. CMS also publishes payment-year-specific software and mappings. Use the applicable release rather than treating all historical diagnoses, every submitted code, or every chronic condition as an additional payment HCC. Documentation and encounter-reporting requirements still govern what may be reported.
Keep APR-DRG Concepts Distinct
Solventum APR DRGs provide a base classification and separate severity of illness and risk of mortality subclasses described as minor, moderate, major, and extreme. SOI and ROM are different dimensions; neither is interchangeable with MS-DRG CC/MCC status or an individual probability of death.
The methodology considers clinical information and relationships. Do not teach that each added secondary diagnosis necessarily increases a subclass or that every extreme subclass requires a fixed number of organ failures. Solventum describes multiple comorbid conditions as commonly associated with extreme classes, not a universal counting rule. Use the actual licensed methodology and complete verified inputs for a real grouping result.
Commercial and Medicaid arrangements can differ by jurisdiction and contract. A stop-loss provision, carve-out, or supplemental payment has the terms specified in that arrangement. Do not assume that crossing a universal charge or LOS threshold converts every case to a percentage-of-charges payment.
Use LOS as a Signal With Limits
A statistical LOS benchmark can identify variation worth investigating. It is not an individual stay allowance or proof of an undocumented complication. An extended stay may involve clinical need, service delays, placement availability, patient preferences, or other circumstances. Review the actual facts and communicate with the responsible teams.
A program may choose a local benchmark-based reminder, but “75% of GMLOS” is not a national CDI re-review mandate. GMLOS also has defined transfer-payment uses; ordinary cost-outlier qualification follows separate cost-based rules. Reaching a benchmark does not independently establish an outlier payment or justify adding diagnoses to explain elapsed days.
Plan Capacity Transparently
In a fictional eight-hour shift, 480 minutes minus 90 minutes of meetings, required education, and other allocated duties leaves 390 minutes. Six initial reviews at 30 minutes use 180 minutes; eight follow-ups at 15 minutes use 120; three query tasks at 20 minutes use 60. Planned work totals 360 minutes, leaving 30 for additional needs. These are illustrative local assumptions, not productivity standards.
The example contains 14 chart-review activities and three query tasks, not 17 unique patient encounters. Some activities may concern the same patient. If actual work takes longer, adjust priorities, coverage, or resources rather than treating a number target as justification for superficial review. Include reconciliation and other assigned work in capacity planning rather than making them invisible.
Reconcile the Final Record Without Forcing a Target
The working DRG reflects provisional information and may appropriately differ from final coding. Investigate the reason: later information, a different principal diagnosis, reportability, a procedure detail, an exclusion, or a coding error. The task is to reach the supported result, not make final coding match the earlier working number.
Use the approved process for significant pending queries, billing holds, escalation, and closure. Not every unresolved item requires an indefinite hold or a response confirming the proposed diagnosis. After escalation is exhausted, the 2026 brief provides for closure under policy and code assignment from the existing record. Later record or claim corrections follow their authorized procedures.
Monitor accuracy, unresolved age, review coverage, and useful outcomes alongside volume. A predictable follow-up process helps maintain continuity, but neither a rigid clock nor a high review count establishes that the underlying clinical and coding questions were resolved correctly.
Source anchors: ACDIS practitioner productivity examples; 2026 query practice brief, sections IX and XIII; CMS IPPS; CMS risk-adjustment resources and payment-year releases; CMS December 2024 technical report, sections 2.3–2.4; Solventum APR-DRG methodology overview; 42 CFR 412.4.
A patient is enrolled in Medicare Advantage. Which statement correctly separates the hospital’s facility payment from CMS-HCC risk adjustment?
Every MA hospital claim receives the same MS-DRG payment plus a fixed amount for every chronic diagnosis.
Verify the hospital’s actual contract; CMS-HCC modeling concerns risk-adjusted plan payments using specified data and model rules, not an automatic hospital-claim supplement for each diagnosis.
All historical diagnoses may be imported into the current encounter because annual risk adjustment overrides encounter-reporting rules.
Once an MCC is documented, neither facility coding accuracy nor chronic-condition reporting requires further review.
A fictional shift has 480 minutes, with 90 allocated to other duties. Six initial reviews at 30 minutes, eight follow-ups at 15 minutes, and three query tasks at 20 minutes are planned. Which report is accurate?
The plan requires 480 review minutes and proves the program has a national 17-patient target.
There are 17 unique patients because every activity must involve a different encounter.
There are 390 available minutes, 360 planned minutes, and 30 remaining; the plan includes 14 chart-review activities and three query tasks, not necessarily 17 unique encounters.
The plan uses only 300 minutes because query work should not be included in capacity calculations.
A policy draft presents initial review within 24–48 hours, re-review every 48–72 hours, and an automatic review at 75% of GMLOS as national CDI requirements. What revision is appropriate?
Keep all three as federal requirements because they appear in some practitioner workflows.
Require every program to wait 48 hours even when a short-stay patient has a significant unresolved issue before discharge.
Remove all follow-up expectations because only post-bill review can be planned.
Identify justified local review expectations, owners, and milestone triggers, separating them from clinical urgency, legal record rules, query windows, and LOS statistics.
Sections you finish are checked off in the contents.