This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SupplyDelivery FHIR Resource Proposal"
Jump to navigation
Jump to search
| (6 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 32: | Line 32: | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
<i>Please enter the date that the committee approved this Resource proposal</i> | <i>Please enter the date that the committee approved this Resource proposal</i> | ||
| − | + | 8/4/2016 (OO call) | |
==Interested Work Groups== | ==Interested Work Groups== | ||
| Line 80: | Line 80: | ||
--> | --> | ||
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. | 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. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Expected implementations== | ==Expected implementations== | ||
| Line 128: | Line 122: | ||
--> | --> | ||
| − | * | + | * Task |
| − | * | + | *SupplyRequest |
| − | * | + | *Medication |
*Device | *Device | ||
| + | *Substance | ||
==Timelines== | ==Timelines== | ||
| Line 137: | Line 132: | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| − | *Ballot | + | *STU3 Ballot |
==gForge Users== | ==gForge Users== | ||
| Line 148: | Line 143: | ||
==Issues== | ==Issues== | ||
| − | + | # RIM mappings needs completion and review (part of QA) | |
| − | + | # Should look at IHE, NCPDP, probably OpenEHR (part of QA) | |
| − | # RIM mappings needs completion and review | ||
| − | # Should look at IHE, NCPDP, probably OpenEHR | ||
| − | |||
Latest revision as of 21:18, 30 August 2016
This page documents a Approved 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 8/4/2016 (OO call)
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.
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
- Task
- SupplyRequest
- Medication
- Device
- Substance
Timelines
- STU3 Ballot
gForge Users
- Eric Haas
- Patrick Loyd
- Jose Costa Teixeira
Issues
- RIM mappings needs completion and review (part of QA)
- Should look at IHE, NCPDP, probably OpenEHR (part of QA)
