This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Supply FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
<div class="messagebox cleanup metadata">
+
 
−
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
+
 
−
<div style="background:#F0F0F0">
 
−
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
−
</div>
 
−
</div>
 
−
[[Category:FHIR Resource Proposal]]
 
−
[[Category:Pending FHIR Resource Proposal]]
 
  
  
Line 12: Line 6:
  
  
−
=Supply=
+
=SupplyRequest =
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 29: Line 23:
  
 
[[Orders & Observations WG]]
 
[[Orders & Observations WG]]
 +
 +
==Committee Approval Date:==
 +
<i>Please enter the date that the committee approved this Resource proposal</i>
 +
Jan 14, 2013
  
 
==Interested Work Groups==
 
==Interested Work Groups==
  
 
* Pharmacy
 
* Pharmacy
−
* Anatomic Pathology
+
* Devices
−
* Clinical Genomics
+
* Patient Care
−
* Imaging Integration
+
* HSI
−
* Public Health and Emergency Response
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
−
952
+
952  
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 52:
 
  -->
 
  -->
  
−
DEFINITION (SUPPLY):
+
DEFINITION SupplyRequest:
−
The supply resource covers information needed for the ordering and distribution of supplies within a healthcare facility or office.
+
Originally proposed as a single resource "Supply", Supply was split into SupplyRequest and SupplyDelivery 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 may be used to request medication, substances and devices when handling them generically (as any other supply) rather than being associated with a patient.
  
−
Scope Challenge: Should MedicationDispense use the supply resource?
 
  
 
==RIM scope==
 
==RIM scope==
  
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
−
*Role: Supply (classCode=SPLY, moodCode=EVN)
+
*Role: Supply (classCode=SPLY, moodCode=RQO )  
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 79: Line 75:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
−
Supplies in healthcare are necessary for the tracking of delivery of materials to the patient's room, dispensing of medicinal products, etc.
+
Resource to record the request(order) of materials, devices, medications etc to the patient's room, ward, central supply etc are necessary in healthcare.
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
−
Required for CCDA
+
*Required for CCDA
 +
*Record request substance and medications when context is generic -i.e. not specifically tied to  a patient record.
  
 
==Content sources==
 
==Content sources==
Line 95: Line 92:
 
*HL7 v2.x
 
*HL7 v2.x
 
*HL7 v3 Diet and Nutrition DAM
 
*HL7 v3 Diet and Nutrition DAM
 +
*IHE Pharmacy(PHARM) White Paper, Supply of Products for Healthcare
 +
 +
 +
==Example Scenarios==
 +
 +
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 +
 +
*Central supply at Acme Hospital is running low on widgets.  EMH orders a widgets  ‘XYZ’  for restock. 
 +
 +
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 100: Line 107:
 
<!-- What are the resources do you expect will reference this resource and in what context?
 
<!-- What are the resources do you expect will reference this resource and in what context?
  
−
What resources do you expect this resource reference and in what context?
+
What resources do you expect these resources reference and in what context?
  
 
Note: These may be existing resources or "expected" resource
 
Note: These may be existing resources or "expected" resource
Line 106: Line 113:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
−
*Order
+
−
*DiagnosticOrder
+
*Order/OrderResponse
−
*MedicationPrescription
+
*Contract
−
*ImagingStudy
+
*CarePlan
 +
*ClinicalImpression
 +
 
  
 
==Timelines==
 
==Timelines==
Line 115: Line 124:
 
<!-- 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 -->
  
−
*Vote by WG (Ready for ballot): July 2013
+
*Ballot: next ballot (Sept 2016?)
−
*Ballot: September 2013
 
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
−
*Lorraine Constable
+
*Eric Haas
 
*Patrick Loyd
 
*Patrick Loyd
 +
*Jose Costa Teixeira
  
  
 
==Issues==
 
==Issues==
−
# Need to decide whether this gets merged with MedicationDispense. If not, need to define scope to explicitly exclude that (both scope & RIM mapping)
+
# Need to determine boundaries and relationships with MedicationDispense and DeviceUseRequest and VisionPrescription.
−
# Need to expand the description a little bit. Is this only for "supply to patient" or does it include any transfer of material within healthcare?  Can it include patient transport?  If not, where is that handled?
+
##current ballot comment: Do the patient centric and bulk supply need different resources (current ballot comments)
−
# Need relationships identified.  (Particularly confused by ImagingStudy)
+
# Align with Workflow Project
−
# Should look at NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims)
+
# RIM mappings needs completion and review
 +
# Expand the description a little bit.  
 +
# Should look at IHE, NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims)

Latest revision as of 04:56, 18 February 2016




SupplyRequest

Owning committee name

Orders & Observations WG

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

DEFINITION SupplyRequest: Originally proposed as a single resource "Supply", Supply was split into SupplyRequest and SupplyDelivery 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 may be used to request medication, substances and devices when handling them generically (as any other supply) rather than being associated with a patient.


RIM scope

  • Role: Supply (classCode=SPLY, moodCode=RQO )

Resource appropriateness

Resource to record the request(order) of materials, devices, medications etc to the patient's room, ward, central supply etc are necessary in healthcare.

Expected implementations

  • Required for CCDA
  • Record request substance and medications when context is generic -i.e. not specifically tied to a patient record.

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 is running low on widgets. EMH orders a widgets ‘XYZ’ for restock.


Resource Relationships

  • Order/OrderResponse
  • Contract
  • CarePlan
  • ClinicalImpression


Timelines

  • Ballot: next ballot (Sept 2016?)

gForge Users

  • Eric Haas
  • Patrick Loyd
  • Jose Costa Teixeira


Issues

  1. Need to determine boundaries and relationships with MedicationDispense and DeviceUseRequest and VisionPrescription.
    1. current ballot comment: Do the patient centric and bulk supply need different resources (current ballot comments)
  2. Align with Workflow Project
  3. RIM mappings needs completion and review
  4. Expand the description a little bit.
  5. Should look at IHE, NCPDP, probably OpenEHR, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims)
Retrieved from "https://wiki.hl7.org/w/index.php?title=Supply_FHIR_Resource_Proposal&oldid=115469"