Recredentialing

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Recredentialing revisits a defined approval

The original credentialing record establishes the baseline. Recredentialing asks whether the provider still meets the reviewing organization's current criteria for the approved role and scope. The review may revisit identity, education, training, licensure, certification, work history, malpractice coverage and history, sanctions, exclusions, disciplinary actions, disclosures, health-status questions when lawfully permitted, clinical privileges, competence evidence, and organizational affiliations.

Create one case for each provider-reviewing-entity-product-role relationship. A clinician credentialed with three payer products may have three due dates and three decisions. A group review and an individual review may also run on different clocks.

Capture:

• controlling policy, contract, delegation agreement, or program rule
• provider, organization, product, role, location, and approved service
• lookback period, due date, internal start date, and response deadline
• required sources, documents, attestations, releases, and disclosures
• reviewer questions, correction history, committee or authorized decision
• continued, limited, suspended, denied, terminated, or appeal state
• decision date, effective date, next review date, owner, and evidence path

Avoid inventing one standard three-year cycle. Use the date and cadence assigned by the source that governs each relationship.

Several renewal processes may run together

The CMS NPI fact sheet supplies another boundary: an NPI does not establish licensure or credentialing, guarantee payment, or enroll a provider in a plan. The identifier usually remains stable while these review states change.

The DataSpring resources page describes recurring Provider Data Portal attestation, generally every 120 days and every 180 days for Illinois providers, with certain directory prompts producing a 90-day deadline. That schedule belongs to the portal workflow. It does not establish a payer's recredentialing cycle or decision.

Medicare revalidation is an enrollment process

The current CMS provider-enrollment guide separates NPI assignment from Medicare enrollment. Its revalidation page defines revalidation as periodically renewing an enrollment record to maintain Medicare billing privileges. In general, providers and suppliers revalidate every five years, while DMEPOS suppliers revalidate every three years; CMS can request off-cycle revalidation.

CMS tells actively enrolled providers to use the Medicare Revalidation List. The tool posts due dates six to seven months ahead and may display TBD when a date has not been set. The revalidation page says providers remain responsible for tracking their due date even when a notice is expected. It warns that lateness can lead to a payment hold or deactivation.

The December 2025 Medicare enrollment guide describes revalidation as resubmitting and recertifying enrollment information. This Medicare process applies only to eligible Medicare provider and supplier types. It does not create Medicare eligibility from BACB certification or set a commercial-payer recredentialing timetable.

Medicaid also requires enrollment revalidation

Current 42 CFR 455.414 requires state Medicaid agencies to revalidate all enrolled providers regardless of provider type at least every five years, with limited statutory-provider exceptions described in the rule. States may revalidate more frequently.

For managed care, 42 CFR 438.602(b) requires the state to screen, enroll, and periodically revalidate network providers for the listed entities. Track state enrollment revalidation and plan recredentialing, contracting, roster, and directory work as separate records even when they share documents.

Build a due-cohort workflow

Start with every relationship whose governing due date falls in the measurement window. Keep a case in the denominator after work begins. Assign enough lead time for provider review, primary-source verification, missing documents, payer questions, committee timing, and correction, while following any rule about how early a submission may be accepted.

Use event triggers between periodic reviews. A license restriction, exclusion, disciplinary action, lapse in coverage, adverse event, ownership or employment change, new site, or material disclosure can require earlier reporting or review. Route urgent scope or safety questions to the qualified owner without waiting for a scheduled cycle.

Pending review does not automatically mean active, inactive, or extended status. Obtain the reviewing entity's written rule or decision. Before scheduling payer-covered care or releasing a claim, verify the credentialing, enrollment, contract, roster, location, effective date, authorization, provider role, supervision, and service-date configuration that actually applies.

If participation changes, coordinate notices, appeals, records, authorizations, schedules, billing, and a clinically responsible continuity or transition process. An internal due-date flag alone should not trigger abrupt discharge.

A fictional recredentialing cohort

A fictional ABA practice locks 20 provider-payer-product relationships whose recredentialing decisions are due by the quarter-end cutoff. Seventeen have complete provider attestations, current source checks, required documents, disclosures, and a submitted package. Submission completeness is 17 of 20, or 85%. Three stay open with owners and ages.

By the cutoff, 14 of the original 20 have final decisions: 12 continued, one limited to specified locations, and one terminated after the applicable process. Decision completion is 14 of 20, or 70%. Reporting 14 of 14 would hide six unresolved relationships. The practice records the operational effect of every decision and keeps the pending cases visible.

These measures describe process control. They cannot establish clinical competence, service quality, claim acceptance, or payment.

Measure timeliness and outcome separately

Useful measures include complete packages divided by relationships due; submissions made by the governing deadline divided by submissions due; payer questions answered on time divided by questions due; final decisions divided by relationships reaching the maturity date; decisions configured across affected systems divided by decisions due for configuration; and overdue cases by count and oldest age.

Report continued, limited, suspended, denied, terminated, pending, returned, and appealed states separately. Segment by provider, payer, product, role, site, owner, source version, due month, and age.