What Is the CAQH Provider Data Portal? A Physician's Complete Guide

Most physicians encounter CAQH's credentialing system at one of two moments: when a credentialing coordinator asks for their CAQH ID, or when a payer rejects their application because their profile is out of date. Neither is a good time to learn what it is.

Here is what you need to know — including some changes in the last six months that affect how you should think about where your credential data lives.

What It Is

The CAQH Provider Data Portal is a centralized database for healthcare provider credentials. You enter your credential information once — licenses, DEA registration, board certifications, malpractice history, education, work history, hospital affiliations — and health plans pull that data directly from your profile instead of asking you to supply it again for each payer relationship.

The short version: it is the central source of truth that most of the commercial insurance world uses when it credentials a physician.

A brief timeline: CAQH (the Council for Affordable Quality Healthcare) was founded in 1999. The current platform launched in 2015 under the name CAQH ProView. In June 2026, CAQH rebranded the organization to DataSpring, powered by CAQH, and renamed the portal the Provider Data Portal. The login address — proview.caqh.org — remains unchanged, and your existing profile, attestation history, and authorizations carry over. If you have heard it called ProView, you are not behind; the new name is only weeks old.

The Ownership Change: What Physicians Should Know

The name change is cosmetic. The ownership change is not.

In January 2026, CAQH converted from a 25-year nonprofit alliance into a for-profit company. Twelve payer-affiliated organizations are now shareholders, and a UnitedHealth Group executive chairs the board.

This matters for a straightforward reason: the entity that holds the canonical record of your credentials — the profile that payers pull directly for credentialing and re-credentialing decisions — is now a for-profit company owned by those same payers. That does not mean your data is being misused. It does mean the structure of the organization has changed, and physicians who want to understand who controls their credentialing infrastructure should know it.

The practical workflow is identical to what it was under the nonprofit structure. The governance question is worth watching.

Who Uses It

Over 1,000 health plans, hospitals, and health systems use the Provider Data Portal to access credentials for enrollment and credentialing. Aetna, UnitedHealthcare, Cigna, Humana, and Blue Cross Blue Shield plans across most states all use it as part of their provider enrollment workflows. Medicaid managed care organizations in many states use it as well.

If you participate in commercial insurance — even with just one or two payers — there is a good chance your profile is already in active use. Credentialing coordinators will ask for your CAQH number almost immediately when you apply to credential at a new hospital or join a new group.

Setting Up Your Profile

You register at proview.caqh.org. The setup process works through several sections:

Personal and professional information. Your name (exactly as it appears on your licenses), NPI number, primary specialty, board certification status, and contact information.

Licensure. Every state medical license you hold — license number, issue date, expiration date, issuing state, and whether any license has ever been restricted, suspended, or revoked. If you have a multistate license through the Interstate Medical Licensure Compact, you will still need to list each state separately.

DEA registration. Your DEA number, schedule, expiration date, and state of registration. Multiple state registrations each get their own entry.

Education and training. Medical school, residency, fellowship — institution, dates attended, and degrees or completion certificates.

Work history. Your employment and practice history for the past five to ten years, depending on the payer's requirements. Gaps need to be explained.

Hospital affiliations. Current and past privileges, by facility.

Malpractice history. Open and closed claims. Payers verify malpractice history against the National Practitioner Data Bank, and discrepancies between your profile and what the NPDB shows are a common source of credentialing delays.

Malpractice insurance. Current carrier, policy number, coverage limits, and expiration date.

Professional references. Some payers require peer references from physicians who can attest to your clinical competence.

Budget two to four hours for initial setup if your practice history is straightforward; more if you have multiple licenses, past affiliations, or any malpractice history to document. Collecting source documents — license certificates, malpractice coverage pages, board certification letters — before you start will significantly reduce the time.

The Re-Attestation Requirement

This is where most physicians run into trouble.

The Provider Data Portal requires you to re-attest your profile every 120 days. Re-attestation means you log in, review your profile for accuracy, confirm or update anything that has changed, and submit. When nothing has changed, the process takes ten minutes.

DataSpring sends automated reminders ahead of your re-attestation deadline and flags documents approaching expiration — so you will get a heads-up before your profile lapses. What you will not get is a notification that payers have already lost access. The reminder goes to you; the downstream consequence plays out quietly on the payer's side.

Here is why that matters: if your profile lapses before you re-attest, payers lose access to your data and cannot pull your credentials. Any in-progress credentialing applications that depend on your profile stall — without any alert to you from the payer that this has happened. Their processing queue keeps moving; your application just sits.

