Provider data management for health plans
Was this provider in that network on the date of service?
Provider data management, for a health plan, means every system gives the same answer to that question: credentialing, contracting, the directory, core administration and claims. Gaine HDMP masters the practitioner, the location, the network and the contract as separate records joined by relationships, each with its own effective dates. Then it sends each system only the change it needs, with the reason.
Request a demoHow a change reaches each system
Managing a network as a provider group? See provider organizations →
Four records, one answer
It sounds like a lookup. It is four mastered records (a practitioner, a location, a network and a contract) and the relationships between them, each starting and ending on its own date. Credentialing owns one part, contracting another, network management a third, and core administration pays claims against all of them. When they disagree, a claim pends, a member is sent to a provider who has left, or a directory audit finds the gap before you do.
What Gaine keeps, and what it sends
- Every provider record, mastered. Practitioners, groups, locations, networks, contracts, products and taxonomy, matched and merged under survivorship rules your team sets attribute by attribute. Losing values are kept, so anyone can see which value won and why.
- Effective dates on the relationship, not only the record. A practitioner can join a network at one location in March and leave another in June. Both are true, and both are kept.
- A picture of each system. Gaine knows what credentialing, the directory and core administration each hold today, field by field.
- Only the difference, with the evidence. Each system receives the change it needs: which source supplied the value, which rule chose it, and when it changed. The system’s owner decides when to take it.
- Unmerge when a match is wrong. Both records and their cross-references come back, and every system that took the merged record is told.
One amendment, one date, every system
Without Gaine HDMP
- March 10
Contracting signs an amendment. From April 1, the group’s Elm Street location joins the plan’s Medicare Advantage network. Its Main Street location stays commercial only.
- April 1
Core administration still holds the old participation. Claims for Medicare Advantage members seen at Elm Street pend as out of network.
- April 20
The directory adds the group for Medicare Advantage, listing every practitioner in it, including two who only work at Main Street.
- May
Claims are reprocessed by hand, and the group files a dispute.
OutcomeThe contract was right. Every system that depended on it held a different version of when and where it applied.
The same amendment, with Gaine HDMP underneath
- March 10
The amendment reaches Gaine from contracting as a new network relationship for the Elm Street location, effective April 1. Practitioners join it through their affiliation with that location, not group-wide.
- March 11
Gaine works out what each system must change:
- core administration receives a change file dated April 1, for its own change control;
- the directory receives listings for the practitioners who work at Elm Street, dated April 1;
- credentialing is told which practitioners now need Medicare Advantage credentialing.
- April 1 onward
Claims for Medicare Advantage members at Elm Street price in network from that date. Earlier dates of service keep the participation that applied then, because the old relationship was end-dated, not overwritten.
OutcomeOne amendment, one effective date, and each system told only what it needed.
Illustrative. Each system connects the way it allows, so how far each one aligns differs.
How changes reach your systems
Gaine has built direct API connectors for HealthRules Payer, Facets, QNXT, EZ-CAP and symplr. Every other system takes one of three routes:
- reconciled change files through your own change control;
- event notifications, for systems that subscribe;
- Gaine’s platform API, for applications that call it.
Each system can use a different route. Providers attest and update their information through a provider portal, and each update is reconciled with the rest of the record before it reaches the directory.
Proof
IDC MarketScape: U.S. Provider Data Management for Payers 2025–2026. Gaine named a Leader.
“Consider Gaine when payers want comprehensive, mature data management with an operational data layer that can distribute clean, harmonized data in real time to all of the organization’s systems in the way that they need to consume it.”
36%average improvement in provider network accuracy.
Figures as of September 2026.
Further reading
Reference sources
- Public sources: NPI and NPPES, CMS, state licensure boards, medical boards, the DEA.
- Through your own subscription: CAQH and LexisNexis.
Systems Gaine keeps aligned for payers
- Core administration: HealthRules Payer, Facets, QNXT, EZ-CAP (direct API connectors).
- Credentialing: symplr (direct API connector), MDStaff.
- Provider data exchange: Availity.
Questions
What does effective dating mean for network participation?
Each relationship (practitioner to location, location to network, network to contract) has its own start and end dates. So Gaine can answer for any date of service, not only today.
What happens to claims for dates before a network change?
They keep the participation that applied on their date of service. The earlier relationship is end-dated, not overwritten.
Can Gaine list every practitioner in a network at a location on a given date?
Yes, from the mastered relationships and their dates.
More on provider data management
Terminations and delegated rosters
A practitioner leaves a group in March, and your systems find out in June. Gaine reads every roster against the provider master, flags who has left, and sends each system the end date.
Explore →Directory accuracy
Your directory is only as accurate as the systems behind it. Gaine fixes provider data upstream, and every listed value can be traced to its source.
Explore →