SupplyDelivery FHIR Resource Proposal

SupplyDelivery

Owning committee name

Orders & Observations WG

Committee Approval Date:

Please enter the date that the committee approved this Resource proposal Mar 10, 2016

Interested Work Groups

• Pharmacy
• Devices
• Patient Care
• HSI

FHIR Resource Development Project Insight ID

952

Scope of coverage

The SupplyDelivery resource records the actual movement of items within healthcare institutions, or between institutions and external suppliers. It is the 'event' resource in response to the SupplyRequest request. This resource is addresses the logistics of supply movement and is therefore not associated with a patient nor has patient specific instructions. The DeviceUseStatement or MedicationDispense would be used for patient specific "events".

RIM scope

• Role: Supply (classCode=SPLY, moodCode=EVN ?)

Resource appropriateness

Resource to record the delivery of materials, devices, medications etc to the patient's room, ward, central supply etc are necessary for the tracking of devices, substance and medications in healthcare.

Other FHIR resources provide information about the delivery of items. supplyDelivery does not intend to overlap these resources, but to articulate.

• medicationDispense is used to handle the delivery of a medication to a patient. That dispense does not handle the physical transport of the material (like when a staff member takes the medication to deliver it to the floor). SupplyDelivery provides that layer
• the same mechanism would exist for device.
• other items are supplied but this is not covered by a resource, e.g. collection tubes for lab results.
• in several parts of the supply chain the supply and delivery is not done for the "unit of use" (e.g. one device, one medication), but on bulk packages, cartons, etc. This can be covered with the supplyDelivery resource.

Expected implementations

• Required for CCDA
• Record delivery of devices, substance and medications when context is generic -i.e. not tied to a specific patient record.
• Track the distribution of items across the chain
• The SupplyRequest is the counterpart to SupplyDelivery although there may be a SupplyDelivery without a SupplyRequest ( For example, unrequested delivery)

Content sources

• HL7 v3 Pharmacy Standard
• HL7 v2.x
• HL7 v3 Diet and Nutrition DAM
• IHE Pharmacy(PHARM) White Paper, Supply of Products for Healthcare

Example Scenarios

• Central supply at Acme Hospital resupply floor stock.
• Placement of a device in consignment at the OR
• Delivering unwanted items back to the pharmacy
• Delivering items from the external supplier to the pharmacy warehouse

Resource Relationships

• (workflow resources e.g. Order/OrderResponse or TASK)
• medicationDispense
• medication
• Device

Timelines

• Ballot: next ballot (Sept 2016)

gForge Users

• Eric Haas
• Patrick Loyd
• Jose Costa Teixeira

Issues

1. Need to determine boundaries and relationships with Device and Medication and Align with Workflow Project.
2. Need to clarify boundaries when it comes to patient-specific delivery (e.g. transport of a patient-specific device after it has been dispensed)
3. RIM mappings needs completion and review
4. Should look at IHE, NCPDP, probably OpenEHR,
5. Examples