The EDI 999
transaction set is an Implementation Acknowledgement document, developed specifically to replace the 997 Functional Acknowledgement
document for use in healthcare. Both the 997 and 999 are used to confirm that a file was received. However, the 999 includes additional information about whether the received transaction had errors. This includes whether the transaction is in compliance with HIPAA requirements.
The 999 Acknowledgement may produce three results:
- Accepted (A)
- Rejected (R)
- Accepted with errors (E)
As a result, the 999 may acknowledge receipt of a transaction, such as a healthcare claim, but it does not necessarily mean that transaction will be processed. The 999 can also report on exactly what syntax issues caused the errors in the original transaction.
The 999 transaction set becomes the standard acknowledgement document for healthcare as of March, 2012, when version 5010 of the HIPAA EDI standards take effect. The exception to this is the use of a 277 Healthcare Status Notification
transaction, used specifically to confirm the receipt of a 276 Health Claim Status Request
Need support meeting HIPAA requirements? HIPAA EDI Compliance consultants at 1EDISource can work with you to ensure you are in full compliance with HIPAA 5010 standards. Contact 1EDISource
today to learn more.
ISA*00* *00* *12*4405197800 *01*999999999 *111219*1802*U*00401*000000001*0*T*:
This X12 Transaction Set contains the format and establishes the data contents of the Implementation Acknowledgment Transaction Set (999) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical and relational analysis of the electronically encoded documents, based upon a full or implemented subset of X12 transaction sets. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.