HL7 FHIR® US Core Implementation Guide CI Build

US Core, published by HL7 International - US Realm Steering Committee. This is not an authorized publication; it is the continuous build for version 3.1.1). This version is based on the current content of https://github.com/HL7/US-Core-R4/ and changes regularly. See the Directory of published versions

StructureDefinition-us-core-medicationrequest

The MedicationRequest resource can be used to record a patient’s medication prescription or order. This profile sets minimum expectations for the MedicationRequest resource to record, search, and fetch medications associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.

Example Usage Scenarios:

The following are example usage scenarios for the US Core-MedicationRequest profile. See the Medication List Guidance section for guidance on accessing a patient medications:

  • Fetching all medications that have been prescribed to a particular patient
  • Fetching all active medications that have been prescribed to particular patient
  • Fetching all medications that have been prescribed to particular patient during a particular encounter
  • Record or update medications that have been prescribed for a particular patient

Mandatory and Must Support Data Elements

The following data-elements are mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each MedicationRequest must have:

  1. a status
  2. an intent code
  3. a medication
  4. a patient
  5. a date for when written
  6. a prescriber

Each MedicationRequest must support:

  1. the reported flag signaling that information is from a secondary source such as a patient.
  2. the encounter
  3. the prescription Sig Profile specific implementation guidance:
  • See the Medication List Guidance section for guidance on accessing a patient medications including over the counter (OTC) medication and other substances taken for medical and recreational use.
  • The MedicationRequest resources can represent a medication using either a code, or reference a Medication resource.
    • When referencing a Medication resource, the resource may be contained or an external resource.
    • The server application MAY choose any combination of these methods, but if an external reference to Medication is used, the server SHALL support the _include parameter for searching this element.
    • The client application SHALL support all methods.
  • Source EHR identifiers SHOULD be included to support deduplication across MedicationRequest resources. Exposing the EHR identifiers helps client applications identify duplicates.

Examples

Formal Views of Profile Content

Description of Profiles, Differentials, and Snapshots.

The official URL for this profile is: http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest

Published on Fri Jun 26 00:00:00 UTC 2020 as active by the HL7 US Realm Steering Committee.

This profile builds on MedicationRequest


MedicationRequest

Summary of the Mandatory Requirements

  1. A code in MedicationRequest.status with a required binding to Medicationrequest status
  2. A code in MedicationRequest.intent with a required binding to Medication request intent
  3. A CodeableConcept or Medication Reference in MedicationRequest.medication[x] with an extensible binding to US Core Medication Codes (RxNorm)
  4. A Patient Reference in MedicationRequest.subject
  5. A dateTime in MedicationRequest.authoredOn
  6. A Requester Reference in MedicationRequest.requester

