Canonical intermediate logical model for medication agreement to medication request translation. It is shaped closely to R4 MedicationRequest with explicit Dutch source additions only where needed.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Medication request identifiers.

State of the medication request.

Reason for the current medication request status.

Intent of the medication request.

Whether the requested medication must not be administered or supplied.

Request priority.

Whether the request was reported rather than primary-source authored.

Source that reported the medication request.

Medication request categories.

Requested medication reference.

Subject of the medication request.

Encounter context for the medication request.

Additional supporting references such as EpisodeOfCare.

Date when the medication agreement was authored.

Requester, including practitioner-role metadata when supplied.

Organization on behalf of which the requester acted.

Recorder, including practitioner-role metadata when supplied.

Intended performer of the medication request.

Intended performer type.

Canonical protocols instantiated by the request.

External protocols instantiated by the request.

Plans or requests on which this request is based.

Composite request group identifier.

Overall pattern of medication administration.

Insurance plans associated with the request.

Prior prescription replaced by this request.

Clinical issues detected for this request.

Provenance events in the request lifecycle.

Route of administration.

Administration body site.

Structured administration body site.

Administration method.

Administration device.

Overall directions description.

Rendered dosage instruction carried by the EU Base R5 backport extension.

Directions in a parsable expression format.

Specific directions description.

Justification for dosage instructions.

Medication safety advice or warnings.

Whether an exceptional safety override was recorded.

Safety override details.

Safety advice that was overridden.

Reason for overriding safety advice.

Maximum dose.

Maximum amount.

Allowed medication order period.

Total daily effective dose.

Purpose of medication order.

Reasons for the medication request.

Clinical reason references for the medication request.

Medication information intended for the patient.

Monitoring instruction.

Therapeutic intent.

Guidance intended for clinicians.

Narrative notes.

Dosage instructions.

Overall period of use carried on the Dutch source extension.

Overall usage duration carried on the Dutch source extension.

Additional agreement information from the Dutch source extension.

Medication treatment identifier.

Stop type from the Dutch source modifier extension.

Dispense instruction.

Amount to dispense.

Boolean substitution permission when represented by the native R4 or STU3 choice.

Substitution direction.

Reason why substitution should or should not occur.

Canonical intermediate logical model for medication agreement to medication request translation. It is shaped closely to R4 MedicationRequest with explicit Dutch source additions only where needed.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Medication request identifiers.

State of the medication request.

Reason for the current medication request status.

Intent of the medication request.

Whether the requested medication must not be administered or supplied.

Request priority.

Whether the request was reported rather than primary-source authored.

Source that reported the medication request.

Medication request categories.

Requested medication reference.

Subject of the medication request.

Encounter context for the medication request.

Additional supporting references such as EpisodeOfCare.

Date when the medication agreement was authored.

Requester, including practitioner-role metadata when supplied.

Organization on behalf of which the requester acted.

Recorder, including practitioner-role metadata when supplied.

Intended performer of the medication request.

Intended performer type.

Canonical protocols instantiated by the request.

External protocols instantiated by the request.

Plans or requests on which this request is based.

Composite request group identifier.

Overall pattern of medication administration.

Insurance plans associated with the request.

Prior prescription replaced by this request.

Clinical issues detected for this request.

Provenance events in the request lifecycle.

Route of administration.

Administration body site.

Structured administration body site.

Administration method.

Administration device.

Overall directions description.

Rendered dosage instruction carried by the EU Base R5 backport extension.

Directions in a parsable expression format.

Specific directions description.

Justification for dosage instructions.

Medication safety advice or warnings.

Whether an exceptional safety override was recorded.

Safety override details.

Safety advice that was overridden.

Reason for overriding safety advice.

Maximum dose.

Maximum amount.

Allowed medication order period.

Total daily effective dose.

Purpose of medication order.

Reasons for the medication request.

Clinical reason references for the medication request.

Medication information intended for the patient.

Monitoring instruction.

Therapeutic intent.

Guidance intended for clinicians.

Narrative notes.

Dosage instructions.

Overall period of use carried on the Dutch source extension.

Overall usage duration carried on the Dutch source extension.

Additional agreement information from the Dutch source extension.

Medication treatment identifier.

Stop type from the Dutch source modifier extension.

Dispense instruction.

Amount to dispense.

Boolean substitution permission when represented by the native R4 or STU3 choice.

Substitution direction.

Reason why substitution should or should not occur.

Canonical intermediate logical model for medication agreement to medication request translation. It is shaped closely to R4 MedicationRequest with explicit Dutch source additions only where needed.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Medication request identifiers.

State of the medication request.

Reason for the current medication request status.

Intent of the medication request.

Whether the requested medication must not be administered or supplied.

Request priority.

Whether the request was reported rather than primary-source authored.

Source that reported the medication request.

Medication request categories.

Requested medication reference.

Subject of the medication request.

Encounter context for the medication request.

Additional supporting references such as EpisodeOfCare.

Date when the medication agreement was authored.

Requester, including practitioner-role metadata when supplied.

Organization on behalf of which the requester acted.

Recorder, including practitioner-role metadata when supplied.

Intended performer of the medication request.

Intended performer type.

Canonical protocols instantiated by the request.

External protocols instantiated by the request.

Plans or requests on which this request is based.

Composite request group identifier.

Overall pattern of medication administration.

Insurance plans associated with the request.

Prior prescription replaced by this request.

Clinical issues detected for this request.

Provenance events in the request lifecycle.

Route of administration.

Administration body site.

Structured administration body site.

Administration method.

Administration device.

Overall directions description.

Rendered dosage instruction carried by the EU Base R5 backport extension.

Directions in a parsable expression format.

Specific directions description.

Justification for dosage instructions.

Medication safety advice or warnings.

Whether an exceptional safety override was recorded.

Safety override details.

Safety advice that was overridden.

Reason for overriding safety advice.

Maximum dose.

Maximum amount.

Allowed medication order period.

Total daily effective dose.

Purpose of medication order.

Reasons for the medication request.

Clinical reason references for the medication request.

Medication information intended for the patient.

Monitoring instruction.

Therapeutic intent.

Guidance intended for clinicians.

Narrative notes.

Dosage instructions.

Overall period of use carried on the Dutch source extension.

Overall usage duration carried on the Dutch source extension.

Additional agreement information from the Dutch source extension.

Medication treatment identifier.

Stop type from the Dutch source modifier extension.

Dispense instruction.

Amount to dispense.

Boolean substitution permission when represented by the native R4 or STU3 choice.

Substitution direction.

Reason why substitution should or should not occur.