Receive the X12 999 (Implementation Acknowledgment) from the clearinghouse or trading partner in response to your 837 or other EDI submission; the 999 supersedes the older 997 acknowledgment for 005010 transactions
Parse the ISA and GS envelope to identify which interchange and functional group the 999 is acknowledging by matching ISA-13 and GS-6 from the 999 to the control numbers in your original submission
Locate the AK1 segment which identifies the functional group being acknowledged; AK1-1 is the functional identifier code (HC for healthcare claim) and AK1-2 is the group control number matching GS-6 of the original submission
For each transaction set in the group, find the AK2 loop which contains the AK2 segment (transaction set reference) and the AK5 segment (transaction set response); AK5-1 indicates acceptance (A), acceptance with errors (E), or rejection (R)
For rejected transaction sets, parse the AK3 segment (data segment note) and AK4 segment (data element note) within the AK2 loop to identify the specific segment, element position, and X12 error code explaining the rejection
Update your submission tracking system: accepted transactions can be considered delivered to the clearinghouse; rejected transactions must be corrected and resubmitted; track each transaction set independently as a group may have mixed acceptance/rejection results
Known gotchas
A 999 acceptance from the clearinghouse confirms only that the EDI structure was valid — it does not indicate payer adjudication; a structurally accepted 837 can still result in a claim denial during payer processing
The X12 error codes in AK4-3 reference X12 standard error code tables; translate these codes using the X12 error code reference rather than guessing meanings — codes like 1 (required data element missing) and 8 (conditionally required data element missing) have distinct meanings
Some clearinghouses return a 999 that acknowledges at the interchange level only (AK1/AK9 without AK2 loops) rather than at the transaction set level; in this case you cannot determine individual transaction acceptance status from the 999 alone
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