Skip to content

Member enrollment for health plans

One member, linked across every member system.

The same member sits in core administration, PBM, care management and CRM, each under a different ID and with a slightly different name and address.

Gaine HDMP links those records into one member profile, then keeps each member’s coverage dates the same in every system. No system is renumbered, and core administration stays your system of record for eligibility.

Request a demoBring two member extracts

The same member, as five systems hold her today

What five systems hold for the same member
SystemIts IDName as heldDate of birthAddress
Medicare Advantage coreM100483922Maria L. GonzalezMar 14, 195812 Elm St, Fresno
Medicaid core7731-0442-9Maria Gonzalez-Ruiz (differs from the member profile)Mar 14, 195812 Elm St, Fresno
Pharmacy benefit manager88200417MARIA GONZALES (differs from the member profile)Mar 14, 195840 Oak Ave, Fresno (differs from the member profile)
Care managementCM-55209Maria GonzalezNot held (differs from the member profile)12 Elm St, Fresno
Member services CRM0031-A9F2Maria L Gonzales (differs from the member profile)Mar 14, 195812 Elm St, Fresno

Matched by rules your team sets. Records the rules cannot settle go to a steward.

One member profile

Maria L. Gonzalez · born Mar 14, 1958 · 12 Elm St, Fresno

Five system IDs cross-referenced, each with the date it became valid. Values that differ are kept, not deleted.

Shaded: differs from the member profile, or not held. Illustrative: an invented member. Each system keeps its own record and its own ID.

How Gaine decides it is the same member, and what a link makes possible →

From every enrollment source to every system

Enrollment sources

  • EDI 834taken directly, or from your EDI gateway system
  • Custom member rostersfrom employer groups and BPO partners
  • Government and exchange filesstate Medicaid intermediaries, exchange platforms, and CMS monthly membership and transaction reply reports
  • Your own systemsold and new core administration, and the member services CRM

Gaine HDMP

Checks each change against the linked member profile

Systems Gaine keeps in step

Core administration
  • HealthRules Payer
  • Facets
  • QNXT
  • EZ-CAP
by direct API connector
Downstream
  • Pharmacy benefit manager
  • Care management
  • Member services CRM
  • Enterprise data warehouse
each by its own route: see the routes

See the full list of integrations →

How changes reach your systems

Each system takes its changes by the route its owner chooses, on its own cadence.

Gaine HDMP

One linked member. Every change carries its source, rule and date.

  1. Direct API connectorbuilt by Gaine

    Core administration
    • HealthRules Payer
    • Facets
    • QNXT
    • EZ-CAP
  2. Reconciled change filethrough your own change control

    Downstream systems
    • Pharmacy benefit manager
    • Enterprise data warehouse
  3. Event notificationfor systems that subscribe

    Downstream systems
    • Care management
  4. Application APIwhere the system’s owner allows it

    Downstream systems
    • Member services CRM

Illustrative pairing. Apart from the direct connectors, each system can use any route, and different systems can use different ones. Core administration remains your system of record for eligibility.

Where enrollment meets provider data

A member’s PCP selection has its own dates, and so does the provider’s place in the network. Gaine checks one against the other on the same date, so a member is not left assigned to a provider who has left the network or moved location.

How Gaine keeps network participation by date →

Proof

Linkage at payer scale

140M+Source-level entity records managed
120M+Mastered entity records
134Production domains, including client extensions to the model

One payer environment, May 2026, all domains. Client not identified.

Regional payer: member enrollment

EDI 834 and multiple custom member roster formats, absorbed through the gateway under strict data-quality audit. In place for open enrollment.

1M+ members · ACA and Medicare · 1,200 hours over 6 months

Further reading

Questions

What is member enrollment data management for a health plan?

It starts with knowing which records are the same member. Gaine HDMP links each member’s records across core administration, pharmacy, care management, member services and the warehouse into one member profile. Then it takes every 834, roster and CMS report and sends each system only the change it needs, with its dates, so they all hold the same coverage for the same dates.

How does Gaine decide two records are the same member?

The same way it matches providers: deterministically where systems share an identifier, and probabilistically but explainably where they do not. Your team sets the rules. Every match records the rule that made it and its score, and records the rules cannot settle go to a steward.

Is a link the same as a merge?

Each system keeps its own record and its own ID. Gaine cross-references them to one member profile, which holds the surviving value for each attribute; the losing values are kept. Nothing is renumbered or deleted in your systems.

What happens if two members are merged by mistake?

A wrong merge can be fully undone. Gaine’s unmerge puts everything back to its original state: both members, their records and their cross-references return as they were before the merge, and every system that took the merged record is told.

Who runs it after go-live?

Your team. Clear matches merge automatically under rules your team defines; stewards work the exceptions, not the routine flow. Help from Gaine or your systems integrator is available if you want it; neither is required.

See it on your own data.

Bring member extracts from two systems that should agree. We will show you the members they hold differently, and how and why Gaine would link each one.

Request a demo