FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

12.27 Resource SupplyRequest - Content

Orders and Observations icon Work GroupMaturity Level: 1 Trial UseSecurity Category: Patient Compartments: Device, Patient, Practitioner, RelatedPerson

A record of a request to deliver a medication, substance or device used in the healthcare setting to a particular destination for a particular person or organization.

12.27.1 Scope and Usage

This resource is a request resource from a FHIR workflow perspective - see Workflow. It is the intent of the Orders and Observation Workgroup to align this resource with the workflow pattern for request resources.

The SupplyRequest resource expresses the need to deliver an item, while the SupplyDelivery tracks the actual delivery.

The SupplyRequest resource is meant for logistics functions only, not for associating a clinical use of the item, which would be done through the clinical resources such as ServiceRequest, DeviceRequest, MedicationRequest resources. The SupplyRequest relates to the Patient resource (in the deliverTo) but that is meant exclusively only for purposes of having a destination for delivery, not a clinical use.

The scope of the SupplyRequest resource is for recording the request of supplies used in the healthcare process to be delivered to a particular location. This includes supplies specifically used in the treatment of patients as well as supply movement within an institution (transport a set of supplies from materials management to a service unit (nurse station). This resource does not include the provisioning of transportation services.

The SupplyRequest resource allows requesting only a single item. If a workflow requires requesting multiple items simultaneously, this is done using multiple instances of this resource. These instances can be linked in different ways, depending on the needs of the workflow. For guidance, refer to the Request pattern

12.27.2 Boundaries and Relationships

Note that the SupplyRequest records the fact that a request was made. To actually act on that request, additional workflow beyond simply the existence of a SupplyRequest is required. This can be achieved by using an Task resource, with the SupplyRequest referenced from the Task.focus, or by using the SupplyRequest resource in the context of a messaging or service workflow where the request is explicit or implicit. The SupplyDelivery resource represents the fulfillment as a result of SupplyRequest being acted upon.

The SupplyRequest resource is used for inventory management. When requesting medication, substances and devices when there is a patient focus or instructions regarding their use, DeviceRequest or MedicationRequest should be used instead.

For DeviceDispense, MedicationDispense, and BiologicallyDerivedProductDispense (planned), a SupplyRequest does not document the formal association of a device, medication, biologically derived product, or supply item to a patient. The DeviceDispense (or MedicationDispense or BiologicallyDerivceProductDispense) is used to formally document that the device, medication, biologically derived product or supply item is to be used by or for a patient in a medical activity.

To determine the purchase date, a search of DeviceRequest, SupplyRequest, DeviceDispense, or SupplyDelivery as defined in an implementation guide can be done , as the context of the use case actually determines which date of either resource is considered the purchase date.

12.27.3 References to this Resource

12.27.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. SupplyRequest TU DomainResource Request for a medication, substance or device

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ 0..* Identifier Business Identifier for SupplyRequest

... status ?!Σ 0..1 code draft | active | suspended +
Binding: Supply Request Status (Required)
... intent ?!Σ 1..1 code proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: RequestIntent (Required)
... category Σ 0..1 CodeableConcept The kind of supply (central, non-stock, etc.)
Binding: Supply Type (Example)
... priority Σ 0..1 code routine | urgent | asap | stat
Binding: RequestPriority (Required)
... deliverFor 0..1 Reference(Patient) The patient for who the supply request is for
... item Σ 1..1 CodeableReference(Medication | Substance | Device | DeviceDefinition | BiologicallyDerivedProduct | NutritionProduct | InventoryItem) Medication, Substance, or Device requested to be supplied
Binding: SNOMED CT Supply Item (Example)
... quantity Σ 1..1 Quantity The requested amount of the item indicated
... parameter 0..* BackboneElement Ordered item details

.... code 0..1 CodeableConcept Item detail
Binding: ParameterCode (Example)
.... value[x] 0..1 Value of detail
..... valueCodeableConcept CodeableConcept
..... valueQuantity Quantity
..... valueRange Range
..... valueBoolean boolean
... occurrence[x] Σ 0..1 When the request should be fulfilled
.... occurrenceDateTime dateTime
.... occurrencePeriod Period
.... occurrenceTiming Timing
... authoredOn Σ 0..1 dateTime When the request was made
... requester Σ 0..1 Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device | CareTeam) Individual making the request
... supplier Σ 0..* Reference(Organization | HealthcareService) Who is intended to fulfill the request

... reason 0..* CodeableReference(Condition | Observation | DiagnosticReport | DocumentReference) The reason why the supply item was requested
Binding: Supply Request Reason (Example)

... deliverFrom 0..1 Reference(Organization | Location) The origin of the supply
... deliverTo 0..1 Reference(Organization | Location | Patient | RelatedPerson) The destination of the supply

doco Documentation for this format icon

See the Extensions for this resource

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

12.27.4.1 Terminology Bindings

Path ValueSet Type Documentation
SupplyRequest.status SupplyRequestStatus Required

Status of the supply request.
SupplyRequest.intent RequestIntent Required

Codes indicating the degree of authority/intentionality associated with a request.
SupplyRequest.category SupplyType Example

This value sets refers to a Category of supply.
SupplyRequest.priority RequestPriority Required

Identifies the level of importance to be assigned to actioning the request.
SupplyRequest.item SNOMEDCTSupplyItem Example

This value set includes SNOMED CT icon where concept is-a 105590001 (Substance (substance)) or concept is-a 260787004 (Physical object) and provided as an example value set.
SupplyRequest.parameter.code Example
SupplyRequest.reason SupplyRequestReason Example

The reason why the supply item was requested.

12.27.5 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource, and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
category token The kind of supply (central, non-stock, etc.) SupplyRequest.category
date date When the request was made SupplyRequest.authoredOn 26 Resources
identifier token Business Identifier for SupplyRequest SupplyRequest.identifier 65 Resources
patient reference The patient or subject for whom the supply is destined SupplyRequest.deliverFor
(Patient)		 65 Resources
requester reference Individual making the request SupplyRequest.requester
(Practitioner, Organization, CareTeam, Device, Patient, PractitionerRole, RelatedPerson)
status token draft | active | suspended + SupplyRequest.status
subject reference The destination of the supply SupplyRequest.deliverTo
(Organization, Patient, RelatedPerson, Location)
supplier reference Who is intended to fulfill the request SupplyRequest.supplier
(Organization, HealthcareService)