Build an X12 834 benefit enrollment transaction for a new hire group enrollment event and handle the subscriber and dependent demographic and coverage loops correctly
Open the 834 with the BGN segment carrying the transaction set purpose code of 00 for original or 15 for change, the original file creation date and time, the sender's file identifier, and the transmission type code indicating full file or change only to prevent the carrier from processing the transaction as a duplicate
Build the 1000A sponsor name loop using N1*P5 to identify the employer sponsor and the 1000B payer loop using N1*IN to identify the insurance carrier; include REF segments with the plan-specific group contract number and the master policy number required by the carrier's implementation guide
For each subscriber, create a 2000 INS loop with INS01 set to Y for the subscriber, INS02 carrying the relationship code, INS03 carrying the maintenance type code such as 021 for new enrollment, and INS04 carrying the maintenance reason code appropriate for the enrollment event
Populate the 2100A member name NM1 loop and the 2100B incorrect member name loop only if a name correction is being processed; populate the 2300 health coverage loop with HD segments specifying the coverage type code, coverage level, and plan-specific benefit description code
For each dependent of the subscriber, build a 2000 INS loop with INS01 set to N and a relationship code in INS02 identifying spouse or child relationship; share the same 2300 health coverage HD segment coverage type as the subscriber if they are enrolled in the same coverage tier
Close each subscriber's enrollment record by populating the DTP segments in the 2300 loop with the benefit begin date in DTP03; verify that the benefit begin date matches the eligibility date agreed upon during carrier enrollment to prevent a gap in coverage from the carrier's effectuation process
Known gotchas
The 834 maintenance type code 001 cancellation paired with a 021 new enrollment in the same file transmits a termination followed by a re-enrollment; carriers may process these as a gap-creating sequence rather than a seamless change, so separate files or carrier-specific workaround codes may be needed for mid-year benefit changes
Some carriers require the INS08 employment status code and INS09 student status code to be populated for COBRA eligibility determination; omitting these elements for employee enrollments causes the carrier to default the employment status incorrectly, leading to premature termination notices when employment status rules are applied
834 files transmitted outside the carrier's effectuation window for a group open enrollment period may not be processed on the effective date even if the file is syntactically correct; confirm the carrier's file submission deadline separately from the standard EDI enrollment process
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp