This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceUseStatement FHIR Resource Proposal"
Jump to navigation
Jump to search
(migrate to Confluence) |
|||
| (8 intermediate revisions by one other user 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 35: | Line 34: | ||
<!-- 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]] | + | *[[Clinical Quality Information Work Group]] |
| Line 58: | Line 57: | ||
--> | --> | ||
| + | '''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 [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== | ||
| Line 102: | Line 109: | ||
*a wheelchair | *a wheelchair | ||
| − | * hearing aid | + | *hearing aid |
| − | * an implanted devices such as a pacemaker. | + | *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 121: | 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== | ||
| − | <!-- | + | <!-- Idefy the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> |
| − | Eric | + | Eric Haas |
| − | == Issues == | + | ==Issues== |
Does there need to be separate Dispense and Statement resources? | 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
This page documents a Pending FHIR Resource Proposal
Contents
- 1 DeviceUseStatement
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
DeviceUseStatement
Owning committee name
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?
