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.

Business 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.

Allows identification of the request as it is known by various participating systems and in a way that remains consistent across servers.

The identifier.type element is used to distinguish between the identifiers assigned by the requester/placer and the performer/filler.

Status of the supply request.

Plan/proposal/order fulfilled by this request.

Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply process.

Indicates how quickly this SupplyRequest should be addressed with respect to other requests.

The patient to whom the supply will be given or for whom they will be used.

The 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.

The amount that is being ordered of the indicated item.

Specific parameters for the ordered item. For example, the size of the indicated item.

A code or string that identifies the device detail being asserted.

The value of the device detail.

Range means device should have a value that falls somewhere within the specified range.

When the request should be fulfilled.

When the request was made.

The device, practitioner, etc. who initiated the request.

Who is intended to fulfill the request.

The reason why the supply item was requested.

Where the supply is expected to come from.

Where the supply is destined to go.