Point-of-Care Device Implementation Guide
1.0.0 - STU 1
Point-of-Care Device Implementation Guide
1.0.0 - STU 1
Point-of-Care Device Implementation Guide, published by HL7 International / Devices. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/uv-pocd/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/pocd/ImplementationGuide/hl7.fhir.uv.pocd | Version: 1.0.0 | |||
| IG Standards status: Trial-use | Maturity Level: 2 | Computable Name: PoCDImplementationGuide | ||
This Implementation Guide defines the use of FHIR resources to convey measurements and supporting data
from acute care point-of-care medical devices (PoCD) intended for use by qualified professional in receiving systems for electronic medical records, clinical decision support, and medical data archiving for aggregate quality measurement and research purposes.
It adds "deep metadata for device observations".
Key goals include supplementing the measurement values in an Observation resource with full provenance for traceability, and with
more details of device architecture and dynamically changing attributes such as
calibration history and battery state than is provided for in a FHIR Observation resource. This guide is intended to supplement — not replace — existing approaches such as HL7v2/IHE PCD-01 for communicating device data to device observation consumers.
The next release of this Guide intends to cover physiological and technical alerts from medical devices. Another related implementation guide focuses on home-based personal health devices.
The scope of this Implementation Guide is a FHIR-based treatment of quantitative and qualitative observations communicated from point-of-care medical devices. Devices without communications capabilities are out of scope. Imaging devices are also out of scope. Personal devices intended for home health and fitness purposes to be used by non-professional users are excluded because they are covered by a related Implementation Guide.
This guide builds on the IEEE 11073-10201 Domain Information Model (DIM) and the ISO/IEEE 11073-10101 Nomenclature standard (MDC) for device data modeling and terminology. It focuses on the representation of device data in FHIR resources, rather than on connectivity, transport, or control aspects of device communication. The guide is intended to support the exchange of device data for clinical use, research, and quality measurement purposes, rather than real-time monitoring or device management. The table below summarizes the scope of this guide in relation to the IEEE 11073-10201 DIM:
| IEEE 11073‑10201 area | PoCD IG scope |
|---|---|
| DIM classes & attributes | ✅ In scope |
| Metric semantics | ✅ In scope |
| Alert meaning | ✅ In scope |
| Service model (GET/SET/EVENT) | ❌ Out of scope |
| Scanners | ❌ Out of scope |
| Communication / FSM | ❌ Out of scope |
| Remote control | ❌ Out of scope |
| Transport timing guarantees | ❌ Out of scope |
The “mental model” that usually clicks:
This Implementation Guide is intended for
All implementers are encouraged to review the FHIR Implementer's Safety Check List.
This guide is organized into four main areas: introductory and conceptual material for all readers, technical implementation guidance for system builders, formal conformance definitions (profiles and terminology), and supporting reference material.
Overview Introduces the IEEE 11073-10201 hierarchical device model (MDS → VMD → Channel → Metric), explains how it maps onto FHIR resources, and describes the value of the MDC nomenclature. Also covers common use cases — clinical flowsheet charting, archiving, clinical decision support, analytics, and research data feeds — and provides orientation for both data-consumer and data-provider implementers.
Abbreviations and Definitions Reference glossary of terms, acronyms, and standard identifiers used throughout the guide.
Technical Implementation Guidance is given on following sub-pages:
Profiles Defines the FHIR profiles and extensions specified by this guide, organized by resource type: Device (MDS, VMD, Channel), DeviceMetric (Numeric, Enumeration, Sample Array), and Observation (Numeric, Compound Numeric, Enumeration, Sample Array). Includes guidance on subject attribution and Must Support semantics.
Terminology Covers the ISO/IEEE 11073-10101 MDC nomenclature as the preferred code system, the locally defined code systems and value sets, rules for terminology usage, and instructions for downloading codes from the RTMMS.
Artifact List — Full listing of all conformance resources (profiles, extensions, code systems, value sets, examples) defined in this guide.
Downloads — Package downloads for offline use.
Change Log — History of significant changes between published versions.
This Implementation Guide covers material related to work in other projects and guides including the Personal Health Device Implementation Guide, and IHE profiles.
The Personal Health Device Implementation guide focuses on wellness and chronic disease management devices used mainly by nonprofessionals in home and exercise settings.
This Point-of-Care Device Implementation Guide is focused on acute-care devices for professional use mainly in healthcare delivery facilities.
The Personal Health Device and Point-of-Care Device guides both use information models and nomenclature from the IEEE 11073 Medical Device Communications series of standards and the guides for these two kinds of devices are being developed cooperatively in the Devices On FHIR project with a goal of consistency and ease of use by receiving systems.
The IHE Devices domain domain has developed profiles for conveying acute care device data with context using HL7 V2. The IHE Devices (DEV) domain is the successor to the IHE Patient Care Devices (PCD) domain. The base information system and nomenclature are based on the IEEE 11073 Medical Device Communications standards, also used in this FHIR Implementation Guide.
These profiles cover Device Enterprise Communications (DEC), reporting device observations to enterprise systems including near-real-time charting to electronic medical records, clinical decision support systems, and patient data archive systems. That is similar to the scope of this FHIR Implementation Guide.
A planned future FHIR use case for the Devices on FHIR group is the near-real-time communication of physiological and technical alerts to clinicians, and internal device status and state transition information for systems designed to process such information. This is similar to IHE DEV Alert Communication Management (ACM) and Infusion Pump Event Communication (IPEC) profiles.
Other DEV profiles include Implantable Device Cardiac Observations (IDCO), Point-of-Care Infusion Verification (PIV), and Point-of-Care Identity Management (PCIM). Future versions of this Implementation Guide will extend scope to cover related functionality based on FHIR rather than HL7 V2.
The Observation resource is used to record data that is retrieved from a device. Some values that are
formalized in this resource are required to conform to the
Vital Signs Profile,
for example, heart rate or respiratory rate. Many of these are often provided by a PoCD patient-connected device.
It is possible that in rare cases using this Implementation Guide that a device or device gateway using only ISO/IEEE 11073 terminology codes may not have sufficient information to recognize a particular measurement as within the Vital Signs set and determine an equivalent LOINC code and UCUM unit code for the result. Therefore, provisions must be made to correctly map these terms from 11073 to LOINC and UCUM, and to ensure that this is done at the earliest possible point.
This is an area of necessary coordination between this IG and the Vital Signs Profile.
This Implementation Guide addresses device data modeling and representation in FHIR resources, but implementers must also consider the connectivity behavior and network characteristics required for safe and effective PoCD deployments. The following considerations are important for understanding how to deploy and operate PoCD systems in practice.
Point-of-care devices can generate data at widely varying rates. Some devices produce observations at discrete intervals (e.g., every few seconds or minutes), while others may produce continuous waveform data or high-frequency measurements requiring substantial bandwidth. Implementation planning must account for:
Different clinical use cases require different connectivity patterns:
The choice of connectivity model should be guided by clinical requirements, network reliability, and system architecture.
The requirements for PoCD connectivity vary significantly by clinical context:
Intensive Care Unit (ICU) and Operating Room (OR): These settings typically demand real-time or near-real-time visibility of device data with high reliability. Network infrastructure is usually robust, and clinical staff are trained to interpret continuous device streams. Systems in these settings should support persistent connections and handle high-frequency data transmission.
General Hospital Wards and Acute Care Settings: Clinical needs for data vary by department and patient acuity. Some observations benefit from continuous monitoring while others can be recorded at intervals. System design should accommodate mixed connectivity models.
Home and Ambulatory Settings: These settings often have less reliable network connectivity and different clinical workflows. Data may be collected and stored locally on the device or gateway, then transmitted when connectivity is available.
Understanding these differences is essential for designing systems that safely and effectively integrate PoCD data into diverse clinical environments.
Clinical decision-making depends on understanding both the immediate values of device measurements and their historical context. Implementation selection must consider:
This Implementation Guide focuses on the data models and FHIR representation necessary for exchanging PoCD observations. As experience accumulates from prototype implementations and real-world deployments, further guidance on optimal connectivity patterns, throughput profiling, and operational practices for different clinical settings will be developed. The interaction between multiple implementations, including considerations of performance under different network conditions and clinical workflow integration, will inform future versions of this guide.
Future capabilities are planned for this General PoCD IG including:
This Implementation Guide builds upon and references the following standards, guides, and external sources:
These standards are available from the IEEE Standards Association.
IHE still uses the named transactions (PCD-01, PCD-02, etc.) for profiles within the Devices domain, although the domain itself was renamed from Patient Care Devices (PCD) to Devices (DEV) around 2019–2020.
These profiles are publicly available on the IHE website.
IG © 2017+ HL7 International / Devices. Package hl7.fhir.uv.pocd#1.0.0 based on FHIR 4.0.1. Generated 2026-04-16
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change