Personal Health Device Implementation Guide, published by HL7 International / Devices. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot 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
| Page standards status: Informative |
This example demonstrates a PHD Device Alert resource that represents a high systolic blood pressure alert condition from a personal health device. The alert is triggered when the systolic blood pressure measurement exceeds the configured threshold limits.
The resource conforms to the PhdDeviceAlert profile, which is based on the FHIR R6 DeviceAlert resource type. This ensures compatibility with the FHIR Personal Health Device (PHD) implementation guide for device alert conditions.
The optional category element provides a coarse, high-level grouping of the alert for
filtering and routing, bound to the Device Alert Category Value Set
(e.g. battery/power, communication/connectivity, measurement-validity). The physiological
vs. technical distinction is carried separately by type. Because this example is a
physiological threshold alert, no operational category is set.
The alert references the source measurement observation via the derivedFrom element:
Observation/compound-numeric-blood-pressureThis structure allows the alert to be associated with a specific component of a compound observation, making it clear that the alert applies to systolic BP rather than diastolic or mean BP.
occurrence has no end)The label element provides a human-readable description: "Systolic BP > 140 mm[Hg]", which combines information about the measurement type, the threshold, and the alert condition.
The signal element describes the annunciation or notification of the alert:
Patient/patientExample-1Device/phd-711000FEFF5F49B0.B0495F001071)This example represents a common scenario in remote patient monitoring where:
Unlike older approaches where alert information was embedded within the measurement observation (using extensions), this example demonstrates the newer pattern of representing alerts as separate DeviceAlert resources. This provides:
Profile: PhdDeviceAlert
status: In Progress
type: Physiological
code: Systolic blood pressure high alert
subject: Sisansarah Lorianthah Piggy (no stated gender), DoB Unknown ( Medical record number: sisansarahId)
occurrence: 2018-11-11 11:38:15-0500 --> (ongoing)
| Observation | Component | Limit |
| Observation Blood pressure | unknown: 150021 (MDC_PRESS_BLD_NONINV_SYS) | 90-140 mm[Hg] |
label: Systolic BP > 140 mm[Hg]
| ActivationState | Presence | Manifestation | Type |
| On | On | Auditory | Alerting when systolic BP > 140 mm[Hg] |