New: Drop-in replacement for Change Healthcare APIs

EDI 999 X231A1 - Implementation Acknowledgment

Functional Group FA

X12C Communications and Controls Subcommittee

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.

What is an EDI 999?

An EDI 999 Implementation Acknowledgment serves as a response to healthcare-related EDI messages or groups of messages. Like the EDI 997 Functional Acknowledgment, it contains important information about the receipt of the upstream document (AK2 segment), and whether or not the receiver accepts or rejects the document as presented (IK5 and AK9 segments). It must be HIPAA 005010 complaint.

How is an EDI 999 used?

For example, Employer A sends Insurance Provider B an EDI 834 Benefit Enrollment and Maintenance to enroll a new employee into a healthcare benefits plan. Insurance Provider B responds with a 999 to confirm that the EDI 834 Benefit Enrollment and Maintenance was received with no errors.

Heading

1. 0100 · ST · Transaction Set Header · Max 1 · Mandatory

   To indicate the start of a transaction set and to assign a control number

   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.

2. 0200 · AK1 · Functional Group Response Header · Max 1 · Mandatory

   To start acknowledgment of a functional group

3. 2000 Loop Optional Repeat >1

   1. 0300 · AK2 · Transaction Set Response Header · Max 1 · Mandatory

      To start acknowledgment of a single transaction set

      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.

   2. 2100 Loop Optional Repeat >1

      1. 0400 · IK3 · Error Identification · Max 1 · Mandatory

         To report implementation errors in a data segment and identify the location of the data segment

         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.

      2. 0500 · CTX · Segment Context · Max 9 · Optional

         Describes an event context in terms of the application or implementation contexts in force at the time the event occurred and the position in the EDI stream at which that context was activated

         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.

      3. 0500 · CTX · Business Unit Identifier · Max 1 · Optional

         Describes an event context in terms of the application or implementation contexts in force at the time the event occurred and the position in the EDI stream at which that context was activated

         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

      4. 2110 Loop Optional Repeat >1

         1. 0600 · IK4 · Implementation Data Element Note · Max 1 · Mandatory

            To report implementation errors in a data element or composite data structure and identify the location of the data element

            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.

         2. 0700 · CTX · Element Context · Max 10 · Optional

            Describes an event context in terms of the application or implementation contexts in force at the time the event occurred and the position in the EDI stream at which that context was activated

            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.

   3. 0800 · IK5 · Transaction Set Response Trailer · Max 1 · Mandatory

      To acknowledge acceptance or rejection and report implementation errors in a transaction set

4. 0900 · AK9 · Functional Group Response Trailer · Max 1 · Mandatory

   To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group

5. 1000 · SE · Transaction Set Trailer · Max 1 · Mandatory

   To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)