Summary of the Must Support Requirements

  1. A boolean or Reference in MedicationRequest.reported[x]
  2. A Encounter Reference in MedicationRequest.encounter
  3. One or more Dosages in MedicationRequest.dosageInstruction
    • which should have a string value in MedicationRequest.dosageInstruction.text
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest 0..*MedicationRequestOrdering of medication for patient or group
... status S1..1codeactive | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required)
... intent S1..1codeproposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required)
... reported[x] S0..1Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Patient Profile | US Core Practitioner Profile | US Core Organization Profile)
... medication[x] S1..1Medication to be taken
Binding: US Core Medication Codes (RxNorm) (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject S1..1Reference(US Core Patient Profile)Who or group medication request is for
... encounter S0..1Reference(Encounter)Encounter created as part of encounter/admission/stay
... authoredOn S1..1dateTimeWhen request was initially authored
... requester S1..1Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile)Who/What requested the Request
... dosageInstruction S0..*DosageHow the medication should be taken
.... text S0..1stringFree text dosage instructions e.g. SIG

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest I0..*MedicationRequestOrdering of medication for patient or group
... id Σ0..1stringLogical id of this artifact
... meta ΣI0..1MetaMetadata about the resource
... implicitRules ?!ΣI0..1uriA set of rules under which this content was created
... language I0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension I0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!I0..*ExtensionExtensions that cannot be ignored
... identifier I0..*IdentifierExternal ids for this request
... status ?!SΣI1..1codeactive | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required)
... statusReason I0..1CodeableConceptReason for current status
Binding: medicationRequest Status Reason Codes (example)
... intent ?!SΣI1..1codeproposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required)
... category I0..*CodeableConceptType of medication usage
Binding: medicationRequest Category Codes (example)
... priority ΣI0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required)
... doNotPerform ?!ΣI0..1booleanTrue if request is prohibiting action
... reported[x] SΣI0..1Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Patient Profile | US Core Practitioner Profile | US Core Organization Profile)
... medication[x] SΣI1..1Medication to be taken
Binding: US Core Medication Codes (RxNorm) (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣI1..1Reference(US Core Patient Profile)Who or group medication request is for
... encounter SI0..1Reference(Encounter)Encounter created as part of encounter/admission/stay
... supportingInformation I0..*Reference(Resource)Information to support ordering of the medication
... authoredOn SΣI1..1dateTimeWhen request was initially authored
... requester SΣI1..1Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile)Who/What requested the Request
... performer I0..1Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam)Intended performer of administration
... performerType ΣI0..1CodeableConceptDesired kind of performer of the medication administration
Binding: ProcedurePerformerRoleCodes (example)
... recorder I0..1Reference(Practitioner | PractitionerRole)Person who entered the request
... reasonCode I0..*CodeableConceptReason or indication for ordering or not ordering the medication
Binding: Condition/Problem/DiagnosisCodes (example)
... reasonReference I0..*Reference(Condition | Observation)Condition or observation that supports why the prescription is being written
... instantiatesCanonical ΣI0..*canonical()Instantiates FHIR protocol or definition
... instantiatesUri ΣI0..*uriInstantiates external protocol or definition
... basedOn ΣI0..*Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation)What request fulfills
... groupIdentifier ΣI0..1IdentifierComposite request this is part of
... courseOfTherapyType I0..1CodeableConceptOverall pattern of medication administration
Binding: medicationRequest Course of Therapy Codes (example)
... insurance I0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note I0..*AnnotationInformation about the prescription
... dosageInstruction SI0..*DosageHow the medication should be taken
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... sequence ΣI0..1integerThe order of the dosage instructions
.... text SΣI0..1stringFree text dosage instructions e.g. SIG
.... additionalInstruction ΣI0..*CodeableConceptSupplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"
Binding: SNOMEDCTAdditionalDosageInstructions (example)
.... patientInstruction ΣI0..1stringPatient or consumer oriented instructions
.... timing ΣI0..1TimingWhen medication should be administered
.... asNeeded[x] ΣI0..1Take "as needed" (for x)
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example)
..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site ΣI0..1CodeableConceptBody site to administer to
Binding: SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)
.... route ΣI0..1CodeableConceptHow drug should enter body
Binding: SNOMEDCTRouteCodes (example)
.... method ΣI0..1CodeableConceptTechnique for administering medication
Binding: SNOMEDCTAdministrationMethodCodes (example)
.... doseAndRate ΣI0..*ElementAmount of medication administered
..... id 0..1stringUnique id for inter-element referencing
..... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... type ΣI0..1CodeableConceptThe kind of dose or rate specified
Binding: DoseAndRateType (example)
..... dose[x] ΣI0..1Amount of medication per dose
...... doseRangeRange
...... doseQuantityQuantity(SimpleQuantity)
..... rate[x] ΣI0..1Amount of medication per unit of time
...... rateRatioRatio
...... rateRangeRange
...... rateQuantityQuantity(SimpleQuantity)
.... maxDosePerPeriod ΣI0..1RatioUpper limit on medication per unit of time
.... maxDosePerAdministration ΣI0..1SimpleQuantityUpper limit on medication per administration
.... maxDosePerLifetime ΣI0..1SimpleQuantityUpper limit on medication per lifetime of the patient
... dispenseRequest I0..1BackboneElementMedication supply authorization
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... initialFill I0..1BackboneElementFirst fill details
..... id 0..1stringUnique id for inter-element referencing
..... extension I0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... quantity I0..1SimpleQuantityFirst fill quantity
..... duration I0..1DurationFirst fill duration
.... dispenseInterval I0..1DurationMinimum period of time between dispenses
.... validityPeriod I0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed I0..1unsignedIntNumber of refills authorized
.... quantity I0..1SimpleQuantityAmount of medication to supply per dispense
.... expectedSupplyDuration I0..1DurationNumber of days supply per dispense
.... performer I0..1Reference(Organization)Intended dispenser
... substitution I0..1BackboneElementAny restrictions on medication substitution
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... allowed[x] I1..1Whether substitution is allowed or not
Binding: ActSubstanceAdminSubstitutionCode (example)
..... allowedBooleanboolean
..... allowedCodeableConceptCodeableConcept
.... reason I0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription I0..1Reference(MedicationRequest)An order/prescription that is being replaced
... detectedIssue I0..*Reference(DetectedIssue)Clinical Issue with action
... eventHistory I0..*Reference(Provenance)A list of events of interest in the lifecycle

