Difference between revisions of "PHD FHIR IG Proposal"
(migrate to Confluence) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
| − | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | + | Current version: https://confluence.hl7.org/display/FHIR/PHD+FHIR+IG+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> |
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]] | This page documents a [[:category:Pending FHIR IG Proposal|Pending]] [[:category:FHIR IG Proposal|FHIR IG Proposal]] | ||
| Line 37: | Line 37: | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | ||
| − | * None | + | *None |
==FHIR Development Project Insight ID== | ==FHIR Development Project Insight ID== | ||
| Line 61: | Line 61: | ||
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | <!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | ||
| − | |||
==Proposed IG realm and code== | ==Proposed IG realm and code== | ||
| Line 83: | Line 82: | ||
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history --> | <!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history --> | ||
| − | |||
==Expected implementations== | ==Expected implementations== | ||
| Line 94: | Line 92: | ||
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? --> | ||
| + | |||
| + | I do not understand this | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | ||
| + | |||
| + | Given the moving target of the IG build tools and FHIR implementations only one example has been generated to date following this IG. It is a Bundle resource containing all the resources generated by measurements taken from a market Pulse Oximeter. All examples in this guide will come from such personal health devices. This IG makes use of only three FHIR resources, Patient, Device, and Observation. The Patient resource is populated by out of band means and and it is possible in this profile that the Patient resource is never generated and/or uploaded by the gateway. This option is for the protection of PHI. The Device and Observation resources are populated entirely by data received by protocol from the personal health device. The guide consists of six Observation profiles based upon the six types of measurements that can be modeled by the IEEE 11073 20601 specification. There is then a profile for the device information describing the mapping of the PHD MDS data to a Device resource and a similar mapping of the PHG information to a Device resource. | ||
==IG Relationships== | ==IG Relationships== | ||
<!-- Are there any IGs this resource depends on or that depend on this IG? --> | <!-- Are there any IGs this resource depends on or that depend on this IG? --> | ||
| + | |||
| + | This IG depends upon no other IGs. | ||
==Timelines== | ==Timelines== | ||
Latest revision as of 16:53, 31 October 2019
This page documents a Pending FHIR IG Proposal
Contents
- 1 Continua Personal Health Device Implementation Guide
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 IG Purpose
- 1.7 Content location
- 1.8 Proposed IG realm and code
- 1.9 Maintenance Plan
- 1.10 Short Description
- 1.11 Long Description
- 1.12 Involved parties
- 1.13 Expected implementations
- 1.14 Content sources
- 1.15 Example Scenarios
- 1.16 IG Relationships
- 1.17 Timelines
- 1.18 When IG Proposal Is Complete
- 1.19 FMG Notes
Continua Personal Health Device Implementation Guide
Owning work group name
Committee Approval Date:
Please enter the date that the committee approved this IGproposal
Contributing or Reviewing Work Groups
- None
FHIR Development Project Insight ID
Scope of coverage
IG Purpose
This guide provides a standardized way of representing data from IEEE 11073 Personal Health Devices in FHIR.
Content location
Proposed IG realm and code
Universal Realm uv
Maintenance Plan
Short Description
The IG provides a mapping of IEEE 11073 20601 Personal Health Device data to FHIR
Long Description
This guide uses the IEEE 11073 20601 object model to represent device and measurement data from Personal Health Devices. This model is then mapped to FHIR resources based upon the model element types and not their values making the mapping both generic and extensible. An implementation written today will be able to map any future device type that follows the 20601 standard. Personal Health Devices are seen as an important constituent of remote patient monitoring and the design of this guide is strongly influenced by remote patient monitoring concerns and needs.
Involved parties
Expected implementations
The most common set of implementations is expected to be personal health gateways sitting in a patient's home that communicates with the personal health devices, decodes the data, and encodes them into the FHIR resources specified by this guide. Implementation of such gateways have been done on mobile and set-top box platforms, although for the most part based upon earlier versions of FHIR which were not completely sufficient for the needed mapping tasks.
Content sources
I do not understand this
Example Scenarios
Given the moving target of the IG build tools and FHIR implementations only one example has been generated to date following this IG. It is a Bundle resource containing all the resources generated by measurements taken from a market Pulse Oximeter. All examples in this guide will come from such personal health devices. This IG makes use of only three FHIR resources, Patient, Device, and Observation. The Patient resource is populated by out of band means and and it is possible in this profile that the Patient resource is never generated and/or uploaded by the gateway. This option is for the protection of PHI. The Device and Observation resources are populated entirely by data received by protocol from the personal health device. The guide consists of six Observation profiles based upon the six types of measurements that can be modeled by the IEEE 11073 20601 specification. There is then a profile for the device information describing the mapping of the PHD MDS data to a Device resource and a similar mapping of the PHG information to a Device resource.
IG Relationships
This IG depends upon no other IGs.
Timelines
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
