Template  BC CDA inFulfillmentOf

Id 2.16.840.1.113883.3.51.60.1.12 ref (from repository: bccdapilot-) Effective Date valid from 2016‑03‑27 09:03:45 Status Draft Version Label Name CDAinFulfillmentOf Display Name BC CDA inFulfillmentOf Description Template CDA inFulfillmentOf (prototype, directly derived from POCD_RM000040 MIF) Classification CDA Header Level Template Open/Closed Open (other than defined elements are allowed) Relationship Specialization: template 2.16.840.1.113883.10.12.109 (2005‑09‑07) Item DT Card Conf Description Label hl7:inFulfillmentOf 0 … * (CDAinFulfillmentOf) @typeCode cs 1 … 1 F FLFS CONF‑BC0524   Constraint The inFulfillmentOf/order element MAY be present and represents the Placer Order (HL7 V2: ORC-2) or the Placer Group (HL7 V2: ORC-4) that was fulfilled, the identifier of which is carried in inFulfillmentOf/order/id.  When present, these elements conform to the constraints described in the general header section of this guide. If  the inFulfillmentOf/order element is present, it SHALL contain exactly one [1..1] statusCode(HL7 V2: ORC-5),which represents the status code of the order.  Therefore, if present, code.codeSystem SHALL contain “statusCode” and  code.code SHALL contain “completed,” “active,” or “aborted.” hl7:order 1 … 1 M CONF‑BC0123 @classCode cs 1 … 1 F ACT CONF‑BC0525 @moodCode cs 1 … 1 F RQO hl7:id II 1 … * M CONF‑BC0124 hl7:code CE 0 … 1 CONF‑BC0526   Constraint inFulfillmentOf/order element MAY contain one [0..1] code element.  If present, code SHALL contain the status code of the order. Therefore, if present, code.codeSystem SHALL contain “statusCode” and  code.code SHALL contain “completed,” “active,” or “aborted.”