Generated Narrative: StructureDefinition BeModelMedicationPrescription Name Flags Card. Type Description & Constraints BeModelMedicationPrescription 0..* Base Medication prescription (model) Instances of this logical model can be the target of a Reference #xD; identifier 1..* Identifier(5.2.0) Business identifier(s) for the prescription #xD; recordedDate 1..1 dateTime Time of authoring the prescription/draft in the information system #xD; basedOnMedicationLine 0..1 Reference(Medication Line (model)) Link to the Medication Line from which this request is based #xD; patient 1..1 Reference() The person for whom the medication is prescribed/ordered #xD; status 1..1 CodeableConcept Status of the prescription, this should not be status of treatment Binding: Medication Prescription Status (required) #xD; statusReason 0..1 CodeableConcept Reason for the current status of prescription, for example the reason why the prescription was made invalid #xD; statusChanged 0..1 dateTime Date and time when the status of the prescription was changed #xD; medication 1..1 Reference(Medication (model)) Prescribed product, branded, generic, virtual, extemporaneous, etc #xD; prescriber 1..1 Reference(Practitioner | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment #xD; organization 0..1 Reference(BeOrganization) The organization from which the prescriber issues the prescription. #xD; indication 0..* BackboneElement Reason for the prescription (typically diagnosis, or a procedure) #xD; reference 0..* Reference() Reason for the prescription (typically diagnosis, or a procedure) #xD; code 0..* CodeableConcept Reason or text for the prescription (typically diagnosis, or a procedure) #xD; dosage 0..* BeModelDosagingInformation Dosaging and administration instructions #xD; offLabel 0..1 boolean Off-Label / Dosage Override #xD; isOffLabelUse 0..1 boolean Off-Label / Dosage Override #xD; reason 1..1 CodeableConcept Dosage Override reason #xD; substitution 0..1 BackboneElement Whether substitution is allowed, and reason #xD; substitutionAllowed 1..1 boolean Substitution of the product is allowed. #xD; instructionForReimbursement 0..1 CodeableConcept Instructions for reimbursement Binding: Medication request reimbursement type ValueSet (extensible) #xD; validFrom 1..1 dateTime Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate #xD; validUntil 0..1 dateTime The validity period end date. The prescription is not dispensable after this date. #xD; dispenseRequest 0..1 BackboneElement Dispense Request or authorization for the prescribed medication #xD; dispenseInterval 0..1 Duration Minimum period of time between dispenses #xD; quantityPerDispense 0..1 SimpleQuantity Amount of medication to supply per dispense #xD; note 0..* string Additional information or comments #xD; Documentation for this format
Logical model for medication prescription (or some other form of order)
Business identifier(s) for the prescription
Time of authoring the prescription/draft in the information system
Link to the Medication Line from which this request is based
The person for whom the medication is prescribed/ordered
Status of the prescription, this should not be status of treatment
Reason for the current status of prescription, for example the reason why the prescription was made invalid
Date and time when the status of the prescription was changed
Prescribed product, branded, generic, virtual, extemporaneous, etc
The person who made the prescription, and who takes the responsibility of the treatment
Question: would we want to add basic Practicioner model?
The organization from which the prescriber issues the prescription.
Reason for the prescription (typically diagnosis, or a procedure)
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
Reason or text for the prescription (typically diagnosis, or a procedure)
Dosaging and administration instructions
unique id for the element within a resource (for internal references)
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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.
Whether substitution is allowed, and reason
Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
The validity period end date. The prescription is not dispensable after this date.
Dispense Request or authorization for the prescribed medication
Minimum period of time between dispenses
Amount of medication to supply per dispense