US Core Implementation Guide
6.1.0 - STU6 United States of America flag

This page is part of the US Core (v6.1.0: STU6 Update) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Resource Profile: US Core MedicationRequest Profile

Official URL: http://hl7.org/fhir/us/core/StructureDefinition/us-core-medicationrequest Version: 6.1.0
Active as of 2020-06-26 Computable Name: USCoreMedicationRequestProfile

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

The US Core Medication Request Profile is based upon the core FHIR MedicationRequest Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 Medications requirements. 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 a patient’s medication to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.

Example Usage Scenarios:

The following are example usage scenarios for the US Core-MedicationRequest profile. See the Medication List 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 must always be present (Mandatory definition) 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 Views 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

* see guidance below

Each MedicationRequest Must Support:

  1. the category (e.g., Discharge Medication)
  2. the reported flag or reference signaling that information is from a secondary source such as a patient
  3. the encounters
  4. a prescriber
  5. a date for when written
  6. the prescription Sig
  7. the amount dispensed and number of refills
  8. the dose and rate

Additional USCDI Requirements

For ONC’s USCDI requirements, each MedicationRequest Must Support the following additional element. This element is included in the formal definition of the profile and the MedicationRequest examples.

  1. the reason or indication for the prescription*

*see guidance below

Profile Specific Implementation Guidance:

  • See the Medication List section for guidance on accessing a patient medications including over the counter (OTC) medication and other substances taken for medical and recreational use.
    • When recording “self-prescribed” medication, requester SHOULD be used to indicate the Patient or RelatedPerson as the prescriber.
  • *This Profile can represent a medication using a code or reference a Medication resource.
    • When using a code, RXNorm concepts are used. They are defined as an extensible binding to .medicationCodeableConcept. USCDI V3+ recommends the National Drug Codes (NDC) as an optional terminology. They can be supplied as an additional coding element.
    • When referencing a Medication resource in .medicationReference, the resource may be contained or an external resource.
    • The server systems are not required to support both a code and a reference, but SHALL support at least one of these methods.
    • If an external reference to a Medication resource is used, the server SHALL support the _include parameter for searching this element.
    • The client application SHALL support all methods.
  • The MedicationRequest resource can represent that information is from a secondary source using either a boolean flag or a reference using MedicationRequest.reportedReference.
    • Although both are marked as Must Support, the server system is not required to support both, but SHALL support at least one of these elements.
    • The client application SHALL support both elements.
  • *The MedicationRequest resource can communicate the reason or indication for treatment using either a code in MedicationRequest.reasonCode or a reference using MedicationRequest.reasonReference.
    • As documented here, when using MedicationRequest.reasonReference, the referenced Condition or Observation SHOULD be a US Core Profile.
  • Source EHR identifiers SHOULD be included to support deduplication across MedicationRequest resources. Exposing the EHR identifiers helps client applications identify duplicates.
  • Servers SHALL follow the guidance in the Medication List page and return all active Medications as MedicationRequest. It is always best practice to confirm this list with the Patient or Caregiver.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MedicationRequest

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... status S1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... intent SC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets

... reported[x] S0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean S
.... reportedReferenceReference S(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile)
... medication[x] S1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject S1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... authoredOn S0..1dateTime(USCDI) When request was initially authored
... requester SC0..1Reference(US Core Practitioner Profile S | US Core Patient Profile | US Core Organization Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile | Device)(USCDI) Who/What requested the Request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... text S0..1string(USCDI) Free text dosage instructions e.g. SIG
.... timing S0..1Timing(USCDI) When medication should be administered
.... doseAndRate S0..*Element(USCDI) Amount of medication administered
..... dose[x] S0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity S
...... doseRangeRange
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding

Constraints

IdGradePath(s)DetailsRequirements
us-core-21errorMedicationRequestrequester SHALL be present if intent is "order"
: (intent='order' or intent='original-order' or intent='reflex-order'or intent='filler-order' or intent='instance-order') implies requester.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... status ?!SΣ1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... intent ?!SΣC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
Binding: medicationRequest Category Codes (example): A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.


.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets


