{
"description": "This profile represents the constraints applied to the MedicationStatement resource by the PS-CA project to represent a record of a medication statement in the patient summary. It is informed by the constraints of the [MedicationStatement IPS-UV profile](http://hl7.org/fhir/uv/ips/StructureDefinition-MedicationStatement-uv-ips.html) and the [Canadian Baseline Profile](http://build.fhir.org/ig/HL7-Canada/ca-baseline/branches/master/StructureDefinition-profile-medicationstatement.html) to allow for cross-border and cross-jurisdiction sharing of Medication Summary information.",
"_filename": "structuredefinition-profile-medicationstatement-ca-ps.json",
"package_name": "ca.infoway.io.psca",
"date": "2024-04-09T00:00:00-08:00",
"derivation": "constraint",
"publisher": null,
"fhirVersion": "4.0.1",
"name": "MedicationStatementPSCA",
"abstract": false,
"copyright": "Copyright © 2024+ 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).",
"type": "MedicationStatement",
"experimental": "false",
"resourceType": "StructureDefinition",
"title": "Medication Statement (PS-CA)",
"package_version": "2.0.0-DFT-Ballot-alpha-1",
"status": "draft",
"id": "6a608a9e-6d91-43c4-8e0c-12cac89bfaa5",
"kind": "resource",
"url": "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/medicationstatement-ca-ps",
"version": null,
"differential": {
"element": [ {
"id": "MedicationStatement",
"path": "MedicationStatement",
"comment": "Jurisdictions mapping prescription data into FHIR profiles for the patient summary should use the MedicationRequest resource. Use of the MedicationStatement profile should be reserved for communicating a statement about the patient's usage of the medication that is ultimately provided by a patient, significant other, or a clinician."
}, {
"id": "MedicationStatement.extension:RenderedDosageInstruction",
"max": "1",
"path": "MedicationStatement.extension",
"type": [ {
"code": "Extension",
"profile": [ "http://prescribeit.ca/fhir/StructureDefinition/ext-rendered-dosage-instruction" ]
} ],
"short": "Extension for representing rendered dosage instruction.",
"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.",
"sliceName": "RenderedDosageInstruction",
"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."
}, {
"id": "MedicationStatement.status",
"path": "MedicationStatement.status",
"comment": "IPS Note: The entered-in-error concept is not permitted. Implementers should be aware that the shift to R5 MedicationUsage will also involve a new value set for status that is expected to be constrained to: recorded, entered-in-error, and draft.",
"mustSupport": true
}, {
"id": "MedicationStatement.medication[x]",
"path": "MedicationStatement.medication[x]",
"type": [ {
"code": "Reference",
"targetProfile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/medication-ca-ps" ]
}, {
"code": "CodeableConcept",
"profile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/CodeableConcept-medication-ca-ps" ]
} ],
"binding": {
"strength": "preferred",
"valueSet": "http://fhir.infoway-inforoute.ca/io/psca/ValueSet/hc-CCDD"
},
"definition": "Identifies the medication being administered or the assertion of no known medications. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code. To improve global interoperability is strongly encouraged that the reference to a medication resource is used, limiting the usage of the medicationCodeableConcept only to the cases in which no other information than a simple code is available.",
"mustSupport": true
}, {
"id": "MedicationStatement.subject",
"path": "MedicationStatement.subject",
"type": [ {
"code": "Reference",
"targetProfile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/patient-ca-ps" ]
} ],
"mustSupport": true
}, {
"id": "MedicationStatement.subject.reference",
"min": 1,
"path": "MedicationStatement.subject.reference",
"mustSupport": true
}, {
"id": "MedicationStatement.effective[x]",
"max": "1",
"min": 1,
"path": "MedicationStatement.effective[x]",
"mustSupport": true
}, {
"id": "MedicationStatement.effective[x].extension",
"path": "MedicationStatement.effective[x].extension",
"slicing": {
"rules": "open",
"description": "Extensions are always sliced by (at least) url",
"discriminator": [ {
"path": "url",
"type": "value"
} ]
}
}, {
"path": "MedicationStatement.effective[x].extension",
"definition": "Provides a reason why the effectiveTime is missing.",
"short": "effective[x] absence reason",
"type": [ {
"code": "Extension",
"profile": [ "http://hl7.org/fhir/StructureDefinition/data-absent-reason" ]
} ],
"mustSupport": true,
"sliceName": "data-absent-reason",
"max": "1",
"id": "MedicationStatement.effective[x].extension:data-absent-reason",
"comment": "While the IPS-UV specification considers this a Must Support element, many systems will not have a field within their data dictionaries that directly corresponds to dataAbsentReason, however it is recommended that systems be able to support the communication of this concept across a number of clinical profiles where population of the clinical element is crucial to clinical interpretation and use. Further feedback is required on whether these systems are still expected to be able to demonstrate they can construct this element when developing the patient summary instance"
}, {
"id": "MedicationStatement.dosage",
"path": "MedicationStatement.dosage",
"mustSupport": true
}, {
"id": "MedicationStatement.dosage.text",
"path": "MedicationStatement.dosage.text",
"mustSupport": true
}, {
"id": "MedicationStatement.dosage.timing",
"path": "MedicationStatement.dosage.timing",
"comment": "IPS-UV flags this as a Must Support element. It is not currently flagged as Must Support in PS-CA, as stakeholders have indicated the element may not be supported by the majority of systems today. Systems that do support the element are encouraged to include it in generated Patient Summary documents, and support it when received. Vendors should expect that some jurisdictions may add a Must Support requirement within the context of their own jurisdictional content."
}, {
"id": "MedicationStatement.dosage.route",
"path": "MedicationStatement.dosage.route",
"type": [ {
"code": "CodeableConcept",
"profile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/CodeableConcept-ca-ps" ]
} ],
"binding": {
"strength": "preferred",
"valueSet": "https://fhir.infoway-inforoute.ca/ValueSet/routeofadministration",
"extension": [ {
"url": "http://hl7.org/fhir/tools/StructureDefinition/additional-binding",
"extension": [ {
"url": "purpose",
"valueCode": "candidate"
}, {
"url": "valueSet",
"valueCanonical": "http://hl7.org/fhir/uv/ips/ValueSet/medicine-route-of-administration"
}, {
"url": "documentation",
"valueMarkdown": "EDQM Standards Terms for route."
} ]
}, {
"url": "http://hl7.org/fhir/tools/StructureDefinition/additional-binding",
"extension": [ {
"url": "purpose",
"valueCode": "candidate"
}, {
"url": "valueSet",
"valueCanonical": "https://fhir.infoway-inforoute.ca/ValueSet/prescriptionrouteofadministration"
}, {
"url": "documentation",
"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."
} ]
} ],
"description": "SCTCA Route of Administration"
},
"comment": "See additionalBinding extension."
} ]
},
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/MedicationStatement"
}