CMS states that a certified IDR entity may consider up to 50 qualified IDR items and services in one payment determination when the finalized batching requirements are satisfied.
The limit is not the eligibility test.
The 50-item ceiling addresses how many qualified items and services may be considered together under the final rule. Each item still needs reliable source data and must fit the applicable batching requirements.
Because implementation is phased, teams should verify the current effective date, form, portal capability, and CMS guidance before submitting under the expanded rule.
Build candidate batches from normalized data.
- Provider, facility, group, and payer identifiers
- Plan and funding information
- Service codes, modifiers, units, and dates
- Payment or denial information
- Open-negotiation and initiation dates
- The rule and rationale used to group the items
Keep item-level records intact.
Batching should create a relationship among claims, not erase the underlying claim records. Teams still need to explain why each item belongs, respond to eligibility questions, and unwind or correct a grouping if necessary.
Track economics and outcomes at both levels.
A useful dashboard shows the batch as an operating unit while preserving item-level amounts, statuses, evidence, determinations, and payments. That supports accurate incremental-recovery reporting and prevents a single batch status from hiding unresolved items.