Generated Narrative: StructureDefinition BeModelMedicationLine Name Flags Card. Type Description & Constraints BeModelMedicationLine 0..* Base Medication Line (model) Instances of this logical model can be the target of a Reference #xD; identifier 1..* Identifier Unique identifier #xD; recordedDate 1..1 dateTime Timestamp the medication line content was recorded or last updated. #xD; recorder 1..1 Reference(BePractitioner) Recorder #xD; patient 1..1 Reference(BePatient) Patient #xD; status 1..1 code Status of the line entry Binding Description: (preferred): Draft, Recorded, or Entered in Error #xD; adherence 0..1 BackboneElement Whether the patient is known to be taking the medication #xD; status 1..1 CodeableConcept The status - taking, not taking,... Binding: BeExtAdherenceStatus ValueSet (required) #xD; adherenceStatusReason 0..1 CodeableConcept Reason for the adherence status Binding: Adherence Status Reason ValueSet (example) #xD; medication 1..1 BackboneElement The product or substance #xD; product 1..1 Reference(Medication (model)) Product reference, identifier or name #xD; type 1..1 CodeableConcept Type of medication - magistral, medicinal product, non-medicinal product Binding: Medication preparation Type value set (required) #xD; reason 0..* BackboneElement Reason for the medication treatment #xD; reference 0..1 Reference() Reference to existing condition or reason #xD; code 0..1 CodeableConcept Code of the condition, or free text #xD; effectivePeriod 1..1 BackboneElement Period of medication treatment #xD; start 1..1 dateTime The begin of the medication line #xD; end 0..1 dateTime The end of the medication line #xD; dosage 0..* BeModelDosagingInformation Structured Dosage #xD; offLabel 0..1 string Reason for Off-label use or dosage override #xD; exposure 0..1 CodeableConcept Therapeutic, Prophylactic Binding: Medication exposure intent (required) #xD; originType 0..1 CodeableConcept The origin of the line - hospital, ambulatory Binding: Medication origin type value set (required) #xD; note 0..* Annotation A note captured by a professional #xD; Documentation for this format
A unique identifier for the medication line. This identifier alone may be the same for different versions of the medication line.
Timestamp the medication line content was recorded or last updated.
We consider this is redundant with the above, given the intended use in Belgium (version is a date). How to ensure the compatibility?
We understand this will be updated as the line changes
`Draft`, `Recorded`, or `Entered in Error`
Whether the patient is known to be taking the medication
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. 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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The value set provided is an indicative example
Type of medication - magistral, medicinal product, non-medicinal product
Reference to existing condition or reason
Reason for Off-label use or dosage override
isOffLabelUse and reason are expected to be manually filled by the prescriber, indicating that this dosage is not entered in error. This information is an indication (for example) for the pharmacist to see that there is a justification of the dosage difference.
The origin of the line - hospital, ambulatory