doco Documentation for this format

MedicationRequest

Summary of the Mandatory Requirements

  1. A code in MedicationRequest.status with a required binding to Medicationrequest status
  2. A code in MedicationRequest.intent with a required binding to Medication request intent
  3. A CodeableConcept or Medication Reference in MedicationRequest.medication[x] with an extensible binding to US Core Medication Codes (RxNorm)
  4. A Patient Reference in MedicationRequest.subject
  5. A dateTime in MedicationRequest.authoredOn
  6. A Requester Reference in MedicationRequest.requester

Summary of the Must Support Requirements

  1. A boolean or Reference in MedicationRequest.reported[x]
  2. A Encounter Reference in MedicationRequest.encounter
  3. One or more Dosages in MedicationRequest.dosageInstruction
    • which should have a string value in MedicationRequest.dosageInstruction.text

Differential View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest 0..*MedicationRequestOrdering of medication for patient or group
... status S1..1codeactive | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required)
... intent S1..1codeproposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required)
... reported[x] S0..1Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Patient Profile | US Core Practitioner Profile | US Core Organization Profile)
... medication[x] S1..1Medication to be taken
Binding: US Core Medication Codes (RxNorm) (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject S1..1Reference(US Core Patient Profile)Who or group medication request is for
... encounter S0..1Reference(Encounter)Encounter created as part of encounter/admission/stay
... authoredOn S1..1dateTimeWhen request was initially authored
... requester S1..1Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile)Who/What requested the Request
... dosageInstruction S0..*DosageHow the medication should be taken
.... text S0..1stringFree text dosage instructions e.g. SIG

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest I0..*MedicationRequestOrdering of medication for patient or group
... id Σ0..1stringLogical id of this artifact
... meta ΣI0..1MetaMetadata about the resource
... implicitRules ?!ΣI0..1uriA set of rules under which this content was created
... language I0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred)
Max Binding: AllLanguages
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension I0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!I0..*ExtensionExtensions that cannot be ignored
... identifier I0..*IdentifierExternal ids for this request
... status ?!SΣI1..1codeactive | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required)
... statusReason I0..1CodeableConceptReason for current status
Binding: medicationRequest Status Reason Codes (example)
... intent ?!SΣI1..1codeproposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required)
... category I0..*CodeableConceptType of medication usage
Binding: medicationRequest Category Codes (example)
... priority ΣI0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required)
... doNotPerform ?!ΣI0..1booleanTrue if request is prohibiting action
... reported[x] SΣI0..1Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Patient Profile | US Core Practitioner Profile | US Core Organization Profile)
... medication[x] SΣI1..1Medication to be taken
Binding: US Core Medication Codes (RxNorm) (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣI1..1Reference(US Core Patient Profile)Who or group medication request is for
... encounter SI0..1Reference(Encounter)Encounter created as part of encounter/admission/stay
... supportingInformation I0..*Reference(Resource)Information to support ordering of the medication
... authoredOn SΣI1..1dateTimeWhen request was initially authored
... requester SΣI1..1Reference(US Core Practitioner Profile | US Core Organization Profile | US Core Patient Profile)Who/What requested the Request
... performer I0..1Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam)Intended performer of administration
... performerType ΣI0..1CodeableConceptDesired kind of performer of the medication administration
Binding: ProcedurePerformerRoleCodes (example)
... recorder I0..1Reference(Practitioner | PractitionerRole)Person who entered the request
... reasonCode I0..*CodeableConceptReason or indication for ordering or not ordering the medication
Binding: Condition/Problem/DiagnosisCodes (example)
... reasonReference I0..*Reference(Condition | Observation)Condition or observation that supports why the prescription is being written
... instantiatesCanonical ΣI0..*canonical()Instantiates FHIR protocol or definition
... instantiatesUri ΣI0..*uriInstantiates external protocol or definition
... basedOn ΣI0..*Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation)What request fulfills
... groupIdentifier ΣI0..1IdentifierComposite request this is part of
... courseOfTherapyType I0..1CodeableConceptOverall pattern of medication administration
Binding: medicationRequest Course of Therapy Codes (example)
... insurance I0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note I0..*AnnotationInformation about the prescription
... dosageInstruction SI0..*DosageHow the medication should be taken
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... sequence ΣI0..1integerThe order of the dosage instructions
.... text SΣI0..1stringFree text dosage instructions e.g. SIG
.... additionalInstruction ΣI0..*CodeableConceptSupplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"
Binding: SNOMEDCTAdditionalDosageInstructions (example)
.... patientInstruction ΣI0..1stringPatient or consumer oriented instructions
.... timing ΣI0..1TimingWhen medication should be administered
.... asNeeded[x] ΣI0..1Take "as needed" (for x)
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example)
..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site ΣI0..1CodeableConceptBody site to administer to
Binding: SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example)
.... route ΣI0..1CodeableConceptHow drug should enter body
Binding: SNOMEDCTRouteCodes (example)
.... method ΣI0..1CodeableConceptTechnique for administering medication
Binding: SNOMEDCTAdministrationMethodCodes (example)
.... doseAndRate ΣI0..*ElementAmount of medication administered
..... id 0..1stringUnique id for inter-element referencing
..... extension I0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... type ΣI0..1CodeableConceptThe kind of dose or rate specified
Binding: DoseAndRateType (example)
..... dose[x] ΣI0..1Amount of medication per dose
...... doseRangeRange
...... doseQuantityQuantity(SimpleQuantity)
..... rate[x] ΣI0..1Amount of medication per unit of time
...... rateRatioRatio
...... rateRangeRange
...... rateQuantityQuantity(SimpleQuantity)
.... maxDosePerPeriod ΣI0..1RatioUpper limit on medication per unit of time
.... maxDosePerAdministration ΣI0..1SimpleQuantityUpper limit on medication per administration
.... maxDosePerLifetime ΣI0..1SimpleQuantityUpper limit on medication per lifetime of the patient
... dispenseRequest I0..1BackboneElementMedication supply authorization
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... initialFill I0..1BackboneElementFirst fill details
..... id 0..1stringUnique id for inter-element referencing
..... extension I0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... quantity I0..1SimpleQuantityFirst fill quantity
..... duration I0..1DurationFirst fill duration
.... dispenseInterval I0..1DurationMinimum period of time between dispenses
.... validityPeriod I0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed I0..1unsignedIntNumber of refills authorized
.... quantity I0..1SimpleQuantityAmount of medication to supply per dispense
.... expectedSupplyDuration I0..1DurationNumber of days supply per dispense
.... performer I0..1Reference(Organization)Intended dispenser
... substitution I0..1BackboneElementAny restrictions on medication substitution
.... id 0..1stringUnique id for inter-element referencing
.... extension I0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!ΣI0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... allowed[x] I1..1Whether substitution is allowed or not
Binding: ActSubstanceAdminSubstitutionCode (example)
..... allowedBooleanboolean
..... allowedCodeableConceptCodeableConcept
.... reason I0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription I0..1Reference(MedicationRequest)An order/prescription that is being replaced
... detectedIssue I0..*Reference(DetectedIssue)Clinical Issue with action
... eventHistory I0..*Reference(Provenance)A list of events of interest in the lifecycle

