Name Flags Card. Type Description & Constraints MedicationOrderIHEPWP 0..* Base [IHE PHARM White Paper] Logical Model for order identifier 0..1 Identifier The business identifier(s) for the medication Order date 0..1 dateTime When prescription was initially made patient 1..1 Reference(Patient) The person for which the medication is prescribed. reason 0..* Reference(Condition | Observation) Reason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)(may or may not be explicitly stated) note 0..* Annotation Additional Information about the prescription requester 0..1 Reference(Practitioner) Who made the prescription status 1..1 code Status of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED prescriptionItem 0..* BackboneElement A prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing. prescriptionItemID 1..1 Identifier Prescription Item ID treatmentDate 0..1 Duration Beginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals reasonForPrescribing 0..1 string Reason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …) Frequency 0..1 string substitutionAllowed 0..1 string Substitution allowed or not (can the pharmacist do a substitution of medication?) route 0..1 string Route of administration Dosage 0..1 string intakePattern 0..1 string Intake pattern for the medication medicalInstructions 0..1 string Diagnosis or reason for prescribing is this similar the 3rd bullet point? alertAboutRestrictions 0..1 string Alert about prescribing restrictions relatedtoChronic 0..1 string Related to a chronic disease or not (listed or unlisted) specificFollowUp 0..1 string Specific follow-up elements additionalComment 0..1 string Additional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA) status 0..1 string Status (see the “Relevant Standards” chapter) Documentation for this format
[IHE PHARM White Paper] Logical Model for order
Integrating the Healthcare Enterprise (IHE)
A prescription is issued by one ordering healthcare professional for one patient, in the context of zero or one encounter (between the patient and the ordering physician and/or the healthcare institution).
IHE http://www.ihe.net/Governance/#Intellectual_Property
The business identifier(s) for the medication Order
The business identifier(s) for the medication order
The person for which the medication is prescribed.
Reason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)(may or may not be explicitly stated)
Additional Information about the prescription
Status of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
A prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
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
Beginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
Reason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
Substitution allowed or not (can the pharmacist do a substitution of medication?)
Diagnosis or reason for prescribing is this similar the 3rd bullet point?
Related to a chronic disease or not (listed or unlisted)
Additional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
Status (see the “Relevant Standards” chapter)