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
This Implementation Guide defines the use of FHIR resources to convey measurements and supporting data from Personal Health Devices (PHDs) to receiving systems for electronic medical records, clinical decision support, and medical data archiving for aggregate quality measurement and research purposes. In most cases there is a Personal Health Gateway (PHG) that handles the PHD communications. The PHG translates the PHD data to the appropriate form and uploads it to the receiving systems. Uploads generated by Continua compliant PHGs shall use this implementation guide (which follows the Continua H.812-5 guidelines) when transforming the PHD data to FHIR resources.
PHDs are typically consumer devices designed to be used by people without any medical background. These devices are often used in the home and/or on the patient’s person and are a key element in any remote patient monitoring program.
Other related implementation guides focus on acute care point-of-care medical devices (PoCD) and physiological and technical alerts from medical devices.
It is anticipated that most readers of this guide will be familiar with FHIR but not with the 11073 20601 and related standards upon which the PHDs are based. The Technical Implementation Guidance section gives an overview of the essential components of the 11073 20601 model and how its concepts are related to FHIR. The Profiles section gives the details of the mapping between 11073 20601 concepts and FHIR resources, making several references to sub-sections in the Technical Implementation Guidance section.
The 11073 20601 to FHIR mapping details are primarily of interest to implementers of PHG FHIR uploaders. Since only one extension is used in this guide, consumers of the uploaded data need only familiarize themselves with the coding systems. Each of the profiles described has a sub-section aimed at the consumer of the uploaded data. For the most part, these sub-sections and any sections describing the coding systems and value sets are all the consumer needs to be concerned with.