An Implementation Data Segment Note
(IK3)
is created when an error is encountered in a data segment in a
transaction set of the subject document. This data segment is
not present in the acknowledgment if no error is found in any data
segment of the transaction set.
POSITION | ELEMENT ID | DESCRIPTION | CONSTRUCT INFO |
01 | 721 | Segment ID Code | The identifier of the data segment that has the error is assigned here. |
02 | 719 | Segment Position in Transaction Set | The position in the transaction set of the data segment that is in error. |
03 | 447 | Loop Identifier Code | The loop ID of the segment group that the data segment belongs to. |
04 | 620 | Implementation Segment Syntax Error Code | Syntax error code that has been translated from the standard error code of the data segment error. |
CTX. If the error is generated as a result of a
condition in a semantic rule not met, then the Context (CTX)
is created as follows:
POSITION | ELEMENT ID | DESCRIPTION | CONSTRUCT INFO |
01 | C998 | Context Identification | By default, this is empty.
NOTE: For HIPAA specifications, the SEF file is modified to fill the context information here as required by HIPAA. |
02 | 721 | Segment ID Code | The identifier of the data segment in error is assigned here. |
03 | 719 | Segment Position in Transaction Set | The position in the transaction set of the data segment in error is assigned here. The transaction set header is position 1. |
04 | 447 | Loop Identifier Code | The identifier of the data segment, that triggers the start of a loop and where the data element in error belongs to, is assigned here. |
05 | C030 | Position in Segment | Not applicable in IK3. |
06 | C999 | Reference in Segment | By default, this is empty.
NOTE: For HIPAA specifications, the SEF file is modified to fill the context information here as required by HIPAA. |
The example below shows where the AK2 data segment populates its data from the ST data segment.
See Also: