HdBe-MedicationUse2
Profile | Description | Status | URL |
---|---|---|---|
HdBe-MedicationUse2 | MedicationUse2 is a statement on the historic, current or intended use of a certain medicine. | draft | https://fhir.healthdata.be/StructureDefinition/HdBe-MedicationUse2 |
MedicationStatement | I | MedicationStatement | Element idMedicationStatement MedicationUse Alternate namesMedicatieGebruik DefinitionA 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. The 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. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered: MedicationStatement.status + MedicationStatement.wasNotTaken
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationStatement.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationStatement.implicitRules A set of rules under which this content was created DefinitionA 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. 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.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationStatement.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idMedicationStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
renderedDosageInstruction | I | 0..1 | Extension(string) | Element idMedicationStatement.extension:renderedDosageInstruction Optional Extensions Element Alternate namesextensions, user content DefinitionPre-adopt from FHIR R5 of the 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. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction
| |
value[x] | 0..1 | Element idMedicationStatement.extension:renderedDosageInstruction.value[x] Value of extension DefinitionThe full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses. The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.
| ||
valueString | string | There are no (further) constraints on this element Data type | ||
prescriber | I | 0..1 | Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) | Element idMedicationStatement.extension:prescriber Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) Extension URLhttps://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber
| |
value[x] | I | 0..1 | Element idMedicationStatement.extension:prescriber.value[x] Prescriber Alternate namesVoorschrijver DefinitionThe health professional that entered the medication agreement with the patient. Each occurrence of the CBB HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of HdBe-HealthProfessional-PractitionerRole) and a Practitioner resource (instance of HdBe-HealthProfessional-Practitioner). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource.
| |
valueReference | pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | There are no (further) constraints on this element Data type pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | ||
asAgreedIndicator | I | 0..1 | Extension(boolean) | Element idMedicationStatement.extension:asAgreedIndicator Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator
| |
value[x] | 0..1 | Element idMedicationStatement.extension:asAgreedIndicator.value[x] AsAgreedIndicator Alternate namesVolgensAfspraakIndicator DefinitionIs the medicine used as outlined in the medication agreement?
| ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
stopType | ?! I | 0..1 | Extension(CodeableConcept) | Element idMedicationStatement.modifierExtension:stopType Optional Extensions Element Alternate namesextensions, user content DefinitionThis StopType ModifierExtension works differently than the For example: suppose you want the patient to stop taking medication definitively three days from today. This is a stop medication agreement with a StopType of definitive. However today, tomorrow and the day after tomorrow the 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-StopType Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-StopType
| |
value[x] | 0..1 | Binding | Element idMedicationStatement.modifierExtension:stopType.value[x] MedicationUseStopType Alternate namesMedicatieGebruikStopType DefinitionStop type, the manner in which this medication is discontinued (temporary or definitive). MedicationAgreementStopType, AdministrationAgreementStopType and MedicationUseStopType all have a bound ValueSet that contain the exact same StopType values. These are represented in the CBB with the same Valueset. This MedicationStopType is used to bind to this extension and reusing this extension for all three concepts. StopType values, based on the valueset named MedicatioStopType, which are applicable for StopType in MedicationAgreement, AdministrationAgreement and MedicationUse.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
repeatPeriodCyclicalSchedule | ?! I | 0..1 | Extension(Duration) | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule
| |
value[x] | 0..1 | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.value[x] RepeatPeriodCyclicalSchedule Alternate namesHerhaalperiodeCyclischSchema DefinitionThe repeated period in a cyclical schedule (of one or more dosing instructions). A cyclic schedule is noted in days, the corresponding dosing duration is also in days. Examples of a cyclical schedule:
| ||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idMedicationStatement.identifier External identifier DefinitionIdentifiers 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. This is a business identifier, not a resource identifier.
|
basedOn | Σ I | 0..* | Reference(MedicationRequest | CarePlan | ServiceRequest) | There are no (further) constraints on this element Element idMedicationStatement.basedOn Fulfils plan, proposal or order DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. 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. Reference(MedicationRequest | CarePlan | ServiceRequest) Constraints
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) | There are no (further) constraints on this element Element idMedicationStatement.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. 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. 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. Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) Constraints
|
status | Σ ?! | 1..1 | codeBinding | Element idMedicationStatement.status UseIndicator / MedicationUseStopType / PeriodOfUse Alternate namesMedicatieGebruikStopType, GebruikIndicator, Gebruiksperiode DefinitionStatus may contain information on the stop type, the manner in which this medication is discontinued (temporary or definitive) and if the medicine is used or not. This element is mapped to the CBB concept UseIndicator and implicitly to MedicationUseStopType and PeriodOfUse. Unless a more appropriate status is recorded, the following guidance applies:
Use ConceptMap 'MedicationStopType-to-MedicationStatementStatus' to translate CBB terminology to profile terminology in ValueSet 'Medication Status Codes'. Permitted Values MedicationStopType_to_MedicationStatementStatus Constraints
|
statusReason | 0..* | CodeableConceptBinding | Element idMedicationStatement.statusReason ReasonForChangeOrDiscontinuationOfUse Alternate namesRedenWijzigenOfStoppenGebruik DefinitionReason for changing or discontinuing use of medication. 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. A coded concept indicating the reason for the status of the statement.
| |
category | Σ | 1..1 | CodeableConceptBindingPattern | Element idMedicationStatement.category Type of medication usage DefinitionIndicates where the medication is expected to be consumed or administered. 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. A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered.
{ "coding": [ { "system": "http://snomed.info/sct", "code": "422979000" } ] }
|
medication[x] | Σ | 1..1 | Element idMedicationStatement.medication[x] What medication was taken DefinitionIdentifies 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. 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. Unordered, Open, by $this(Type) BindingA coded concept identifying the substance or product being taken.
| |
medicationCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
medicationReference | Σ | 0..1 | Reference(Medication | HdBe-PharmaceuticalProduct) | Element idMedicationStatement.medication[x]:medicationReference ProductUsed Alternate namesGebruiksproduct DefinitionThe product used. This is usually medication. Food, blood products, aids and bandages do not strictly fall under the category of medication, but can be recorded as well. In principle, this will be the prescribed product, but the product used may differ from the prescribed product. 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. Reference(Medication | HdBe-PharmaceuticalProduct) Constraints
|
subject | Σ I | 1..1 | Reference(Group | HdBe-Patient) | Element idMedicationStatement.subject Who is/was taking the medication DefinitionThe person, animal or group who is/was taking the medication. 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. Reference(Group | HdBe-Patient) Constraints
|
context | Σ I | 0..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idMedicationStatement.context Encounter / Episode associated with MedicationStatement DefinitionThe encounter or episode of care that establishes the context for this MedicationStatement. 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. Reference(Encounter | EpisodeOfCare) Constraints
|
effective[x] | Σ | 0..1 | Element idMedicationStatement.effective[x] The date/time or interval when the medication is/was/will be taken DefinitionThe 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). 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. Unordered, Open, by $this(Type) Constraints
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||
effectivePeriod | Σ I | 0..1 | HdBe-TimeInterval | Element idMedicationStatement.effective[x]:effectivePeriod PeriodOfUse Alternate namesGebruiksperiode DefinitionMedication use can be recorded for a certain moment or over a certain period. Thus, medication use can be recorded multiple times during the use of medication. The usage period is the period or moment over which the data is recorded. Start date: This is the time at which the agreement was to take effect (or took effect or will take effect). End date: The time at which the period of use ends (or ended or will end). To avoid confusion between 'to' and 'up to', the submission of time is always mandatory for the end date. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
dateAsserted | Σ | 0..1 | dateTime | Element idMedicationStatement.dateAsserted MedicationUseDateTime Alternate namesMedicatieGebruikDatumTijd DefinitionDate on which this use is entered.
|
informationSource | I | 0..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idMedicationStatement.informationSource Person or organization that provided the information about the taking of this medication DefinitionThe 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. 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. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Constraints
|
derivedFrom | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationStatement.derivedFrom Additional supporting information DefinitionAllows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. 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.
|
reasonCode | 0..* | CodeableConcept | Element idMedicationStatement.reasonCode Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. Unordered, Open, by text(Exists) BindingA coded concept identifying why the medication is being taken.
| |
reasonForUse | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. A coded concept identifying why the medication is being taken.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
text | Σ | 1..1 | string | Element idMedicationStatement.reasonCode:reasonForUse.text ReasonForUse Alternate namesRedenGebruik DefinitionThe reason for using the medication, particularly in self-care medicine purchased by the patient themselves. 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. Very often the text is the same as a displayName of one of the codings.
|
reasonReference | I | 0..* | Reference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationStatement.reasonReference Condition or observation that supports why the medication is being/was taken DefinitionCondition or observation that supports why the medication is being/was taken. 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. Reference(Condition | Observation | DiagnosticReport) Constraints
|
note | 0..1 | Annotation | There are no (further) constraints on this element Element idMedicationStatement.note Further information about the statement DefinitionProvides extra information about the medication statement that is not conveyed by the other attributes. 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).
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idMedicationStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idMedicationStatement.note.text Comment Alternate namesToelichting DefinitionComments on the medication use. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
dosage | 0..* | HdBe-InstructionsForUse.DosageInstructions | Element idMedicationStatement.dosage DosingInstructions / InstructionsForUse Alternate namesDoseerinstructie, Gebruiksinstructie DefinitionInstructions for the use of the medication, e.g. dose and route of administration. In the event of medication use, this is the pattern of use established by the patient or which the patient followed. This element mostly represents the DosingInstructions container from CBB InstructionsForUse, but also includes the AdditionalInstructions and RouteOfAdministration concepts, which are normally placed on the same level as this container. As a result, these concepts are duplicated in every repetition of this element, even though these concepts should be present just once according to the CBB. The RepeatPeriodCyclicalSchedule and Description elements of the CBB are not represented in this profile. When a HdBe profile contains a InstructionsForUse.DosageInstructions datatype, the RepeatPeriodCyclicalSchedule and Description elements are separately added to this profile as well. This element does not contain a mapping to the Dosage container from CBB InstructionsForUse. However, the child concepts of Dosage are all mapped. Multiple Dosage instances are represented by another DosingInstructions that contains a similiar SequenceNumber. HdBe-InstructionsForUse.DosageInstructions Constraints
|
MedicationStatement | I | MedicationStatement | Element idMedicationStatement MedicationUse Alternate namesMedicatieGebruik DefinitionA 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. The 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. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered: MedicationStatement.status + MedicationStatement.wasNotTaken
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationStatement.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationStatement.implicitRules A set of rules under which this content was created DefinitionA 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. 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.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationStatement.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idMedicationStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
renderedDosageInstruction | I | 0..1 | Extension(string) | Element idMedicationStatement.extension:renderedDosageInstruction Optional Extensions Element Alternate namesextensions, user content DefinitionPre-adopt from FHIR R5 of the 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. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction
| |
value[x] | 0..1 | Element idMedicationStatement.extension:renderedDosageInstruction.value[x] Value of extension DefinitionThe full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses. The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.
| ||
valueString | string | There are no (further) constraints on this element Data type | ||
prescriber | I | 0..1 | Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) | Element idMedicationStatement.extension:prescriber Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) Extension URLhttps://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber
| |
value[x] | I | 0..1 | Element idMedicationStatement.extension:prescriber.value[x] Prescriber Alternate namesVoorschrijver DefinitionThe health professional that entered the medication agreement with the patient. Each occurrence of the CBB HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of HdBe-HealthProfessional-PractitionerRole) and a Practitioner resource (instance of HdBe-HealthProfessional-Practitioner). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource.
| |
valueReference | pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | There are no (further) constraints on this element Data type pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | ||
asAgreedIndicator | I | 0..1 | Extension(boolean) | Element idMedicationStatement.extension:asAgreedIndicator Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator
| |
value[x] | 0..1 | Element idMedicationStatement.extension:asAgreedIndicator.value[x] AsAgreedIndicator Alternate namesVolgensAfspraakIndicator DefinitionIs the medicine used as outlined in the medication agreement?
| ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
stopType | ?! I | 0..1 | Extension(CodeableConcept) | Element idMedicationStatement.modifierExtension:stopType Optional Extensions Element Alternate namesextensions, user content DefinitionThis StopType ModifierExtension works differently than the For example: suppose you want the patient to stop taking medication definitively three days from today. This is a stop medication agreement with a StopType of definitive. However today, tomorrow and the day after tomorrow the 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-StopType Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-StopType
| |
value[x] | 0..1 | Binding | Element idMedicationStatement.modifierExtension:stopType.value[x] MedicationUseStopType Alternate namesMedicatieGebruikStopType DefinitionStop type, the manner in which this medication is discontinued (temporary or definitive). MedicationAgreementStopType, AdministrationAgreementStopType and MedicationUseStopType all have a bound ValueSet that contain the exact same StopType values. These are represented in the CBB with the same Valueset. This MedicationStopType is used to bind to this extension and reusing this extension for all three concepts. StopType values, based on the valueset named MedicatioStopType, which are applicable for StopType in MedicationAgreement, AdministrationAgreement and MedicationUse.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
repeatPeriodCyclicalSchedule | ?! I | 0..1 | Extension(Duration) | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule
| |
value[x] | 0..1 | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.value[x] RepeatPeriodCyclicalSchedule Alternate namesHerhaalperiodeCyclischSchema DefinitionThe repeated period in a cyclical schedule (of one or more dosing instructions). A cyclic schedule is noted in days, the corresponding dosing duration is also in days. Examples of a cyclical schedule:
| ||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idMedicationStatement.identifier External identifier DefinitionIdentifiers 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. This is a business identifier, not a resource identifier.
|
basedOn | Σ I | 0..* | Reference(MedicationRequest | CarePlan | ServiceRequest) | There are no (further) constraints on this element Element idMedicationStatement.basedOn Fulfils plan, proposal or order DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. 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. Reference(MedicationRequest | CarePlan | ServiceRequest) Constraints
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) | There are no (further) constraints on this element Element idMedicationStatement.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. 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. 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. Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) Constraints
|
status | Σ ?! | 1..1 | codeBinding | Element idMedicationStatement.status UseIndicator / MedicationUseStopType / PeriodOfUse Alternate namesMedicatieGebruikStopType, GebruikIndicator, Gebruiksperiode DefinitionStatus may contain information on the stop type, the manner in which this medication is discontinued (temporary or definitive) and if the medicine is used or not. This element is mapped to the CBB concept UseIndicator and implicitly to MedicationUseStopType and PeriodOfUse. Unless a more appropriate status is recorded, the following guidance applies:
Use ConceptMap 'MedicationStopType-to-MedicationStatementStatus' to translate CBB terminology to profile terminology in ValueSet 'Medication Status Codes'. Permitted Values MedicationStopType_to_MedicationStatementStatus Constraints
|
statusReason | 0..* | CodeableConceptBinding | Element idMedicationStatement.statusReason ReasonForChangeOrDiscontinuationOfUse Alternate namesRedenWijzigenOfStoppenGebruik DefinitionReason for changing or discontinuing use of medication. 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. A coded concept indicating the reason for the status of the statement.
| |
category | Σ | 1..1 | CodeableConceptBindingPattern | Element idMedicationStatement.category Type of medication usage DefinitionIndicates where the medication is expected to be consumed or administered. 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. A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered.
{ "coding": [ { "system": "http://snomed.info/sct", "code": "422979000" } ] }
|
medication[x] | Σ | 1..1 | Element idMedicationStatement.medication[x] What medication was taken DefinitionIdentifies 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. 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. Unordered, Open, by $this(Type) BindingA coded concept identifying the substance or product being taken.
| |
medicationCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
medicationReference | Σ | 0..1 | Reference(Medication | HdBe-PharmaceuticalProduct) | Element idMedicationStatement.medication[x]:medicationReference ProductUsed Alternate namesGebruiksproduct DefinitionThe product used. This is usually medication. Food, blood products, aids and bandages do not strictly fall under the category of medication, but can be recorded as well. In principle, this will be the prescribed product, but the product used may differ from the prescribed product. 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. Reference(Medication | HdBe-PharmaceuticalProduct) Constraints
|
subject | Σ I | 1..1 | Reference(Group | HdBe-Patient) | Element idMedicationStatement.subject Who is/was taking the medication DefinitionThe person, animal or group who is/was taking the medication. 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. Reference(Group | HdBe-Patient) Constraints
|
context | Σ I | 0..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idMedicationStatement.context Encounter / Episode associated with MedicationStatement DefinitionThe encounter or episode of care that establishes the context for this MedicationStatement. 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. Reference(Encounter | EpisodeOfCare) Constraints
|
effective[x] | Σ | 0..1 | Element idMedicationStatement.effective[x] The date/time or interval when the medication is/was/will be taken DefinitionThe 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). 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. Unordered, Open, by $this(Type) Constraints
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||
effectivePeriod | Σ I | 0..1 | HdBe-TimeInterval | Element idMedicationStatement.effective[x]:effectivePeriod PeriodOfUse Alternate namesGebruiksperiode DefinitionMedication use can be recorded for a certain moment or over a certain period. Thus, medication use can be recorded multiple times during the use of medication. The usage period is the period or moment over which the data is recorded. Start date: This is the time at which the agreement was to take effect (or took effect or will take effect). End date: The time at which the period of use ends (or ended or will end). To avoid confusion between 'to' and 'up to', the submission of time is always mandatory for the end date. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
dateAsserted | Σ | 0..1 | dateTime | Element idMedicationStatement.dateAsserted MedicationUseDateTime Alternate namesMedicatieGebruikDatumTijd DefinitionDate on which this use is entered.
|
informationSource | I | 0..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idMedicationStatement.informationSource Person or organization that provided the information about the taking of this medication DefinitionThe 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. 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. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Constraints
|
derivedFrom | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationStatement.derivedFrom Additional supporting information DefinitionAllows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. 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.
|
reasonCode | 0..* | CodeableConcept | Element idMedicationStatement.reasonCode Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. Unordered, Open, by text(Exists) BindingA coded concept identifying why the medication is being taken.
| |
reasonForUse | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. A coded concept identifying why the medication is being taken.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
text | Σ | 1..1 | string | Element idMedicationStatement.reasonCode:reasonForUse.text ReasonForUse Alternate namesRedenGebruik DefinitionThe reason for using the medication, particularly in self-care medicine purchased by the patient themselves. 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. Very often the text is the same as a displayName of one of the codings.
|
reasonReference | I | 0..* | Reference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationStatement.reasonReference Condition or observation that supports why the medication is being/was taken DefinitionCondition or observation that supports why the medication is being/was taken. 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. Reference(Condition | Observation | DiagnosticReport) Constraints
|
note | 0..1 | Annotation | There are no (further) constraints on this element Element idMedicationStatement.note Further information about the statement DefinitionProvides extra information about the medication statement that is not conveyed by the other attributes. 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).
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idMedicationStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idMedicationStatement.note.text Comment Alternate namesToelichting DefinitionComments on the medication use. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
dosage | 0..* | HdBe-InstructionsForUse.DosageInstructions | Element idMedicationStatement.dosage DosingInstructions / InstructionsForUse Alternate namesDoseerinstructie, Gebruiksinstructie DefinitionInstructions for the use of the medication, e.g. dose and route of administration. In the event of medication use, this is the pattern of use established by the patient or which the patient followed. This element mostly represents the DosingInstructions container from CBB InstructionsForUse, but also includes the AdditionalInstructions and RouteOfAdministration concepts, which are normally placed on the same level as this container. As a result, these concepts are duplicated in every repetition of this element, even though these concepts should be present just once according to the CBB. The RepeatPeriodCyclicalSchedule and Description elements of the CBB are not represented in this profile. When a HdBe profile contains a InstructionsForUse.DosageInstructions datatype, the RepeatPeriodCyclicalSchedule and Description elements are separately added to this profile as well. This element does not contain a mapping to the Dosage container from CBB InstructionsForUse. However, the child concepts of Dosage are all mapped. Multiple Dosage instances are represented by another DosingInstructions that contains a similiar SequenceNumber. HdBe-InstructionsForUse.DosageInstructions Constraints
|
MedicationStatement | I | MedicationStatement | Element idMedicationStatement MedicationUse Alternate namesMedicatieGebruik DefinitionA 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. The 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. When interpreting a medicationStatement, the value of the status and NotTaken needed to be considered: MedicationStatement.status + MedicationStatement.wasNotTaken
| |
id | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationStatement.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationStatement.implicitRules A set of rules under which this content was created DefinitionA 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. 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.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationStatement.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationStatement.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idMedicationStatement.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
renderedDosageInstruction | I | 0..1 | Extension(string) | Element idMedicationStatement.extension:renderedDosageInstruction Optional Extensions Element Alternate namesextensions, user content DefinitionPre-adopt from FHIR R5 of the 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. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:renderedDosageInstruction.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-RenderedDosageInstruction
| |
value[x] | 0..1 | Element idMedicationStatement.extension:renderedDosageInstruction.value[x] Value of extension DefinitionThe full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses. The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.
| ||
valueString | string | There are no (further) constraints on this element Data type | ||
prescriber | I | 0..1 | Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) | Element idMedicationStatement.extension:prescriber Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. Extension(pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner)) Extension URLhttps://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:prescriber.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.Prescriber
| |
value[x] | I | 0..1 | Element idMedicationStatement.extension:prescriber.value[x] Prescriber Alternate namesVoorschrijver DefinitionThe health professional that entered the medication agreement with the patient. Each occurrence of the CBB HealthProfessional is normally represented by two FHIR resources: a PractitionerRole resource (instance of HdBe-HealthProfessional-PractitionerRole) and a Practitioner resource (instance of HdBe-HealthProfessional-Practitioner). The Practitioner resource is referenced from the PractitionerRole instance. For this reason, sending systems should fill the reference to the PractitionerRole instance here, and not the Practitioner resource.
| |
valueReference | pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | There are no (further) constraints on this element Data type pattern HealthProfessional Reference(HdBe-HealthProfessional PractitionerRole | HdBe-HealthProfessional Practitioner) | ||
asAgreedIndicator | I | 0..1 | Extension(boolean) | Element idMedicationStatement.extension:asAgreedIndicator Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.extension:asAgreedIndicator.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-MedicationUse2.AsAgreedIndicator
| |
value[x] | 0..1 | Element idMedicationStatement.extension:asAgreedIndicator.value[x] AsAgreedIndicator Alternate namesVolgensAfspraakIndicator DefinitionIs the medicine used as outlined in the medication agreement?
| ||
valueBoolean | boolean | There are no (further) constraints on this element Data type | ||
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
stopType | ?! I | 0..1 | Extension(CodeableConcept) | Element idMedicationStatement.modifierExtension:stopType Optional Extensions Element Alternate namesextensions, user content DefinitionThis StopType ModifierExtension works differently than the For example: suppose you want the patient to stop taking medication definitively three days from today. This is a stop medication agreement with a StopType of definitive. However today, tomorrow and the day after tomorrow the 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-StopType Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:stopType.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-StopType
| |
value[x] | 0..1 | Binding | Element idMedicationStatement.modifierExtension:stopType.value[x] MedicationUseStopType Alternate namesMedicatieGebruikStopType DefinitionStop type, the manner in which this medication is discontinued (temporary or definitive). MedicationAgreementStopType, AdministrationAgreementStopType and MedicationUseStopType all have a bound ValueSet that contain the exact same StopType values. These are represented in the CBB with the same Valueset. This MedicationStopType is used to bind to this extension and reusing this extension for all three concepts. StopType values, based on the valueset named MedicatioStopType, which are applicable for StopType in MedicationAgreement, AdministrationAgreement and MedicationUse.
| |
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
repeatPeriodCyclicalSchedule | ?! I | 0..1 | Extension(Duration) | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule Optional Extensions Element Alternate namesextensions, user content DefinitionOptional Extension Element - found in all resources. 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. 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. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule Constraints
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://fhir.healthdata.be/StructureDefinition/ext-InstructionsForUse.RepeatPeriodCyclicalSchedule
| |
value[x] | 0..1 | Element idMedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.value[x] RepeatPeriodCyclicalSchedule Alternate namesHerhaalperiodeCyclischSchema DefinitionThe repeated period in a cyclical schedule (of one or more dosing instructions). A cyclic schedule is noted in days, the corresponding dosing duration is also in days. Examples of a cyclical schedule:
| ||
valueDuration | Duration | There are no (further) constraints on this element Data type | ||
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idMedicationStatement.identifier External identifier DefinitionIdentifiers 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. This is a business identifier, not a resource identifier.
|
basedOn | Σ I | 0..* | Reference(MedicationRequest | CarePlan | ServiceRequest) | There are no (further) constraints on this element Element idMedicationStatement.basedOn Fulfils plan, proposal or order DefinitionA plan, proposal or order that is fulfilled in whole or in part by this event. Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon. 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. Reference(MedicationRequest | CarePlan | ServiceRequest) Constraints
|
partOf | Σ I | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) | There are no (further) constraints on this element Element idMedicationStatement.partOf Part of referenced event DefinitionA larger event of which this particular event is a component or step. 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. 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. Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation) Constraints
|
status | Σ ?! | 1..1 | codeBinding | Element idMedicationStatement.status UseIndicator / MedicationUseStopType / PeriodOfUse Alternate namesMedicatieGebruikStopType, GebruikIndicator, Gebruiksperiode DefinitionStatus may contain information on the stop type, the manner in which this medication is discontinued (temporary or definitive) and if the medicine is used or not. This element is mapped to the CBB concept UseIndicator and implicitly to MedicationUseStopType and PeriodOfUse. Unless a more appropriate status is recorded, the following guidance applies:
Use ConceptMap 'MedicationStopType-to-MedicationStatementStatus' to translate CBB terminology to profile terminology in ValueSet 'Medication Status Codes'. Permitted Values MedicationStopType_to_MedicationStatementStatus Constraints
|
statusReason | 0..* | CodeableConceptBinding | Element idMedicationStatement.statusReason ReasonForChangeOrDiscontinuationOfUse Alternate namesRedenWijzigenOfStoppenGebruik DefinitionReason for changing or discontinuing use of medication. 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. A coded concept indicating the reason for the status of the statement.
| |
category | Σ | 1..1 | CodeableConceptBindingPattern | Element idMedicationStatement.category Type of medication usage DefinitionIndicates where the medication is expected to be consumed or administered. 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. A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered.
{ "coding": [ { "system": "http://snomed.info/sct", "code": "422979000" } ] }
|
medication[x] | Σ | 1..1 | Element idMedicationStatement.medication[x] What medication was taken DefinitionIdentifies 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. 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. Unordered, Open, by $this(Type) BindingA coded concept identifying the substance or product being taken.
| |
medicationCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||
medicationReference | Σ | 0..1 | Reference(Medication | HdBe-PharmaceuticalProduct) | Element idMedicationStatement.medication[x]:medicationReference ProductUsed Alternate namesGebruiksproduct DefinitionThe product used. This is usually medication. Food, blood products, aids and bandages do not strictly fall under the category of medication, but can be recorded as well. In principle, this will be the prescribed product, but the product used may differ from the prescribed product. 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. Reference(Medication | HdBe-PharmaceuticalProduct) Constraints
|
subject | Σ I | 1..1 | Reference(Group | HdBe-Patient) | Element idMedicationStatement.subject Who is/was taking the medication DefinitionThe person, animal or group who is/was taking the medication. 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. Reference(Group | HdBe-Patient) Constraints
|
context | Σ I | 0..1 | Reference(Encounter | EpisodeOfCare) | There are no (further) constraints on this element Element idMedicationStatement.context Encounter / Episode associated with MedicationStatement DefinitionThe encounter or episode of care that establishes the context for this MedicationStatement. 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. Reference(Encounter | EpisodeOfCare) Constraints
|
effective[x] | Σ | 0..1 | Element idMedicationStatement.effective[x] The date/time or interval when the medication is/was/will be taken DefinitionThe 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). 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. Unordered, Open, by $this(Type) Constraints
| |
effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||
effectivePeriod | Σ I | 0..1 | HdBe-TimeInterval | Element idMedicationStatement.effective[x]:effectivePeriod PeriodOfUse Alternate namesGebruiksperiode DefinitionMedication use can be recorded for a certain moment or over a certain period. Thus, medication use can be recorded multiple times during the use of medication. The usage period is the period or moment over which the data is recorded. Start date: This is the time at which the agreement was to take effect (or took effect or will take effect). End date: The time at which the period of use ends (or ended or will end). To avoid confusion between 'to' and 'up to', the submission of time is always mandatory for the end date. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
dateAsserted | Σ | 0..1 | dateTime | Element idMedicationStatement.dateAsserted MedicationUseDateTime Alternate namesMedicatieGebruikDatumTijd DefinitionDate on which this use is entered.
|
informationSource | I | 0..1 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idMedicationStatement.informationSource Person or organization that provided the information about the taking of this medication DefinitionThe 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. 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. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Constraints
|
derivedFrom | I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idMedicationStatement.derivedFrom Additional supporting information DefinitionAllows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. 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.
|
reasonCode | 0..* | CodeableConcept | Element idMedicationStatement.reasonCode Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. Unordered, Open, by text(Exists) BindingA coded concept identifying why the medication is being taken.
| |
reasonForUse | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse Reason for why the medication is being/was taken DefinitionA reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference. A coded concept identifying why the medication is being taken.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 0..* | Coding | There are no (further) constraints on this element Element idMedicationStatement.reasonCode:reasonForUse.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. 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. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
text | Σ | 1..1 | string | Element idMedicationStatement.reasonCode:reasonForUse.text ReasonForUse Alternate namesRedenGebruik DefinitionThe reason for using the medication, particularly in self-care medicine purchased by the patient themselves. 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. Very often the text is the same as a displayName of one of the codings.
|
reasonReference | I | 0..* | Reference(Condition | Observation | DiagnosticReport) | There are no (further) constraints on this element Element idMedicationStatement.reasonReference Condition or observation that supports why the medication is being/was taken DefinitionCondition or observation that supports why the medication is being/was taken. 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. Reference(Condition | Observation | DiagnosticReport) Constraints
|
note | 0..1 | Annotation | There are no (further) constraints on this element Element idMedicationStatement.note Further information about the statement DefinitionProvides extra information about the medication statement that is not conveyed by the other attributes. 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).
| |
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationStatement.note.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationStatement.note.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationStatement.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation. Organization is used when there's no need for specific attribution as to who made the comment.
| |
authorString | string | There are no (further) constraints on this element Data type | ||
authorReference | Reference(Practitioner | Patient | RelatedPerson | Organization) | There are no (further) constraints on this element Data type Reference(Practitioner | Patient | RelatedPerson | Organization) | ||
time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idMedicationStatement.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
text | Σ | 1..1 | markdown | Element idMedicationStatement.note.text Comment Alternate namesToelichting DefinitionComments on the medication use. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
|
dosage | 0..* | HdBe-InstructionsForUse.DosageInstructions | Element idMedicationStatement.dosage DosingInstructions / InstructionsForUse Alternate namesDoseerinstructie, Gebruiksinstructie DefinitionInstructions for the use of the medication, e.g. dose and route of administration. In the event of medication use, this is the pattern of use established by the patient or which the patient followed. This element mostly represents the DosingInstructions container from CBB InstructionsForUse, but also includes the AdditionalInstructions and RouteOfAdministration concepts, which are normally placed on the same level as this container. As a result, these concepts are duplicated in every repetition of this element, even though these concepts should be present just once according to the CBB. The RepeatPeriodCyclicalSchedule and Description elements of the CBB are not represented in this profile. When a HdBe profile contains a InstructionsForUse.DosageInstructions datatype, the RepeatPeriodCyclicalSchedule and Description elements are separately added to this profile as well. This element does not contain a mapping to the Dosage container from CBB InstructionsForUse. However, the child concepts of Dosage are all mapped. Multiple Dosage instances are represented by another DosingInstructions that contains a similiar SequenceNumber. HdBe-InstructionsForUse.DosageInstructions Constraints
|
Mapping FHIR profile to CBB
Path | map | CBB | comment |
---|---|---|---|
MedicationStatement.extension:renderedDosageInstruction.value[x] | InstructionsForUse.Description | HdBe-InstructionsForUse | |
MedicationStatement.modifierExtension:repeatPeriodCyclicalSchedule.value[x] | InstructionsForUse.RepeatPeriodCyclicalSchedule | HdBe-InstructionsForUse | |
MedicationStatement | MedicationUse2 | HdBe-MedicationUse2 | |
MedicationStatement.extension:prescriber.value[x] | MedicationUse2.Prescriber | HdBe-MedicationUse2 | |
MedicationStatement.extension:asAgreedIndicator.value[x] | MedicationUse2.AsAgreedIndicator | HdBe-MedicationUse2 | |
MedicationStatement.modifierExtension:stopType.value[x] | MedicationUse2.MedicationUseStopType | HdBe-MedicationUse2 | |
MedicationStatement.status | MedicationUse2.UseIndicator | HdBe-MedicationUse2 | |
MedicationStatement.status | MedicationUse2.MedicationUseStopType | HdBe-MedicationUse2 | implicit, main mapping is on the modifier extension ext-StopType |
MedicationStatement.status | MedicationUse2.PeriodOfUse | HdBe-MedicationUse2 | implicit, main mapping is on `.effective[x]:effectivePeriod` and extension ext-TimeInterval.Duration |
MedicationStatement.statusReason | MedicationUse2.ReasonForChangeOrDiscontinuationOfUse | HdBe-MedicationUse2 | |
MedicationStatement.medication[x]:medicationReference | MedicationUse2.ProductUsed | HdBe-MedicationUse2 | |
MedicationStatement.effective[x]:effectivePeriod | MedicationUse2.PeriodOfUse | HdBe-MedicationUse2 | |
MedicationStatement.dateAsserted | MedicationUse2.MedicationUseDateTime | HdBe-MedicationUse2 | |
MedicationStatement.reasonCode:reasonForUse.text | MedicationUse2.ReasonForUse | HdBe-MedicationUse2 | |
MedicationStatement.note.text | MedicationUse2.Comment | HdBe-MedicationUse2 | |
MedicationStatement.dosage | MedicationUse2.InstructionsForUse | HdBe-MedicationUse2 |
zib MedicationUse2 difference
| Concept | Category | Description |
|-----------------|-------------------|-----------------------------------------|
|status
| terminology | Replaced values of ConceptMap MedicationStopType-to-MedicationStatementStatus in correspondence with changes of ValueSet MedicationStopType. |
|status
| textual | Replaced Dutch SNOMED-CT codes with the corresponding codes in the ValueSet MedicationStopType in the guidance on the correct use of status. |
|statusReason
| terminology | Renamed the ValueSet from ReasonForChangeOrDiscontinuationOfUse to MedicationReason, to be able to reuse it at MedicationAgreement. Replaced several values in MedicationReason valueSet
: 1. Replaced OTH with SNOMED-CT code for Other. 2. Added SNOMED-CT code for Unknown. 3. Added CodeSystem MedicationReason which replaces all Dutch SNOMED-CT codes. 4. Removed all Dutch SNOMED-CT codes from valueset.
| modifierExtension:stopType
| textual | Edited guidance on the reuse of the MedicationStopType ValueSet. |
| modifierExtension:stopType
| terminology | Renamed the ValueSet from MedicationUseStopType to MedicationStopType, to be able to reuse it in MedicationAgreement and AdministrationAgreement. Replaced Dutch SNOMED-CT codes with international codes. |
|extension:prescriber.value[x]
| reference | Added reference to HdBe-HealthProfessional-Practitioner as it should be possible to reference to Practitioner directly using the pattern. |
Terminology Bindings
Path | Name | Strength | URL | ConceptMap |
---|---|---|---|---|
MedicationStatement.status | medication-statement-status|4.0.1 | required | http://hl7.org/fhir/ValueSet/medication-statement-status|4.0.1 | |
MedicationStatement.statusReason | MedicationReason | required | https://fhir.healthdata.be/ValueSet/MedicationReason | No bound ConceptMap |