This wiki has undergone a migration to Confluence found Here

Difference between revisions of "DeviceUseRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<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:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
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:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 30: Line 30:
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
[[Clinical Quality Information Work Group]]
+
[[Orders & Observations WG]]
 +
 
 +
==Approval Date==
 +
8/4/2016 (OO Call)
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
Line 36: Line 39:
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
* [[Clinical Decision Support Workgroup]]
 
* [[Clinical Decision Support Workgroup]]
 +
[[Clinical Quality Information Work Group]]
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 41: Line 45:
 
<!-- 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 -->
 
<!-- 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 -->
  
Ken to provide
+
1125
 
 
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 56: Line 59:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
This resource describes the request for the use of a device by a patient. The device may be any pertinent device specified in the Device resource. The device use request may represent an order or a prescription that entered by a practitioner in a CPOE system or a proposal made by a clinical decision support system (CDSS) based on a patient's clinical record and context of care.
+
This resource describes the request for the use of a device by a patient. The device may be any pertinent device specified in the Device resource. The device use request may represent an order or a prescription that was entered by a practitioner in a CPOE system or a proposal made by a clinical decision support (CDS) system based on a patient's clinical record and context of care
 +
 
 +
The [http://hl7-fhir.github.io/supplyrequest.html SupplyRequest] resource is used to request devices when handling them generically (as any other supply) rather than being associated with a patient or having patient specific instructions. When requests are for things associated with a patient, then use DeviceUseRequest.
 +
 
 +
For requesting medications use the [http://hl7-fhir.github.io/medicationrequest.html MedicationRequest] 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. -->
Lloyd to provide
+
*Role: Supply (classCode=SPLY, moodCode=RQO )
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 77: Line 84:
 
* 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  
 
  -->
 
  -->
 +
Resource to record the request(order) of devices for patients are necessary in healthcare.
  
 
==Expected implementations==
 
==Expected implementations==
Line 88: Line 96:
  
 
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? -->
 +
 +
*FHIR request pattern
  
 
==Example Scenarios==
 
==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.) -->
 
<!-- 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.) -->
Examples of devices that may be requested include wheelchair, hearing aids, or an insulin pump. The request will lead to the dispensing of the device to the patient or for use by the patient.
+
 
 +
 
 +
1) A provider may order a:
 +
 
 +
* wheelchair
 +
* hearing aids
 +
* an insulin pump
 +
* pacemaker
 +
 
 +
for his patient.
 +
 
 +
2) A decision support tool may suggest a device based upon a particular protocol.
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 104: Line 125:
 
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)
 
  -->
 
  -->
 +
 +
* CarePlan
 +
* ClnicalImpression
 +
* Device
 +
* Task
 
For additional information, please refer to proposed resource on FHIR site: http://hl7-fhir.github.io/deviceuserequest.html
 
For additional information, please refer to proposed resource on FHIR site: http://hl7-fhir.github.io/deviceuserequest.html
  
Line 109: Line 135:
  
 
<!-- 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 -->
May 2015 DSTU
+
STU3 Ballot
  
 
==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.) -->
cnanjo
+
 
 +
Eric Haas

Latest revision as of 21:18, 30 August 2016



DeviceUseRequest

Owning committee name

Orders & Observations WG

Approval Date

8/4/2016 (OO Call)

Contributing or Reviewing Work Groups

Clinical Quality Information Work Group

FHIR Resource Development Project Insight ID

1125

Scope of coverage

This resource describes the request for the use of a device by a patient. The device may be any pertinent device specified in the Device resource. The device use request may represent an order or a prescription that was entered by a practitioner in a CPOE system or a proposal made by a clinical decision support (CDS) system based on a patient's clinical record and context of care.

The SupplyRequest resource is used to request devices when handling them generically (as any other supply) rather than being associated with a patient or having patient specific instructions. When requests are for things associated with a patient, then use DeviceUseRequest.

For requesting medications use the MedicationRequest resource.

RIM scope

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

Resource appropriateness

Resource to record the request(order) of devices for patients are necessary in healthcare.

Expected implementations

  • CPOE Systems

Content sources

  • FHIR request pattern

Example Scenarios

1) A provider may order a:

  • wheelchair
  • hearing aids
  • an insulin pump
  • pacemaker

for his patient.

2) A decision support tool may suggest a device based upon a particular protocol.

Resource Relationships

  • CarePlan
  • ClnicalImpression
  • Device
  • Task

For additional information, please refer to proposed resource on FHIR site: http://hl7-fhir.github.io/deviceuserequest.html

Timelines

STU3 Ballot

gForge Users

Eric Haas