Short Description

Data from Point-of-Care (acute care) and Personal Health (ranging from exercise trackers to advanced home care equipment) devices are pervasive in health care organizations, and have some special requirements for effective use including data reporting, consumption and archiving, handling of alerts and alarms, traceability to specific subsystems and functions of devices, and troubleshooting. Track activities will include review of R4 to R5 device-related resource changes + definition of a FHIR Device Module page.  Definition of a DeviceAlert resource will also be advanced. Presentations will include standards for communicating device structure and state in addition to what is in a basic clinical observation record based on IEEE and ISO standards, existing practice in IHE Device HL7 V2 profiles such as Device Enterprise Communications (IHE DEC), Point-of-Care Infusion management (IHE PIV/IPEC), and Alert Communication Management (IHE ACM) with proposed mapping to FHIR R4. The new capabilities in the emerging Service-Oriented Point-of-Care Interoperability standard in IEEE and the associated IHE DEV SDPi Profile Supplement will be the subject of a presentation.

Long Description

Setting groundwork to extend the existing HL7 V2 NIST test tools for Patient Care Devices to FHIR


Information and exercise on device data use cases and challenges in FHIR environments

Related Tracks?

Call for participants

People familiar with devices and less familiar with FHIR, and also people fairly familiar with FHIR and less familiar with device data and scenarios. Drop-ins from individuals mainly participating in other tracks are very welcome - if you are interested in the FHIR Point-of-Care Device IG or the FHIR Personal Health Device IG or talking over some device data use case, or some device-related technical problem, stop by at any time.

Track Prerequisites

Basic FHIR operations, Observation and Device resource elements and usage

Track Lead(s)

John Rhoads, Todd Cooper

Track Lead Email(s),

Specification Information

PoCD IG  PHD IG Confluence pages in Devices on FHIR project

Zulip stream

devices stream

Track Kick off Call

Wednesday, April 26 at 4:00 ET

Testing Scenario:

System roles:

network-capable device, device gate gateway, EMR, clinical data repository

A developed EMR or clinical data repository would probably be capable of basic data reception from provided simulators

without a great deal of advance effort. A device or gateway that has not already tried working with the FHIR Personal Health Device IG or the FHIR Point-of-Care IG would probably have a heavy lift supporting testing by Connectathon time, but that level of preparation is not required and tutorial material and samples will be provided to learn how to progress.

Role 1 Name: Device Data Reporter


Providing data for constructing observations with supporting  device detail

Scenario Step 1 Name

Action: Send a simulated point-of care observation to a FHIR server, examine and check relevant resource instances on the FHIR server


Success Criteria:  See details in script

Role 2 Name; Device data consumer

Receive simulated observation with supporting information

Show traceability to specific components sourcing the observation with unique identifying information

Security and Privacy Considerations: At this stage, no special security features are expected.