... doNotPerform ?!Σ0..1booleanTrue if request is prohibiting action
... reported[x] SΣ0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Practitioner Profile)
... medication[x] SΣ1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... authoredOn SΣ0..1dateTime(USCDI) When request was initially authored
... requester SΣC0..1Reference(US Core Practitioner Profile)(USCDI) Who/What requested the Request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... text SΣ0..1string(USCDI) Free text dosage instructions e.g. SIG
.... timing SΣ0..1Timing(USCDI) When medication should be administered
.... doseAndRate SΣ0..*Element(USCDI) Amount of medication administered
..... dose[x] SΣ0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.categoryexamplemedicationRequest Category Codes
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorMedicationRequestIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorMedicationRequestIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorMedicationRequestIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorMedicationRequestIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceMedicationRequestA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
us-core-21errorMedicationRequestrequester SHALL be present if intent is "order"
: (intent='order' or intent='original-order' or intent='reflex-order'or intent='filler-order' or intent='instance-order') implies requester.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal ids for this request
... status ?!SΣ1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... statusReason 0..1CodeableConceptReason for current status
Binding: medicationRequest Status Reason Codes (example): Identifies the reasons for a given status.

... intent ?!SΣC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
Binding: medicationRequest Category Codes (example): A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.


.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets


... priority Σ0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.

... doNotPerform ?!Σ0..1booleanTrue if request is prohibiting action
... reported[x] SΣ0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean S
.... reportedReferenceReference S(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile)
... medication[x] SΣ1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... supportingInformation 0..*Reference(Resource)Information to support ordering of the medication
... authoredOn SΣ0..1dateTime(USCDI) When request was initially authored
... requester SΣC0..1Reference(US Core Practitioner Profile S | US Core Patient Profile | US Core Organization Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile | Device)(USCDI) Who/What requested the Request
... performer 0..1Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam)Intended performer of administration
... performerType Σ0..1CodeableConceptDesired kind of performer of the medication administration
Binding: ProcedurePerformerRoleCodes (example): Identifies the type of individual that is desired to administer the medication.

... recorder 0..1Reference(Practitioner | PractitionerRole)Person who entered the request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... instantiatesCanonical Σ0..*canonical()Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation)What request fulfills
... groupIdentifier Σ0..1IdentifierComposite request this is part of
... courseOfTherapyType 0..1CodeableConceptOverall pattern of medication administration
Binding: medicationRequest Course of Therapy Codes (example): Identifies the overall pattern of medication administratio.

... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*AnnotationInformation about the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... sequence Σ0..1integerThe order of the dosage instructions
.... text SΣ0..1string(USCDI) Free text dosage instructions e.g. SIG
.... additionalInstruction Σ0..*CodeableConceptSupplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"
Binding: SNOMEDCTAdditionalDosageInstructions (example): A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".


.... patientInstruction Σ0..1stringPatient or consumer oriented instructions
.... timing SΣ0..1Timing(USCDI) When medication should be administered
.... asNeeded[x] Σ0..1Take "as needed" (for x)
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.

..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site Σ0..1CodeableConceptBody site to administer to
Binding: SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example): A coded concept describing the site location the medicine enters into or onto the body.

.... route Σ0..1CodeableConceptHow drug should enter body
Binding: SNOMEDCTRouteCodes (example): A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.

.... method Σ0..1CodeableConceptTechnique for administering medication
Binding: SNOMEDCTAdministrationMethodCodes (example): A coded concept describing the technique by which the medicine is administered.

.... doseAndRate SΣ0..*Element(USCDI) Amount of medication administered
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... type Σ0..1CodeableConceptThe kind of dose or rate specified
Binding: DoseAndRateType (example): The kind of dose or rate specified.

..... dose[x] SΣ0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity S
...... doseRangeRange
..... rate[x] Σ0..1Amount of medication per unit of time
...... rateRatioRatio
...... rateRangeRange
...... rateQuantityQuantity(SimpleQuantity)
.... maxDosePerPeriod Σ0..1RatioUpper limit on medication per unit of time
.... maxDosePerAdministration Σ0..1SimpleQuantityUpper limit on medication per administration
.... maxDosePerLifetime Σ0..1SimpleQuantityUpper limit on medication per lifetime of the patient
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... initialFill 0..1BackboneElementFirst fill details
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... quantity 0..1SimpleQuantityFirst fill quantity
..... duration 0..1DurationFirst fill duration
.... dispenseInterval 0..1DurationMinimum period of time between dispenses
.... validityPeriod 0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense
.... expectedSupplyDuration 0..1DurationNumber of days supply per dispense
.... performer 0..1Reference(Organization)Intended dispenser
... substitution 0..1BackboneElementAny restrictions on medication substitution
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... allowed[x] 1..1Whether substitution is allowed or not
Binding: ActSubstanceAdminSubstitutionCode (example): Identifies the type of substitution allowed.

..... allowedBooleanboolean
..... allowedCodeableConceptCodeableConcept
.... reason 0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example): A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.

