StructureDefinition-2.16.840.1.113883.10.20.22.4.16

Sourcehl7.cda.us.ccda#current:Consolidated CDA Release 2.1 StructureDefinition Publication (v5.0.0)
resourceTypeStructureDefinition
id2.16.840.1.113883.10.20.22.4.16
canonicalhttp://hl7.org/cda/us/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.4.16
version2.1
statusactive
publisherHealth Level Seven
nameMedicationActivity
titleMedication Activity
date2023-08-24T14:33:15+00:00
descriptionA Medication Activity describes substance administrations that have 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 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. A moodCode of INT is allowed, but it is recommended that the Planned Medication Activity (V2) template be used for moodCodes other than EVN if the document type contains a section that includes Planned Medication Activity (V2) (for example a Care Plan document with Plan of Treatment, Intervention, or Goal sections). At a minimum, a Medication Activity shall include an effectiveTime indicating the duration of the administration (or single-administration timestamp). Ambulatory medication lists generally provide a summary of use for a given medication over time - a medication activity in event mood with the duration reflecting when the medication started and stopped. Ongoing medications will not have a stop date (or will have a stop date with a suitable NULL value). Ambulatory medication lists will generally also have a frequency (e.g., a medication is being taken twice a day). Inpatient medications generally record each administration as a separate act. The dose (doseQuantity) represents how many of the consumables are to be administered at each administration event. As a result, the dose is always relative to the consumable and the interval of administration. Thus, a patient consuming a single "metoprolol 25mg tablet" per administration will have a doseQuantity of "1", whereas a patient consuming "metoprolol" will have a dose of "25 mg".
jurisdictionsus
fhirVersion5.0.0
kindlogical
abstractfalse
sdTtypehttp://hl7.org/cda/stds/core/StructureDefinition/SubstanceAdministration
derivationconstraint
basehttp://hl7.org/cda/stds/core/StructureDefinition/SubstanceAdministration
Usages
Name Flags Card. Type Description & Constraints doco
. . SubstanceAdministration C CDAR2.SubstanceAdministration XML Namespace: urn:hl7-org:v3
This logical model cannot be the target of a reference
1098-30800: Medication Activity **SHOULD** include doseQuantity **OR** rateQuantity (CONF:1098-30800).
. . . classCode 1..1
. . . moodCode 1..1 Binding: MoodCodeEvnInt ( required )
. . . Slices for templateId 1 .. Slice: Unordered, Open by value:extension, value:root
. . . . templateId:primary 1..1
. . . . . root 1..1 Required Pattern: 2.16.840.1.113883.10.20.22.4.16
. . . . . extension 1..1 Required Pattern: 2014-06-09
. . . id 1..*
. . . code 0..1 SubstanceAdministration.code is an optional field. Per HL7 Pharmacy Committee, "this is intended to further specify the nature of the substance administration act. To date the committee has made no use of this attribute". Because the type of substance administration is generally implicit in the routeCode, in the consumable participant, etc., the field is generally not used, and there is no defined value set.
. . . statusCode 1..1
. . . . code 1..1 The substance administration effectiveTime field can repeat, in order to represent varying levels of complex dosing. effectiveTime can be used to represent the duration of administration (e.g., "10 days"), the frequency of administration (e.g., "every 8 hours"), and more. Here, we require that there SHALL be an effectiveTime documentation of the duration (or single-administration timestamp), and that there SHOULD be an effectiveTime documentation of the frequency. Other timing nuances, supported by the base CDA R2 standard, may also be included.
Binding: Medication Status ( required )
. . . Slices for effectiveTime 1 .. Slice: Unordered, Open by value:operator
. . . . effectiveTime:duration C 1..1 IVL_TS This effectiveTime represents either the medication duration (i.e., the time the medication was started and stopped) or the single-administration timestamp.
1098-32890: This effectiveTime **SHALL** contain either a low or a @value but not both (CONF:1098-32890).
. . . . . value 0..1 indicates a single-administration timestamp
. . . . . low 0..1 indicates when medication started
. . . . . high 0..1 indicates when medication stopped
. . . . effectiveTime:frequency C 0..1 SXCM_TS This effectiveTime represents the medication frequency (e.g., administration times per day).
1098-28499: **SHALL** contain exactly one [1..1] @xsi:type="PIVL_TS" or "EIVL_TS" (CONF:1098-28499).
. . . . . operator 1..1 Required Pattern: A
. . . repeatNumber 0..1 In "INT" (intent) mood, the repeatNumber defines the number of allowed administrations. For example, a repeatNumber of "3" means that the substance can be administered up to 3 times. In "EVN" (event) mood, the repeatNumber is the number of occurrences. For example, a repeatNumber of "3" in a substance administration event means that the current administration is the 3rd in a series.
. . . routeCode 0..1 Binding: SPL Drug Route of Administration Terminology ( required )
. . . . translation 0..* Binding: Medication Route ( required )
. . . approachSiteCode 0..1 Binding: Body Site Value Set ( required )
. . . doseQuantity C 1..1 1098-16879: Not pre-coordinated consumable: If the consumable code is not pre-coordinated (e.g., is simply "metoprolol"), then doseQuantity must represent a physical quantity with @unit, e.g., "25" and "mg", specifying the amount of product given per administration (CONF:1098-16879).
1098-16878: Pre-coordinated consumable: If the consumable code is a pre-coordinated unit dose (e.g., "metoprolol 25mg tablet") then doseQuantity is a unitless number that indicates the number of products given per administration (e.g., "2", meaning 2 x "metoprolol 25mg tablet" per administration) (CONF:1098-16878).
. . . . unit 0..1 Binding: UnitsOfMeasureCaseSensitive ( required )
. . . rateQuantity 0..1
. . . . unit 1..1 Binding: UnitsOfMeasureCaseSensitive ( required )
. . . maxDoseQuantity 0..1
. . . administrationUnitCode 0..1 administrationUnitCode@code describes the units of medication administration for an item using a code that is pre-coordinated to include a physical unit form (ointment, powder, solution, etc.) which differs from the units used in administering the consumable (capful, spray, drop, etc.). For example when recording medication administrations, 'metric drop (C48491)'' would be appropriate to accompany the RxNorm code of 198283 (Timolol 0.25% Ophthalmic Solution) where the number of drops would be specified in doseQuantity@value.
Binding: AdministrationUnitDoseForm ( required )
. . . consumable 1..1
. . . . manufacturedProduct 1..1 http://hl7.org/cda/stds/core/StructureDefinition/ManufacturedProduct
. . . performer 0..1
. . . author 0..* http://hl7.org/cda/stds/core/StructureDefinition/Author
. . . Slices for participant Slice: Unordered, Open by value:participantRole, value:typeCode
. . . . participant:drugVehicle 0..*
. . . . . typeCode 1..1 Fixed Value: CSM
. . . . . participantRole 1..1 http://hl7.org/cda/stds/core/StructureDefinition/ParticipantRole
. . . Slices for entryRelationship Slice: Unordered, Open by profile:substanceAdministration, profile:observation, profile:act, profile:supply
. . . . entryRelationship:indication 0..*
. . . . . typeCode 1..1 Fixed Value: RSON
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation
. . . . entryRelationship:instruction 0..1
. . . . . typeCode 1..1 Fixed Value: SUBJ
. . . . . inversionInd 1..1 Fixed Value: true
. . . . . act 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Act
. . . . entryRelationship:supplyOrder 0..1
. . . . . typeCode 1..1 Fixed Value: REFR
. . . . . supply 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Supply
. . . . entryRelationship:medicationDispense 0..*
. . . . . typeCode 1..1 Fixed Value: REFR
. . . . . supply 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Supply
. . . . entryRelationship:reaction 0..*
. . . . . typeCode 1..1 Fixed Value: CAUS
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation
. . . . entryRelationship:drugMonitoring 0..1
. . . . . typeCode 1..1 Fixed Value: COMP
. . . . . act 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Act
. . . . entryRelationship:substanceAdministered 0..* The following entryRelationship is used to indicate a given medication's order in a series. The nested Substance Administered Act identifies an administration in the series. The entryRelationship/sequenceNumber shows the order of this particular administration in that series.
. . . . . typeCode 1..1 Fixed Value: COMP
. . . . . inversionInd 1..1 Fixed Value: true
. . . . . sequenceNumber 0..1
. . . . . act 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Act
. . . . entryRelationship:signature 0..*
. . . . . typeCode 1..1 Fixed Value: COMP
. . . . . substanceAdministration 1..1 http://hl7.org/cda/stds/core/StructureDefinition/SubstanceAdministration
. . . precondition 0..*
. . . . typeCode 1..1 Fixed Value: PRCN
. . . . criterion 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Criterion

doco Documentation for this format

Produced 08 Sep 2023