Obtain the applicable X12 278 Health Care Services Review — Request and Response implementation guide from x12.org; note that X12 278 covers both the request (278-13) and response (278-11) in the same transaction set.
Review the transaction set structure: an ISA/GS interchange and group envelope, followed by the ST-SE transaction set wrapper, then the hierarchical level (HL) structure organizing payer, subscriber, dependent, and service information into loops.
Study Loop 2000A (payer information), 2000B (subscriber), 2000C (dependent if applicable), 2000D (service provider), 2000E (facility if applicable), and 2000F (services requested) to understand the hierarchical parent-child relationships via HL04 (parent HL ID).
Review the UM (health care services review information) segment at Loop 2000F, which specifies the request category code (UM01), certification type (UM02), service type (UM03), and level of service (UM06).
Review the 278 response structure: HCR (health care services review information) segment in the response returns the action code (A1 certified, A3 not certified, A4 pended), and TR3 (trace number) for tracking.
Map denial codes and pend codes from HCR01 and associated message text segments to your system's authorization status model and implement handling for each action code category.
Known gotchas
X12 278 uses a hierarchical loop structure with HL segments rather than repeating flat segments — the parent HL number must be correctly set in each child HL04 field; an incorrect parent reference produces an invalid transaction that many payers will reject without explanation.
The 278 request (certification request) and 278 response (certification response) are different transaction directions but share the same transaction set identifier (278) — intermediaries must correctly distinguish request from response to route transactions.
X12 documents are copyright X12; the implementation guides are only legally accessible to X12 members or licensed purchasers — implementers should not rely on third-party summaries alone for compliance-critical mappings.
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