... priorPrescription 0..1Reference(MedicationRequest)An order/prescription that is being replaced
... detectedIssue 0..*Reference(DetectedIssue)Clinical Issue with action
... eventHistory 0..*Reference(Provenance)A list of events of interest in the lifecycle

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
MedicationRequest.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.statusReasonexamplemedicationRequest Status Reason Codes
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.categoryexamplemedicationRequest Category Codes
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.priorityrequiredRequestPriority
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.performerTypeexampleProcedurePerformerRoleCodes
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.courseOfTherapyTypeexamplemedicationRequest Course of Therapy Codes
MedicationRequest.dosageInstruction.additionalInstructionexampleSNOMEDCTAdditionalDosageInstructions
MedicationRequest.dosageInstruction.asNeeded[x]exampleSNOMEDCTMedicationAsNeededReasonCodes
MedicationRequest.dosageInstruction.siteexampleSNOMEDCTAnatomicalStructureForAdministrationSiteCodes
MedicationRequest.dosageInstruction.routeexampleSNOMEDCTRouteCodes
MedicationRequest.dosageInstruction.methodexampleSNOMEDCTAdministrationMethodCodes
MedicationRequest.dosageInstruction.doseAndRate.typeexampleDoseAndRateType
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding
MedicationRequest.substitution.allowed[x]exampleActSubstanceAdminSubstitutionCode
MedicationRequest.substitution.reasonexampleSubstanceAdminSubstitutionReason

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Differential View

This structure is derived from MedicationRequest

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... status S1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... intent SC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets

... reported[x] S0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean S
.... reportedReferenceReference S(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile)
... medication[x] S1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject S1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... authoredOn S0..1dateTime(USCDI) When request was initially authored
... requester SC0..1Reference(US Core Practitioner Profile S | US Core Patient Profile | US Core Organization Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile | Device)(USCDI) Who/What requested the Request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... text S0..1string(USCDI) Free text dosage instructions e.g. SIG
.... timing S0..1Timing(USCDI) When medication should be administered
.... doseAndRate S0..*Element(USCDI) Amount of medication administered
..... dose[x] S0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity S
...... doseRangeRange
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding

Constraints

IdGradePath(s)DetailsRequirements
us-core-21errorMedicationRequestrequester SHALL be present if intent is "order"
: (intent='order' or intent='original-order' or intent='reflex-order'or intent='filler-order' or intent='instance-order') implies requester.exists()

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... status ?!SΣ1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... intent ?!SΣC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
Binding: medicationRequest Category Codes (example): A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.


.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets


... doNotPerform ?!Σ0..1booleanTrue if request is prohibiting action
... reported[x] SΣ0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean
.... reportedReferenceReference(US Core Practitioner Profile)
... medication[x] SΣ1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... authoredOn SΣ0..1dateTime(USCDI) When request was initially authored
... requester SΣC0..1Reference(US Core Practitioner Profile)(USCDI) Who/What requested the Request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... text SΣ0..1string(USCDI) Free text dosage instructions e.g. SIG
.... timing SΣ0..1Timing(USCDI) When medication should be administered
.... doseAndRate SΣ0..*Element(USCDI) Amount of medication administered
..... dose[x] SΣ0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.categoryexamplemedicationRequest Category Codes
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorMedicationRequestIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorMedicationRequestIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorMedicationRequestIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorMedicationRequestIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceMedicationRequestA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
us-core-21errorMedicationRequestrequester SHALL be present if intent is "order"
: (intent='order' or intent='original-order' or intent='reflex-order'or intent='filler-order' or intent='instance-order') implies requester.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationRequest C0..*MedicationRequestOrdering of medication for patient or group
us-core-21: requester SHALL be present if intent is "order"
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierExternal ids for this request
... status ?!SΣ1..1code(USCDI) active | on-hold | cancelled | completed | entered-in-error | stopped | draft | unknown
Binding: medicationrequest Status (required): A code specifying the state of the prescribing event. Describes the lifecycle of the prescription.

... statusReason 0..1CodeableConceptReason for current status
Binding: medicationRequest Status Reason Codes (example): Identifies the reasons for a given status.

... intent ?!SΣC1..1code(USCDI) proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Binding: medicationRequest Intent (required): The kind of medication order.

... Slices for category S0..*CodeableConcept(USCDI) Type of medication usage
Slice: Unordered, Open by pattern:$this
Binding: medicationRequest Category Codes (example): A coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment.


