Back To Index  <<  Back To Templates

active Template  Order Reference - inFulfillmentOf

Id 2.16.756.5.30.1.1.10.2.16
ref
hl7chcda-
Effective Date 2018‑04‑18
Status active Active Version Label 2017
Name cdach_header_OrderReference Display Name Order Reference - inFulfillmentOf
Description
Reference to one or more orders which led to the creation of this CDA document. It SHALL be declared, when the order reference is relevant for some reason. All CDA-CH V2 derivatives, i.e. Swiss exchange formats MUST reference this template.
Context Parent nodes of template element with id 2.16.756.5.30.1.1.10.2.16
Label CDA‑CH V2
Classification CDA Header Level Template
Open/Closed Open (other than defined elements are allowed)
Used by / Uses
Used by 6 transactions and 16 templates, Uses 0 templates
Used by as Name Version
cdachemed-transaction-4 Transaction draft Medication Prescription document 2018‑04‑04 15:33:29
cdachemed-transaction-9 Transaction draft Medication Treatment Plan document 2019‑12‑12 14:11:31
cdachemed-transaction-5 Transaction draft Medication Dispense document 2018‑04‑04 15:35:51
cdachemed-transaction-6 Transaction draft Pharmaceutical Advice document 2018‑04‑04 15:36:35
cdachemed-transaction-7 Transaction draft Medication List document 2018‑04‑04 15:37:19
cdachemed-transaction-8 Transaction draft Medication Card document 2018‑04‑04 15:42:50
2.16.756.5.30.1.1.10.9.36 Include active CDA-CH v2.0 Header Template Compilation (2017) 2018‑04‑18
2.16.756.5.30.1.1.10.1.9 link active CDA-CH v2.1 - structuredBody (2020) 2019‑10‑17 15:22:41
2.16.756.5.30.1.1.10.1.9 link retired CDA-CH v2.0 - structuredBody (2017) 2018‑04‑18
2.16.756.5.30.1.1.10.9.41 Include pending Header Template Compilation Medication Dispense document (2019) 2018‑01‑08 15:56:47
2.16.756.5.30.1.1.10.1.5 link draft Medication Dispense document (2020) 2016‑05‑21
2.16.756.5.30.1.1.10.9.42 Include pending Header Template Compilation Medication Card document (2019) 2019‑10‑17 13:58:45
2.16.756.5.30.1.1.10.1.3 link draft Medication Card document (2020) 2016‑05‑13
2.16.756.5.30.1.1.10.9.42 Include cancelled Header Template Compilation Medication Card document (2017) 2018‑01‑08 16:20:12
2.16.756.5.30.1.1.10.9.43 Include pending Header Template Compilation Pharmaceutical Advice document (2019) 2018‑01‑08 16:23:16
2.16.756.5.30.1.1.10.1.6 link draft Pharmaceutical Advice document (2020) 2016‑05‑21
2.16.756.5.30.1.1.10.9.44 Include pending Header Template Compilation MedicationTreatmentPlan (2019) 2018‑01‑08 16:26:11
2.16.756.5.30.1.1.10.1.7 link draft Medication Treatment Plan document (2020) 2017‑04‑12 13:57:31
2.16.756.5.30.1.1.10.9.45 Include pending Header Template Compilation Medication Prescription document (2019) 2018‑01‑08 16:28:39
2.16.756.5.30.1.1.10.1.4 link draft Medication Prescription document (2020) 2016‑05‑21
2.16.756.5.30.1.1.10.9.46 Include pending Header Template Compilation Medication List document (2019) 2018‑01‑22 15:29:29
2.16.756.5.30.1.1.10.1.13 link draft Medication List document (2020) 2018‑01‑22 15:17:26
Relationship Specialization: template 2.16.840.1.113883.10.12.109 CDA inFulfillmentOf (2005‑09‑07)
ref
ad1bbr-
Example
Order reference on a CDA-CH V2 (2017) document
<inFulfillmentOf>
  <templateId root="2.16.756.5.30.1.1.10.2.16"/>  <order>
    <id root="9F44AE66-D70B-46DA-89AD-82A51C7A11C6"/>  </order>
</inFulfillmentOf>
Example
Order reference to an order created by an ERP system
<inFulfillmentOf>
  <templateId root="2.16.756.5.30.1.1.10.2.16"/>  <order>
    <id root="2.999" extension="AU-20170021987"/>  </order>
</inFulfillmentOf>
Item DT Card Conf Description Label
hl7:inFulfillmentOf
0 … * Reference to one or more orders which led to the creation of this CDA document. It SHALL be declared, when the order reference is relevant for some reason. CDA‑CH V2
hl7:templateId
II 1 … 1 M CDA‑CH V2
@root
uid 1 … 1 F 2.16.756.5.30.1.1.10.2.16
hl7:order
1 … 1 R CDA‑CH V2
hl7:id
II 1 … * R Order number. CDA‑CH V2
@root
uid 1 … 1 R Either the same GUID (order id) or the same OID (order issuing system) as the order itself.
@extension
st 0 … 1   Contains the order ID itself. The ID MUST be unique within the system that issued the ID.