Skip to content

The platform

The golden record was the first step.

Our founders built the first enterprise MDM platform. In 2010 they started Gaine to solve the next step in data integration: enabling systems to align on their own terms without losing the benefits of integration.

In 2001 they released the first enterprise master data management platform. It became the leading MDM product worldwide, and much of the market still runs on its core. It cleansed, matched and merged, and gave enterprises a set of “golden records”. That work still matters, but it falls short of enabling data interoperability across a complex enterprise. Gaine was created to complete this journey, building on a quarter century of learning.

We chose US healthcare because the need is the greatest, and the rewards surpass financial success: we are creating a positive impact in the lives of real people desperate for a better healthcare system.

A trusted record is the foundation. The ability to coordinate this across stakeholders creates the value.

Gaine HDMP is an operational health data management platform. It resolves every healthcare entity — patients, providers, organizations, networks, contracts, products — against a healthcare ontology refined over more than fifteen years, then keeps the systems that run your operations aligned with the result.

Every system believes something different.

Without Gaine HDMP

  1. AM

    A provider updates their practice location in the provider portal of the payer.

  2. Noon

    The credentialing system receives an update from the portal with details of the new service location and queues the change for review.

  3. PM

    A claim arrives from the provider at the new location and it pends in core admin because of a location mismatch.

  4. Late afternoon

    Member services takes a call from a member looking for an in-network provider. The agent checks the provider directory and sends them to the provider’s old location.

OutcomeEvery system did its job, yet two failures occurred.

The same events, with Gaine HDMP underneath

  1. AM

    Client: Provider portal

    The provider changes their service location in the provider portal application. The portal uses real-time API integration to connect to HDMP and make the location change.

    Gaine HDMP:

    Provider portal to HDMP

    The new practice location is added to the provider’s profile in Gaine HDMP, along with the source and timestamp of the change.

  2. No client activity

    Gaine HDMP:

    Gaine HDMP internal

    Gaine HDMP understands via the ontology that unless a location change is confirmed by an update from the credentialing system, the new location is not yet authorized. As HDMP does not yet have the confirmation from credentialing, the new location is on the profile, but marked “in process”.

  3. PM

    Client: Claim pended

    A claim arrives from the provider at the new location and it pends in core admin because of a location mismatch.

    No HDMP activity

  4. Late afternoon

    Client: Member services

    Member services takes a call from a member looking for an in-network provider. Member services CRM queries HDMP via its API to check the status of a provider record before they make a referral. HDMP shows the pending service location change and the member services rep avoids recommending this provider to the member.

    Gaine HDMP:

    HDMP from Member services CRM

    Returns the provider along with the service location change with a status of “in process”.

  5. Evening

    Client: Daily claims update

    Claims are loaded into the data lake by the client’s ETL processes where they are immediately accessible to HDMP via a data share.

    Gaine HDMP:

    Claims to HDMP to Daily recon report

    HDMP processes all new and updated claims each evening after the claims update. The pended claim is matched to the provider (and member, service location, product and billing org). HDMP knows that the core admin still has the old service location, knows about the pending location change from the portal, and uses business rules to classify the status of the pended claim in a daily claims reconciliation report.

OutcomeWith Gaine HDMP, everyone is kept informed in a workflow that works for them.

Illustrative. Each system connects the way it allows, so how far each one aligns differs.

Gaine keeps a picture of every system.

It knows what each of your systems holds, field by field, and when it last changed. That picture is what lets Gaine send each one only what it needs, explain why, and see whether it was taken.

Each change arrives with its evidence, by the route that system already uses.

Then Gaine reads the result.

  1. 123System A holds a value of 123
  2. 456Gaine suggests a value of 456, with its evidence
  3. ?Next time Gaine sees System A’s data, it knows whether the change was taken

See the three outcomes →

More than 500 million transactions a year run through this, in real time.

Built for healthcare, and nothing else.

Was this provider in that network on the date of service?

It sounds like a lookup. It is four mastered things (a practitioner, a location, a network and a contract) joined by relationships that each start and end on their own dates.

A general-purpose MDM can model that once someone builds it, and keeps building it. Gaine’s ontology arrived with it. Yours to adopt or extend.

Data elements
3,500+
Mastered relationships
500+
Domains
28
Years refined in healthcare
15+

Gaine is an AND, not an OR.

  • Your existing EMPI or master data management

    stays the master of identity. Gaine takes its identifiers and masters the data around them.

  • Your operational systems

    keep running the work, and each team continues to make independent decisions on what updates to accept.

  • Your enterprise data warehouse or lakehouse

    keeps the analysis. Gaine publishes governed records to it, one way, as they change.

40+ systems on our integrations list, and an open integration layer for the ones that aren’t. See the list →

Proven at scale.

  • Statewide provider universe

    Organizations, affiliations and providers from 85 payers.

  • National and regional payers

    Provider and organization data across multiple plans.

  • Three top-20 life sciences organizations

    Patient mastering extended to consent and preference, for patients and providers.

Records mastered
2.7B+
IDC MarketScape: U.S. Provider Data Management for Payers 2025–2026
Leader
Patient consents under management
50M+

Clients are not named, due to confidentiality agreements.

See it on your own data.

Bring an extract from two of your systems. We will show you where they disagree, what Gaine would send each one, and why.

Request a demo

Yours if you leave. The identifiers, the crosswalk, the policies and the runbook belong to you.