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.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Medication request identifiers.

State of the medication request.

Intent of 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.

Reasons for the medication request.

Clinical reason references for the medication request.

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.

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.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Medication request identifiers.

State of the medication request.

Intent of 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.

Reasons for the medication request.

Clinical reason references for the medication request.

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.

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.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Medication request identifiers.

State of the medication request.

Intent of 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.

Reasons for the medication request.

Clinical reason references for the medication request.

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.