CMS large-group revalidation needs roster-level deduplication
CMS tells groups with more than 200 members to coordinate Medicare revalidation from the Revalidation List and the MAC's group spreadsheet so only one application is submitted for each provider or supplier. That coordination needs identity, enrollment, due-date, ownership, submission, correction, and MAC-status evidence at the roster row.
Editorial figure by Credentialing Current. Source context: CMS Medicare Provider Enrollment Resources.
Start with the enrollment relationship, not a name match
The direct answer is that a large-group revalidation roster should identify the exact Medicare enrollment relationship that requires action. CMS's education record says groups with more than 200 members can search the Medicare Revalidation List by organization name and will receive a MAC letter and spreadsheet for providers linked to the group who must revalidate within six months. A provider's name, NPI, or appearance on an internal credentialing roster alone does not identify every enrollment, reassignment, practice location, organization link, or contractor responsibility.
Preserve the organization legal name and identifier, individual or supplier identity, NPI, enrollment and reassignment references available to the authorized team, provider or supplier type, practice location, MAC, current group link, Revalidation List snapshot, listed due date or TBD state, notice date, applicable cycle or off-cycle request, internal owner, and source row. Resolve duplicate names, changed identifiers, terminated clinicians, acquisitions, moves, and multiple group relationships before assigning work. Keep an uncertain match open rather than merging records by convenience.
The list, MAC notice, and local roster need recurring reconciliation
CMS says the public list is updated every 60 days at the start of the month, presents due dates up to seven months ahead, and uses TBD for dates farther out. CMS also says a MAC generally sends a revalidation notice 90 to 120 days before the due date. Those are separate sources with different timing and operational use. The group should retain each list snapshot and MAC file, compare identities and dates, document additions, removals, changed due dates, and missing notices, and route discrepancies for review.
Do not submit merely because an internal calendar predicts a routine cycle. CMS says that if neither a due date nor a MAC request exists, an unsolicited revalidation should not be submitted, while a provider within three months of a listed due date should submit even if the notice did not arrive. Encode those instructions with source date and review authority. A future list refresh or contractor notice may supersede the work queue; the system should preserve why a case was opened, held, canceled, or reprioritized.
Deduplication requires one accountable case per enrollment action
CMS specifically tells large groups to work together so they submit only one application from each provider or supplier. Achieving that result requires more than deleting duplicate rows. Create an accountable case keyed to the relevant person or entity and enrollment action, then link every source roster row, business unit, credentialing team, delegated user, external service, and application attempt. Record who may prepare, sign, certify, submit, answer corrections, and receive notices. Access to PECOS does not itself grant internal authority to act for every record.
This is a population-control decision before and alongside application processing, not a repeat of the separate question whether one PECOS submission has completed Medicare revalidation. The test here is whether every roster row resolves to exactly one warranted case for each distinct enrollment action. Block parallel preparation only when records truly describe the same action; clinicians may legitimately have multiple enrollment or reassignment needs. When a duplicate is detected after work begins, preserve both case histories, identify the surviving record, reconcile conflicting values and attachments, and document why the other attempt stopped. Separate controls govern the later submission and MAC response states.
Test a provider linked to two operating divisions
Use a representative group roster in which one clinician appears under two divisions, recently changed a practice location, has a listed due date, and is also present in the MAC spreadsheet under a slightly different name. Add a terminated provider, a new provider with TBD, one missed notice, one duplicate preparation case, and one MAC correction request. Verify that identity resolution is reviewable, only the true duplicate is consolidated, due-date provenance remains visible, signing authority is enforced, response deadlines are tracked, and every source roster resolves to a current disposition.
CMS's official education record supports the attributed statements about revalidation meaning, general cycles, public-list cadence and horizon, MAC notices, large-group coordination, duplicate-application instruction, and consequences that may follow late or incomplete action. It does not establish the current status of a specific enrollment, the completeness of a group's roster, a contractor's decision, credentialing or privileging status, network participation, billing eligibility for a claim, payment, or rebuttal outcome. Enrollment, credentialing, compliance, legal, revenue-cycle, and authorized organizational officials retain those decisions.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Credentialing Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.