.... category:us-core S0..*CodeableConcept(USCDI) Type of medication usage
Binding: medicationRequest Category Codes (required): The type of medication order. Note that other codes are permitted, see Required Bindings When Slicing by Value Sets


... priority Σ0..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): Identifies the level of importance to be assigned to actioning the request.

... doNotPerform ?!Σ0..1booleanTrue if request is prohibiting action
... reported[x] SΣ0..1(USCDI) Reported rather than primary record
.... reportedBooleanboolean S
.... reportedReferenceReference S(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile)
... medication[x] SΣ1..1(USCDI) Medication to be taken
Binding: Medication Clinical Drug (extensible)
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(US Core Medication Profile)
... subject SΣ1..1Reference(US Core Patient Profile)(USCDI) Who or group medication request is for
... encounter S0..1Reference(US Core Encounter Profile)(USCDI) Encounter created as part of encounter/admission/stay
... supportingInformation 0..*Reference(Resource)Information to support ordering of the medication
... authoredOn SΣ0..1dateTime(USCDI) When request was initially authored
... requester SΣC0..1Reference(US Core Practitioner Profile S | US Core Patient Profile | US Core Organization Profile | US Core PractitionerRole Profile | US Core RelatedPerson Profile | Device)(USCDI) Who/What requested the Request
... performer 0..1Reference(Practitioner | PractitionerRole | Organization | Patient | Device | RelatedPerson | CareTeam)Intended performer of administration
... performerType Σ0..1CodeableConceptDesired kind of performer of the medication administration
Binding: ProcedurePerformerRoleCodes (example): Identifies the type of individual that is desired to administer the medication.

... recorder 0..1Reference(Practitioner | PractitionerRole)Person who entered the request
... reasonCode 0..*CodeableConcept(USCDI) Reason or indication for ordering or not ordering the medication
Binding: US Core Condition Codes (extensible)
... reasonReference 0..*Reference(Condition | Observation)(USCDI) US Core Condition or Observation that supports the prescription
... instantiatesCanonical Σ0..*canonical()Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation)What request fulfills
... groupIdentifier Σ0..1IdentifierComposite request this is part of
... courseOfTherapyType 0..1CodeableConceptOverall pattern of medication administration
Binding: medicationRequest Course of Therapy Codes (example): Identifies the overall pattern of medication administratio.

... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*AnnotationInformation about the prescription
... dosageInstruction S0..*Dosage(USCDI) How the medication should be taken
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... sequence Σ0..1integerThe order of the dosage instructions
.... text SΣ0..1string(USCDI) Free text dosage instructions e.g. SIG
.... additionalInstruction Σ0..*CodeableConceptSupplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness"
Binding: SNOMEDCTAdditionalDosageInstructions (example): A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".


.... patientInstruction Σ0..1stringPatient or consumer oriented instructions
.... timing SΣ0..1Timing(USCDI) When medication should be administered
.... asNeeded[x] Σ0..1Take "as needed" (for x)
Binding: SNOMEDCTMedicationAsNeededReasonCodes (example): A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.

..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site Σ0..1CodeableConceptBody site to administer to
Binding: SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (example): A coded concept describing the site location the medicine enters into or onto the body.

.... route Σ0..1CodeableConceptHow drug should enter body
Binding: SNOMEDCTRouteCodes (example): A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.

.... method Σ0..1CodeableConceptTechnique for administering medication
Binding: SNOMEDCTAdministrationMethodCodes (example): A coded concept describing the technique by which the medicine is administered.

.... doseAndRate SΣ0..*Element(USCDI) Amount of medication administered
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... type Σ0..1CodeableConceptThe kind of dose or rate specified
Binding: DoseAndRateType (example): The kind of dose or rate specified.

..... dose[x] SΣ0..1(USCDI) Amount of medication per dose
Binding: Common UCUM units (preferred)
Additional BindingsPurpose
UCUMCodesMax Binding
...... doseQuantityQuantity S
...... doseRangeRange
..... rate[x] Σ0..1Amount of medication per unit of time
...... rateRatioRatio
...... rateRangeRange
...... rateQuantityQuantity(SimpleQuantity)
.... maxDosePerPeriod Σ0..1RatioUpper limit on medication per unit of time
.... maxDosePerAdministration Σ0..1SimpleQuantityUpper limit on medication per administration
.... maxDosePerLifetime Σ0..1SimpleQuantityUpper limit on medication per lifetime of the patient
... dispenseRequest S0..1BackboneElement(USCDI) Medication supply authorization
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... initialFill 0..1BackboneElementFirst fill details
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... quantity 0..1SimpleQuantityFirst fill quantity
..... duration 0..1DurationFirst fill duration
.... dispenseInterval 0..1DurationMinimum period of time between dispenses
.... validityPeriod 0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed S0..1unsignedInt(USCDI) Number of refills authorized
.... quantity S0..1SimpleQuantity(USCDI) Amount of medication to supply per dispense
.... expectedSupplyDuration 0..1DurationNumber of days supply per dispense
.... performer 0..1Reference(Organization)Intended dispenser
... substitution 0..1BackboneElementAny restrictions on medication substitution
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... allowed[x] 1..1Whether substitution is allowed or not
Binding: ActSubstanceAdminSubstitutionCode (example): Identifies the type of substitution allowed.

