Resource type: supplyrequest

Description

A record of a request for a medication, substance or device used in the healthcare setting.

Elements

PathShortDefinitionComments
Request for a medication, substance or deviceA record of a request for a medication, substance or device used in the healthcare setting.
identifierBusiness Identifier for SupplyRequestBusiness identifiers assigned to this SupplyRequest by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler.
statusdraft | active | suspended +Status of the supply request.
categoryThe kind of supply (central, non-stock, etc.)Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply process.
priorityroutine | urgent | asap | statIndicates how quickly this SupplyRequest should be addressed with respect to other requests.
item[x]Medication, Substance, or Device requested to be suppliedThe item that is requested to be supplied. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list.Note that there's a difference between a prescription - an instruction to take a medication, along with a (sometimes) implicit supply, and an explicit request to supply, with no explicit instructions.
quantityThe requested amount of the item indicatedThe amount that is being ordered of the indicated item.
parameterOrdered item detailsSpecific parameters for the ordered item. For example, the size of the indicated item.
parameter.idUnique id for inter-element referencingUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
parameter.extensionAdditional content defined by implementationsMay be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
parameter.modifierExtensionExtensions that cannot be ignored even if unrecognizedMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
parameter.codeItem detailA code or string that identifies the device detail being asserted.
parameter.value[x]Value of detailThe value of the device detail.Range means device should have a value that falls somewhere within the specified range.
occurrence[x]When the request should be fulfilledWhen the request should be fulfilled.
authoredOnWhen the request was madeWhen the request was made.
requesterIndividual making the requestThe device, practitioner, etc. who initiated the request.
supplierWho is intended to fulfill the requestWho is intended to fulfill the request.
reasonCodeThe reason why the supply item was requestedThe reason why the supply item was requested.
reasonReferenceThe reason why the supply item was requestedThe reason why the supply item was requested.
deliverFromThe origin of the supplyWhere the supply is expected to come from.
deliverToThe destination of the supplyWhere the supply is destined to go.

Scope and Usage

[%stu-note%] In terms of scope and usage, the Orders and Observations workgroups wish to draw the attention of reviewers and implementers to the following issues and changes.

  1. We are seeking input from the implementation community on whether to combine SupplyRequest and DeviceRequest for R4.
  2. The parameters element was added to SupplyRequest for representing custom details for ordering devices.

[todo: where to send input?] [%end-note%]

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 scope of the SupplyRequest resource is for recording the request of supplies used in the healthcare process. 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

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 an 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

Search Parameters

categoryThe kind of supply (central, non-stock, etc.)SupplyRequest.category
requesterIndividual making the requestSupplyRequest.requester
statusdraft | active | suspended +SupplyRequest.status
subjectThe destination of the supplySupplyRequest.deliverTo
supplierWho is intended to fulfill the requestSupplyRequest.supplier

Extension Definitions

These are extension definitions for this resource defined by the spec