Member enrollment for health plans
Was this member covered on that date, in every system?
Enrollment is right only if it is right for the date. Gaine HDMP keeps each member’s coverage as effective-dated spans, reconciles every 834 and change against them, and sends each system only the change it needs, with its dates. Core administration stays your system of record for eligibility.
One retro term, four systems
On June 10 a state Medicaid 834 ends a member’s coverage retroactively, effective April 30. Ten days later, without Gaine, core administration has taken the end date and three other systems have not:
One member’s coverage on a timeline from January to July 2026, as it stands on June 20 without Gaine. A state Medicaid 834 received on June 10 ends the coverage retroactively on April 30. Core administration has applied the end date. The pharmacy benefit manager, the member services CRM and the PCP panel still show the member as covered from May 1 to June 20. On April 15 every system agrees the member was covered. On May 15 the member was not covered, but three systems still say they were.
One member’s coverage on June 20, without Gaine HDMP
With Gaine HDMP underneath, each of those systems receives the April 30 end date by its own route, and the claims paid after it are listed for your team.
What Gaine keeps for each member
- Coverage as effective-dated spans. The subscription and its coverage spans, with the dates each source gave and the one that applies.
- The reason for each change. The qualifying life event, the 834 transaction or the roster that brought it, kept with the change.
- Subscribers and dependents. Each relationship with its own dates, so a dependent’s coverage can end without the subscriber’s.
- PCP selection history. Each PCP selection with its active period, checked against the practitioner’s network participation on the same date.
- Claims paid against ended coverage. When a retro term arrives, Gaine lists the claims paid between the new end date and today.
- Full files, compared if you choose. When a group sends a full replacement file, Gaine can compare it with the member record. It is an option, because a member missing from a file is not always a termed member.
The same retro term, without and with Gaine
Without Gaine HDMP
- June 10
A state Medicaid 834 ends a member’s coverage retroactively, effective April 30.
- June 12
Core administration applies the term at its next eligibility load. Claims paid since May 1 were paid against coverage that had ended.
- June 20
The pharmacy benefit manager still shows coverage until its next monthly file. Member services sees an active member, and the PCP’s panel still lists them.
- July
The paid claims and the panel are found by hand, one system at a time.
OutcomeFour systems, four answers to “was this member covered on May 15?”
The same 834, with Gaine HDMP underneath
- June 10
The 834 reaches Gaine, directly or from your EDI gateway. It is matched to the member, and the coverage span ends April 30, with the 834 recorded as its source.
- June 10
Gaine works out what each system must change:
- core administration receives the ended span through its connector;
- the pharmacy benefit manager receives it in its next change file;
- member services receives an event notification for its CRM;
- the PCP selection’s active period ends April 30.
- June 10
Gaine lists the claims paid against the coverage after April 30, for your team to review.
OutcomeOne end date in every system, and a list of what was paid after it.
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 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.
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
Questions
What happens when an 834 and core administration disagree about an effective date?
Rules your team defines decide, attribute by attribute, and the reason is recorded. What the rules cannot settle goes to a steward queue.
Does a member missing from a full file mean a termination?
Not always. Comparing a full replacement file with the member record is an option you choose, because a missing record does not always mean a termed member.
What happens to claims paid after a retro term’s end date?
Gaine lists the claims paid against the coverage after its new end date. Your claims process decides what to do with them.
More on member enrollment
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 →834 in, change out
Enrollment arrives as 834s, custom rosters and CMS reports. Gaine reconciles each against the member record and sends every system its change, while core administration stays in charge of eligibility.
Explore →