Member enrollment for health plans
834 in. Reconciled change out.
Enrollment arrives as EDI 834s and custom rosters from exchanges, state Medicaid intermediaries, BPO partners and employer groups. Gaine HDMP absorbs each file, checks it against the member record and what core administration holds, and sends each system the reconciled change through the route that system allows.
Where Gaine sits
| Stage | What happens | Who sets it |
|---|---|---|
| Sources | EDI 834s, directly or from your EDI gateway system. Custom rosters, state Medicaid and exchange files, and CMS monthly membership and transaction reply reports. | Your trading partners |
| Intake | Each file format is mapped once. Every file is then checked under data-quality audit. | Gaine or your systems integrator, during implementation |
| Match | Clear matches merge automatically. The rest go to a steward queue. | Rules your team defines, attribute by attribute |
| Member record | Coverage spans, relationships and every system ID, with the source of each value. | Gaine HDMP |
| Routes out | Direct API connectors for HealthRules Payer, Facets, QNXT and EZ-CAP. Change files, event notifications or a direct write to the application API for everything else. | Each system’s owner applies the change |
| Core administration | Stays your system of record for eligibility. Gaine does not replace it or your enrollment workflow. | |
Whether the 834 comes to Gaine directly or from your EDI gateway system, the process is the same.
Who configures what
- Match and survivorship rules: defined by your team, attribute by attribute, with Gaine or your systems integrator during implementation.
- Model extensions: added for your plan’s own fields and domains without changing the core model.
- Full replacement files: compared with the member record if you choose. It is an option, because a member missing from a file is not always a termed member.
- The route each system takes: chosen system by system, and changed without touching the others.
Proof
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
How changes reach your systems
Gaine has built direct API connectors for HealthRules Payer, Facets, QNXT and EZ-CAP. Every other system, such as the pharmacy benefit manager, care management, the member services CRM or the warehouse, takes one of three routes:
- reconciled change files through your own change control;
- event notifications, for systems that subscribe;
- Gaine writes directly to the application API.
Each system can use a different route, on its own cadence. Every change carries the source, the rule and the date behind it, and core administration remains your system of record for eligibility.
Enrollment sources
- EDI 834: taken directly, or from your EDI gateway system.
- Custom member rosters: from employer groups and BPO partners.
- Government and exchange files: state Medicaid intermediaries, exchange platforms, and CMS monthly membership and transaction reply reports.
- Your own systems: old and new core administration, and the member services CRM.
Systems Aligned
- Core administration: HealthRules Payer, Facets, QNXT, EZ-CAP (direct API connectors).
- Downstream: pharmacy benefit manager, care management, member services CRM and the enterprise data warehouse, each by its own route.
Questions
Does Gaine take the 834 directly, or from our EDI gateway?
Either. Gaine can take the 834 directly or from your EDI gateway system, and the process is the same.
Who writes the match rules?
Your team, attribute by attribute, with Gaine or your systems integrator during implementation. What the rules cannot settle goes to a steward queue.
Which systems does Gaine connect to directly?
HealthRules Payer, Facets, QNXT and EZ-CAP, through built connectors. Every other system through change files, event notifications or its application API.
Does Gaine take CMS enrollment files?
Yes. CMS’s monthly membership and transaction reply reports are inputs, reconciled against the member record like any other source.
More on member enrollment
Coverage by date
A state 834 ends a member’s coverage two months back. Gaine holds coverage as effective-dated spans, so every system receives the same end date, and the claims paid since are listed.
Explore →One member, many IDs
A member changes product, line of business or core system and collects a new ID each time. Gaine links every ID to one member, so their history does not split.
Explore →