Name Flags Card. Type Description & Constraints MedicationPrescription 0..* Base Medication prescription (model) Instances of this logical model can be the target of a Reference identifier 1..* II Business identifier(s) for the prescription groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders recordingDate 0..1 DT Time of authoring the prescription/draft in the information system issueDate 1..1 DT Time of issuing (signing) the prescription by health care practicioner recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc). validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date. patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered status 1..1 CD Status of the prescription, this should not be status of treatment statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid statusReasonText 0..1 ST Textual reason for the current status of prescription medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure) indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations. usageInstructions 1..1 Reference(Dosaging (model)) Dosaging and administration instructions preparationInstructions 0..* ST Additional instructions about preparation or dispense noSubstitution 0..1 BackboneElement Substitution is not allowed for a given reason noSubstitutionFlag 1..1 BL Substitution of the product is not allowed. noSubstitutionReason 0..1 CD Coded reason for the no-substitution requirement noSubstitutionReasonText 0..1 ST Textual reason for the no-substitution requirement allowedSubstitutionType 0..* CD Specific type of substitution that is allowed. Can be an explicit relaxation to normal jurisdictional substitution rules, especially in hospital context. comment 0..* ST Additional information or comments Documentation for this format
Integrating the Healthcare Enterprise (IHE)
Logical model for medication prescription (or some other form of order)
IHE http://www.ihe.net/Governance/#Intellectual_Property
Business identifier(s) for the prescription
Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
Time of authoring the prescription/draft in the information system
Time of issuing (signing) the prescription by health care practicioner
The recorder of the prescription/draft in the information system
The person who made the prescription, and who takes the responsibility of the treatment
Question: would we want to add basic Practicioner model?
Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
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.
The person for whom the medication is prescribed/ordered
Question: would we want to add basic Patient model?
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
Textual reason for the current status of prescription
Prescribed product, branded, generic, virtual, extemporal, etc
Reason for the prescription (typically diagnosis, or a procedure)
Reason for the prescription in textual form. This might not be allowed by some implementations.
Dosaging and administration instructions
Additional instructions about preparation or dispense
Substitution is not allowed for a given reason
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 managable, 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
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 managable, 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/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Substitution of the product is not allowed.
Coded reason for the no-substitution requirement
Textual reason for the no-substitution requirement
Specific type of substitution that is allowed. Can be an explicit relaxation to normal jurisdictional substitution rules, especially in hospital context.