999 Implementation Acknowledgment (X231)
X12 HIPAA · X12 005010X231
X12 HIPAA’s published 999 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
11 of 11 segments
HEADING
ST
Transaction Set Header
- When acknowledging a healthcare implementation guide (TR3) based transaction, only a single transaction set 999 can be used. When acknowledging a healthcare implementation guide (TR3) based transaction, the transaction set 997 must not be used.
pos 0100
Optional
max —
AK1
Functional Group Response Header
pos 0200
Required
max —
2000 LoopTransaction Set Response Header Loop
AK2
Transaction Set Response Header
- Required when an error is present in a transaction set contained in the functional group to which this 999 transaction set is responding. If not required by this implementation guide, may be provided at the sender's discretion but cannot be required by the receiver.
- While it is not required that an AK2 loop be included for each transaction set received, it is required that an AK2 loop be included for each transaction set that contains an error. When AK2 loops are included in this transaction set, they must be in the same order as received in the functional group to which this 999 is responding.
pos 0300
Required
max —
2100 LoopError Identification Loop
IK3
Error Identification
- Required when an error is present in the transaction set identified in this AK2 loop and the location of the data segment containing the error can be identified by the submitter of this 999. If not required by this implementation guideline, do not send.
pos 0400
Required
max —
CTX
Segment Contextvariant 1 of 2
- Required when the error identified in this IK3 loop was triggered by a situational requirement of the implementation guide and the error occurs at the segment level. If not required by this implementation guide, do not send.
- The CTX segment is used to identify the data that triggered the situational requirement.
pos 0500
Optional
max 9
CTX
Business Unit Identifiervariant 2 of 2
- Required when the error reported in this IK3 loop is within a business unit and the business unit identifier is known by the submitter of the 999. If not required by this implementation guide, do not send.
- Valid values for the business unit identifier are:
TRN02 269 business unit identifier
TRN02 270 business unit identifier
TRN02 271 business unit identifier
NM109 274 business unit identifier
PATIENT NAME NM109 275 business unit identifier
TRN02 276 business unit identifier
TRN02 277 business unit identifier
SUBSCRIBER NAME NM109 278 business unit identifier
ENT01 820 business unit identifier
SUBSCRIBER NUMBER REF02 834 business unit identifier
TRN02 835 business unit identifier
CLM01 837 business unit identifier
pos 0500
Optional
max —
2110 LoopImplementation Data Element Note Loop
IK4
Implementation Data Element Note
- Required when the error in the segment described in the IK3 segment applies to a data element and the location of the data element containing the error can be identified by the submitter of the 999. If not required by this implementation guideline, do not send.
pos 0600
Required
max —
CTX
Element Context
- Required when the error identified in this IK4 loop was triggered by a situational requirement of the implementation guide and the error occurs at the element level. If not required by this implementation guide, do not send.
- The CTX segment is used to identify the data that triggered the situational requirement.
pos 0700
Optional
max 10
IK5
Transaction Set Response Trailer
pos 0800
Required
max —
AK9
Functional Group Response Trailer
pos 0900
Required
max —
SE
Transaction Set Trailer
pos 1000
Optional
max —
Validate a 999
Paste or upload a document and check it against X12 HIPAA’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on X12 HIPAA’s 999 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with X12 HIPAA, and keeps the spec current as it changes.