Page tree
Skip to end of metadata
Go to start of metadata

DeviceAlert[edit | edit source]

Owning committee name[edit | edit source]

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups[edit | edit source]

Health Care Devices (DEV) WG

FHIR Resource Development Project Insight ID[edit | edit source]


Scope of coverage[edit | edit source]

The DeviceAlert resource is used to represent the status of a simple alarm condition check that a medical device is able to detect. It represents a single alarm only, and alarm can be one of the following type:

  • Physiological alarm (for example: Low SpO2)
  • Technical alarm (for example: Fluid line occlusion)
  • Advisory alert (for example: Alarm of undocumented timeout prior to a surgical procedure)


For the initial scope, this DeviceAlert resource is only applicable to the alarm condition produced by any medical device that implements or derives from the ISO/IEEE 11073 standard.

RIM scope[edit | edit source]


Resource appropriateness[edit | edit source]

This DeviceAlert resource is solely used to communicate a single alarm that produced by any medical device that implements or derives from the ISO/IEEE 11073 standard. If there is a need to communicate multiple alarms are triggered from the same medical device, refers to the DeviceAlertList profile for a more appropriate usage.

Expected implementations[edit | edit source]

  • Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the resource definition for the DeviceAlert.
  • Center for Medical Interoperability is going to work on a prototype ACM system around this DeviceAlert resource.

Content sources[edit | edit source]

  • ISO/IEEE 11073
  • IHE PCD Technical Framework (ACM profile, PCD-04)

Example Scenarios[edit | edit source]

  • Low SpO2, a physiological alarm from a patient monitoring device.
  • Fluid line occlusion, a technical alarm from an infusion pump.
  • An advisory alarm of undocumented timeout prior to a surgical procedure.

Resource Relationships[edit | edit source]


Potentially used by

  • List (DeviceAlertList profile)

Timelines[edit | edit source]

  • This proposal will not be addressed in the current DSTU cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future.

gForge Users[edit | edit source]