DSTU2 QA Preview

This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

5.24 Resource SupplyRequest - Content

Orders and Observations Work GroupMaturity Level: 0Compartments: Patient

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

5.24.1 Scope and Usage

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.

5.24.2 Boundaries and Relationships

Note that the SupplyRequest a record of the fact that a request was made. To actually request that a a supply be ordered, additional workflow beyond simply the existence of a SupplyRequest is required. This can be achieved by using an Order resource, with the SupplyRequest referenced from the Order.details, or by using the SupplyRequest resource in the context of an messaging or service workflow where the request is explicit or implicit.

This resource overlaps with DeviceUseRequest and MedicationOrder. The SupplyRequest resource may be used to request medication, substances and devices when handling them generically (as any other supply). For example, when processing bulk orders, etc. TODO - finish defining boundaries.

This resource is referenced by CarePlan and ClinicalImpression

5.24.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. SupplyRequest ΣDomainResourceRequest for a medication, substance or device
... patient Σ0..1Reference(Patient)Patient for whom the item is supplied
... source Σ0..1Reference(Practitioner | Organization | Patient)Who initiated this order
... date Σ0..1dateTimeWhen the request was made
... identifier Σ0..1IdentifierUnique identifier
... status ?! Σ0..1coderequested | completed | failed | cancelled
SupplyRequestStatus (Required)
... kind Σ0..1CodeableConceptThe kind of supply (central, non-stock, etc)
Supply Type (Required)
... orderedItem Σ0..1Reference(Medication | Substance | Device)Medication, Substance, or Device requested to be supplied
... supplier Σ0..*Reference(Organization)Who is intended to fulfill the request
... reason[x] Σ0..1Why the supply item was requested
.... reasonCodeableConceptCodeableConcept
.... reasonReferenceReference(any)
... when Σ0..1BackboneElementWhen the request should be fulfilled
.... code Σ0..1CodeableConceptFulfilment code
.... schedule Σ0..1TimingFormal fulfillment schedule

doco Documentation for this format

XML Template

<SupplyRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <patient><!-- 0..1 Reference(Patient) Patient for whom the item is supplied --></patient>
 <source><!-- 0..1 Reference(Practitioner|Organization|Patient) Who initiated this order --></source>
 <date value="[dateTime]"/><!-- 0..1 When the request was made -->
 <identifier><!-- 0..1 Identifier Unique identifier --></identifier>
 <status value="[code]"/><!-- 0..1 requested | completed | failed | cancelled -->
 <kind><!-- 0..1 CodeableConcept The kind of supply (central, non-stock, etc) --></kind>
 <orderedItem><!-- 0..1 Reference(Medication|Substance|Device) Medication, Substance, or Device requested to be supplied --></orderedItem>
 <supplier><!-- 0..* Reference(Organization) Who is intended to fulfill the request --></supplier>
 <reason[x]><!-- 0..1 CodeableConcept|Reference(any) Why the supply item was requested --></reason[x]>
 <when>  <!-- 0..1 When the request should be fulfilled -->
  <code><!-- 0..1 CodeableConcept Fulfilment code --></code>
  <schedule><!-- 0..1 Timing Formal fulfillment schedule --></schedule>
 </when>
</SupplyRequest>

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. SupplyRequest ΣDomainResourceRequest for a medication, substance or device
... patient Σ0..1Reference(Patient)Patient for whom the item is supplied
... source Σ0..1Reference(Practitioner | Organization | Patient)Who initiated this order
... date Σ0..1dateTimeWhen the request was made
... identifier Σ0..1IdentifierUnique identifier
... status ?! Σ0..1coderequested | completed | failed | cancelled
SupplyRequestStatus (Required)
... kind Σ0..1CodeableConceptThe kind of supply (central, non-stock, etc)
Supply Type (Required)
... orderedItem Σ0..1Reference(Medication | Substance | Device)Medication, Substance, or Device requested to be supplied
... supplier Σ0..*Reference(Organization)Who is intended to fulfill the request
... reason[x] Σ0..1Why the supply item was requested
.... reasonCodeableConceptCodeableConcept
.... reasonReferenceReference(any)
... when Σ0..1BackboneElementWhen the request should be fulfilled
.... code Σ0..1CodeableConceptFulfilment code
.... schedule Σ0..1TimingFormal fulfillment schedule

doco Documentation for this format

XML Template

<SupplyRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <patient><!-- 0..1 Reference(Patient) Patient for whom the item is supplied --></patient>
 <source><!-- 0..1 Reference(Practitioner|Organization|Patient) Who initiated this order --></source>
 <date value="[dateTime]"/><!-- 0..1 When the request was made -->
 <identifier><!-- 0..1 Identifier Unique identifier --></identifier>
 <status value="[code]"/><!-- 0..1 requested | completed | failed | cancelled -->
 <kind><!-- 0..1 CodeableConcept The kind of supply (central, non-stock, etc) --></kind>
 <orderedItem><!-- 0..1 Reference(Medication|Substance|Device) Medication, Substance, or Device requested to be supplied --></orderedItem>
 <supplier><!-- 0..* Reference(Organization) Who is intended to fulfill the request --></supplier>
 <reason[x]><!-- 0..1 CodeableConcept|Reference(any) Why the supply item was requested --></reason[x]>
 <when>  <!-- 0..1 When the request should be fulfilled -->
  <code><!-- 0..1 CodeableConcept Fulfilment code --></code>
  <schedule><!-- 0..1 Timing Formal fulfillment schedule --></schedule>
 </when>
</SupplyRequest>

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.24.3.1 Terminology Bindings

PathDefinitionTypeReference
SupplyRequest.status Status of the supply requestRequiredSupplyRequestStatus
SupplyRequest.kind Category of supply requestRequiredSupply Type

5.24.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
datedateWhen the request was madeSupplyRequest.date
identifiertokenUnique identifierSupplyRequest.identifier
kindtokenThe kind of supply (central, non-stock, etc)SupplyRequest.kind
patientreferencePatient for whom the item is suppliedSupplyRequest.patient
(Patient)
sourcereferenceWho initiated this orderSupplyRequest.source
(Patient, Organization, Practitioner)
statustokenrequested | completed | failed | cancelledSupplyRequest.status
supplierreferenceWho is intended to fulfill the requestSupplyRequest.supplier
(Organization)