Release 5 Draft Ballot
WorkflowThis page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). 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
| Orders and Observations Work Group | Maturity Level: 1 | Trial Use | Security Category: Patient | Compartments: Patient, Practitioner |
Record of delivery of what is supplied.
This resource is an event 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 event resources.
The scope of the supply resource is for 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.
This resource overlaps with others such as Device and Medication. The Supply resource may be used to describe medications and devices when handling them generically (as any other supply). For example, when processing bulk orders, etc. However, when the medication, device or other aspects of the resource are important, (e.g. in a MedicationRequest or when identifying a device as a performer), the more detailed resource must be used.
This resource is referenced by ChargeItem and itself.
This resource implements the Event pattern.
Structure
UML Diagram (Legend)
XML Template
<SupplyDelivery xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <identifier><!-- 0..* Identifier External identifier --></identifier> <basedOn><!-- 0..* Reference(SupplyRequest) Fulfills plan, proposal or order --></basedOn> <partOf><!-- 0..* Reference(Contract|SupplyDelivery) Part of referenced event --></partOf> <status value="[code]"/><!-- 0..1 in-progress | completed | abandoned | entered-in-error --> <patient><!-- 0..1 Reference(Patient) Patient for whom the item is supplied --></patient> <type><!-- 0..1 CodeableConcept Category of dispense event --></type> <suppliedItem> <!-- 0..1 The item that is delivered or supplied --> <quantity><!-- 0..1 Quantity(SimpleQuantity) Amount dispensed --></quantity> <item[x]><!-- 0..1 CodeableConcept|Reference(Device|Medication|Substance) Medication, Substance, or Device supplied --></item[x]> </suppliedItem> <occurrence[x]><!-- 0..1 dateTime|Period|Timing When event occurred --></occurrence[x]> <supplier><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Dispenser --></supplier> <destination><!-- 0..1 Reference(Location) Where the Supply was sent --></destination> <receiver><!-- 0..* Reference(Practitioner|PractitionerRole) Who collected the Supply --></receiver> </SupplyDelivery>
JSON Template
{
"resourceType" : "SupplyDelivery",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External identifier
"basedOn" : [{ Reference(SupplyRequest) }], // Fulfills plan, proposal or order
"partOf" : [{ Reference(Contract|SupplyDelivery) }], // Part of referenced event
"status" : "<code>", // in-progress | completed | abandoned | entered-in-error
"patient" : { Reference(Patient) }, // Patient for whom the item is supplied
"type" : { CodeableConcept }, // Category of dispense event
"suppliedItem" : { // The item that is delivered or supplied
"quantity" : { Quantity(SimpleQuantity) }, // Amount dispensed
// item[x]: Medication, Substance, or Device supplied. One of these 2:
"itemCodeableConcept" : { CodeableConcept }
"itemReference" : { Reference(Device|Medication|Substance) }
},
// occurrence[x]: When event occurred. One of these 3:
"occurrenceDateTime" : "<dateTime>",
"occurrencePeriod" : { Period },
"occurrenceTiming" : { Timing },
"supplier" : { Reference(Organization|Practitioner|PractitionerRole) }, // Dispenser
"destination" : { Reference(Location) }, // Where the Supply was sent
"receiver" : [{ Reference(Practitioner|PractitionerRole) }] // Who collected the Supply
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since R3
| SupplyDelivery | |
| SupplyDelivery.status |
|
| SupplyDelivery.type |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 2 tests that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)
Structure
XML Template
<SupplyDelivery xmlns="http://hl7.org/fhir">
JSON Template
{
"resourceType" : "SupplyDelivery",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // External identifier
"basedOn" : [{ Reference(SupplyRequest) }], // Fulfills plan, proposal or order
"partOf" : [{ Reference(Contract|SupplyDelivery) }], // Part of referenced event
"status" : "<code>", // in-progress | completed | abandoned | entered-in-error
"patient" : { Reference(Patient) }, // Patient for whom the item is supplied
"type" : { CodeableConcept }, // Category of dispense event
"suppliedItem" : { // The item that is delivered or supplied
"quantity" : { Quantity(SimpleQuantity) }, // Amount dispensed
// item[x]: Medication, Substance, or Device supplied. One of these 2:
"itemCodeableConcept" : { CodeableConcept }
"itemReference" : { Reference(Device|Medication|Substance) }
},
// occurrence[x]: When event occurred. One of these 3:
"occurrenceDateTime" : "<dateTime>",
"occurrencePeriod" : { Period },
"occurrenceTiming" : { Timing },
"supplier" : { Reference(Organization|Practitioner|PractitionerRole) }, // Dispenser
"destination" : { Reference(Location) }, // Where the Supply was sent
"receiver" : [{ Reference(Practitioner|PractitionerRole) }] // Who collected the Supply
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since Release 3
| SupplyDelivery | |
| SupplyDelivery.status |
|
| SupplyDelivery.type |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 2 tests that all execute ok. All tests pass round-trip testing and all r3 resources are valid.)
See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis a
| Path | Definition | Type | Reference |
|---|---|---|---|
| SupplyDelivery.status | Required | SupplyDeliveryStatus | |
| SupplyDelivery.type | Required | SupplyItemType | |
| SupplyDelivery.suppliedItem.item[x] | Example | SNOMEDCTSupplyItem |
Search parameters for 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 |
| identifier | token | External identifier | SupplyDelivery.identifier | |
| patient | reference | Patient for whom the item is supplied | SupplyDelivery.patient (Patient) | |
| receiver | reference | Who collected the Supply | SupplyDelivery.receiver (Practitioner, PractitionerRole) | |
| status N | token | in-progress | completed | abandoned | entered-in-error | SupplyDelivery.status | |
| supplier | reference | Dispenser | SupplyDelivery.supplier (Practitioner, Organization, PractitionerRole) |
FHIR ®© HL7.org 2011+. FHIR R5 Draft Ballot hl7.fhir.core#4.6.0 generated on Thu, Apr 15, 2021 12:30+1000.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change