Stedi maintains this guide based on public documentation from X12 HIPAA. Contact X12 HIPAA for official EDI specifications. To report any errors in this guide, please contact us.
X12 999 Implementation Acknowledgment (X231)
—
Delimiters
- ~ Segment
- * Element
- > Component
- ^ Repetition
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
Transaction Set Header
Max use 1
Required
AK1
0200
Functional Group Response Header
Max use 1
Required
Transaction Set Response Header Loop
AK9
0900
Functional Group Response Trailer
Max use 1
Required
SE
1000
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA
Interchange Control Header
RequiredMax use 1
—
Example
Required
Identifier (ID)
—
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Required
Identifier (ID)
—
- 00
- No Security Information Present (No Meaningful Information in I04)
Required
Identifier (ID)
—
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Required
Identifier (ID)
Min 1Max 1
—
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Required
Identifier (ID)
Min 1Max 1
—
- I
- Information
- P
- Production Data
- T
- Test Data
GS
Functional Group Header
RequiredMax use 1
—
Example
Required
Identifier (ID)
—
- FA
- Functional or Implementation Acknowledgment Transaction Sets (997, 999)
Required
Identifier (ID)
Min 1Max 2
—
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Heading
ST
0100
Heading > ST
Transaction Set Header
RequiredMax use 1
—
Usage notes
—
Example
AK1
0200
Heading > AK1
Functional Group Response Header
RequiredMax use 1
—
Example
2000 Transaction Set Response Header Loop
OptionalMax >1
AK2
0300
Heading > Transaction Set Response Header Loop > AK2
Transaction Set Response Header
RequiredMax use 1
—
Usage notes
—
Example
2100 Error Identification Loop
OptionalMax >1
IK3
0400
Heading > Transaction Set Response Header Loop > Error Identification Loop > IK3
Error Identification
RequiredMax use 1
—
Usage notes
—
Example
Required
Identifier (ID)
—
- 1
- Unrecognized segment ID
- 2
- Unexpected segment
- 3
- Required Segment Missing
- 4
- Loop Occurs Over Maximum Times
- 5
- Segment Exceeds Maximum Use
- 6
- Segment Not in Defined Transaction Set
- 7
- Segment Not in Proper Sequence
- 8
- Segment Has Data Element Errors
- I4
- Implementation "Not Used" Segment Present
- I6
- Implementation Dependent Segment Missing
- I7
- Implementation Loop Occurs Under Minimum Times
- I8
- Implementation Segment Below Minimum Use
- I9
- Implementation Dependent "Not Used" Segment Present
CTX
0500
Heading > Transaction Set Response Header Loop > Error Identification Loop > CTX
Segment Context
OptionalMax use 9
—
Usage notes
—
Example
Variants (all may be used)
CTXBusiness Unit IdentifierRequiredMax use 10
Holds information to identify a context
OptionalMax use 1
Code indicating the relative position of the simple data element or composite data structure in error within a segment, count beginning with 1 for the position immediately following the segment ID; additionally indicating the relative position of a repeating structure in error, count beginning with 1 for the position immediately following the preceding element separator; additionally indicating the relative position of a component of a composite data structure in error, count beginning with 1 for the position following the preceding element or repetition separator
Usage notes
—
CTX
0500
Heading > Transaction Set Response Header Loop > Error Identification Loop > CTX
Business Unit Identifier
OptionalMax use 1
—
Usage notes
—
Example
Variants (all may be used)
CTXSegment Context2110 Implementation Data Element Note Loop
OptionalMax >1
IK4
0600
Heading > Transaction Set Response Header Loop > Error Identification Loop > Implementation Data Element Note Loop > IK4
Implementation Data Element Note
RequiredMax use 1
—
Usage notes
—
Example
RequiredMax use 1
Code indicating the relative position of the simple data element or composite data structure in error within a segment, count beginning with 1 for the position immediately following the segment ID; additionally indicating the relative position of a repeating structure in error, count beginning with 1 for the position immediately following the preceding element separator; additionally indicating the relative position of a component of a composite data structure in error, count beginning with 1 for the position following the preceding element or repetition separator
Required
Identifier (ID)
—
- 1
- Required Data Element Missing
- 2
- Conditional Required Data Element Missing
- 3
- Too Many Data Elements
- 4
- Data Element Too Short
- 5
- Data Element Too Long
- 6
- Invalid Character In Data Element
- 7
- Invalid Code Value
- 8
- Invalid Date
- 9
- Invalid Time
- 10
- Exclusion Condition Violated
- 12
- Too Many Repetitions
- 13
- Too Many Components
- I10
- Implementation "Not Used" Data Element Present
- I11
- Implementation Too Few Repetitions
- I12
- Implementation Pattern Match Failure
- I13
- Implementation Dependent "Not Used" Data Element Present
- I6
- Code Value Not Used in Implementation
- I9
- Implementation Dependent Data Element Missing
CTX
0700
Heading > Transaction Set Response Header Loop > Error Identification Loop > Implementation Data Element Note Loop > CTX
Element Context
OptionalMax use 10
—
Usage notes
—
Example
RequiredMax use 10
Holds information to identify a context
OptionalMax use 1
Code indicating the relative position of the simple data element or composite data structure in error within a segment, count beginning with 1 for the position immediately following the segment ID; additionally indicating the relative position of a repeating structure in error, count beginning with 1 for the position immediately following the preceding element separator; additionally indicating the relative position of a component of a composite data structure in error, count beginning with 1 for the position following the preceding element or repetition separator
Usage notes
—
2110 Implementation Data Element Note Loop end
2100 Error Identification Loop end
IK5
0800
Heading > Transaction Set Response Header Loop > IK5
Transaction Set Response Trailer
RequiredMax use 1
—
Example
Required
Identifier (ID)
—
- A
- Accepted
- E
- Accepted But Errors Were Noted—
- M
- Rejected, Message Authentication Code (MAC) Failed
- R
- Rejected—
- W
- Rejected, Assurance Failed Validity Tests
- X
- Rejected, Content After Decryption Could Not Be Analyzed
Optional
Identifier (ID)
—
- 1
- Transaction Set Not Supported
- 2
- Transaction Set Trailer Missing
- 3
- Transaction Set Control Number in Header and Trailer Do Not Match
- 4
- Number of Included Segments Does Not Match Actual Count
- 5
- One or More Segments in Error
- 6
- Missing or Invalid Transaction Set Identifier
- 7
- Missing or Invalid Transaction Set Control Number
- 8
- Authentication Key Name Unknown
- 9
- Encryption Key Name Unknown
- 10
- Requested Service (Authentication or Encrypted) Not Available
- 11
- Unknown Security Recipient
- 12
- Incorrect Message Length (Encryption Only)
- 13
- Message Authentication Code Failed
- 15
- Unknown Security Originator
- 16
- Syntax Error in Decrypted Text
- 17
- Security Not Supported
- 18
- Transaction Set not in Functional Group
- 19
- Invalid Transaction Set Implementation Convention Reference
- 23
- Transaction Set Control Number Not Unique within the Functional Group
- 24
- S3E Security End Segment Missing for S3S Security Start Segment
- 25
- S3S Security Start Segment Missing for S3E Security End Segment
- 26
- S4E Security End Segment Missing for S4S Security Start Segment
- 27
- S4S Security Start Segment Missing for S4E Security End Segment
- I5
- Implementation One or More Segments in Error
- I6
- Implementation Convention Not Supported
2000 Transaction Set Response Header Loop end
AK9
0900
Heading > AK9
Functional Group Response Trailer
RequiredMax use 1
—
Example
Required
Identifier (ID)
—
- A
- Accepted—
- E
- Accepted, But Errors Were Noted.—
- M
- Rejected, Message Authentication Code (MAC) Failed
- P
- Partially Accepted, At Least One Transaction Set Was Rejected
- R
- Rejected—
- W
- Rejected, Assurance Failed Validity Tests
- X
- Rejected, Content After Decryption Could Not Be Analyzed
Optional
Identifier (ID)
—
- 1
- Functional Group Not Supported
- 2
- Functional Group Version Not Supported
- 3
- Functional Group Trailer Missing
- 4
- Group Control Number in the Functional Group Header and Trailer Do Not Agree
- 5
- Number of Included Transaction Sets Does Not Match Actual Count
- 6
- Group Control Number Violates Syntax
- 10
- Authentication Key Name Unknown
- 11
- Encryption Key Name Unknown
- 12
- Requested Service (Authentication or Encryption) Not Available
- 13
- Unknown Security Recipient
- 14
- Unknown Security Originator
- 15
- Syntax Error in Decrypted Text
- 16
- Security Not Supported
- 17
- Incorrect Message Length (Encryption Only)
- 18
- Message Authentication Code Failed
- 19
- Functional Group Control Number not Unique within Interchange
- 23
- S3E Security End Segment Missing for S3S Security Start Segment
- 24
- S3S Security Start Segment Missing for S3E End Segment
- 25
- S4E Security End Segment Missing for S4S Security Start Segment
- 26
- S4S Security Start Segment Missing for S4E Security End Segment
SE
1000
Heading > SE
Transaction Set Trailer
RequiredMax use 1
—
Example
Heading end
GE
Functional Group Trailer
RequiredMax use 1
—
Example
IEA
Interchange Control Trailer
RequiredMax use 1
—
Example
EDI Samples
Example 1: Response to a Functional Group Containing Three 837s
ISA*00* *00* *ZZ*123456789012345*ZZ*123456789012346*080503*1705*^*00501*000010216*0*T*>~
GS*FA*1234567890*2345678901*20080503*1705*20213*X*005010X231~
ST*999*2870001*005010X231~
AK1*HC*17456*005010X222A2~
AK2*837*0001~
IK5*A~
AK2*837*0002~
IK3*CLM*22**8~
CTX*CLM01>123456789~
IK4*2*782*1~
IK5*R*5~
AK2*837*0003~
IK3*REF*57**3~
CTX*SITUATIONAL TRIGGER*CLM*43**5>3~
CTX*CLM01>987654321~
IK5*R*5~
AK9*P*3*3*1~
SE*16*2870001~
GE*1*20213~
IEA*1*000010216~
GS*FA*1234567890*2345678901*20080503*1705*20213*X*005010X231~
ST*999*2870001*005010X231~
AK1*HC*17456*005010X222A2~
AK2*837*0001~
IK5*A~
AK2*837*0002~
IK3*CLM*22**8~
CTX*CLM01>123456789~
IK4*2*782*1~
IK5*R*5~
AK2*837*0003~
IK3*REF*57**3~
CTX*SITUATIONAL TRIGGER*CLM*43**5>3~
CTX*CLM01>987654321~
IK5*R*5~
AK9*P*3*3*1~
SE*16*2870001~
GE*1*20213~
IEA*1*000010216~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.