|
|
| MESSAGE/PACKAGE RESPONSE |
 |
|
To identify a message or package in the subject interchange, and to indicate that message's or package's acknowledgement or rejection (action taken), and to identify any error related to the UNH, UNT, UNO, and UNP segments. It can also identify errors related to the USA, USC, USD, USH, USR, UST, or USU security segments when they appear at the message or package level.
Dependency Notes:
1. D1(010,070) One and only one
2. D2(010,020) All or none
3. D2(070,080) All or none
4. D5(050,040) If first, then all
5. D5(060,050,040) If first, then all
6. D5(090,050,040,100) If first, then all
7. D5(100,090,050,040) If first, then all
Notes:
050 0135, may only contain the values UNH, UNT, UNO, UNP, USA, USC, USD, USH, USR, UST, or USU.
(090,100) This data element shall be present when reporting an error in a security segment. |
|
| Pos |
|
Tag |
Name |
S |
R |
Repr |
|
Notes |
| 010 |
|
|
| MESSAGE REFERENCE NUMBER |
| Unique message reference assigned by the sender. |
|
C |
1 |
an..14 |
|
1,2 |
| 020 |
|
|
| MESSAGE IDENTIFIER |
| Identification of the type, version, etc. of the message being interchanged. |
|
C |
1 |
|
|
2 |
| |
|
|
| Message type |
| Code identifying a type of message and assigned by its controlling agency. |
|
M |
1 |
an..6 |
|
|
| |
|
|
| Message version number |
| Version number of a message type. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Message release number |
| Release number within the current message version number. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Controlling agency, coded |
| Code identifying a controlling agency. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Association assigned code |
| Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message. |
|
C |
1 |
an..6 |
|
|
| |
|
|
| Code list directory version number |
| Version number of the code list directory. |
|
C |
1 |
an..6 |
|
|
| |
|
|
| Message type sub-function identification |
| Code identifying a sub-function of a message type. |
|
C |
1 |
an..6 |
|
|
| 030 |
|
|
| ACTION, CODED |
| A code indicating acknowledgement, or rejection (the action taken) of a subject interchange, or part of the subject interchange, or indication of interchange receipt. |
|
M |
1 |
an..3 |
|
|
| 040 |
|
|
| SYNTAX ERROR, CODED |
| A code indicating the error detected. |
|
C |
1 |
an..3 |
|
4,5,6,7 |
| 050 |
|
|
| SERVICE SEGMENT TAG, CODED |
| Code identifying a service segment. |
|
C |
1 |
an..3 |
|
4,5,6,7 |
| 060 |
|
|
| DATA ELEMENT IDENTIFICATION |
| Identification of the position for an erroneous data element. This can be the position of a stand-alone or composite data element in the definition of a segment or a component data element in the definition of a composite data element. |
|
C |
1 |
|
|
5 |
| |
|
|
| Erroneous data element position in segment |
| The numerical count position of the stand-alone or composite data element in error. The segment code and each following stand-alone or composite data element defined in the segment description shall cause the count to be incremented. The segment tag has position number 1. |
|
M |
1 |
n..3 |
|
|
| |
|
|
| Erroneous component data element position |
| The numerical count position of the component data element in error. Each component data element position defined in the composite data element description shall cause the count to be incremented. The count starts at 1. |
|
C |
1 |
n..3 |
|
|
| |
|
|
| Erroneous data element occurrence |
| The numerical occurrence of the repeating stand-alone or composite data element in error. Each occurrence (as indicated by the repetition separator) shall cause the count to be incremented. The count starts at 1. |
|
C |
1 |
n..6 |
|
|
| 070 |
|
|
| PACKAGE REFERENCE NUMBER |
| Unique package reference number assigned by the sender. |
|
C |
1 |
an..35 |
|
1,3 |
| 080 |
|
|
| REFERENCE IDENTIFICATION |
| Identification of the reference relating to the object. |
|
C |
99 |
|
|
3 |
| |
|
|
| Reference qualifier |
| Code giving specific meaning to a reference identification number. |
|
M |
1 |
an..3 |
|
|
| |
|
|
| Reference identification number |
| Reference number to identify a message, message group and/or interchange, which relates to the object. |
|
M |
1 |
an..35 |
|
|
| 090 |
|
|
| SECURITY REFERENCE NUMBER |
| Unique reference number assigned by the security originator to a pair of security header and security trailer groups. |
|
C |
1 |
an..14 |
|
6,7,9 |
| 100 |
|
|
| SECURITY SEGMENT POSITION |
| The numerical count position of a specific security segment that is within the actual received security header/trailer segment group pair, identified by its security reference number. The numbering starts with, and includes, the USH segment as segment number 1. To identify a security segment that contains an error, this is the numerical count position of that security segment. To report that a security segment is missing, this is the numerical count position of the last security segment that was processed before the position where the missing security segment was expected to be. A missing security segment group is denoted by identifying the first segment in the security segment group as missing. |
|
C |
1 |
n..6 |
|
6,7,9 |
