This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Supply FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
Line 1: Line 1:
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
Line 13: Line 12:
  
  
=putProposedResourceNameHere=
+
=Supply=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 29: Line 28:
 
==Owning committee name==
 
==Owning committee name==
  
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
+
[[Orders & Observations WG]]
[[YourCommitteeName]]
 
  
 
==Interested Work Groups==
 
==Interested Work Groups==
  
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) -->
+
* Anatomic Pathology
* Work Group Name
+
* Clinical Genomics
* or link
+
* Imaging Integration
* or "None"
+
* Public Health and Emergency Response
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
+
952
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 53:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
DEFINITION (SUPPLY):
 +
Supplies in healthcare are necessary for the ordering of supplies for the patient's room, dispensing of medicinal products,
  
 
==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 (ActClass=SPLY)
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 74: Line 76:
 
* 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  
 
  -->
 
  -->
 +
The supply resource covers information needed for the dispense and otherwise distribution of supplies within a healthcare facility or office.
  
 
==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) -->
 +
??
  
 
==Content sources==
 
==Content sources==
Line 84: Line 88:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
*HL7 v3 Pharmacy Standard
 +
*HL7 v2.x
 +
*HL7 v3 Diet and Nutrition DAM
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 95: Line 103:
 
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
 +
*OrderResponse ?
 +
*Prescription
  
 
==Timelines==
 
==Timelines==
  
 
<!-- 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: 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
 +
*Patrick Loyd

Revision as of 19:24, 1 April 2013



Supply

Owning committee name

Orders & Observations WG

Interested Work Groups

  • Anatomic Pathology
  • Clinical Genomics
  • Imaging Integration
  • Public Health and Emergency Response

FHIR Resource Development Project Insight ID

952

Scope of coverage

DEFINITION (SUPPLY): Supplies in healthcare are necessary for the ordering of supplies for the patient's room, dispensing of medicinal products,

RIM scope

  • Role: Supply (ActClass=SPLY)

Resource appropriateness

The supply resource covers information needed for the dispense and otherwise distribution of supplies within a healthcare facility or office.

Expected implementations

??

Content sources

  • HL7 v3 Pharmacy Standard
  • HL7 v2.x
  • HL7 v3 Diet and Nutrition DAM

Resource Relationships

  • Order
  • OrderResponse ?
  • Prescription

Timelines

  • Vote by WG (Ready for ballot): July 2013
  • Ballot: September 2013

gForge Users

  • Lorraine Constable
  • Patrick Loyd