Oracle Cloud Infrastructure Documentation

MedicationRequest

Work with FHIR R4 4.0.1 MedicationRequest resources.

Choose an operation for this resource:

The diagram summarizes MedicationRequest requests and responses. See Supported FHIR REST Interactions for the shared interaction model.


A FHIR client sends requests to the DDFS R4 MedicationRequest API. Search returns a Bundle; create, read and update return a resource; vread returns one historical version; delete returns HTTP 204 without a body. Custom operations and FHIR-formatted errors can return OperationOutcome.

FHIR R4 definition: https://hl7.org/fhir/R4/medicationrequest.html. See interaction response codes and common error responses.

Interactions and permissions

MedicationRequest capabilitySupport or requirement
Conditional createNot supported.
Conditional updateNot supported.
Transaction bundlesNot supported.

Resource content

For shared validation-error responses, see OperationOutcome errors.

MedicationRequest detailRequirement or behavior
Required contentSupply status, intent, subject, and exactly one of medicationCodeableConcept or medicationReference.
StatusValid R4 status values are active, on-hold, cancelled, completed, entered-in-error, stopped, draft, and unknown.
Patient referencesThe subject references a Patient or Group.
Patient referencesPatient searches recognize external FHIR Patient URLs without requiring Reference.type.
Patient referencesFor opaque external URLs or identifier-only Patient subjects, supply Reference.type=Patient to identify the target type.
Resource ruleDDFS does not retrieve remote resources to determine their type.
ReferencesA medicationReference targets Medication.
Required contentSupply a valid intent: proposal, plan, order, original-order, reflex-order, filler-order, instance-order, or option.
Choice elementsIf substitution is supplied, include exactly one allowedBoolean or allowedCodeableConcept.
ReferencesreportedBoolean and reportedReference are mutually exclusive.
Token filtersOptional identifiers, reasons, supporting references, notes, dosage instructions, dispense details, substitution, narrative, and extensions are preserved.
Contained resourcesContained Medication and MedicationRequest resources and their fragment IDs are preserved with the enclosing resource, including historical versions.
Contained resourcesLocal references must resolve within the enclosing resource and satisfy the same R4 target-type restrictions as other references.
{
  "resourceType": "MedicationRequest",
  "status": "active",
  "intent": "order",
  "medicationCodeableConcept": {
    "coding": [{"system": "http://www.nlm.nih.gov/research/umls/rxnorm", "code": "860975"}]
  },
  "subject": {"reference": "Patient/{patient-id}"},
  "authoredOn": "2026-01-01"
}