CAQH Is Now DataSpring in 2026: What Changed for Provider Enrollment Teams

What changed in June 2026

The visible change is primarily naming. The organization now uses the DataSpring brand, while the provider portal previously known as CAQH ProView is called the CAQH Provider Data Portal. Enrollment staff should expect both old and new terminology to appear during the transition because payer documents, internal SOPs, saved bookmarks, and staff habits may not update at the same speed.

There was also a separate organizational change earlier in January 2026, when CAQH moved from nonprofit to for-profit status. That event preceded the June rebrand and should not be treated as the same event. For day-to-day enrollment work, the June name change is the more visible operational change.

Add both names to internal search terms for several months. A staff member looking for an old payer instruction may search 'CAQH ProView,' while a new payer email may say 'DataSpring' or 'CAQH Provider Data Portal.' Using cross-references in the SOP and tracker preserves institutional memory without creating duplicate profiles or duplicate maintenance tasks.

What did not change for the provider profile

Existing provider data does not disappear because of the rebrand. The same portal URL, proview.caqh.org, continues to be used, and the same login is expected to work. A clinician or practice should not create a duplicate profile merely because a payer or third-party vendor now refers to DataSpring instead of CAQH.

The reattestation rhythm also remains approximately every 120 days. Teams that already maintain a calendar for profile review should continue using that cadence unless a separate payer requirement creates an earlier internal deadline.

When access fails after the branding change, troubleshoot it as an account-access problem before calling it a migration problem. Confirm the usual username, password-reset path, provider record, and portal URL. Escalate only after verifying the practice is using the official provider portal rather than a saved third-party link or an outdated training screenshot.

How to update internal enrollment workflows

The cleanest transition is to update labels without changing the underlying workflow. Rename internal checklist items from CAQH ProView to CAQH Provider Data Portal, keep the existing portal bookmark, and note that DataSpring is the new organization brand. This reduces the chance that a staff member mistakenly opens a new registration task.

If a payer asks whether the provider has a current DataSpring profile, staff can treat that as the same provider-data workflow previously handled through CAQH ProView. The important operational checks remain profile completeness, current documents, and timely attestation.

For new hires, update templates so the clinician sees the new name from the start, but retain 'formerly CAQH ProView' for context. That one line can prevent a clinician from believing they have two separate payer-data profiles to complete. The operational goal is continuity: one provider record, one maintenance calendar, and terminology everyone can recognize.

What to tell clinicians who see the new name

A short internal explanation is usually enough: CAQH changed its brand to DataSpring, the provider portal was renamed, and the provider does not need to start over. This is particularly useful for clinicians who only log in when they must attest and may be surprised by different branding.

Enrollment teams should avoid describing the change as a new credentialing system. It is a rebrand of the organization and portal naming, not a requirement to rebuild the provider record from scratch.

If a payer request still says CAQH, do not spend time asking the payer to reissue the request under the DataSpring name. Confirm that the request points to the same provider-data workflow, complete the substantive profile or attestation work, and note the naming transition only when it helps staff understand what system the payer means.

Build a rebrand-safe credentialing workflow

Treat the DataSpring change as a terminology and communication project rather than a profile-migration project. Start by identifying every place your team still writes CAQH ProView: onboarding checklists, payer spreadsheets, standard emails, training notes, shared drive folders, and instructions sent to clinicians. Update the label to CAQH Provider Data Portal or DataSpring, powered by CAQH, while keeping the working URL and existing login workflow unchanged. That distinction prevents staff from creating duplicate tasks for a change that does not require a new registration or a rebuilt profile.

For a small practice, the most useful control is a short note in the provider enrollment tracker that separates platform identity from profile status. The platform name changed in June 2026, but the underlying provider record, login, stored information, and attestation cycle continue. A credentialing specialist opening an old task six months later should be able to tell immediately that an older reference to ProView points to the same provider data workflow rather than to a retired account that must be recreated.

Also standardize the wording used when a payer, clinician, or consultant uses different names for the same portal. One person may still say CAQH, another may say DataSpring, and an older payer checklist may say ProView. The operational question is not which label appears in the email; it is whether everyone is referring to the provider-facing portal at the same URL. Recording that equivalence in your internal instructions avoids unnecessary password resets, duplicate profile creation attempts, and false escalation tickets.

Common 2026 mistakes to prevent

The first mistake is treating the rebrand as a trigger to register again. providers do not lose their existing data and do not need a new account. A second registration attempt can create internal confusion because staff may begin tracking a nonexistent migration instead of maintaining the established profile. The safer response is to sign in through the existing portal, verify that the clinician can access the expected profile, and continue the normal maintenance workflow.

The second mistake is allowing the new name to interrupt the attestation calendar. A branding change does not reset the roughly 120-day reattestation rhythm. If your office tracks due dates, keep the existing next-attestation date and simply update the system name in the task. This matters because a team distracted by the rebrand can spend time documenting the name change while missing the ordinary maintenance work that actually affects payer use of the profile.

Finally, do not merge the January 2026 organizational change with the June 2026 rebrand into one event. They happened at different times and answer different questions. The January change concerns CAQH's organizational status, while the June change concerns the DataSpring brand and provider portal naming. Keeping those events separate helps office managers interpret old notices, new portal screens, and payer instructions without assuming that every 2026 CAQH update changed provider enrollment operations.

Operational checklist

• Keep the existing proview.caqh.org bookmark
• Do not create a second provider account because of the rebrand
• Update internal SOP language to DataSpring / CAQH Provider Data Portal
• Continue the approximately 120-day attestation schedule
• Tell clinicians that existing login credentials and profile data remain in place

Sources reviewed