The fix is straightforward: set a recurring calendar reminder for every 90 days. That gives you a 30-day buffer before the 120-day lapse, independent of whatever the system sends.

Keeping Credential Data Current

Re-attestation handles the lapse problem. Accuracy is a separate issue.

Common updates physicians miss:

Medical license renewals. Most states require renewal every one to two years. If your license renews and you do not update the portal with the new expiration date, payers will eventually see an expired license in your profile. Some will flag this automatically; others will not — until a coordinator runs a manual check.

DEA registration. DEA registrations renew every three years. Update the portal as soon as you renew.

Malpractice insurance. Annual renewals are standard. Your profile needs the current policy period and coverage limits, not last year's.

Board certifications. Many boards now require maintenance of certification activities and periodic recertification. If your board certification has a time limit, the portal needs the current certification.

Practice address. If you move, change groups, or add a new location, update the portal. Credentialing applications cross-reference your portal address against your NPI record and your state license registration. Mismatches slow things down.

The discipline here is less about each individual update and more about having a system. The default is to renew a document and not think about the downstream effect on the portal or any other credentialing database that holds your information.

The Provider Data Portal and the Broader Credentialing Picture

The Provider Data Portal is one piece of a fragmented credentialing system. It feeds payer enrollment and re-credentialing, but it does not replace hospital-specific credentialing applications, which typically go through separate systems — many hospitals use Symplr, MD-Staff, or similar platforms. Hospital credentialing committees will often request your CAQH ID and pull data from your profile, but may also ask you to complete their own forms with overlapping information.

This is why credentialing is as time-consuming as it is. You may be maintaining credentials in your state licensing portal, your DEA portal, the DataSpring Provider Data Portal, the NPDB (passively), your hospital's credentialing system, and your malpractice carrier's portal — all with different update cycles and different expiration dates.

The organizations that move through credentialing efficiently typically have a document management system: something that tracks what expires when, surfaces advance notice before a lapse, and stores source documents in one accessible place.

What Happens When You Get It Wrong

The downstream consequences of neglected profile data fall into two categories: delays and denials.

Delays are the most common outcome. A payer running a credentialing application finds a lapsed re-attestation, an expired license date, or a missing insurance certificate. They issue a deficiency notice and pause processing. You fix the issue, re-attest, and processing resumes. Add two to four weeks, minimum.

Denials happen when a payer finds a material discrepancy — most often in malpractice history — between what your profile reports and what other verification sources show. Depending on the nature of the discrepancy and the payer's policies, this can result in a denial requiring formal appeal.

Neither outcome is catastrophic, but both are expensive. A physician who cannot bill a payer during credentialing is generating revenue at a reduced rate or not at all. A two-week delay for a full-time physician is not a rounding error.

A Note on Where VestaCreds Fits

There's a quieter takeaway in all of this. As more of your credentialing infrastructure consolidates under payer ownership, there's value in keeping your own independent record of your credentials — one source of truth that answers to you, not to the plans you contract with. That's the gap VestaCreds is built to fill.

VestaCreds does not connect to the DataSpring Provider Data Portal directly — that integration is on our roadmap, not live today. What VestaCreds does today is help you track your credentials in one place: your licenses, DEA registrations, board certifications, malpractice coverage, and the documents behind each of them, with expiration alerts so you know what needs attention before it lapses.

If you are managing credentials across multiple states, multiple hospital affiliations, or a practice with more than a handful of clinicians, a system that surfaces expiration dates in advance — before they turn into portal discrepancies or credentialing delays — is the part that changes the workflow.

You can learn more or request access at vestacreds.com.

The Short Version

The CAQH Provider Data Portal (DataSpring, formerly CAQH ProView) is the central credentialing database used by most major commercial payers.
In January 2026, CAQH converted from a nonprofit to a for-profit company owned by twelve payer-affiliated shareholders.
You register once, then re-attest every 120 days or your profile lapses — the system sends reminders to you, but payer access loss is not proactively flagged.
Expired or missing credential data stalls in-progress applications without automatic notification on the payer's side.
The system rewards physicians who track their own credential expirations and update proactively — independent of whatever the portal sends.
The Provider Data Portal centralizes some of credentialing, not all of it. The rest requires its own discipline.

The 90-to-120-day credentialing timelines that frustrate physicians and administrators alike are not all caused by payers. A significant portion is credentials data — expired, missing, or inconsistent — that could have been caught and corrected before the application was ever submitted.

VestaCreds is building an AI-powered credentialing platform that helps clinicians track, organize, and share their credentials. Currently in pilot. Learn more at vestacreds.com.