CA Core+
1.2.0-dft 
1.2.0-DFT - The specification is version 1.2.0-DFT of CA Core+ For a full list of available versions, see the Directory of published versions
MedicationStatement (CA-Core)
Many ValueSet and CodeSystem bindings in this guide link to resources hosted on the Canada Health Infoway Terminology Service (Ontoserver). If you are redirected to a login page: This is expected and you are being directed to Infoway’s secure environment. To access these resources: You’ll need an InfoCentral Account.
Links
Profile
Derived from
http://hl7.org/fhir/StructureDefinition/MedicationStatement
Examples
example-medicationstatement-ca-core
Description
This profile applies constraints to the MedicationStatement resource for CA Core+ to support documentation of medication usage in the pan-Canadian context.
References to this resource
CFMM: 2
Resource Content
| MedicationStatementCACore (MedicationStatement) | C | MedicationStatement | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| RenderedDosageInstruction | C | 0..1 | Extension(string) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| basedOn | Σ C | 0..* | Reference(CarePlan | MedicationRequest | ServiceRequest) |
| partOf | Σ C | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Observation | Procedure) |
| status | SO Σ ?! | 1..1 | codeBinding |
| statusReason | 0..* | CodeableConcept | |
| category | Σ | 0..1 | CodeableConceptBinding |
| medication[x] | SO Σ | 1..1 | |
| medicationReference | Σ | 0..1 | Reference(MedicationCACore) |
| medicationCodeableConcept | Σ | 0..1 | CodeableConceptCACoreBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | CodingCACore |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 0..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ | 0..1 | code |
| display | Σ | 0..1 | string |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| translation | C | 0..* | Extension(Complex) |
| value | 0..1 | System.String | |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| subject | SO Σ C | 1..1 | Reference(PatientCACore | Group) |
| context | Σ C | 0..1 | Reference(Encounter | EpisodeOfCare) |
| effective[x] | SO Σ | 0..1 | |
| effectiveDateTime | dateTime | ||
| effectivePeriod | Σ | 0..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | Σ C | 0..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| dateAsserted | Σ | 0..1 | dateTime |
| informationSource | C | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| derivedFrom | C | 0..* | Reference(Resource) |
| reasonCode | O | 0..* | CodeableConceptCACoreBinding |
| reasonReference | O C | 0..* | Reference(Condition | DiagnosticReport | Observation) |
| note | 0..* | Annotation | |
| dosage | O | 0..* | Dosage |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| sequence | Σ | 0..1 | integer |
| text | O Σ | 0..1 | string |
| additionalInstruction | Σ | 0..* | CodeableConcept |
| patientInstruction | Σ | 0..1 | string |
| timing | Σ | 0..1 | Timing |
| asNeeded[x] | Σ | 0..1 | |
| asNeededBoolean | boolean | ||
| asNeededCodeableConcept | CodeableConcept | ||
| site | Σ | 0..1 | CodeableConcept |
| route | Σ | 0..1 | CodeableConceptCACoreBinding |
| method | Σ | 0..1 | CodeableConcept |
| doseAndRate | Σ | 0..* | Element |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| type | Σ | 0..1 | CodeableConcept |
| dose[x] | Σ | 0..1 | Binding |
| doseRange | Range | ||
| doseQuantity | Σ C | 0..1 | SimpleQuantity |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| value | Σ | 0..1 | decimal |
| comparator | Σ ?! | 0..0 | codeBinding |
| unit | Σ | 0..1 | string |
| system | Σ C | 0..1 | uri |
| code | Σ | 0..1 | code |
| rate[x] | Σ | 0..1 | |
| rateQuantity | SimpleQuantity | ||
| rateRange | Range | ||
| rateRatio | Ratio | ||
| maxDosePerPeriod | Σ C | 0..1 | Ratio |
| maxDosePerAdministration | Σ C | 0..1 | SimpleQuantity |
| maxDosePerLifetime | Σ C | 0..1 | SimpleQuantity |
| MedicationStatementCACore (MedicationStatement) | C | MedicationStatement | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| RenderedDosageInstruction | C | 0..1 | Extension(string) |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| basedOn | Σ C | 0..* | Reference(CarePlan | MedicationRequest | ServiceRequest) |
| partOf | Σ C | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Observation | Procedure) |
| status | SO Σ ?! | 1..1 | codeBinding |
| statusReason | 0..* | CodeableConcept | |
| category | Σ | 0..1 | CodeableConceptBinding |
| medication[x] | SO Σ | 1..1 | |
| medicationReference | Σ | 0..1 | Reference(MedicationCACore) |
| medicationCodeableConcept | Σ | 0..1 | CodeableConceptCACoreBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | CodingCACore |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 0..1 | uri |
| version | Σ | 0..1 | string |
| code | Σ | 0..1 | code |
| display | Σ | 0..1 | string |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| translation | C | 0..* | Extension(Complex) |
| value | 0..1 | System.String | |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| subject | SO Σ C | 1..1 | Reference(PatientCACore | Group) |
| context | Σ C | 0..1 | Reference(Encounter | EpisodeOfCare) |
| effective[x] | SO Σ | 0..1 | |
| effectiveDateTime | dateTime | ||
| effectivePeriod | Σ | 0..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | Σ C | 0..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| dateAsserted | Σ | 0..1 | dateTime |
| informationSource | C | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| derivedFrom | C | 0..* | Reference(Resource) |
| reasonCode | O | 0..* | CodeableConceptCACoreBinding |
| reasonReference | O C | 0..* | Reference(Condition | DiagnosticReport | Observation) |
| note | 0..* | Annotation | |
| dosage | O | 0..* | Dosage |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| sequence | Σ | 0..1 | integer |
| text | O Σ | 0..1 | string |
| additionalInstruction | Σ | 0..* | CodeableConcept |
| patientInstruction | Σ | 0..1 | string |
| timing | Σ | 0..1 | Timing |
| asNeeded[x] | Σ | 0..1 | |
| asNeededBoolean | boolean | ||
| asNeededCodeableConcept | CodeableConcept | ||
| site | Σ | 0..1 | CodeableConcept |
| route | Σ | 0..1 | CodeableConceptCACoreBinding |
| method | Σ | 0..1 | CodeableConcept |
| doseAndRate | Σ | 0..* | Element |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| type | Σ | 0..1 | CodeableConcept |
| dose[x] | Σ | 0..1 | Binding |
| doseRange | Range | ||
| doseQuantity | Σ C | 0..1 | SimpleQuantity |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| value | Σ | 0..1 | decimal |
| comparator | Σ ?! | 0..0 | codeBinding |
| unit | Σ | 0..1 | string |
| system | Σ C | 0..1 | uri |
| code | Σ | 0..1 | code |
| rate[x] | Σ | 0..1 | |
| rateQuantity | SimpleQuantity | ||
| rateRange | Range | ||
| rateRatio | Ratio | ||
| maxDosePerPeriod | Σ C | 0..1 | Ratio |
| maxDosePerAdministration | Σ C | 0..1 | SimpleQuantity |
| maxDosePerLifetime | Σ C | 0..1 | SimpleQuantity |
</extension>
<url value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/medicationstatement-ca-core" />
</telecom>
</telecom>
</contact>
<description value="This profile applies constraints to the MedicationStatement resource for CA Core+ to support documentation of medication usage in the pan-Canadian context." />
</jurisdiction>
<copyright value="Copyright © 2025+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy)." />
<comment value="Mapping for MedicationStatementCACore to Canadian Core Data for Interoperability (CACDI)." />
</mapping>
<definition value="A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. 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. 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. \n\nThe primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information." />
<comment value="When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered:\nMedicationStatement.status + MedicationStatement.wasNotTaken\nStatus=Active + NotTaken=T = Not currently taking\nStatus=Completed + NotTaken=T = Not taken in the past\nStatus=Intended + NotTaken=T = No intention of taking\nStatus=Active + NotTaken=F = Taking, but not as prescribed\nStatus=Active + NotTaken=F = Taking\nStatus=Intended +NotTaken= F = Will be taking (not started)\nStatus=Completed + NotTaken=F = Taken in past\nStatus=In Error + NotTaken=N/A = In Error." />
</base>
<human value="If the resource is contained in another resource, it SHALL NOT contain nested Resources" />
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated" />
<xpath value="not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))" />
</constraint>
<human value="If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource" />
<expression value="contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()" />
<xpath value="not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))" />
</constraint>
</extension>
<extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bestpractice-explanation">
<valueMarkdown value="When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time." />
</extension>
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a security label" />
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes." />
<comment value="The only time that a resource does not have an id is when it is being submitted to the server using a create operation." />
</base>
</extension>
</type>
</constraint>
</mapping>
</element>
<definition value="The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
<definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc." />
<comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc." />
</base>
</type>
</constraint>
<isModifierReason value="This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation" />
</mapping>
</element>
<comment value="Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)." />
</base>
</type>
</constraint>
</extension>
</extension>
</binding>
</mapping>
</element>
<definition value="A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety." />
<comment value="Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope." />
<comment value="This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels." />
</base>
</type>
</mapping>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<definition value="A free form textual specification generated from the input specifications as created by the provider. This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider." />
<comment value="Use of structured fields for dosage instructions is heavily encouraged by this specification to promote interoperability of patient summaries. However, this extension is provided to make implementers aware that legacy medication data may come from some systems in this format. This extension is used by PrescribeIT implementations when the system has difficulty sending very complex dosage instructions in the form of structured data. Implementers are encouraged to read the PrescribeIT Specification (https://specs.prescribeit.ca/R5.0/erx/extension-ext-medication-rendered-dosage.html) to understand the context around its use." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
<requirements value="Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them" />
</mapping>
</mapping>
</element>
<definition value="Identifiers associated with this Medication Statement that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server." />
</base>
</type>
</constraint>
</mapping>
</mapping>
<map value="II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]" />
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="A plan, proposal or order that is fulfilled in whole or in part by this event." />
<comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository." />
<requirements value="Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
<map value=".outboundRelationship[typeCode=FLFS].target[classCode=SBADM or PROC or PCPR or OBS, moodCode=RQO orPLAN or PRP]" />
</mapping>
</element>
<comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository." />
<requirements value="This should not be used when indicating which resource a MedicationStatement has been derived from. If that is the use case, then MedicationStatement.derivedFrom should be used." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
<map value=".outboundRelationship[typeCode=COMP]/target[classCode=SPLY or SBADM or PROC or OBS,moodCode=EVN]" />
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<short value="active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken" />
<definition value="A code representing the patient or other source's judgment about the state of the medication used that this statement is about. Generally, this will be active or completed." />
<comment value="MedicationStatement is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for MedicationStatement.status contains codes that assert the status of the use of the medication by the patient (for example, stopped or on hold) as well as codes that assert the status of the medication statement itself (for example, entered in error).\n\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid." />
</base>
</type>
</constraint>
<isModifierReason value="This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid" />
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="This is generally only used for "exception" statuses such as "not-taken", "on-hold", "cancelled" or "entered-in-error". The reason for performing the event at all is captured in reasonCode, not here." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." />
</base>
</type>
</constraint>
</extension>
<description value="A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered." />
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
<map value=".inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="type of medication usage"].value" />
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</discriminator>
</slicing>
<definition value="Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications." />
<comment value="The decision whether to use medicationCodeableConcept versus medicationReference is highly context dependent. Therefore, Ca Core+ defers that decision to downstream, use case specific implementation guides." />
</base>
</type>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications." />
<comment value="If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource." />
</base>
<targetProfile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/medication-ca-core" />
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text." />
<comment value="The preferred binding on this element may continue to change as pCHDCF undergoes further refinement. The point-in-time materials provided by pCHDCF to create the profiles in this release recommends the use of the PrescriptionMedicinalProduct valueSet which uses a codeSystem canonical url that is heavily implemented in production but is not the preferred codeSystem (HC-CCDD) expressed in THO. This will be addressed through pCHDCF and is expected to resolve any current differences in other pan-Canadian specifications (e.g., PS-CA) that currently utilize the HC-CCDD valueSet." />
</base>
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</constraint>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="per pCHDCF: Can be used for the international use case where a medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets. ATC is the recommended supporting classification for reporting and analysis" />
</extension>
</extension>
</extension>
<valueCanonical value="https://fhir.infoway-inforoute.ca/ValueSet/pharmaceuticalbiologicproductandsubstancecode" />
</extension>
<valueMarkdown value="per PCHDCF: The alternate value set can be used for the international use case where the medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets" />
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="A Drug Identification Number (DIN) is a computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. It uniquely identifies all drug products sold in a dosage form in Canada" />
</extension>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<comment value="Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information." />
<requirements value="Allows for alternative encodings within a code system, and translations to other code systems." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<definition value="The identification of the code system that defines the meaning of the symbol in the code." />
<comment value="The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged." />
<comment value="Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination)." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
<definition value="A representation of the meaning of the code in the system, following the rules of the system." />
<requirements value="Need to be able to carry a human-readable meaning of the code for readers that do not know the system." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<element id="MedicationStatement.medication[x]:medicationCodeableConcept.coding.display.extension:translation">
<definition value="Language translation from base language of resource to another language, used to provide translations for strings, including markdown. Generally, the type of the translation extension SHOULD match that of the element being extended." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</base>
</extension>
</extension>
</type>
</element>
<definition value="Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays)." />
<comment value="Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely." />
<requirements value="This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
<map value="fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]" />
</mapping>
</element>
</extension>
<definition value="A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user." />
<requirements value="The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository." />
</base>
<targetProfile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/patient-ca-core" />
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The encounter or episode of care that establishes the context for this MedicationStatement." />
<comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
<map value=".inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN, code="type of encounter or episode"]" />
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</discriminator>
</slicing>
<definition value="The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No)." />
<comment value="This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the "end" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text." />
</base>
</type>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No)." />
<comment value="This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the "end" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<comment value="If the low element is missing, the meaning is that the low boundary is not known." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time." />
<comment value="The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03." />
</base>
</type>
<meaningWhenMissing value="If the end of the period is missing, it means that the period is ongoing" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The date when the medication statement was asserted by the information source." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<short value="Person or organization that provided the information about the taking of this medication" />
<definition value="The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest." />
<comment value="References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
<map value=".participation[typeCode=INF].role[classCode=PAT, or codes for Practioner or Related Person (if PAT is the informer, then syntax for self-reported =true)" />
</mapping>
</element>
<definition value="Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement." />
<comment value="Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<definition value="A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text." />
<comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." />
</base>
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</constraint>
</extension>
</extension>
</extension>
<valueMarkdown value="Commonly used reason for which a medication is being ordered reference set (foundation metadata concept)" />
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="A value set for health-related conditions which can be diagnoses, the results of a clinical observation or assessment of judgment" />
</extension>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<definition value="Condition or observation that supports why the medication is being/was taken." />
<comment value="This is a reference to a condition that is the reason why the medication is being/was taken. If only a code exists, use reasonForUseCode." />
</base>
</type>
</constraint>
<expression value="reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))" />
<xpath value="not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
<map value=".outboundRelationship[typeCode=RSON]/target[classCode=OBS,moodCode=EVN, code="reason for use"].value" />
</mapping>
</mapping>
</element>
<definition value="Provides extra information about the medication statement that is not conveyed by the other attributes." />
<comment value="For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. *Annotations SHOULD NOT* be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible)." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
<map value=".inboundRelationship[typeCode=SUBJ]/source[classCode=OBS,moodCode=EVN,code="annotation"].value" />
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<comment value="The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, "from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily." It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
<requirements value="Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
<isModifierReason value="Modifier extensions are expected to modify the meaning or interpretation of the element that contains them" />
</mapping>
</mapping>
</element>
<definition value="Indicates the order in which the dosage instructions should be applied or interpreted." />
<requirements value="If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<requirements value="Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<short value="Supplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"" />
<definition value="Supplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps")." />
<comment value="Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or "immediately following drug x") should be populated in dosage.text." />
<requirements value="Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded." />
</base>
</type>
</constraint>
</extension>
<description value="A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery"." />
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing." />
<requirements value="The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept)." />
<comment value="Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not "prn" or "as needed"." />
</base>
</type>
</type>
</constraint>
</extension>
<description value="A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc." />
</binding>
</mapping>
</mapping>
<map value=".outboundRelationship[typeCode=PRCN].target[classCode=OBS, moodCode=EVN, code="as needed"].value=boolean or codable concept" />
</mapping>
</element>
<comment value="If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both." />
<requirements value="A coded specification of the anatomic site where the medication first enters the body." />
</base>
</type>
</constraint>
</extension>
<description value="A coded concept describing the site location the medicine enters into or onto the body." />
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text." />
<comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." />
<requirements value="A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body." />
</base>
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</constraint>
</extension>
</extension>
<valueCanonical value="https://fhir.infoway-inforoute.ca/ValueSet/prescriptionrouteofadministration" />
</extension>
<valueMarkdown value="Route of administration for the prescription from the PrescribeIT value set. Implementers should anticipate that data collected and or exchanged in the context of ePrescribing may contain concepts from this valueSet. While not the preferred terminology for broader pan-Canadian exchange use cases, this additional binding is surfaced to socialize the value sets that may be more commonly in use. Where multiple codings can be supplied, it is encouraged to supply the original coding alongside the pan-Canadian preferred terminology." />
</extension>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="Terminologies used often pre-coordinate this term with the route and or form of administration." />
<requirements value="A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV." />
</base>
</type>
</constraint>
</extension>
<description value="A coded concept describing the technique by which the medicine is administered." />
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<comment value="Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</discriminator>
</slicing>
<comment value="Mapping of this concept applies to the Quantity data type, however implementers should note that some systems use the Range data type to convey a similar concept when dosing is done as a range" />
<requirements value="The amount of therapeutic or other substance given at one administration event." />
</base>
</type>
</type>
</constraint>
<description value="Units of measure and/or products that convey the amount of drug to be given to a patient in one dose from the PrescribeIT value set" />
</binding>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
<comment value="The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator." />
<requirements value="The amount of therapeutic or other substance given at one administration event." />
</base>
</type>
</constraint>
</constraint>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
<definition value="The value of the measured amount. The value includes an implicit precision in the presentation of the value." />
<comment value="The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books)." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<requirements value="Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology." />
</base>
</type>
<meaningWhenMissing value="If there is no comparator, then there is no modification of the value" />
</constraint>
<isModifierReason value="This is labeled as "Is Modifier" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value" />
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</element>
</extension>
<requirements value="There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system." />
<requirements value="Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate.\n\nIt is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour." />
<requirements value="Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period." />
</base>
</type>
</type>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day"." />
<requirements value="The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours." />
</base>
</type>
</constraint>
<human value="Numerator and denominator SHALL both be present, or both are absent. If both are absent, there SHALL be some extension present" />
<expression value="(numerator.empty() xor denominator.exists()) and (numerator.exists() or extension.exists())" />
<xpath value="(count(f:numerator) = count(f:denominator)) and ((count(f:numerator) > 0) or (count(f:extension) > 0))" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg." />
<requirements value="The maximum total quantity of a therapeutic substance that may be administered to a subject per administration." />
</base>
</type>
</constraint>
</constraint>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator." />
<requirements value="The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject." />
</base>
</type>
</constraint>
</constraint>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</snapshot>
</discriminator>
</slicing>
</element>
<definition value="A free form textual specification generated from the input specifications as created by the provider. This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider." />
<comment value="Use of structured fields for dosage instructions is heavily encouraged by this specification to promote interoperability of patient summaries. However, this extension is provided to make implementers aware that legacy medication data may come from some systems in this format. This extension is used by PrescribeIT implementations when the system has difficulty sending very complex dosage instructions in the form of structured data. Implementers are encouraged to read the PrescribeIT Specification (https://specs.prescribeit.ca/R5.0/erx/extension-ext-medication-rendered-dosage.html) to understand the context around its use." />
</type>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</discriminator>
</slicing>
<comment value="The decision whether to use medicationCodeableConcept versus medicationReference is highly context dependent. Therefore, Ca Core+ defers that decision to downstream, use case specific implementation guides." />
</element>
<targetProfile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/medication-ca-core" />
</type>
</element>
<comment value="The preferred binding on this element may continue to change as pCHDCF undergoes further refinement. The point-in-time materials provided by pCHDCF to create the profiles in this release recommends the use of the PrescriptionMedicinalProduct valueSet which uses a codeSystem canonical url that is heavily implemented in production but is not the preferred codeSystem (HC-CCDD) expressed in THO. This will be addressed through pCHDCF and is expected to resolve any current differences in other pan-Canadian specifications (e.g., PS-CA) that currently utilize the HC-CCDD valueSet." />
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="per pCHDCF: Can be used for the international use case where a medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets. ATC is the recommended supporting classification for reporting and analysis" />
</extension>
</extension>
</extension>
<valueCanonical value="https://fhir.infoway-inforoute.ca/ValueSet/pharmaceuticalbiologicproductandsubstancecode" />
</extension>
<valueMarkdown value="per PCHDCF: The alternate value set can be used for the international use case where the medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets" />
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="A Drug Identification Number (DIN) is a computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. It uniquely identifies all drug products sold in a dosage form in Canada" />
</extension>
</extension>
</binding>
</mapping>
</element>
</mapping>
</element>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<targetProfile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/patient-ca-core" />
</type>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</discriminator>
</slicing>
</element>
</type>
</element>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</extension>
</extension>
<valueMarkdown value="Commonly used reason for which a medication is being ordered reference set (foundation metadata concept)" />
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="A value set for health-related conditions which can be diagnoses, the results of a clinical observation or assessment of judgment" />
</extension>
</extension>
</binding>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
</extension>
</element>
</mapping>
</element>
<profile value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core" />
</type>
</extension>
<valueCanonical value="https://fhir.infoway-inforoute.ca/ValueSet/prescriptionrouteofadministration" />
</extension>
<valueMarkdown value="Route of administration for the prescription from the PrescribeIT value set. Implementers should anticipate that data collected and or exchanged in the context of ePrescribing may contain concepts from this valueSet. While not the preferred terminology for broader pan-Canadian exchange use cases, this additional binding is surfaced to socialize the value sets that may be more commonly in use. Where multiple codings can be supplied, it is encouraged to supply the original coding alongside the pan-Canadian preferred terminology." />
</extension>
</extension>
</binding>
</mapping>
</element>
</discriminator>
</slicing>
<comment value="Mapping of this concept applies to the Quantity data type, however implementers should note that some systems use the Range data type to convey a similar concept when dosing is done as a range" />
<description value="Units of measure and/or products that convey the amount of drug to be given to a patient in one dose from the PrescribeIT value set" />
</binding>
</element>
</type>
</element>
</mapping>
</element>
</mapping>
</element>
</differential>
</StructureDefinition>
{
],
{
{
},
{
}
]
}
],
"description": "This profile applies constraints to the MedicationStatement resource for CA Core+ to support documentation of medication usage in the pan-Canadian context.",
],
"copyright": "Copyright © 2025+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy).",
{
"comment": "Mapping for MedicationStatementCACore to Canadian Core Data for Interoperability (CACDI)."
}
],
{
"definition": "A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. 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. 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. \n\nThe primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information.",
"comment": "When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered:\nMedicationStatement.status + MedicationStatement.wasNotTaken\nStatus=Active + NotTaken=T = Not currently taking\nStatus=Completed + NotTaken=T = Not taken in the past\nStatus=Intended + NotTaken=T = No intention of taking\nStatus=Active + NotTaken=F = Taking, but not as prescribed\nStatus=Active + NotTaken=F = Taking\nStatus=Intended +NotTaken= F = Will be taking (not started)\nStatus=Completed + NotTaken=F = Taken in past\nStatus=In Error + NotTaken=N/A = In Error.",
},
{
},
{
"human": "If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated",
"xpath": "not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))",
},
{
"human": "If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource",
"expression": "contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()",
"xpath": "not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))",
},
{
{
},
{
"valueMarkdown": "When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time."
}
],
},
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"comment": "The only time that a resource does not have an id is when it is being submitted to the server using a create operation.",
},
{
{
}
],
}
],
"ele-1"
],
{
}
],
]
},
{
"definition": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.",
},
],
"ele-1"
],
{
}
],
]
},
{
"definition": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.",
"comment": "Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.",
},
],
"ele-1"
],
{
}
],
"isModifierReason": "This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation",
]
},
{
"comment": "Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).",
},
],
"ele-1"
],
{
}
],
{
},
{
}
],
},
]
},
{
"definition": "A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"comment": "Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later.",
"narrative",
"html",
"xhtml",
"display"
],
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"comment": "This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.",
"inline resources",
"anonymous resources",
"contained resources"
],
},
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"definition": "A free form textual specification generated from the input specifications as created by the provider. This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.",
"comment": "Use of structured fields for dosage instructions is heavily encouraged by this specification to promote interoperability of patient summaries. However, this extension is provided to make implementers aware that legacy medication data may come from some systems in this format. This extension is used by PrescribeIT implementations when the system has difficulty sending very complex dosage instructions in the form of structured data. Implementers are encouraged to read the PrescribeIT Specification (https://specs.prescribeit.ca/R5.0/erx/extension-ext-medication-rendered-dosage.html) to understand the context around its use.",
"extensions",
"user content"
],
},
{
"http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage"
]
}
],
"ele-1"
],
{
},
{
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"requirements": "Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them",
]
},
{
"definition": "Identifiers associated with this Medication Statement that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
"map": "II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]"
},
{
},
{
},
{
},
{
}
]
},
{
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"requirements": "Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.",
},
{
"http://hl7.org/fhir/StructureDefinition/MedicationRequest",
"http://hl7.org/fhir/StructureDefinition/CarePlan",
"http://hl7.org/fhir/StructureDefinition/ServiceRequest"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
"map": ".outboundRelationship[typeCode=FLFS].target[classCode=SBADM or PROC or PCPR or OBS, moodCode=RQO orPLAN or PRP]"
}
]
},
{
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"requirements": "This should not be used when indicating which resource a MedicationStatement has been derived from. If that is the use case, then MedicationStatement.derivedFrom should be used.",
},
{
"http://hl7.org/fhir/StructureDefinition/MedicationAdministration",
"http://hl7.org/fhir/StructureDefinition/MedicationDispense",
"http://hl7.org/fhir/StructureDefinition/MedicationStatement",
"http://hl7.org/fhir/StructureDefinition/Procedure",
"http://hl7.org/fhir/StructureDefinition/Observation"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
"map": ".outboundRelationship[typeCode=COMP]/target[classCode=SPLY or SBADM or PROC or OBS,moodCode=EVN]"
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"short": "active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken",
"definition": "A code representing the patient or other source's judgment about the state of the medication used that this statement is about. Generally, this will be active or completed.",
"comment": "MedicationStatement is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for MedicationStatement.status contains codes that assert the status of the use of the medication by the patient (for example, stopped or on hold) as well as codes that assert the status of the medication statement itself (for example, entered in error).\n\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.",
},
],
"ele-1"
],
{
}
],
"isModifierReason": "This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid",
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
"comment": "This is generally only used for \"exception\" statuses such as \"not-taken\", \"on-hold\", \"cancelled\" or \"entered-in-error\". The reason for performing the event at all is captured in reasonCode, not here.",
},
],
"ele-1"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"comment": "Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
},
],
"ele-1"
],
{
}
],
{
}
],
"description": "A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered.",
},
{
},
{
},
{
},
{
},
{
},
{
"map": ".inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code=\"type of medication usage\"].value"
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
"definition": "Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.",
"comment": "The decision whether to use medicationCodeableConcept versus medicationReference is highly context dependent. Therefore, Ca Core+ defers that decision to downstream, use case specific implementation guides.",
},
{
},
{
}
],
"ele-1"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.",
"comment": "If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/medication-ca-core"
]
}
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.",
"comment": "The preferred binding on this element may continue to change as pCHDCF undergoes further refinement. The point-in-time materials provided by pCHDCF to create the profiles in this release recommends the use of the PrescriptionMedicinalProduct valueSet which uses a codeSystem canonical url that is heavily implemented in production but is not the preferred codeSystem (HC-CCDD) expressed in THO. This will be addressed through pCHDCF and is expected to resolve any current differences in other pan-Canadian specifications (e.g., PS-CA) that currently utilize the HC-CCDD valueSet.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
"ele-1"
],
{
}
],
{
},
{
{
},
{
},
{
}
],
},
{
{
},
{
},
{
"valueMarkdown": "per pCHDCF: Can be used for the international use case where a medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets. ATC is the recommended supporting classification for reporting and analysis"
}
],
},
{
{
},
{
"valueCanonical": "https://fhir.infoway-inforoute.ca/ValueSet/pharmaceuticalbiologicproductandsubstancecode"
},
{
"valueMarkdown": "per PCHDCF: The alternate value set can be used for the international use case where the medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets"
}
],
},
{
{
},
{
},
{
"valueMarkdown": "A Drug Identification Number (DIN) is a computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. It uniquely identifies all drug products sold in a dosage form in Canada"
}
],
}
],
},
{
},
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"comment": "Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.",
"requirements": "Allows for alternative encodings within a code system, and translations to other code systems.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/coding-ca-core"
]
}
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"definition": "The identification of the code system that defines the meaning of the symbol in the code.",
"comment": "The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.",
"comment": "Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
}
],
"definition": "A representation of the meaning of the code in the system, following the rules of the system.",
"requirements": "Need to be able to carry a human-readable meaning of the code for readers that do not know the system.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"id": "MedicationStatement.medication[x]:medicationCodeableConcept.coding.display.extension:translation",
"definition": "Language translation from base language of resource to another language, used to provide translations for strings, including markdown. Generally, the type of the translation extension SHOULD match that of the element being extended.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
},
{
{
},
{
}
],
}
],
},
{
"definition": "Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).",
"comment": "Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.",
"requirements": "This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
"map": "fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\\#true a [ fhir:source \"true\"; fhir:target dt:CDCoding.codingRationale\\#O ]"
}
]
},
{
{
}
],
"definition": "A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.",
"requirements": "The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/patient-ca-core",
"http://hl7.org/fhir/StructureDefinition/Group"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "The encounter or episode of care that establishes the context for this MedicationStatement.",
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
},
{
"http://hl7.org/fhir/StructureDefinition/Encounter",
"http://hl7.org/fhir/StructureDefinition/EpisodeOfCare"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
"map": ".inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN, code=\"type of encounter or episode\"]"
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
"definition": "The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No).",
"comment": "This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the \"end\" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No).",
"comment": "This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken at the time the statement is recorded, the \"end\" date will be omitted. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
},
],
"ele-1",
"per-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.",
"comment": "The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.",
},
],
"ele-1",
"per-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"short": "Person or organization that provided the information about the taking of this medication",
"definition": "The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest.",
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
},
{
"http://hl7.org/fhir/StructureDefinition/Patient",
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://hl7.org/fhir/StructureDefinition/RelatedPerson",
"http://hl7.org/fhir/StructureDefinition/Organization"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
"map": ".participation[typeCode=INF].role[classCode=PAT, or codes for Practioner or Related Person (if PAT is the informer, then syntax for self-reported =true)"
}
]
},
{
"definition": "Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement.",
"comment": "Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from.",
},
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"definition": "A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.",
"comment": "Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
"ele-1"
],
{
}
],
{
},
{
{
},
{
},
{
"valueMarkdown": "Commonly used reason for which a medication is being ordered reference set (foundation metadata concept)"
}
],
},
{
{
},
{
},
{
"valueMarkdown": "A value set for health-related conditions which can be diagnoses, the results of a clinical observation or assessment of judgment"
}
],
}
],
},
{
},
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"comment": "This is a reference to a condition that is the reason why the medication is being/was taken. If only a code exists, use reasonForUseCode.",
},
{
"http://hl7.org/fhir/StructureDefinition/Condition",
"http://hl7.org/fhir/StructureDefinition/Observation",
"http://hl7.org/fhir/StructureDefinition/DiagnosticReport"
]
}
],
"ele-1"
],
{
},
{
"expression": "reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource))",
"xpath": "not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])",
}
],
{
},
{
},
{
},
{
},
{
"map": ".outboundRelationship[typeCode=RSON]/target[classCode=OBS,moodCode=EVN, code=\"reason for use\"].value"
},
{
}
]
},
{
"definition": "Provides extra information about the medication statement that is not conveyed by the other attributes.",
"comment": "For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. *Annotations SHOULD NOT* be used to communicate \"modifying\" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
},
{
"map": ".inboundRelationship[typeCode=SUBJ]/source[classCode=OBS,moodCode=EVN,code=\"annotation\"].value"
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"comment": "The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, \"from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily.\" It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"requirements": "Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
"ele-1"
],
{
},
{
}
],
"isModifierReason": "Modifier extensions are expected to modify the meaning or interpretation of the element that contains them",
]
},
{
"definition": "Indicates the order in which the dosage instructions should be applied or interpreted.",
"requirements": "If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
"requirements": "Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"short": "Supplemental instruction or warnings to the patient - e.g. \"with meals\", \"may cause drowsiness\"",
"definition": "Supplemental instructions to the patient on how to take the medication (e.g. \"with meals\" or\"take half to one hour before food\") or warnings for the patient about the medication (e.g. \"may cause drowsiness\" or \"avoid exposure of skin to direct sunlight or sunlamps\").",
"comment": "Information about administration or preparation of the medication (e.g. \"infuse as rapidly as possibly via intraperitoneal port\" or \"immediately following drug x\") should be populated in dosage.text.",
"requirements": "Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, \"Swallow with plenty of water\" which might or might not be coded.",
},
],
"ele-1"
],
{
}
],
{
}
],
"description": "A coded concept identifying additional instructions such as \"take with water\" or \"avoid operating heavy machinery\".",
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.",
"requirements": "The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: \"Every 8 hours\"; \"Three times a day\"; \"1/2 an hour before breakfast for 10 days from 23-Dec 2011:\"; \"15 Oct 2013, 17 Oct 2013 and 1 Nov 2013\". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept).",
"comment": "Can express \"as needed\" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express \"as needed\" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not \"prn\" or \"as needed\".",
},
],
"ele-1"
],
{
}
],
{
}
],
"description": "A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example \"pain\", \"30 minutes prior to sexual intercourse\", \"on flare-up\" etc.",
},
{
},
{
},
{
"map": ".outboundRelationship[typeCode=PRCN].target[classCode=OBS, moodCode=EVN, code=\"as needed\"].value=boolean or codable concept"
}
]
},
{
"comment": "If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.",
"requirements": "A coded specification of the anatomic site where the medication first enters the body.",
},
],
"ele-1"
],
{
}
],
{
}
],
"description": "A coded concept describing the site location the medicine enters into or onto the body.",
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.",
"comment": "Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
"requirements": "A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.",
},
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
"ele-1"
],
{
}
],
{
},
{
{
},
{
},
{
"valueMarkdown": "Route of administration for the prescription from the PrescribeIT value set. Implementers should anticipate that data collected and or exchanged in the context of ePrescribing may contain concepts from this valueSet. While not the preferred terminology for broader pan-Canadian exchange use cases, this additional binding is surfaced to socialize the value sets that may be more commonly in use. Where multiple codings can be supplied, it is encouraged to supply the original coding alongside the pan-Canadian preferred terminology."
}
],
}
],
},
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
"comment": "Terminologies used often pre-coordinate this term with the route and or form of administration.",
"requirements": "A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV.",
},
],
"ele-1"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
},
],
"ele-1"
],
{
}
],
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"comment": "Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
},
],
"ele-1"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
},
{
}
]
},
{
},
"comment": "Mapping of this concept applies to the Quantity data type, however implementers should note that some systems use the Range data type to convey a similar concept when dosing is done as a range",
},
{
},
{
}
],
"ele-1"
],
{
}
],
"description": "Units of measure and/or products that convey the amount of drug to be given to a patient in one dose from the PrescribeIT value set",
},
{
},
{
},
{
}
]
},
{
{
},
{
}
],
"comment": "The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.",
},
],
"ele-1"
],
{
},
{
},
{
}
],
{
},
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"definition": "The value of the measured amount. The value includes an implicit precision in the presentation of the value.",
"comment": "The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"requirements": "Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.",
},
],
"ele-1"
],
{
}
],
"isModifierReason": "This is labeled as \"Is Modifier\" because the comparator modifies the interpretation of the value significantly. If there is no comparator, then there is no modification of the value",
{
}
],
},
{
},
{
},
{
}
]
},
{
{
}
],
"requirements": "There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
},
],
"ele-1",
"qty-3"
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency. The context of use may additionally require a code from a particular system.",
"requirements": "Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate.\n\nIt is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammer where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.",
"requirements": "Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period.",
},
{
},
{
},
{
}
],
"ele-1"
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "This is intended for use as an adjunct to the dosage when there is an upper cap. For example \"2 tablets every 4 hours to a maximum of 8/day\".",
"requirements": "The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours.",
},
],
"ele-1"
],
{
},
{
"human": "Numerator and denominator SHALL both be present, or both are absent. If both are absent, there SHALL be some extension present",
"expression": "(numerator.empty() xor denominator.exists()) and (numerator.exists() or extension.exists())",
"xpath": "(count(f:numerator) = count(f:denominator)) and ((count(f:numerator) > 0) or (count(f:extension) > 0))",
}
],
{
},
{
},
{
},
{
},
{
}
]
},
{
"comment": "This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.",
"requirements": "The maximum total quantity of a therapeutic substance that may be administered to a subject per administration.",
},
],
"ele-1"
],
{
},
{
},
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"comment": "The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.",
"requirements": "The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject.",
},
],
"ele-1"
],
{
},
{
},
{
}
],
{
},
{
},
{
},
{
}
]
}
]
},
{
}
},
{
"definition": "A free form textual specification generated from the input specifications as created by the provider. This is made up of either an 'Ad-hoc instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.",
"comment": "Use of structured fields for dosage instructions is heavily encouraged by this specification to promote interoperability of patient summaries. However, this extension is provided to make implementers aware that legacy medication data may come from some systems in this format. This extension is used by PrescribeIT implementations when the system has difficulty sending very complex dosage instructions in the form of structured data. Implementers are encouraged to read the PrescribeIT Specification (https://specs.prescribeit.ca/R5.0/erx/extension-ext-medication-rendered-dosage.html) to understand the context around its use.",
{
"http://prescribeit.ca/fhir/StructureDefinition/ext-medication-rendered-dosage"
]
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
"comment": "The decision whether to use medicationCodeableConcept versus medicationReference is highly context dependent. Therefore, Ca Core+ defers that decision to downstream, use case specific implementation guides.",
},
{
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/medication-ca-core"
]
}
]
},
{
"comment": "The preferred binding on this element may continue to change as pCHDCF undergoes further refinement. The point-in-time materials provided by pCHDCF to create the profiles in this release recommends the use of the PrescriptionMedicinalProduct valueSet which uses a codeSystem canonical url that is heavily implemented in production but is not the preferred codeSystem (HC-CCDD) expressed in THO. This will be addressed through pCHDCF and is expected to resolve any current differences in other pan-Canadian specifications (e.g., PS-CA) that currently utilize the HC-CCDD valueSet.",
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
{
{
},
{
},
{
}
],
},
{
{
},
{
},
{
"valueMarkdown": "per pCHDCF: Can be used for the international use case where a medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets. ATC is the recommended supporting classification for reporting and analysis"
}
],
},
{
{
},
{
"valueCanonical": "https://fhir.infoway-inforoute.ca/ValueSet/pharmaceuticalbiologicproductandsubstancecode"
},
{
"valueMarkdown": "per PCHDCF: The alternate value set can be used for the international use case where the medication is not available in Canada and therefore does not appear in the recommended pan-Canadian value sets"
}
],
},
{
{
},
{
},
{
"valueMarkdown": "A Drug Identification Number (DIN) is a computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. It uniquely identifies all drug products sold in a dosage form in Canada"
}
],
}
],
},
]
},
{
]
},
{
{
},
{
}
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/patient-ca-core",
"http://hl7.org/fhir/StructureDefinition/Group"
]
}
],
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
},
{
]
},
{
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
{
{
},
{
},
{
"valueMarkdown": "Commonly used reason for which a medication is being ordered reference set (foundation metadata concept)"
}
],
},
{
{
},
{
},
{
"valueMarkdown": "A value set for health-related conditions which can be diagnoses, the results of a clinical observation or assessment of judgment"
}
],
}
],
},
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
]
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
{
{
{
},
{
}
],
},
{
{
},
{
}
],
}
],
},
{
]
},
{
{
"http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/codeableconcept-ca-core"
]
}
],
{
{
},
{
},
{
"valueMarkdown": "Route of administration for the prescription from the PrescribeIT value set. Implementers should anticipate that data collected and or exchanged in the context of ePrescribing may contain concepts from this valueSet. While not the preferred terminology for broader pan-Canadian exchange use cases, this additional binding is surfaced to socialize the value sets that may be more commonly in use. Where multiple codings can be supplied, it is encouraged to supply the original coding alongside the pan-Canadian preferred terminology."
}
],
}
],
},
]
},
{
},
"comment": "Mapping of this concept applies to the Quantity data type, however implementers should note that some systems use the Range data type to convey a similar concept when dosing is done as a range",
"description": "Units of measure and/or products that convey the amount of drug to be given to a patient in one dose from the PrescribeIT value set",
}
},
{
]
},
{
]
},
{
]
}
]
}
}
Terminology bindings
| Path | Conformance | ValueSet |
|---|---|---|
| MedicationStatement.medication[x]:medicationCodeableConcept | preferred | https://fhir.infoway-inforoute.ca/ValueSet/prescriptionmedicinalproduct |
| MedicationStatement.reasonCode | preferred | https://fhir.infoway-inforoute.ca/ValueSet/medicationreasoncode |
| MedicationStatement.dosage.route | preferred | https://fhir.infoway-inforoute.ca/ValueSet/routeofadministration |
| MedicationStatement.dosage.doseAndRate.dose[x] | preferred | https://fhir.infoway-inforoute.ca/ValueSet/prescriptiondosequantityunit |
Additional Terminology Bindings
These bindings may be used in lieu of the primary bindings in the table above.
| Path | Conformance | AdditionalValueSet |
|---|---|---|
| MedicationStatement.medication[x]:medicationCodeableConcept | candidate | https://fhir.infoway-inforoute.ca/ValueSet/LicensedNaturalHealthProducts |
| MedicationStatement.reasonCode | candidate | https://fhir.infoway-inforoute.ca/ValueSet/prescriptionindicationforuse |
| MedicationStatement.dosage.route | candidate | https://fhir.infoway-inforoute.ca/ValueSet/prescriptionrouteofadministration |
Mappings to CACDI
The following tables list how the data elements from CA Core+ map to CACDI. For more information visit Mapping Logic.
| FHIR Profile Element | CACDI Element(s) |
|---|---|
| MedicationStatement.medication[x]:medicationCodeableConcept | Medication |
| MedicationStatement.medication[x]:medicationCodeableConcept.coding.system | Drug Code System URI |
| MedicationStatement.medication[x]:medicationCodeableConcept.coding.display | Drug English Description, Drug French Description |
| MedicationStatement.effective[x]:effectivePeriod.end | Medication End Date and Time |
| MedicationStatement.reasonCode | Medication Reason |
| MedicationStatement.reasonReference | Medication Reason |
| MedicationStatement.dosage.timing | Medication Timing |
| MedicationStatement.dosage.route | Medication Route of Administration |
| MedicationStatement.dosage.doseAndRate.dose[x]:doseQuantity.value | Medication Dose Value |
| MedicationStatement.dosage.doseAndRate.dose[x]:doseQuantity.unit | Medication Dose Unit of Measure |
Constraints
The following table lists constraints (from differential).