1. Key concepts for DeviceAlert rationale


Todd Cooper, John Donnelly, John Garguilo, Peter Gunter, Martin Hurrell, Stefan Karl, Tom Kowalczyk, Koichiro Matsumoto

Meeting Notes

  1. Key issues
    1. Distinction between alert condition and alert signals
    2. Identity of the alert condition in one or more well-designed nomenclatures
    3. Each instance of a time period when the alert condition exists has a life cycle and a unique identifier
    4. Signal state is distinct from the state of the underlying alert condition. It may be latched, that is, be held active when the underlying condition is no longer active
    5. Relation to the state of signals to related content in a hierarchy of Device and DeviceMetric resource instances
  2. For a reasonable degree of completeness, rationale for the DeviceAlert resource needs to include not just giving the key attributes of the alert itself, but also
    1. the IHE ACM uses cases involving communication with end users. This not only the originating device of the alert, but also other devices signaling the alert
    2. This also brings in policy for dynamic management of alert signaling. This involves safety and effectiveness standards and risk management

Action: add discussion of alert policy implementation to HL7 DEV agenda for Work Group Meeting


Draft DeviceAlert rationale mockup

Device Alerting Project (PSS-2005)

DoF: Alerting

Draft DeviceAlert element definitions mockup

  • No labels