Submit benefits enrollment data for new hires to a carrier using the ANSI X12 834 EDI transaction set via a clearinghouse
domain: x12.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Map employee and dependent enrollment data from your HRIS to the 834 transaction set structure: ISA/GS envelope, ST/SE transaction, Loop 2000 member-level segments
Build the REF*0F subscriber identifier segment, INS benefit status code, and DTP enrollment date segments for each enrollee
Populate HD (Health Coverage) and DTP (Coverage Period) loops for each benefit plan type (medical, dental, vision)
Transmit the 834 file to the clearinghouse (e.g., Stedi, Availity, or directly to carrier) via SFTP or AS2 and capture the 999 functional acknowledgment
Parse the 999 AK2/IK3/IK4 segments to identify rejected transactions and resubmit corrected records within the carrier's acceptance window
Known gotchas
Each carrier implements their own 834 companion guide with required/optional segment variations that may deviate significantly from the base X12 standard
Dependent relationship codes and coverage type codes are not standardized across carriers; always obtain and follow the trading partner's companion guide
Full-file replacement vs. incremental change files have different ISA control structures; sending a full-file replacement by mistake can drop existing enrollments
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?