Generated Narrative: StructureDefinition MedicationActivity Name Flags Card. Type Description & Constraints SubstanceAdministration <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-text-ref-value, 1098-7513, should-routeCode, dose-unit-or-admin-unit, should-author )">C 1..1 SubstanceAdministration XML Namespace: urn:hl7-org:v3 Base for all types and resources Instance of this type are validated by templateId Logical Container: ClinicalDocument (CDA Class) Constraints: should-text-ref-value, 1098-7513, should-routeCode, dose-unit-or-admin-unit, should-author #xD; Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension #xD; templateId:medication-activity 1..1 II #xD; @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.4.16 #xD; @extension 1..1 st Required Pattern: 2014-06-09 #xD; @classCode 1..1 cs #xD; @moodCode 1..1 cs Binding: MoodCodeEvnInt (required) #xD; id 1..* II #xD; code 0..1 CD 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. #xD; text <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-text-ref-value )">C 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry #xD; reference <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( value-starts-octothorpe )">C 0..1 TEL Constraints: value-starts-octothorpe #xD; statusCode 1..1 CS #xD; @code 1..1 cs 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) #xD; Slices for effectiveTime 1..* SXCM_TS, IVL_TS, EIVL_TS, PIVL_TS, SXPR_TS Slice: Unordered, Open by type:$this #xD; effectiveTime:duration <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( 1098-32890, should-value-att, should-low )">C 1..1 IVL_TS 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. Note: This effectiveTime represents either the time the medication was started and stopped or the single-administration timestamp. Constraints: 1098-32890, should-value-att, should-low #xD; @value 0..1 ts indicates a single-administration timestamp #xD; low 0..1 IVXB_TS indicates when medication started #xD; high 0..1 IVXB_TS indicates when medication stopped #xD; effectiveTime:periodicFrequency C 0..1 PIVL_TS This effectiveTime represents a periodic medication frequency (e.g., administration times per day). #xD; @operator 1..1 cs Required Pattern: A #xD; effectiveTime:eventFrequency C 0..1 EIVL_TS This effectiveTime represents an event-based medication frequency (e.g., administration at bedtime). #xD; @operator 1..1 cs Required Pattern: A #xD; repeatNumber 0..1 IVL_INT 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. #xD; routeCode <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-translation, should-routeCode )">C 0..1 CE 헨?헦?헖?헗?헜?: Route Code - SPL Binding: SPL Drug Route of Administration Terminology (required) Constraints: should-translation #xD; translation 0..* CD 헨?헦?헖?헗?헜?: Route Code - SNOMED Binding: Medication Route (required) #xD; approachSiteCode 0..* CD Binding: Body Site Value Set (required) #xD; doseQuantity C 1..1 IVL_PQ If the consumable code is not pre-coordinated (e.g., is "simply metoprolol Oral Product" (RxCUI 1163523), 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).&#10;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). Constraints: should-unit #xD; @unit <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( dose-unit-or-admin-unit )">C 0..1 cs 헨?헦?헖?헗?헜?: Dose Unit of Measure. NOTE: The base CDA R2.0 standard requires @unit to be drawn from UCUM, and best practice is to use case sensitive UCUM units Binding: UnitsOfMeasureCaseSensitive (preferred) #xD; rateQuantity 0..1 IVL_PQ #xD; @unit 1..1 cs NOTE: The base CDA R2.0 standard requires @unit to be drawn from UCUM, and best practice is to use case sensitive UCUM units Binding: UnitsOfMeasureCaseSensitive (required) #xD; maxDoseQuantity 0..1 RTO_PQ_PQ #xD; administrationUnitCode <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( dose-unit-or-admin-unit )">C 0..1 CE 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) #xD; consumable 1..1 InfrastructureRoot 헨?헦?헖?헗?헜?: Medications #xD; manufacturedProduct 1..1 MedicationInformation #xD; performer 0..* Performer2 #xD; author C 0..* AuthorParticipation SHOULD contain author #xD; Slices for participant 0..* Participant2 Slice: Unordered, Open by value:typeCode #xD; participant:drugVehicle 0..* Participant2 #xD; @typeCode 1..1 cs Fixed Value: CSM #xD; participantRole 1..1 DrugVehicle #xD; Slices for entryRelationship 0..* EntryRelationship Slice: Unordered, Open by profile:substanceAdministration, profile:observation, profile:act, profile:supply #xD; entryRelationship:indication 0..* EntryRelationship 헨?헦?헖?헗?헜?: Indication #xD; @typeCode 1..1 cs Fixed Value: RSON #xD; observation 1..1 Indication #xD; entryRelationship:instruction 0..* EntryRelationship #xD; @typeCode 1..1 cs Fixed Value: SUBJ #xD; @inversionInd 1..1 bl Fixed Value: true #xD; observation 1..1 InstructionObservation #xD; entryRelationship:supplyOrder 0..* EntryRelationship #xD; @typeCode 1..1 cs Fixed Value: REFR #xD; supply 1..1 MedicationSupplyOrder #xD; entryRelationship:medicationDispense 0..* EntryRelationship #xD; @typeCode 1..1 cs Fixed Value: REFR #xD; supply 1..1 MedicationDispense #xD; entryRelationship:reaction 0..* EntryRelationship #xD; @typeCode 1..1 cs Fixed Value: CAUS #xD; observation 1..1 ReactionObservation #xD; entryRelationship:drugMonitoring 0..* EntryRelationship #xD; @typeCode 1..1 cs Fixed Value: COMP #xD; act 1..1 DrugMonitoringAct #xD; entryRelationship:substanceAdministered 0..* EntryRelationship 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. #xD; @typeCode 1..1 cs Fixed Value: COMP #xD; @inversionInd 1..1 bl Fixed Value: true #xD; sequenceNumber 0..1 INT #xD; act 1..1 SubstanceAdministeredAct #xD; entryRelationship:adherence 0..* EntryRelationship 헨?헦?헖?헗?헜?: Medication Adherence #xD; @typeCode 1..1 cs Fixed Value: COMP #xD; observation 1..1 MedicationAdherence #xD; entryRelationship:signature 0..* EntryRelationship 헨?헦?헖?헗?헜?: Medication Instructions #xD; @typeCode 1..1 cs Fixed Value: COMP #xD; substanceAdministration 1..1 MedicationFreeTextSig #xD; precondition 0..* Precondition #xD; @typeCode 1..1 cs #xD; criterion 1..1 PreconditionforSubstanceAdministration #xD; Documentation for this format
HL7 International - Structured Documents
A 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 template be used for moodCodes other than EVN if the document type contains a section that includes Planned Medication Activity (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 Oral Product" (RxCUI 1163523) will have a dose of "25 mg". #### Templates Used Although open templates may contain any valid CDA content, the following templates are specifically called out by this template: **Optional EntryRelationships**: [DrugMonitoringAct](StructureDefinition-DrugMonitoringAct.html), [Indication](StructureDefinition-Indication.html), [InstructionObservation](StructureDefinition-InstructionObservation.html), [MedicationAdherence](StructureDefinition-MedicationAdherence.html), [MedicationDispense](StructureDefinition-MedicationDispense.html), [MedicationFreeTextSig](StructureDefinition-MedicationFreeTextSig.html), [MedicationSupplyOrder](StructureDefinition-MedicationSupplyOrder.html), [ReactionObservation](StructureDefinition-ReactionObservation.html), [SubstanceAdministeredAct](StructureDefinition-SubstanceAdministeredAct.html)
Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
SHOULD contain zero or one [0..1] effectiveTime (CONF:1098-7513) such that it **SHALL** contain exactly one [1..1] @xsi:type="PIVL_TS" or "EIVL_TS" (CONF:1098-28499).
effectiveTime.ofType(CDA.PIVL_TS).exists() or effectiveTime.ofType(CDA.EIVL_TS).exists()
If doseQuantity/@unit is present, then administrationUnitCode SHALL NOT be present.
doseQuantity.unit.exists() implies administrationUnitCode.empty()
If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
An II instance must have either a root or an nullFlavor.
A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Identifies the type as an HL7 Registered model
A character string as a unique identifier within the scope of the identifier root.
When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
SHALL contain exactly one [1..1] @classCode="SBADM" (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:1098-7496).
SHALL contain exactly one [1..1] @moodCode, which SHALL be selected from ValueSet MoodCodeEvnInt urn:oid:2.16.840.1.113883.11.20.9.18 STATIC 2011-04-03 (CONF:1098-7497).
SHALL contain at least one [1..*] id (CONF:1098-7500).
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.
MAY contain zero or one [0..1] code (CONF:1098-7506).
SHOULD reference the portion of section narrative text corresponding to this entry
Indicates whether the raw byte data is compressed, and what compression algorithm was used.
The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encapsulated data value with reference was created.
Specifies the algorithm used to compute the integrityCheck value. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default choice for the integrity check algorithm. Note that SHA-256 is also entering widespread usage.
For character based information the language property specifies the human language of the text.
Identifies the type of the encapsulated data and identifies a method to interpret or render the data.
Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
Data that is primarily intended for human interpretation or for further machine processing is outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information as defined by a different standard (e.g., XML-signatures.)
This element is represented in XML as textual content. The actual name "xmlText" will not appear in a CDA instance.
A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data.
If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative
value.exists() implies value.startsWith('#')
An abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encapsulated data. It allows a user to select data more efficiently before actually downloading through the reference.
Thumbnails cannot contain their own thumbnails
SHALL contain exactly one [1..1] statusCode (CONF:1098-7507).
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.
The plain code symbol defined by the code system. For example, "784.0" is the code symbol of the ICD-9 code "784.0" for headache.
This statusCode SHALL contain exactly one [1..1] @code, which SHALL be selected from ValueSet Medication Status urn:oid:2.16.840.1.113762.1.4.1099.11 DYNAMIC (CONF:1098-32360).
Specifies the code system that defines the code.
If applicable, a version descriptor defined specifically for the given code system.
A name or title for the code, under which the sending system shows the code value to its users.
The valueSet extension adds an attribute for elements with a CD dataType which indicates the particular value set constraining the coded concept.
The valueSetVersion extension adds an attribute for elements with a CD dataType which indicates the version of the particular value set constraining the coded concept.
The text or phrase used as the basis for the coding.
Specifies additional codes that increase the specificity of the the primary code.
A set of other concept descriptors that translate this concept descriptor into other code systems.
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. Note: This effectiveTime represents either the time the medication was started and stopped or the single-administration timestamp.
SHALL contain exactly one [1..1] effectiveTime (CONF:1098-7508) such that it
This effectiveTime **SHALL** contain either a low or a @value but not both (CONF:1098-32890).
(value.exists() or low.exists()) and ((value.exists() and low.exists()).not())
indicates a single-administration timestamp
A quantity specifying a point on the axis of natural time. A point in time is most often represented as a calendar expression.
SHOULD contain zero or one [0..1] @value (CONF:1098-32775).
A code specifying whether the set component is included (union) or excluded (set-difference) from the set, or other set operations with the current set component and the set as constructed from the representation stream up to the current point.
SHOULD contain zero or one [0..1] low (CONF:1098-32776).
The arithmetic mean of the interval (low plus high divided by 2). The purpose of distinguishing the center as a semantic property is for conversions of intervals from and to point values.
The difference between high and low boundary. The purpose of distinguishing a width property is to handle all cases of incomplete information symmetrically. In any interval representation only two of the three properties high, low, and width need to be stated and the third can be derived.
MAY contain zero or one [0..1] high (CONF:1098-32777).
This effectiveTime represents a periodic medication frequency (e.g., administration times per day).
SHALL contain exactly one [1..1] @operator="A" (CONF:1098-9106).
A prototype of the repeating interval, specifying the duration of each occurrence and anchors the periodic interval sequence at a certain point in time.
A time duration specifying as a reciprocal measure of the frequency at which the periodic interval repeats.
Specifies if and how the repetitions are aligned to the cycles of the underlying calendar (e.g., to distinguish every 30 days from "the 5th of every month".) A non-aligned periodic interval recurs independently from the calendar. An aligned periodic interval is synchronized with the calendar.
Indicates whether the exact timing is up to the party executing the schedule (e.g., to distinguish "every 8 hours" from "3 times a day".)
This effectiveTime represents an event-based medication frequency (e.g., administration at bedtime).
A code for a common (periodical) activity of daily living based on which the event related periodic interval is specified.
An interval of elapsed time (duration, not absolute point in time) that marks the offsets for the beginning, width and end of the event-related periodic interval measured from the time each such event actually occurred.
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.
MAY contain zero or one [0..1] repeatNumber (CONF:1098-7555).
SHOULD contain zero or one [0..1] routeCode, which SHALL be selected from ValueSet SPL Drug Route of Administration Terminology urn:oid:2.16.840.1.113883.3.88.12.3221.8.7 DYNAMIC (CONF:1098-7514).
The routeCode, if present, SHOULD contain zero or more [0..*] translation, which SHALL be selected from ValueSet Medication Route urn:oid:2.16.840.1.113762.1.4.1099.12 DYNAMIC (CONF:1098-32950).
MAY contain zero or one [0..1] approachSiteCode, where the code SHALL be selected from ValueSet Body Site Value Set urn:oid:2.16.840.1.113883.3.88.12.3221.8.9 DYNAMIC (CONF:1098-7515).
If the consumable code is not pre-coordinated (e.g., is "simply metoprolol Oral Product" (RxCUI 1163523), 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). 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).
SHALL contain exactly one [1..1] doseQuantity (CONF:1098-7516).
𝗨𝗦𝗖𝗗𝗜: Dose Unit of Measure. NOTE: The base CDA R2.0 standard requires @unit to be drawn from UCUM, and best practice is to use case sensitive UCUM units
NOTE: The base CDA R2.0 standard requires @unit to be drawn from UCUM, and best practice is to use case sensitive UCUM units
This doseQuantity SHOULD contain zero or one [0..1] @unit, which SHOULD be selected from ValueSet UnitsOfMeasureCaseSensitive urn:oid:2.16.840.1.113883.1.11.12839 DYNAMIC (CONF:1098-7526).
The magnitude of the quantity measured in terms of the unit.
An alternative representation of the same physical quantity expressed in a different unit, of a different unit code system and possibly with a different value.
MAY contain zero or one [0..1] rateQuantity (CONF:1098-7517).
The unit of measure specified in the Unified Code for Units of Measure (UCUM) [].
The rateQuantity, if present, SHALL contain exactly one [1..1] @unit, which SHALL be selected from ValueSet UnitsOfMeasureCaseSensitive urn:oid:2.16.840.1.113883.1.11.12839 DYNAMIC (CONF:1098-7525).
MAY contain zero or one [0..1] maxDoseQuantity (CONF:1098-7518).
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.
MAY contain zero or one [0..1] administrationUnitCode, which SHALL be selected from ValueSet AdministrationUnitDoseForm urn:oid:2.16.840.1.113762.1.4.1021.30 DYNAMIC (CONF:1098-7519).
The consumable participation is used to bring in the LabeledDrug or Material entity that describes the administered substance. The LabeledDrug class, which is an Entity class playing the Role of Manufactured Product, identifies the drug that is consumed in the substance administration. The medication is identified by means of the LabeledDrug.code or the LabeledDrug.name. The Material entity is used to identify non-drug administered substances such as vaccines and blood products.
This consumable SHALL contain exactly one [1..1] Medication Information (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.23:2014-06-09) (CONF:1098-16085).
MAY contain zero or one [0..1] performer (CONF:1098-7522).
SHOULD contain zero or more [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:1098-31150).
MAY contain zero or more [0..*] participant (CONF:1098-7523) such that it
SHALL contain exactly one [1..1] @typeCode="CSM" (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90 STATIC) (CONF:1098-7524).
SHALL contain exactly one [1..1] @typeCode="RSON" (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1098-7537).
The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed.
The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.
MAY contain zero or one [0..1] entryRelationship (CONF:1098-7539) such that it
SHALL contain exactly one [1..1] @typeCode="SUBJ" (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1098-7540).
SHALL contain exactly one [1..1] @inversionInd="true" True (CONF:1098-7542).
MAY contain zero or one [0..1] entryRelationship (CONF:1098-7543) such that it
SHALL contain exactly one [1..1] @typeCode="REFR" (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1098-7547).
MAY contain zero or more [0..*] entryRelationship (CONF:1098-7549) such that it
SHALL contain exactly one [1..1] @typeCode="REFR" (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1098-7553).
MAY contain zero or more [0..*] entryRelationship (CONF:1098-7552) such that it
SHALL contain exactly one [1..1] @typeCode="CAUS" (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1098-7544).
MAY contain zero or one [0..1] entryRelationship (CONF:1098-30820) such that it
SHALL contain exactly one [1..1] @typeCode="COMP" Has component (CONF:1098-30821).
SHALL contain exactly one [1..1] Drug Monitoring Act (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.123) (CONF:1098-30822).
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.
MAY contain zero or more [0..*] entryRelationship (CONF:1098-31515) such that it
SHALL contain exactly one [1..1] @typeCode="COMP" Component (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-31516).
SHALL contain exactly one [1..1] @inversionInd="true" (CONF:1098-31517).
MAY contain zero or one [0..1] sequenceNumber (CONF:1098-31518).
SHALL contain exactly one [1..1] Substance Administered Act (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.118) (CONF:1098-31519).
MAY contain zero or more [0..*] entryRelationship such that it
SHALL contain exactly one [1..1] @typeCode="COMP" Component (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002).
SHALL contain exactly one [1..1] Medication Adherence (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.508).
MAY contain zero or more [0..*] entryRelationship (CONF:1098-32907) such that it
SHALL contain exactly one [1..1] @typeCode="COMP" Has component (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:1098-32908).
SHALL contain exactly one [1..1] Medication Free Text Sig (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.147) (CONF:1098-32909).
MAY contain zero or more [0..*] precondition (CONF:1098-31520).
The precondition, if present, SHALL contain exactly one [1..1] @typeCode="PRCN" (CONF:1098-31882).
The precondition, if present, SHALL contain exactly one [1..1] Precondition for Substance Administration (identifier: urn:hl7ii:2.16.840.1.113883.10.20.22.4.25:2014-06-09) (CONF:1098-31883).