999 Implementation Acknowledgment (X231)
X12 HIPAA · X12 005010X231
La spécification 999 publiée par X12 HIPAA, présentée sous forme de guide interactif. Déployez n’importe quel segment pour voir ses éléments, types de données, longueurs et codes acceptés, puis validez votre propre document ci-dessous.
Spécification
11 segments sur 11
HEADING
ST
Transaction Set Header
- 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.
pos. 0100
Facultatif
max. —
AK1
Functional Group Response Header
pos. 0200
Obligatoire
max. —
Boucle 2000Transaction Set Response Header Loop
AK2
Transaction Set Response Header
- 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.
pos. 0300
Obligatoire
max. —
Boucle 2100Error Identification Loop
IK3
Error Identification
- 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.
pos. 0400
Obligatoire
max. —
CTX
Segment Contextvariante 1 de 2
- 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.
pos. 0500
Facultatif
max. 9
CTX
Business Unit Identifiervariante 2 de 2
- 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
pos. 0500
Facultatif
max. —
Boucle 2110Implementation Data Element Note Loop
IK4
Implementation Data Element Note
- 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.
pos. 0600
Obligatoire
max. —
CTX
Element Context
- 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.
pos. 0700
Facultatif
max. 10
IK5
Transaction Set Response Trailer
pos. 0800
Obligatoire
max. —
AK9
Functional Group Response Trailer
pos. 0900
Obligatoire
max. —
SE
Transaction Set Trailer
pos. 1000
Facultatif
max. —
Validez un 999
Collez ou téléversez un document et vérifiez-le par rapport aux règles publiées par X12 HIPAA : ordre et répétition des segments, éléments obligatoires, longueurs de champs, types de données et codes acceptés. Rien n’est conservé.
Passez en production sur le 999 de X12 HIPAA en quelques jours, pas en quelques mois
Weredi établit le schéma entre ce guide et votre ERP, mène le cycle de tests avec X12 HIPAA et maintient la spécification à jour au fil de ses changements.