Provider Credentialing Timeline: What Takes So Long and How to Speed It Up

The Credentialing Black Box

For most health plan executives who aren't steeped in credentialing operations, the process feels like a black box: providers go in, time passes, and eventually they come out credentialed. The 90-120 day cycle time that credentialing coordinators quote seems impossibly long for what appears to be a verification process. Why does checking a medical license take three months?

The answer is not that any individual step takes three months. It is that the process involves multiple external parties — licensing boards, malpractice carriers, hospital medical staff offices, the DEA, the NPDB — each of which operates on their own timeline, and that multiple sequential dependencies in the process mean that delays at any single step cascade forward. Understanding exactly where time is consumed in credentialing is the prerequisite for compressing it.

Stage 1: Application (Days 1-14)

The credentialing process begins when a provider completes and submits a credentialing application. For most plans, this means completing or updating their CAQH ProView profile (which serves as the universal credentialing application) and submitting plan-specific forms for anything CAQH doesn't cover.

Time consumed: 5-14 days, depending on how current the provider's CAQH profile is and how quickly the provider's office responds to requests for supplemental documentation.

Common bottlenecks: Stale CAQH profiles that require re-attestation, missing supplemental documentation (procedure-specific training documentation for high-risk specialties, hospital affiliation letters, DEA certificates), and provider offices that deprioritize the administrative work of completing the application. Strategies to compress this stage include: requiring CAQH profile update confirmation before contract execution (so the profile is current when the credentialing application is initiated) and assigning a dedicated credentialing coordinator to assist provider offices with the application process.

Stage 2: Primary Source Verification (Days 14-75)

Primary Source Verification (PSV) is the process of verifying each element of the provider's credentials directly with the issuing body, not through the provider themselves. This is where the majority of credentialing cycle time is consumed. PSV elements for a typical physician include:

• Medical license verification — typically completed in 5-15 days, as most state medical boards now have online verification systems
• Board certification verification — ABMS certifications can be verified quickly online; for specialties with multiple certifying boards, verification may require direct contact with the board
• DEA registration verification — usually 5-10 days
• Malpractice coverage verification — requires written request to the malpractice carrier; response times vary from 5 to 30 days, and carriers who are slow are the single biggest source of PSV delay
• Hospital privileges verification — requires written request to the hospital medical staff office; response times range from 10 to 45 days, with academic medical centers and large teaching hospitals being the slowest
• National Practitioner Data Bank (NPDB) query — typically 2-5 days for electronic queries
• Work history verification for gaps — for providers with gaps in their work history, verifying the explanation takes additional time

The PSV stage cannot be completed until all elements are verified. The total PSV timeline is determined by the slowest element — which is almost always malpractice carrier or hospital privileges verification. Strategies to compress PSV: send all verification requests on day one of PSV simultaneously rather than sequentially; follow up on malpractice and hospital requests weekly starting on day 5; use a credentialing verification organization (CVO) for providers with complex credential histories.

Stage 3: Committee Review (Days 75-90)

Most plans hold monthly credentialing committee meetings. A provider whose PSV completes on day 31 of the monthly cycle must wait until the next committee meeting — which could be up to 30 days away. For a provider who needs to be credentialed by a specific date to count toward an adequacy submission, a single committee meeting cycle delay can mean the difference between making the adequacy model run date and needing an exception filing.

Strategies to compress this stage: hold bi-monthly committee meetings during peak network build periods; use a delegated credentialing arrangement with a managed services organization that has more frequent approval cycles; for large groups, negotiate a delegated credentialing agreement that allows the group to credential their own providers subject to plan oversight and retrospective audit.

Stage 4: Effective Date Assignment (Days 90-105)

After committee approval, the plan assigns a credentialing effective date, which is the date from which the provider can see plan members and be counted toward adequacy. Effective date assignment typically requires 5-15 days of administrative processing: system entry, contract validation, and provider notification.

The effective date must precede your adequacy model run date for the provider to count toward adequacy. Build at least 10 business days of buffer between committee approval and adequacy model run date to account for effective date processing time.

Running Credentialing in Parallel with Contracting

The single highest-impact change most network ops teams can make to their credentialing timeline is to initiate credentialing in parallel with contracting, not after contracting is complete. Most teams wait for a fully executed contract before initiating the credentialing application — which means the 90-120 day credentialing clock doesn't start until contracting is done.

Best practice: initiate the credentialing application at the same time as the Letter of Intent (LOI). The LOI signals the provider's intent to join the network; the credentialing application can proceed in parallel with contract negotiation. If a provider ultimately doesn't execute the contract, the credentialing work is wasted — but the probability of that outcome is low (most LOI signers execute), and the cost of wasted credentialing work for the occasional non-signer is far lower than the cost of a late adequacy submission.

Plans that run credentialing in parallel with contracting routinely complete their adequacy builds 30-45 days ahead of plans that run them sequentially. In a build where the adequacy submission deadline is fixed and non-negotiable, those 30-45 days are the buffer that separates clean submissions from exception filings.