STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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

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

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

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, DeviceUseRequest or MedicationRequest should be used instead

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[x] Σ0..1Medication, Substance, or Device requested to be supplied
SNOMED CT Supply Item (Example)
.... orderedItemCodeableConceptCodeableConcept
.... orderedItemReferenceReference(Medication | Substance | Device)
... supplier Σ0..*Reference(Organization)Who is intended to fulfill the request
... reason[x] Σ0..1Why the supply item was requested
SupplyRequestReason (Example)
.... reasonCodeableConceptCodeableConcept
.... reasonReferenceReference(Any)
... when Σ0..1BackboneElementWhen the request should be fulfilled
.... code Σ0..1CodeableConceptFulfilment code
Supply Request When (Example)
.... schedule Σ0..1TimingFormal fulfillment schedule

doco Documentation for this format

UML Diagram (Legend)

SupplyRequest (DomainResource)A link to a resource representing the person whom the ordered item is forpatient : Reference [0..1] « Patient »The Practitioner , Organization or Patient who initiated this order for the supplysource : Reference [0..1] « Practitioner|Organization|Patient »When the request was madedate : dateTime [0..1]Unique identifier for this supply requestidentifier : Identifier [0..1]Status of the supply request (this element modifies the meaning of other elements)status : code [0..1] « Status of the supply request (Strength=Required)SupplyRequestStatus! »Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply processkind : CodeableConcept [0..1] « Category of supply request (Strength=Required)Supply Type! »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 listorderedItem[x] : Type [0..1] « CodeableConcept|Reference(Medication| Substance|Device); The item that was requested (Strength=Example)SNOMED CT Supply Item?? »Who is intended to fulfill the requestsupplier : Reference [0..*] « Organization »Why the supply item was requestedreason[x] : Type [0..1] « CodeableConcept|Reference(Any); Why the supply item was requested (Strength=Example) SupplyRequestReason?? »WhenCode indicating when the request should be fulfilledcode : CodeableConcept [0..1] « When the request should be fulfilled (Strength=Example)Supply Request When?? »Formal fulfillment scheduleschedule : Timing [0..1]When the request should be fulfilledwhen[0..1]

XML Template

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:SupplyRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:SupplyRequest.patient [ Reference(Patient) ]; # 0..1 Patient for whom the item is supplied
  fhir:SupplyRequest.source [ Reference(Practitioner|Organization|Patient) ]; # 0..1 Who initiated this order
  fhir:SupplyRequest.date [ dateTime ]; # 0..1 When the request was made
  fhir:SupplyRequest.identifier [ Identifier ]; # 0..1 Unique identifier
  fhir:SupplyRequest.status [ code ]; # 0..1 requested | completed | failed | cancelled
  fhir:SupplyRequest.kind [ CodeableConcept ]; # 0..1 The kind of supply (central, non-stock, etc.)
  # SupplyRequest.orderedItem[x] : 0..1 Medication, Substance, or Device requested to be supplied. One of these 2
    fhir:SupplyRequest.orderedItemCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.orderedItemReference [ Reference(Medication|Substance|Device) ]
  fhir:SupplyRequest.supplier [ Reference(Organization) ], ... ; # 0..* Who is intended to fulfill the request
  # SupplyRequest.reason[x] : 0..1 Why the supply item was requested. One of these 2
    fhir:SupplyRequest.reasonCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.reasonReference [ Reference(Any) ]
  fhir:SupplyRequest.when [ # 0..1 When the request should be fulfilled
    fhir:SupplyRequest.when.code [ CodeableConcept ]; # 0..1 Fulfilment code
    fhir:SupplyRequest.when.schedule [ Timing ]; # 0..1 Formal fulfillment schedule
  ];
]

Changes since DSTU2

SupplyRequest
SupplyRequest.orderedItem[x] Renamed from orderedItem to orderedItem[x]
Add CodeableConcept

