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

Difference between revisions of "DeviceUseStatement FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
(migrate to Confluence)
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
 
+
<br /><div class="messagebox cleanup metadata">
−
<div class="messagebox cleanup metadata">
+
Current version: https://confluence.hl7.org/display/FHIR/DeviceUseStatement+FHIR+Resource+Proposal<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:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
Line 13: Line 12:
  
  
−
=PutProposedResourceNameHere=
+
=DeviceUseStatement=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 30: Line 29:
  
 
<!-- 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. -->
−
[[YourCommitteeName]]
+
[[Orders & Observations WG]]
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
 
<!-- 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) -->
−
* Work Group Name
+
*[[Clinical Decision Support Workgroup]]
−
* or link
+
*[[Clinical Quality Information Work Group]]
−
* or "None"
+
 
  
 
==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 -->
 
<!-- 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 -->
 +
 +
1125
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 56:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
'''Note:''' This resource will be undergoing major revisions to align with the FHIR workflow 'event pattern'.
 +
 +
The [http://hl7-fhir.github.io/deviceusestatement.html '''DeviceUseStatement'''] resource:
 +
 +
*records ??? the use of  a healthcare-related device by a patient. The record is the result of a report of use by the patient or another provider. ??? 
 +
**is this within the 80% or are observations used?.
 +
*Is it also the 'event' resource in response to the DeviceUseRequest request  i.e a record of the Delivery?
 +
**Do we need another resource for this??
 +
 +
*This resource does not address the logistics of supply movement and is not associated with a patient.  The SupplyDelivery resource would be used for 'generic' movement of devices.
  
 
==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
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 74: Line 87:
 
* 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 use/receipt of devices by patient are necessary in healthcare.
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 +
 +
*EHRs
  
 
==Content sources==
 
==Content sources==
Line 84: Line 100:
  
 
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 Wrokflow event template
  
 
==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.) -->
 +
1) The resource can be used to note the patient reported use of a
 +
 +
*a wheelchair
 +
*hearing aid
 +
*an  implanted devices such as a pacemaker.
 +
 +
2) The resource can be used to record the delivery of a ordered device  such as:
 +
 +
*bone fixature
 +
*glucometer
 +
*IV Pump
 +
*a home health application
 +
 +
to a patient's room or home
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 99: Line 131:
 
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)
 
  -->
 
  -->
 +
*Task
 +
*Device
 +
*Bodysite
  
 
==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 -->
 +
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.) -->
+
<!-- Idefy the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 +
Eric Haas
 +
 
 +
==Issues==
 +
 
 +
Does there need to be separate Dispense and Statement resources?

Latest revision as of 15:06, 31 October 2019


Current version: https://confluence.hl7.org/display/FHIR/DeviceUseStatement+FHIR+Resource+Proposal
OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



DeviceUseStatement

Owning committee name

Orders & Observations WG

Contributing or Reviewing Work Groups


FHIR Resource Development Project Insight ID

1125

Scope of coverage

Note: This resource will be undergoing major revisions to align with the FHIR workflow 'event pattern'.

The DeviceUseStatement resource:

  • records ??? the use of a healthcare-related device by a patient. The record is the result of a report of use by the patient or another provider. ???
    • is this within the 80% or are observations used?.
  • Is it also the 'event' resource in response to the DeviceUseRequest request i.e a record of the Delivery?
    • Do we need another resource for this??
  • This resource does not address the logistics of supply movement and is not associated with a patient. The SupplyDelivery resource would be used for 'generic' movement of devices.

RIM scope

Lloyd to provide

Resource appropriateness

Resource to record the use/receipt of devices by patient are necessary in healthcare.

Expected implementations

  • EHRs

Content sources

  • FHIR Wrokflow event template

Example Scenarios

1) The resource can be used to note the patient reported use of a

  • a wheelchair
  • hearing aid
  • an implanted devices such as a pacemaker.

2) The resource can be used to record the delivery of a ordered device such as:

  • bone fixature
  • glucometer
  • IV Pump
  • a home health application

to a patient's room or home

Resource Relationships

  • Task
  • Device
  • Bodysite

Timelines

STU3 Ballot

gForge Users

Eric Haas

Issues

Does there need to be separate Dispense and Statement resources?

Retrieved from "https://wiki.hl7.org/w/index.php?title=DeviceUseStatement_FHIR_Resource_Proposal&oldid=166868"