Describes a noteworthy condition or occurrence determined to exist by a device.

The DeviceAlert resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable.

Business identifiers assigned to this alert, by the source device, gateway software, manufacturers, or other systems or organizations. These identifiers remain constant as the resource is updated and propagates from server to server.

Allows identification of the device alert as it is known by various participating systems and in a way that remains consistent across servers.

Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For identifiers assigned to an alert by the device or gateway software, the system element of the identifier might be set to an identifier of the device.

The procedure (or procedures) during which the alert condition was raised.

The current state of the device alert.

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.

Partitions the device alert into one or more categories that can be used to filter searching, to govern access control and/or to guide system behavior.

Categorization might be done automatically (inferred by code) or manually by user assertion. The absence of a category may limit the ability to determine when the element should be handled, so strong consideration should be given to how systems will be able to determine category values for legacy data and how data that cannot be categorized will be handled. As well, some categories might not be mutually exclusive, so systems should prepare for multiple declared categories - even within a single category 'axis'.

physiological | technical.

The alert priority is usually reported by the source device. A priority of info may indicate that the alert is “for information only” and not urgent action is required. The element may be omitted if the priority is unknown.

A code that indicates the specific condition that triggered the alert.

Who or what the alert is about.

Links the device alert to the appropriate subject context. May also affect access control.

The Encounter during which the alert condition was raised.

Links the device alert to the Encounter context. May also affect access control.

Whether the alert condition is currently active.

This element is used to record the date or time period when the alert condition did occur or is occurring.

This element is used to record the time period during which the alert condition is or was active. The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. A date/time value should be used for instantaneous conditions; without additional guidance, partial date/time values are ambiguous about whether they represent the condition occurring at some point in the partially specified period, or for all of the period. Ongoing events should not include a Period upper bound.

Indicates the device that detected the alert condition. The device may be a top-level Device or component Device (such as an MDS, VMD, or Channel); or may identify the specific DeviceMetric of a Device (e.g., a heart rate reading) that was in an alert condition.

An indication of whether (true) or not (false) the alert condition has been acknowledged.

An indication of who or what acknowledged the alert condition.

The principal physical location of the subject at the time the alert condition occurred. This may be different from the location of the alerting device at that time, and from the current location of either the subject or the alert condition detecting device.

Provides context around the alert occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).

The value causing the alert condition.

Indicates the Observation whose value is causing the alert condition; or, if component is present, the Observation with a component causing the alert condition.

If applicable, the code of the component (of the Observation identified in derivedFrom.observation) having a value causing the alert condition. This may be used when the alert is associated with a specific component of an Observation, rather than the overall Observation; for example, a low diastolic blood pressure. Since the component is identified by matching Observation.component.code, if more than one component have the same code, the specific component is ambiguous. Repetitions of this element indicate additional components contributing to the alert condition.

The limits beyond which a value was detected to cause the alert condition. The actual value is the Observation.value[x] referenced by derivedFrom.observation or, if specified, the Observation.component.value[x] of the component (with Observation.component.code matching derivedFrom.component) of the reference Observation.

The label may combine information from the alert code, priority, the measurement type, measurement value, body sites and other sources, e.g., “HR > 180”.

Annunciation or notification of the alert condition.

Paused indicates that annunciation has temporarily been disabled ("snooze").

Indicates whether the signal is currently being annunciated. An on signal is currently being annunciated; a latched signal is currently being being annunciated although the alert condition has ended; an off signal is not currently being annunciated; and an acknowledged signal is not currently being annunciated because the user has acknowledged the signal.

Signalling by the source device is local; signalling elsewhere is considered remote. A reference to the "top level" signalling device may also be present.

How the signal is being annunciated.

Details of the signal manifestation, such as a 1 meter visual indicator or a 4 meter visual indicator.

The period during which the signal was being annunciated. If there is no indicated period end, the annunciation is on-going.

The indication period start when the signal presence is first on (or latched) and ends when the signal becomes off or acknowledged.