CAQH is now DataSpring, powered by CAQH, according to DataSpring's June 2026 announcement. The 2026 change updates the name and organization. Payer credentialing still requires its own evidence. Clinicians and practice administrators should update bookmarks, owner records, training, and vendor inventories while preserving profile attestations, recipient permissions, payer applications, and effective dates as separate evidence.

Use current and former names during transition

DataSpring's clinician Q&A uses DataSpring, CAQH Provider Data Portal, and former CAQH or ProView references to explain continuity. Search instructions, payer emails, contracts, and staff notes under all applicable names. Record the exact URL and screen label. Brand language alone creates no new credentialing status.

Create an alias map for help-desk scripts, policy names, password-manager entries, payer instructions, and evidence exports. Give the current name, former name, product function, approved URL, account owner, and last verified date. Keep historical artifacts under the name displayed when the event occurred. This allows an auditor to connect a prior CAQH attestation to the current DataSpring environment without rewriting the original evidence.

Keep profile control with the clinician

DataSpring's credentialing page describes clinicians entering and verifying profile information and choosing organizations that receive access. Group administrators may manage data through delegated workflows, while the individual clinician remains responsible for required verification and attestation. Preserve who entered, who verified, who attested, what changed, and which recipient had permission.

Separate the portal from payer decisions

A complete or attested profile can supply data to participating organizations. It does not prove that a payer received an application, completed primary-source verification, approved credentialing, executed a contract, loaded a roster, assigned an effective date, published a directory entry, accepted a claim, or issued payment. Track each state with its own source and owner.

Review authorization and terms

Provider Data Portal terms describe recurring confirmation and access through the service. Inventory individual and group accounts, administrators, delegated access, payer recipients, inactive staff, retained accounts, recovery channels, and exported evidence. Remove access promptly when duties change and preserve required business records outside a single user's inbox.

Separate individual-profile permissions from group or delegated roster workflows. A clinician's recipient choices should reflect that person's authorized profile sharing. A group administrator needs only the access required for assigned duties. Record the request, approver, role, activation date, last review, removal date, and evidence location for each account. Test recovery through an organization-controlled route before the original administrator leaves.

Reconcile the profile before attestation

Use a field-level review for identity, practice locations, licenses, education, work history, specialties, hospital relationships when applicable, liability coverage, disclosures, supporting documents, recipient choices, and expiration dates. Compare the portal value with the current authoritative record and label any unresolved mismatch. The clinician should verify and attest where the workflow requires personal attestation; staff preparation cannot substitute for the clinician's confirmation.

After attestation, save the date, profile version or export, clinician identity, recipient configuration, and unresolved items. Keep the next required review on a controlled calendar. A portal reminder is useful operational evidence, while the organization's own task register supplies continuity when notifications or account ownership change.

Update systems without losing history

Replace user-facing names where DataSpring supplies the current label, retain former-name aliases for search and audit, and avoid bulk rewriting historical evidence. A 2025 attestation occurred under the label then in use. Add a vendor-identity field, product-name field, URL, checked date, and former-name alias so reports can explain the transition accurately.

A fictional rebrand audit

Niko's group locks 31 bookmarks, templates, account owners, permissions, payer references, and evidence exports affected by the change. Twenty-four are verified, so completion is 24 of 31, or 77.4%. Seven remain visible with owners. The figure measures operational migration. Profile accuracy, credentialing approval, network status, and directory accuracy require separate evidence.

The group tracks profile accuracy in a separate review with a fixed field denominator. It also tracks each payer application, credentialing decision, contract, roster load, directory entry, and effective date as its own event. A rebrand task closes only when the relevant operational reference is current; it never closes a payer-controlled state.

Close the migration with a practical checklist

Confirm official domains and bookmarks, account ownership, multifactor and recovery setup, delegated access, inactive-user removal, recipient permissions, profile review, clinician attestation, exports, payer-specific workflows, training, help-desk language, and evidence retention. Test one real administrative workflow without changing payer or credentialing status. Keep former-name aliases until searches, audits, and open applications no longer depend on them.

Ask payers which workflow they use

Use the brand change as a revalidation trigger. For every payer, confirm whether it consumes Provider Data Portal data, requires a separate application or supplement, controls recipient authorization, uses a roster, and assigns its own credentialing and participation dates. Record the payer's answer and checked date without changing the payer's authority.

Related resources

Sources