doco Documentation for this format

Downloads: StructureDefinition: (XML, JSON), Schema: XML Schematron


Quick Start

Below is an overview of the required set of Server RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.

  • The syntax used to describe the interactions is described here.
  • See the General Guidance section for additional rules and expectations when a server requires status parameters.
  • See the General Guidance section for additional guidance on searching for multiple patients.

Mandatory Search Parameters:

The following search parameters and search parameter combinations SHALL be supported.:

  1. SHALL support searching using the combination of the patient and intent search parameters:
    • including support for composite OR search on intent (e.g.intent={system|}[code],{system|}[code],...)

    GET [base]/MedicationRequest?patient=[reference]&intent=order,plan

    Example:

    1. GET [base]/MedicationRequest?patient=14676&intent=order,plan
    2. GET [base]/MedicationRequest?patient=14676&intent=order,plan&_include=MedicationRequest:medication

    Implementation Notes: Fetches a bundle of all MedicationRequest resources for the specified patient and intent code = order,plan (how to search by reference and how to search by token)

  2. SHALL support searching using the combination of the patient and intent and status search parameters:
    • including support for composite OR search on intent (e.g.intent={system|}[code],{system|}[code],...)
    • including support for composite OR search on status (e.g.status={system|}[code],{system|}[code],...)

    GET [base]/MedicationRequest?patient=[reference]&intent=order,plan&status={system|}[code]{,{system|}[code],...}

    Example:

    1. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&status=active
    2. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&status=active&_include=MedicationRequest:medication

    Implementation Notes: Fetches a bundle of all MedicationRequest resources for the specified patient and intent code = order,plan and status (how to search by reference and how to search by token)

