CAQH becomes DataSpring—and buyers should separate the corporate name from the provider-data products they already use

One change creates several identity records

A corporate rebrand affects more than a masthead. Vendor master records, contracts, data-use terms, security reviews, API documentation, trust relationships, source labels, integration credentials, support channels, and internal training may still use the former name. Provider-facing instructions may continue to say CAQH because that is the name clinicians recognize for the portal and attestation workflow.

A mature provider-operations system should preserve aliases and effective dates rather than replacing every historical CAQH reference with DataSpring. The correct label depends on the date and object: organization, product, portal, dataset, contract, or source. Historical records need to remain intelligible to auditors and operators who saw the prior identity.

The product boundaries still matter

DataSpring's credentialing suite, provider data portal, data services, directory functions, and other offerings participate in different operating stages. A provider maintaining a portal profile is not the same as a health plan using credentialing services or a platform consuming provider data. Editorial and procurement records should name the specific offering and workflow.

The receiving organization remains accountable for its requirements and decisions. An attested profile can reduce repeated collection, while primary-source verification, committee review, delegated oversight, payer enrollment, contracting, and downstream activation may remain separate. A brand change does not collapse those stages.

What buyers should update

Inventory contracts, integrations, identity-provider configurations, support contacts, security records, data dictionaries, internal procedures, provider instructions, and downstream source labels. Decide where the current corporate name belongs and where a legacy product label remains necessary for users or historical clarity. Preserve both names in search and record matching during the transition.

Ask DataSpring and connected organizations to identify which legal entity, product, terms, API, and support path apply today. Confirm whether any endpoint, certificate, domain, data schema, authorization, or contractual notice changed. Do not assume a visible rebrand means the technical or legal relationship remained untouched.

How the publication will represent the transition

Credentialing Current uses DataSpring, powered by CAQH, as the organization identity and retains CAQH Provider Data Portal where it is the official product name. Older records will preserve CAQH as the organization name appropriate to their original date rather than being silently rewritten.

The change ledger will connect the rebrand to product profiles, comparisons, authority-style records, and future announcements. That approach keeps current navigation clear while preserving a truthful historical sequence.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Credentialing Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.