This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SupplyDelivery FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 111: | Line 111: | ||
| − | *Central supply at Acme Hospital resupply floor stock | + | *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== | ==Resource Relationships== | ||
Revision as of 18:09, 26 February 2016
This page documents a Pending FHIR Resource Proposal
Contents
- 1 SupplyDelivery
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Interested Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 Issues
SupplyDelivery
Owning committee name
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal Jan 14, 2013
Interested Work Groups
- Pharmacy
- Devices
- Patient Care
- HSI
FHIR Resource Development Project Insight ID
952
Scope of coverage
The supplyDelivery resource handles the movement of supplies, by providing the "logistics" layer to items that are supplied within healthcare institutions, or between institutions and external suppliers.
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 specifically tied to a patient record.
- Track the distribution of items across the chain (overlap with patient-specific items, like a reserved medication or a named device is to be clarified).
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
- Order/OrderResponse
- medicationDispense
- medication
- Device
- (workflow resources)
Timelines
- Ballot: next ballot (Sept 2016)
gForge Users
- Eric Haas
- Patrick Loyd
- Jose Costa Teixeira
Issues
- Need to determine boundaries and relationships with Device and Medication and Workflow resource.
- Align with Workflow Project
- RIM mappings needs completion and review
- Expand the description a little bit
- Should look at IHE, NCPDP, probably OpenEHR,
- Examples
