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.
The same member, as five systems hold her today
| System | Its ID | Name as held | Date of birth | Address |
|---|---|---|---|---|
| Medicare Advantage core | M100483922 | Maria L. Gonzalez | Mar 14, 1958 | 12 Elm St, Fresno |
| Medicaid core | 7731-0442-9 | Maria Gonzalez-Ruiz (differs from the member profile) | Mar 14, 1958 | 12 Elm St, Fresno |
| Pharmacy benefit manager | 88200417 | MARIA GONZALES (differs from the member profile) | Mar 14, 1958 | 40 Oak Ave, Fresno (differs from the member profile) |
| Care management | CM-55209 | Maria Gonzalez | Not held (differs from the member profile) | 12 Elm St, Fresno |
| Member services CRM | 0031-A9F2 | Maria L Gonzales (differs from the member profile) | Mar 14, 1958 | 12 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.
How Gaine decides it is the same member, and what a link makes possible →
Where member records fall out of step
Linking members across systems
Core administration, the pharmacy benefit manager, care management and the CRM each hold the same member under a different ID and a slightly different name. Gaine links those records into one member profile. Each system keeps its own ID.
Explore furtherAligning coverage dates
A state can end a member’s coverage months after the fact. Gaine sends every system the same end date and lists the claims paid after it, for your team to review.
Explore furtherReconciling 834s and rosters
Enrollment changes arrive as 834s and in many other formats. Gaine checks each change against the member profile and sends each system only what it needs. Core administration still decides eligibility.
Explore further
No system is renumbered. Gaine holds the cross-reference.
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
- HealthRules Payer
- Facets
- QNXT
- EZ-CAP
- Pharmacy benefit manager
- Care management
- Member services CRM
- Enterprise data warehouse
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.
Direct API connectorbuilt by Gaine
Core administration- HealthRules Payer
- Facets
- QNXT
- EZ-CAP
Reconciled change filethrough your own change control
Downstream systems- Pharmacy benefit manager
- Enterprise data warehouse
Event notificationfor systems that subscribe
Downstream systems- Care management
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.
Proof
Linkage at payer scale
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.