..... allowedBooleanboolean
..... allowedCodeableConceptCodeableConcept
.... reason 0..1CodeableConceptWhy should (not) substitution be made
Binding: SubstanceAdminSubstitutionReason (example): A coded concept describing the reason that a different medication should (or should not) be substituted from what was prescribed.

... priorPrescription 0..1Reference(MedicationRequest)An order/prescription that is being replaced
... detectedIssue 0..*Reference(DetectedIssue)Clinical Issue with action
... eventHistory 0..*Reference(Provenance)A list of events of interest in the lifecycle

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
MedicationRequest.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
MedicationRequest.statusrequiredmedicationrequest Status
MedicationRequest.statusReasonexamplemedicationRequest Status Reason Codes
MedicationRequest.intentrequiredmedicationRequest Intent
MedicationRequest.categoryexamplemedicationRequest Category Codes
MedicationRequest.category:us-corerequiredmedicationRequest Category Codes
MedicationRequest.priorityrequiredRequestPriority
MedicationRequest.medication[x]extensibleMedicationClinicalDrug
MedicationRequest.performerTypeexampleProcedurePerformerRoleCodes
MedicationRequest.reasonCodeextensibleUSCoreConditionCodes
MedicationRequest.courseOfTherapyTypeexamplemedicationRequest Course of Therapy Codes
MedicationRequest.dosageInstruction.additionalInstructionexampleSNOMEDCTAdditionalDosageInstructions
MedicationRequest.dosageInstruction.asNeeded[x]exampleSNOMEDCTMedicationAsNeededReasonCodes
MedicationRequest.dosageInstruction.siteexampleSNOMEDCTAnatomicalStructureForAdministrationSiteCodes
MedicationRequest.dosageInstruction.routeexampleSNOMEDCTRouteCodes
MedicationRequest.dosageInstruction.methodexampleSNOMEDCTAdministrationMethodCodes
MedicationRequest.dosageInstruction.doseAndRate.typeexampleDoseAndRateType
MedicationRequest.dosageInstruction.doseAndRate.dose[x]preferredCommon UCUM units
Additional Bindings Purpose
UCUMCodes Max Binding
MedicationRequest.substitution.allowed[x]exampleActSubstanceAdminSubstitutionCode
MedicationRequest.substitution.reasonexampleSubstanceAdminSubstitutionReason

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Quick Start

Below is an overview of the required Server RESTful FHIR interactions for this profile - for example, search and read operations - when supporting the US Core interactions to access this profile’s information (Profile Support + Interaction Support). Note that systems that support only US Core Profiles (Profile Only Support) are not required to support these interactions. See the US Core Server CapabilityStatement for a complete list of supported RESTful interactions for this IG.

  • The syntax used to describe the interactions is described here.

  • Servers providing access to prescription data can use US Core SMART Scopes for:
  • See the General Requirements 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:

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

    GET [base]/MedicationRequest?patient={Type/}[id]&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 optional support for these _include parameters: MedicationRequest:medication
    • including support for OR search on intent (e.g.intent={system|}[code],{system|}[code],...)
    • including support for OR search on status (e.g.status={system|}[code],{system|}[code],...)

    GET [base]/MedicationRequest?patient={Type/}[id]&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 optional support for these _include parameters: MedicationRequest:medication
    • including support for OR search on intent (e.g.intent={system|}[code],{system|}[code],...)

    GET [base]/MedicationRequest?patient={Type/}[id]&intent=order,plan&encounter={Type/}[id]

    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 optional support for these _include parameters: MedicationRequest:medication
    • including support for 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 AND search on authoredon (e.g.authoredon=[date]&authoredon=[date]]&...)

    GET [base]/MedicationRequest?patient={Type/}[id]&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-01-01T00:00:00Z
    2. GET [base]/MedicationRequest?patient=1137192&intent=order,plan&authoredon=ge2019-01-01T00:00:00Z&_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)