Optional Search Parameters:

The following search parameter combinations SHOULD be supported.:

  1. SHOULD support searching using the combination of the patient and intent and encounter search parameters:
    • including support for composite OR search on intent (e.g.intent={system|}[code],{system|}[code],...)

    GET [base]/MedicationRequest?patient=[reference]&intent=order,plan&encounter=[reference]

    Example:

    1. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&status=active&encounter=Encounter/123
    2. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&status=active&&encounter=Encounter/123&_include=MedicationRequest:medication

    Implementation Notes: Fetches a bundle of all MedicationRequest resources for the specified patient and intent code = order,plan and encounter (how to search by reference and how to search by token)

  2. SHOULD support searching using the combination of the patient and intent and authoredon search parameters:
    • including support for composite OR search on intent (e.g.intent={system|}[code],{system|}[code],...)
    • including support for these authoredon comparators: gt,lt,ge,le
    • including optional support for composite AND search on authoredon (e.g.authoredon=[date]&authoredon=[date]]&...)

    GET [base]/MedicationRequest?patient=[reference]&intent=order,plan&authoredon={gt|lt|ge|le}[date]{&authoredon={gt|lt|ge|le}[date]&...}

    Example:

    1. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&authoredon=ge2019
    2. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&authoredon=ge2019&_include=MedicationRequest:medication

    Implementation Notes: Fetches a bundle of all MedicationRequest resources for the specified patient and intent code = order,plan and authoredon date (how to search by reference and how to search by token and how to search by date)