This fragment is available on Appendix.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | github.com | Personal Health Device Implementation Guide, published by HL7 International / Health Care Devices. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phd/ and changes regularly. See the Directory of published versions |
| web | ucum.org |
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
|
| web | github.com | The source for this Implementation Guide is available on HL7 GitHub . |
| web | www.bluetooth.com | Not all PHDs are using a protocol such as GHS that is based upon the 11073-10206 ACOM standard. This IG also supports Bluetooth devices that follow various Bluetooth SIG defined personal health device profiles and services. However, this requires that the information provided by the device can be mapped to IEEE 11073-10206 ACOM System Information, Power, Clock, and Observation objects by the PHG as specified in the transcoding white paper (the latest version can be found here ) when the generated observations are going to be uploaded to a FHIR server. The requirement does not mandate that the PHG actually create these objects, but the resulting FHIR resources have to be composed as if they had come from an IEEE 11073-10206 ACOM compliant PHD device supporting the same type of observations. |
| web | sagroups.ieee.org | IEEE 11073 Standards Committee |
| web | www.bluetooth.com | Bluetooth SIG (Special Interest Group) |
| web | www.ihe.net | IHE (Integrating the Healthcare Enterprise) |
| web | www.pchalliance.org | PCHAlliance (Personal Connected Health Alliance) |
| web | www.itu.int | For those consumer applications that would like to have the codes as LOINC and the uploader did not provide them, a mapping table between MDC and LOINC is also included in LOINC since v2.54 available here . The FHIR MDC to LOINC concept map is available here . One may freely download and use this material as needed in an implementation, but it does require a (free) login account. A mapping from MDC to SNOMED CT for some of the more common codes is available in the somewhat outdated Continua Design Guidelines H.813 HIS Interface document. The guidelines are freely available for download, however licensing requirements for the use of the SNOMED CT code system apply. |
| web | profiles.ihe.net |
The identifier.value
and identifier.system
entries are used to quantify the entries of the given identifier.type. For example, the identifier.system
might be the institution's XDS.b assigning authority and the identifier.value
the patient record number (also known as the patient identifier). See IHE Cross-Enterprise Document Sharing
.
|
| web | standards.ieee.org | A partner IG is the Point of Care Devices (PoCD) Implementation Guide . PoCDs focus on acute care and are operated by medical professionals. PoCDs are more complex than PHDs but both are based upon the IEEE 11073-10201 Domain Information Model (DIM) and use the same coding system, IEEE 11073-10101 . The PoCD DIM is defined by the IEEE 11073-10201 standard while the PHD DIM is based upon the subset defined by the IEEE 11073-10206 Abstract Content Information Model (ACOM) standard. The purpose of both the PHD and PoCD IGs is to ensure that the DIM is mapped to FHIR in a complete, standardized, and consistent manner. Since both IGs are based on the IEEE 11073-10201 DIM, they are harmonized as much as possible. Neither IG provides any interpretation of the mapped data or guidance on actions to be taken with the data once it has been uploaded to a FHIR server. |
| web | standards.ieee.org | ACOM - IEEE 11073-10206: Health Informatics—Device Interoperability Part 10206: Personal Health Device Communication—Abstract Content Information Model |
| web | www.bluetooth.com | GHS - Bluetooth SIG Generic Health Sensor profile and service specifications |
| web | standards.ieee.org | MDC - IEEE 11073-10101: Health informatics — Device interoperability — Part 10101: Point-of-care medical device communication — Nomenclature |
|
PHD-context-complete.jpg
|
|
acom-observations.png
|
|
tree-filter.png
|