Difference between revisions of "PHD FHIR IG Proposal"
Line 87: | Line 87: | ||
==Expected implementations== | ==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== | ==Content sources== |
Revision as of 21:38, 24 October 2018
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
Example Scenarios
IG Relationships
Timelines
When IG Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org