This page is part of the Personal Health Device FHIR IG (v0.2.0: STU 1 Ballot 2) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions 
Artifact Packages
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
Profiles for mapping 11073 20601 Personal Health Devices to FHIR resources
Value Sets used and defined in this Implementation Guide
| • CodeableConcept11073MDC | |
| • Quantity11073MDC | |
| • Range11073MDC | |
| • String11073MDC | |
| • 11073MDCnotObject | |
| • ASN1attribute | |
| • ASN1measurement |
Code Systems defined in this Implementation Guide
| • ContinuaDeviceIdentifiers | |
| • ASN1ToHL7 | |
| • ContinuaHFS | |
| • ContinuaPHD |
Capability Statements defined in this Implementation Guide
| • PhdServerCapabilityStatement |
Examples of resources following the Implementation Guide Profiles
| • Example of a first time Bundle upload | This example shows a full transaction Bundle containing Patient, Device, and Observation resources. In subsequent uploads, the Patient and Device resources would not need to be present. |
| • Example of PHD Device | This example PHD Device resource is referenced by other examples and is present for the validator. |
| • Example Bundled upload | This example is an upload from a Bluetooth Low Energy Pulse oximeter device streaming data. In this case the gateway has previously uploaded measurements and saved the logical ids of the Patient and Device resources so they are not re-uploaded. |
| • Example of a numeric. | This example is a simple numeric observation of a pulse rate from a pulse oximeter. This particular example also has a component as the original measurement has a Supplemental Types attribute indicating that this is a SPOT measurement (a stable average). |
| • Example of a NaN case | This example contains a NaN (not a number) measurement. |
| • Example of coded enumeration | This example contains measurement that is itself a code. The measurement comes from a Glucose meter and indicates that the glucose measurement was taken after lunch or dinner. It is also known as the meal context. |
| • Example of a ASN1 BITs measurement | This example is a device and sensor status measurement from a pulse oximeter. This measurement indicates one or more issues the sensor had attempting to take the measurement, for example, finger poorly positioned, cannot get a sufficiently strong signal, etc. |
| • Example of Compound measurement | This example is from a Blood Pressure cuff. |
| • Example of a Coincident Time Stamp | This example is a Coincident Time stamp where the PHG is better synchronized to NTP time than the PHD. This situation is the most prevalent. |
| • Example of a Coincident Time Stamp with a Time Fault | This example is a Coincident Time stamp where the PHD has a time fault; it's current time line is unknown and it reported time stamps in its measurements. |
| • Example of a Blood Pressure PHD | This example maps the MDS data from a Blood Pressure PHD. This device did not report Reg-Cert-Data-List information. |
| • Example of a Glucose Monitor PHD | This example maps an Glucose monitor PHD. It is referenced by a coded Glucose meal context observation |
| • Example of a Coincident Time Stamp | This Coincident Time Stamp observation is referenced by the Blood Pressure Observation |
| • Example of a Coincident Time Stamp referenced by the Glucose Meal Context Observation | This Coincident Time Stamp observation is referenced by the the Glucose meal context Observation |
| • Example of a Gateway | This example maps an Android Gateway |
| • Example of a Patient | This example maps a patient where an optional patient name is included |
Implementation Guide v0.2.0, based on FHIR v4.0.0. © 2017+ Health Level Seven International (Health Care Devices Work Group). IG generated on Tue, Dec 4, 2018 11:36+1100.
Links: Table of Contents |
QA Report | Search |
Version History |
|
Propose a change