2.16.840.1.113883.10.22.4.4/static-2016-11-11T000000

Id	2.16.840.1.113883.10.22.4.4	Effective Date	valid from 2016‑11‑11
Status	Draft	Version Label
Name	IPSMedicationEntry	Display Name	IPS Medication Entry
Description <div class="yui-wk-div">An IPS Medication entry describes a medication statement, that is a substance administration that has actually occurred (e.g., pills ingested or injections given) or are intended to occur (e.g., "take 2 tablets twice a day for the next 10 days"). Medication activities in "INT" mood are reflections of what a clinician intends a patient to be taking. For example, a clinician may intend that a patient to be administered Lisinopril 20 mg PO for blood pressure control. If what was actually administered was Lisinopril 10 mg., then the Medication activities in the "EVN" mood would reflect actual use.<br clear="none"/> <br clear="none"/>The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay, but it could be derived from the medications information recorded into a GP's EHR-system, in form of prescribed medication, or administration statements.<br clear="none"/>The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains. <br clear="none"/> <br clear="none"/> A medication statement is usually less specific than an a prescription or a medication administration record. &#160;<br clear="none"/> <br clear="none"/>This entry is composed by a main substanceAdministration act and a subordinate substanceAdministration act, unless it is asserted that there are no medications data.&#160;<br clear="none"/> <br clear="none"/>The first conveys information as the product, the period of administration and the route of administration; the latter is used to provide dosage information as the frequency of intakes or the amount of the medication given.</div>
Context	Parent nodes of template element with id 2.16.840.1.113883.10.22.4.4
Classification	CDA Entry Level Template
Open/Closed	Open (other than defined elements are allowed)
Used by / Uses	Used by 0 transactions and 2 templates, Uses 3 templates Used by as Name Version 2.16.840.1.113883.10.22.3.1 Containment IPS Medication Summary Section () 2016‑11‑11 2.16.840.1.113883.10.22.1.1 International Patient Summary () 2017‑04‑11 Uses as Name Version 2.16.840.1.113883.10.22.4.2 Containment IPS ManufacturedProduct () DYNAMIC 2.16.840.1.113883.10.22.4.14 Containment IPS Body Author () DYNAMIC 2.16.840.1.113883.10.22.4.33 Containment IPS Subordinate SubstanceAdministration () DYNAMIC
Relationship	Adaptation: template 1.3.6.1.4.1.12559.11.10.1.3.1.3.4 Medication Item (2013‑12‑20) ref (from repository: epsos-)
Example	Example <substanceAdministration classCode="SBADM" moodCode="INT">   <templateId root="2.16.840.1.113883.10.22.4.4"/>  <code code="DRUG" codeSystem="2.16.840.1.113883.5.4" displayName="Drug"/>  <statusCode code="active"/>  <effectiveTime>     <width value="2" unit="wk"/>  </effectiveTime>  <consumable typeCode="CSM">     <!-- template 'IPS ManufacturedProduct' (dynamic) -->   </consumable>  <entryRelationship typeCode="COMP">     <substanceAdministration classCode="SBADM" moodCode="EVN">       <statusCode code="active"/>      <effectiveTime xsi:type="PIVL_TS" institutionSpecified="true">         <period value="12" unit="h"/>      </effectiveTime>      <doseQuantity value="2" unit="{puff}"/>      <consumable>         <manufacturedProduct>           <manufacturedMaterial nullFlavor="NA"/>        </manufacturedProduct>      </consumable>    </substanceAdministration>  </entryRelationship></substanceAdministration>
Example	No medication infos <substanceAdministration classCode="SBADM" moodCode="INT">   <templateId root="2.16.840.1.113883.10.22.4.4"/>  <code code="X-DrugTreatmentNotKnown" codeSystem="2.16.840.1.113883.5.1150.999.1" displayName="Drug treatment not known"/>  <statusCode code="completed"/>  <effectiveTime nullFlavor="NA" xsi:type="IVL_TS"/>  <consumable>     <manufacturedProduct>       <manufacturedMaterial nullFlavor="NA"/>    </manufacturedProduct>  </consumable></substanceAdministration>
Item DT Card Conf Description Label hl7:substanceAdministration R IPSM...ntry @classCode cs 1 … 1 F SBADM @moodCode cs 1 … 1 R If the statement refers to a prescribed medication then a <substanceAdministration> intent (moodCode='INT') is used; otherwise, to record medications which are stated to have taken, the moodCode shall be set to 'EVN'.   CONF The value of @moodCode shall be drawn from value set 2.16.840.1.113883.11.20.9.18 MoodCodeEvnInt (DYNAMIC) hl7:templateId II 1 … 1 M IPSM...ntry @root uid 1 … 1 F 2.16.840.1.113883.10.22.4.4 hl7:id II 0 … * R IPSM...ntry hl7:code CD.IPS 1 … 1 R <div>The &lt;code&gt; element is valorized with the Substance Administration ACT code "DRUG" unless it is used for asserting the &#160;known absence of medication treatments or no information about them.</div> IPSM...ntry   CONF The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.14 DRUGActCode (DYNAMIC) or The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.15 Absent or Unknown Medication (DYNAMIC) hl7:text ED 0 … 1 R The URI given in the value attribute of the <reference> element points to an element in the narrative content that contains the complete text describing the medication. In a CDA document, the URI given in the value attribute of the <reference> element points to an element in the narrative content that contains the complete text describing the medication. IPSM...ntry hl7:reference TEL 1 … 1 M IPSM...ntry @value 1 … 1 R Reference pointing to the narrative, typically #{label}-{generated-id}, e.g. #xxx-1 hl7:statusCode CS 1 … 1 M IPSM...ntry   CONF The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.12 ActStatusActiveCompletedAbortedSuspended (DYNAMIC)   Example <statusCode code="active"/> Choice 1 … 1 The &lt;effectiveTime&gt; element encodes the period of administration of the medication, it is always expressed as an interval of time.<br clear="none"/>It may be expressed using the &lt;low&gt; and &lt;high&gt; OR with the &lt;width&gt; element.<br clear="none"/>The first is used to indicate a specified interval (e.g. from march 15th, 2017); the latter for indicating a 'floating' period (e.g. 2 weeks) <i>.</i> Elements to choose from: hl7:effectiveTime[hl7:low | hl7:high] hl7:effectiveTime[hl7:width] hl7:effectiveTime IVL_TS 0 … 1 C <b>Case 1: specified interval</b> <br clear="none"/>The &lt;low&gt; and &lt;high&gt; values of the first &lt;effectiveTime&gt; element represent the start and stop times for the medication. The &lt;low&gt; value represents the start time, and the &lt;high&gt; value represents the stop time. If either the &lt;low&gt; or the &lt;high&gt; value is unknown, this shall be recorded by setting the nullFlavor attribute to UNK.<br clear="none"/> <br clear="none"/>In case of unbounded period (continous terapy) the &lt;high&gt; element will be valued with the nullFlavor attribute to NA.<br clear="none"/> <br clear="none"/>The &lt;high&gt; value records the end of the medication regime according to the information provided in the prescription or order. For example, if the prescription is for enough medication to last 30 days, then the high value should contain a date that is 30 days later then the &lt;low&gt; value. The rationale is that a provider, seeing an un-refilled prescription would normally assume that the medication is no longer being taken, even if the intent of the treatment plan is to continue the medication indefinitely.<i> <br clear="none"/> </i> IPSM...ntry where [hl7:low or hl7:high] @nullFlavor cs 0 … 1     Example Known Interval <effectiveTime>   <low value="20130321"/>  <high value="20140321"/></effectiveTime>   Example Information not available about the period <effectiveTime nullFlavor="NI"/>   Example Unknown end date <effectiveTime>   <low value="20130321"/>  <high nullFlavor="UNK"/></effectiveTime>   Example Continuous terapy <effectiveTime>   <low value="20130321"/>  <high nullFlavor="NA"/></effectiveTime> hl7:low IVXB_TS 1 … 1 R IPSM...ntry hl7:high IVXB_TS 0 … 1 R IPSM...ntry hl7:effectiveTime IVL_TS 0 … 1 C <b>Case 2: 'floating' period<br clear="none"/> </b>The width element is used to specify a period of (actual or intended) administration &#160;that is not anchored to any specific date (e.g. a two weeks therapy.....) IPSM...ntry where [hl7:width]   Example 2 week period <effectiveTime>   <width value="2" unit="wk"/></effectiveTime> hl7:width PQ 1 … 1 R IPSM...ntry @unit cs 1 … 1 R   CONF The value of @unit shall be drawn from value set 2.16.840.1.113883.11.22.13 Time units (UCUM) (DYNAMIC) hl7:routeCode CE.IPS 0 … 1 R The &lt;routeCode&gt; element specifies the route of administration using the EDQM route of administration vocabulary. <br clear="none"/>A code must be specified if the route is known.&#160;<br clear="none"/> <br clear="none"/> <div>Since the EDQM Standards Terms, together with UCUM,&#160;is one of the IDMP terminologies actually available for usage, this code system has been selected &#160;as referecne terminology for representing Pharmaceutical Dose forms; Packages and Route of Administration.<br clear="none"/> <br clear="none"/>It is known that also alternative jurisdictional and international terminologies are also used for this concept domain, as NCI or SNOMED CT.<br clear="none"/> <br clear="none"/>Official NCI and EDQM maps for the route of administration are available from the EDQM site.</div> IPSM...ntry   CONF The value of @code shall be drawn from value set 2.16.840.1.113883.11.22.33 Medicine Route of Administration (DYNAMIC) hl7:doseQuantity IVL_PQ NP IPSM...ntry hl7:consumable 1 … 1 M Contains 2.16.840.1.113883.10.22.4.2 IPS ManufacturedProduct (DYNAMIC) IPSM...ntry where [not(@nullFlavor)] @typeCode cs 1 … 1 F CSM hl7:author 0 … * Contains 2.16.840.1.113883.10.22.4.14 IPS Body Author (DYNAMIC) IPSM...ntry hl7:entryRelationship 0 … * C Unless medications are unknown or known absent, at least one subordinated &lt;substanceAdministration&gt; has to be present to convey information about dosages (dose, frequency of intakes,..). <br clear="none"/>Subordinated &lt;substanceAdministration&gt;&#160;elements can be also used either to handle split dosing, or to support combination medications. Contains 2.16.840.1.113883.10.22.4.33 IPS Subordinate SubstanceAdministration (DYNAMIC) IPSM...ntry @typeCode cs 1 … 1 F COMP   Constraint At least one subordinate <substanceAdministration> element SHALL be present unless medications are unknown or known absent. hl7:sequenceNumber INT 0 … 1 Sequence number of the Subordinate Substance Administration IPSM...ntry