StructureDefinition-2.16.840.1.113883.10.20.22.4.42

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.42
canonicalhttp://hl7.org/cda/us/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.4.42
version2.1
statusactive
publisherHealth Level Seven
namePlannedMedicationActivity
titlePlanned Medication Activity
date2023-08-24T14:33:15+00:00
descriptionThis template represents planned medication activities. The priority of the medication activity to the patient and provider is communicated through Priority Preference. The effectiveTime indicates the time when the medication activity is intended to take place. The authorTime indicates when the documentation of the plan occurred.
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 CDAR2.SubstanceAdministration XML Namespace: urn:hl7-org:v3
This logical model cannot be the target of a reference
. . . classCode 1..1 Fixed Value: SBADM
. . . moodCode 1..1 Binding: Planned moodCode (SubstanceAdministration/Supply) ( 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.42
. . . . . extension 1..1 Required Pattern: 2014-06-09
. . . id 1..*
. . . statusCode 1..1
. . . . code 1..1 Fixed Value: active
. . . effectiveTime 1..1 IVL_TS The effectiveTime in a planned medication activity represents the time that the medication activity should occur.
. . . repeatNumber 0..1 In a Planned Medication Activity, repeatNumber defines the number of allowed administrations. For example, a repeatNumber of "3" means that the substance can be administered up to 3 times.
. . . routeCode 0..1 Binding: SPL Drug Route of Administration Terminology ( required )
. . . . translation 0..* Binding: Medication Route ( required )
. . . approachSiteCode 0..* Binding: Body Site Value Set ( required )
. . . doseQuantity 0..1
. . . . unit 0..1 Binding: UnitsOfMeasureCaseSensitive ( required )
. . . rateQuantity 0..1
. . . . unit 0..1 Binding: UnitsOfMeasureCaseSensitive ( required )
. . . maxDoseQuantity 0..1
. . . administrationUnitCode 0..1 Binding: AdministrationUnitDoseForm ( required )
. . . consumable 1..1
. . . . manufacturedProduct 1..1 http://hl7.org/cda/stds/core/StructureDefinition/ManufacturedProduct
. . . performer 0..* The clinician who is expected to perform the medication activity could be identified using substanceAdministration/performer.
. . . author 0..1 http://hl7.org/cda/stds/core/StructureDefinition/Author The author in a planned medication activity represents the clinician who is requesting or planning the medication activity.
. . . Slices for entryRelationship The following entryRelationship captures any instructions associated with the planned medication activity.
Slice: Unordered, Open by profile:act, profile:observation
. . . . entryRelationship:priorityPreference 0..* The following entryRelationship represents the priority that a patient or a provider places on the planned medication activity.
. . . . . typeCode 1..1 Fixed Value: REFR
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation
. . . . entryRelationship:indication 0..* The following entryRelationship represents the indication for the planned medication activity.
. . . . . typeCode 1..1 Fixed Value: RSON
. . . . . observation 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Observation
. . . . entryRelationship:instruction 0..*
. . . . . typeCode 1..1 Fixed Value: SUBJ
. . . . . act 1..1 http://hl7.org/cda/stds/core/StructureDefinition/Act
. . . 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