See the Full Difference for further information

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[x] Σ0..1Medication, Substance, or Device requested to be supplied
SNOMED CT Supply Item (Example)
.... orderedItemCodeableConceptCodeableConcept
.... orderedItemReferenceReference(Medication | Substance | Device)
... supplier Σ0..*Reference(Organization)Who is intended to fulfill the request
... reason[x] Σ0..1Why the supply item was requested
SupplyRequestReason (Example)
.... reasonCodeableConceptCodeableConcept
.... reasonReferenceReference(Any)
... when Σ0..1BackboneElementWhen the request should be fulfilled
.... code Σ0..1CodeableConceptFulfilment code
Supply Request When (Example)
.... schedule Σ0..1TimingFormal fulfillment schedule

doco Documentation for this format

UML Diagram (Legend)

SupplyRequest (DomainResource)A link to a resource representing the person whom the ordered item is forpatient : Reference [0..1] « Patient »The Practitioner , Organization or Patient who initiated this order for the supplysource : Reference [0..1] « Practitioner|Organization|Patient »When the request was madedate : dateTime [0..1]Unique identifier for this supply requestidentifier : Identifier [0..1]Status of the supply request (this element modifies the meaning of other elements)status : code [0..1] « Status of the supply request (Strength=Required)SupplyRequestStatus! »Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply processkind : CodeableConcept [0..1] « Category of supply request (Strength=Required)Supply Type! »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 listorderedItem[x] : Type [0..1] « CodeableConcept|Reference(Medication| Substance|Device); The item that was requested (Strength=Example)SNOMED CT Supply Item?? »Who is intended to fulfill the requestsupplier : Reference [0..*] « Organization »Why the supply item was requestedreason[x] : Type [0..1] « CodeableConcept|Reference(Any); Why the supply item was requested (Strength=Example) SupplyRequestReason?? »WhenCode indicating when the request should be fulfilledcode : CodeableConcept [0..1] « When the request should be fulfilled (Strength=Example)Supply Request When?? »Formal fulfillment scheduleschedule : Timing [0..1]When the request should be fulfilledwhen[0..1]

XML Template

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:SupplyRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:SupplyRequest.patient [ Reference(Patient) ]; # 0..1 Patient for whom the item is supplied
  fhir:SupplyRequest.source [ Reference(Practitioner|Organization|Patient) ]; # 0..1 Who initiated this order
  fhir:SupplyRequest.date [ dateTime ]; # 0..1 When the request was made
  fhir:SupplyRequest.identifier [ Identifier ]; # 0..1 Unique identifier
  fhir:SupplyRequest.status [ code ]; # 0..1 requested | completed | failed | cancelled
  fhir:SupplyRequest.kind [ CodeableConcept ]; # 0..1 The kind of supply (central, non-stock, etc.)
  # SupplyRequest.orderedItem[x] : 0..1 Medication, Substance, or Device requested to be supplied. One of these 2
    fhir:SupplyRequest.orderedItemCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.orderedItemReference [ Reference(Medication|Substance|Device) ]
  fhir:SupplyRequest.supplier [ Reference(Organization) ], ... ; # 0..* Who is intended to fulfill the request
  # SupplyRequest.reason[x] : 0..1 Why the supply item was requested. One of these 2
    fhir:SupplyRequest.reasonCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.reasonReference [ Reference(Any) ]
  fhir:SupplyRequest.when [ # 0..1 When the request should be fulfilled
    fhir:SupplyRequest.when.code [ CodeableConcept ]; # 0..1 Fulfilment code
    fhir:SupplyRequest.when.schedule [ Timing ]; # 0..1 Formal fulfillment schedule
  ];
]

Changes since DSTU2

SupplyRequest
SupplyRequest.orderedItem[x] Renamed from orderedItem to orderedItem[x]
Add CodeableConcept

See the Full Difference for further information

 

Alternate definitions: Master Definition (XML, JSON), XML Schema/Schematron (for ) + JSON Schema, ShEx (for Turtle), JSON-LD (for RDF as JSON-LD),

PathDefinitionTypeReference
SupplyRequest.status Status of the supply requestRequiredSupplyRequestStatus
SupplyRequest.kind Category of supply requestRequiredSupply Type
SupplyRequest.orderedItem[x] The item that was requestedExampleSNOMED CT Supply Item
SupplyRequest.reason[x] Why the supply item was requestedExampleSupplyRequestReason
SupplyRequest.when.code When the request should be fulfilledExampleSupply Request When

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

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