Attribute | Purpose within 360X | Required (Source of Requirement) | Corresponding HL7 Field/Component/Subcomponent |
author | If supplied, MUST indicate the document's (order) author, which may be different from the message sender. For the order, this is the clinician who is requesting the referral. | >R2 (XDR and XDM for Direct Messaging) | Ordering Provider in ORC-12 |
classCode | Identifies the specific document type, in this case an HL7 V2 Order. See also typeCode which further refines the class definition and should not be ambiguous | R (360X) (R2 XDR and XDM for Direct Messaging) | Message Type in MSH-9.1 (OMG) |
confidentialityCode | Identifies the confidentiality defined for the order. Implementations SHOULD NOT use codes that reveal the specific trigger causes of confidentiality (e.g., ETH, HIV, PSY, SDV) | R2 (XDR and XDM for Direct Messaging) | Confidentiality Code in ORC-28 Implementations SHOULD constrain to values that do not reflect the cause of confidentiality such as: V Very restricted R Restricted U Usual control |
creationTime | Defines the creation time of the message (vs. the order) | R2 (XDR and XDM for Direct Messaging) | Date/Time of Message in MSH-7 |
entryUUID | The identifier used for referencing the Document Entry object within the metadata | R (XDR and XDM for Direct Messaging) | N/A
|
eventCodeList | This list of codes represents the main clinical acts which does not conflict with the class and type codes. In this case, extends the document type (classCode=OMG, type=O19) to define the specific service requested. | O (IHE XDR) | Universal Service Identifier in OBR-4, CWE_2.1 Where XDR classification scheme is name of coding system in CWE_2.3 |
formatCode | Globally unique identifier specifying the format of the document (referral request/order) to allow systems to determine if / how to process. For 360X can be formed from MSH-9 Message Type MSH-12 Version ID MSH-21 MessageProfileIdentifier | R (360X) | OMG^O19_2.5.1_360XReferralRequest |
healthcareFacilityTypeCode | See also practice setting type. This code represents the type of organizational setting of the clinical encounter during which the documented act occurred. Note that in context of 360X, this is the facility type of the Referral Request Initiator. | R2 (XDR and XDM for Direct) | Should be derived from / mapped to the information in ORC-21 through | 24 | 24 |
languageCode | Specifies the language of the document (order / referral request) | R2 (XDR and XDM for Direct) | Principal Language of Message in MSH-19 |
mimeType | The MIME type of the document | R (XDR and XDM for Direct Messaging) | x-application/hl7-v2+er7 |
patientId | See also sourcePatientID. patient ID MUST be the same as the patientID in the submission set (which, not does not include the sourcePatientID) and all document entries. Per IHE, is the ID as known to the referral request recipient / target document registry, if known. | R2 (360X) (R2 XDR and XDM for Direct Messaging) | The patientID in context of the message recipient (referral request recipient), if known, from the PID-3 list in the order. Referral request acceptance/responses will include a sourcePatientID (ID in context of referral request recipient) which the initiator shall use as patientID in subsequent transactions to aid in matching. |
sourcePatientId | See also Patient ID. The sourcePatientID is the ID as known by the document submitter (in this case, the referral request initiator). This ID Shall be the same as that for the C-CDA document meta data. | R (360X) | The patient ID in the PID-3 list that represents the referral request initiator’s patient ID. |
sourcePatientInfo | Relevant patient demographics such as last name, first name, sex, DOB that may help in matching (electronically or by a person) if IDs are insufficient. | R2 per XDR, O per IHE?? | PID-5, PID-7, PID-8 content should be used. |
practiceSettingCode | Identifies the setting that created the order at a high granularity e.g., Cardiology, FamilyPractice. Should not create ambiguity as compared to healthcareFacilityTypeCode. | R2 (XDR and XDM for Direct) | Should be derived from/mapped to the information in ORC-21 through 24 |
typeCode | Further refines classCode and should not make ambiguous. Defines the specific HL7 V2 message event type, for this message it is O19 | R (360X) | MSH-9.2^9.3 OMG^O19^OMG_O19 |
uniqueId | Globally unique identifier assigned to the document by its creator. | R (XDR and XDM for Direct Messaging) | May be based on Message Control ID in MSH-10 |