RFI Browser

Back  RFI # 53: Scope of TA1 Reporting

Formal vs. Informal Help Informal Formal

Submitter

Todd Cochrane

Description

The WEDI Acknowledgements Subworkgroup is requesting ASC X12 to provide a formal interpretation regarding the scope of the TA1 reporting. V00501 of the ASC X12 standard X12.5, Section 3.2.2 states in part: (emphasis added) An Interchange Acknowledgment segment (TA1) is used to report the receipt of the contents of one interchange control header and trailer envelope where that envelope surrounds one or more functional groups. This acknowledgment is transferred between the interchange receiver and sender as addressed in the interchange header. The TA1 reports the results of the syntactical analysis of the interchange control header and trailer. There is no acknowledgment for the TA1, thereby preventing an endless loop of acknowledgments. The flow of the original interchange and the corresponding acknowledgment are diagrammed in Figure 1. The TA1 reports the status of the interchange envelope only. It is not used to report the status of the functional groups and transaction sets in the interchange. Version 005010 of the ASC X12 Segment Directory includes the entry below for the TA1 along with the associated segment description. TA1 - Interchange Acknowledgment To report the status of processing a received interchange header and trailer or the non-delivery by a network provider Version 005010 of the ASC X12 Data Element Dictionary Segment Directory includes the entries below for data elements I17 and I18 used in the TA1 segment. I17 - Interchange Acknowledgment Code TYPE=ID MIN=1 MAX=1 Code indicating the status of the receipt of the interchange control structure CODE DEFINITION & EXPLANATION A The Transmitted Interchange Control Structure Header and Trailer Have Been Received and Have No Errors. E The Transmitted Interchange Control Structure Header and Trailer Have Been Received and Are Accepted But Errors Are Noted. This Means the Sender Must Not Resend This Data. R The Transmitted Interchange Control Structure Header and Trailer are Rejected Because of Errors. I18 - Interchange Note Code TYPE=ID MIN=3 MAX=3 Code specifying the error found processing the interchange control structure 024 Invalid Interchange Content (e.g., Invalid GS Segment) Given that X12.5 clearly specifies that the TA1 is scoped solely to reporting on the status of the Interchange envelope only clarification is being requested on Code 024 Invalid Interchange Content (e.g., Invalid GS Segment). Since the example included in the code definitions indicates that an Invalid GS segment could be invalid interchange content, what would constitute an invalid GS segment in the context of reporting that in a TA1? Further, how would the originator of the TA1 indicate what errors were detected in a GS segment. Additionally, other than the example of an invalid GS segment, what are other examples of Invalid Interchange Content? Lastly, since the TA1 scope is limited to the Interchange envelope only the inclusion of Code 024 would appear to be in conflict with the stated TA1 scope.

Response

Although Code 024 as defined ' Invalid Interchange Content (e.g., Invalid GS Segment)' appears to be outside the scope of the TA1, it is valid under the follow circumstances: 1. The GS segment has a missing control number, whereby the subsequent 997/999 acknowledgment cannot be generated. 2. The GS segment has an invalid control number, whereby the subsequent 997/999 acknowledgment cannot be generated. 3. The GS segment has a missing functional identifier code, whereby the subsequent 997/999 acknowledgment cannot be generated. 4. The GS segment has an invalid functional identifier code, whereby the subsequent 997/999 acknowledgment cannot be generated. 5. The GS segment is incomplete or missing, whereby a subsequent 997/999 acknowledgement would potentially reference an arbitrary group control number or cannot be generated. 6. The GE segment is incomplete or missing, whereby a subsequent 997/999 acknowledgement would potentially reference an arbitrary group control number or cannot be generated. In all of these circumstances the 997 or 999 acknowledgment cannot properly identify and report against a specific group (GS-GE). This situation requires the interchange to be acknowledged and keeps these errors within the published TA1 scope.

Recommendation

The official response to a formal RFI is a letter from the current ASC X12 chair. This website often displays a summary of the RFI. Click here to view a PDF of the letter for this RFI.

Further Discussion: Transaction Set 997 or Transaction Set 999 should be used to report syntactical errors in functional groups if doing so would not cause syntax violations in the Transaction Set 997 or Transaction Set 999. X12C will consider data maintenance to make the formal interpretation explicit in the standard with regards to the following: 997 Functional Acknowledgement 999 Implementation Acknowledgement TA1 Interchange Acknowledgement ARM The Acknowledgment Reference Model
Submission 1/1/2010
Status Date 1/1/2010
Status F - Final
Primary References
Document 5010