X12 999 acknowledgment error codes

EDI X12 999 implementation acknowledgment reports standard syntax errors, as well as implementation guide errors. The ASC X12 999 transaction set is designed to respond to one and only one functional group (i.e. GS/GE), but will respond to all transaction sets (i.e. ST/SE) within that functional group. EdiFabric AckMan supports 5010 compliant 999.

The X12 implementation acknowledgment reports the status of the processing of a functional group for HIPAA transactions. It follows almost the same rules as that of 997, however the structure and codes of the acknowledgment contents are different and follow the 999 rules. AckMan allows you to raise either 997 or 999 acknowledgments, but not both in the same time.

EdiFabric AckMan does not automatically generate CTX segments.

This topic lists the error codes used within the segments of an X12 999 acknowledgment. Each table indicates which error codes specified by the X12 specification are supported/unsupported in EdiFabric AckMan.

IK304 Error Codes

The following table lists the error codes used in the IK304 data element of the IK3 segment.

Error CodeDefinitionSupported?
1Unrecognized segment IDYes
2Unexpected segmentYes
3Mandatory segment missingYes
4Loop occurs over maximum timesYes
5Segment exceeds maximum useYes
6Segment not in defined transaction setYes
7Segment not in proper sequenceYes
8Segment has data element errorsYes

IK403 Error Codes

The following table lists the error codes used in the IK403 data element of the IK4 segment.

Error CodeDefinitionSupported?
1Mandatory data element missingYes
2Conditional required data element missingYes
3Too many data elementsYes
4Data element is too shortYes
5Data element is too longYes
6Invalid character in data elementYes
7Invalid code valueYes
8Invalid dateYes
9Invalid timeYes
10Exclusion condition violatedYes
12Too many repetitionsYes
13Too many componentsYes

IK501 Error Codes

The following table lists the error codes used in the IK501 data element of the IK5 segment.

Error CodeDefinitionSupported?
AAcceptedYes
EAccepted but errors were notedYes
MRejected, message authentication code (MAC) failedNo
PPartially accepted, at least one transaction set was rejectedYes
RRejectedYes
WRejected, assurance failed validity testsNo
XRejected, content after decryption could not be analyzedNo

IK502 through IK506 Error Codes

The following table lists the error codes used in the IK502 through IK506 data elements of the IK5 segment.

Error CodeDefinitionSupported?
1Transaction set not supportedYes
2Transaction set trailer missingYes
3Transaction set control number in header and trailer do not matchYes
4Number of included segments does not match actual countYes
5One or more segments in errorYes
6Missing or invalid transaction set identifierYes
7Missing or invalid transaction set control number (a duplicate transaction number may have occurred)Yes
8 through 27-No

AK901 Error Codes

The following table lists the error codes used in the AK901 data elements of the AK9 segment.

Error CodeDefinitionSupported?
AAcceptedYes
EAccepted, but errors were notedYes
MRejected, message authentication code (MAC) failedNo
PPartially accepted, at least one transaction set was rejectedYes
RRejectedYes
WRejected, assurance failed validity testsNo
XRejected, content after decryption could not be analyzedNo

AK905 through AK909 Error Codes

The following table lists the error codes used in the AK905 through AK909 data elements of the AK9 segment.

Error CodeDefinitionSupported?
1Functional group not supportedYes
2Functional group version not supportedYes
3Functional group trailer missingYes
4Group control number in the functional group header and trailer do not agreeYes
5Number of included transaction sets does not match actual countYes
6Group control number violates syntax (a duplicate group control number may have occurred)Yes
7 through 26-No