This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions 
Health Care Devices Work Group | Maturity Level: 2 | Draft | Security Category: Patient | Compartments: Device, Encounter, Patient |
Detailed Descriptions for the elements in the DeviceAlert resource.
| DeviceAlert | |
| Element Id | DeviceAlert |
| Definition | Describes a noteworthy condition or occurrence determined to exist by a device. |
| Short Display | Describes a noteworthy condition or occurrence determined to exist by a medical device |
| Cardinality | 0..* |
| Type | DomainResource |
| Summary | false |
| Comments | The DeviceAlert resource is derived from the ISO/IEEE 11073-10201 Domain Information Model standard, but is more widely applicable. |
| DeviceAlert.identifier | |
| Element Id | DeviceAlert.identifier |
| Definition | Instance identifiers assigned to a device, by the device or gateway software, manufacturers, other organizations or owners. For example, handle ID. |
| Short Display | Instance identifier |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Cardinality | 0..* |
| Type | Identifier |
| Summary | true |
| Comments | For identifiers assigned to a device by the device or gateway software, the |
| DeviceAlert.procedure | |
| Element Id | DeviceAlert.procedure |
| Definition | The procedure (or procedures) during which the alert condition was raised. |
| Short Display | Procedure during which the alert occurred |
| Cardinality | 0..* |
| Type | Reference(Procedure) |
| Summary | false |
| DeviceAlert.status | |
| Element Id | DeviceAlert.status |
| Definition | in-progress | completed | entered-in-error. |
| Short Display | in-progress | completed | entered-in-error |
| Cardinality | 1..1 |
| Terminology Binding | DeviceAlert Status Codes (Required) |
| Type | code |
| Is Modifier | true (Reason: This element is labeled as a modifier because it has a potential code that indicates the Alert was entered in error.) |
| Summary | true |
| DeviceAlert.category | |
| Element Id | DeviceAlert.category |
| Definition | Partitions the DeviceAlert into one or more categories that can be used to filter searching, to govern access control, or guide system behavior. |
| Short Display | High-level categorization of the DeviceAlert |
| Cardinality | 0..* |
| Terminology Binding | DeviceAlert Category Codes (Example) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAlert.type | |
| Element Id | DeviceAlert.type |
| Definition | physiological | technical. |
| Short Display | physiological | technical |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAlert Type Codes (Extensible) |
| Type | CodeableConcept |
| Summary | false |
| DeviceAlert.priority | |
| Element Id | DeviceAlert.priority |
| Definition | The alert priority is usually reported by the source device. A priority of |
| Short Display | high | medium | low | info |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAlert Priority Codes (Extensible) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAlert.code | |
| Element Id | DeviceAlert.code |
| Definition | The DeviceAlert.code indicates the specific condition that triggered the alert. It may correspond to a DeviceMetric.alert.code or Device.alert.code. |
| Short Display | The meaning of the alert |
| Cardinality | 1..1 |
| Terminology Binding | DeviceAlert Condition Codes (Preferred) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAlert.subject | |
| Element Id | DeviceAlert.subject |
| Definition | Who or what the alert is about. |
| Short Display | Who or what the alert is about |
| Cardinality | 1..1 |
| Type | Reference(Patient | Device | Location | Medication | BiologicallyDerivedProduct | Specimen | NutritionProduct) |
| Summary | true |
| DeviceAlert.encounter | |
| Element Id | DeviceAlert.encounter |
| Definition | The encounter during which the alert condition was raised. |
| Short Display | Encounter during which the alert occurred |
| Cardinality | 0..1 |
| Type | Reference(Encounter) |
| Summary | false |
| DeviceAlert.presence | |
| Element Id | DeviceAlert.presence |
| Definition | Whether the alert condition is currently active. |
| Short Display | Whether the alert condition is currently active |
| Cardinality | 1..1 |
| Type | boolean |
| Summary | true |
| DeviceAlert.presencePeriod | |
| Element Id | DeviceAlert.presencePeriod |
| Definition | An instantaneous condition is reported with the same start and end value. The end value is omitted if the condition is ongoing. |
| Short Display | The period during which the alert condition was active |
| Cardinality | 0..1 |
| Type | Period |
| Summary | false |
| DeviceAlert.device | |
| Element Id | DeviceAlert.device |
| Definition | A top-level or component Device (such as a MDS, VMD, or Channel) that detected the alert condition; or, within such a Device, the specific DeviceMetric (e.g. a heart rate reading) that was in an alert condition. |
| Short Display | The Device (or DeviceMetric) that detected the alert condition |
| Cardinality | 0..1 |
| Type | Reference(Device | DeviceMetric) |
| Summary | false |
| DeviceAlert.location | |
| Element Id | DeviceAlert.location |
| Definition | The location of the subject of the alert at the time that the alert was raised. |
| Short Display | Location of the subject when the alert was raised |
| Cardinality | 0..1 |
| Type | Reference(Location) |
| Summary | false |
| DeviceAlert.derivedFrom | |
| Element Id | DeviceAlert.derivedFrom |
| Definition | The value causing the alert condition. |
| Short Display | The value causing the alert condition |
| Cardinality | 0..* |
| Summary | false |
| DeviceAlert.derivedFrom.observation | |
| Element Id | DeviceAlert.derivedFrom.observation |
| Definition | The Observation whose value is causing the alert condition; or, if |
| Short Display | The Observation having a value causing the alert condition |
| Cardinality | 1..1 |
| Type | Reference(Observation) |
| Summary | false |
| DeviceAlert.derivedFrom.component | |
| Element Id | DeviceAlert.derivedFrom.component |
| Definition | If applicable, the code of the component (of the Observation identified in |
| Short Display | The Observation.component having a value causing the alert condition |
| Cardinality | 0..1 |
| Type | Coding |
| Summary | false |
| DeviceAlert.derivedFrom.limit | |
| Element Id | DeviceAlert.derivedFrom.limit |
| Definition | The limits beyond which a value was detected to cause the alert condition. The actual value is the |
| Short Display | The boundaries beyond which a value was detected to cause the alert condition |
| Cardinality | 0..1 |
| Type | Range |
| Summary | false |
| DeviceAlert.acknowledged | |
| Element Id | DeviceAlert.acknowledged |
| Definition | An indication of whether (true) or not (false) the alert condition has been acknowledged. |
| Short Display | Whether the alert condition has been acknowledged |
| Cardinality | 0..1 |
| Type | boolean |
| Summary | false |
| DeviceAlert.label | |
| Element Id | DeviceAlert.label |
| Definition | The label may combine information from the alert code, priority, the measurement type, measurement value, body sites and other sources, e.g., “HR > 180”. |
| Short Display | Text to be displayed for the alert condition |
| Cardinality | 0..1 |
| Type | string |
| Summary | false |
| DeviceAlert.signal | |
| Element Id | DeviceAlert.signal |
| Definition | Annunciation or notification of the alert condition. |
| Short Display | Annunciation or notification of the alert condition |
| Cardinality | 0..* |
| Summary | false |
| DeviceAlert.signal.activationState | |
| Element Id | DeviceAlert.signal.activationState |
| Definition | Paused indicates that annunciation has temporarily been disabled ("snooze"). |
| Short Display | on | off | paused |
| Cardinality | 1..1 |
| Terminology Binding | DeviceAlert Activation State Codes (Extensible) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAlert.signal.presence | |
| Element Id | DeviceAlert.signal.presence |
| Definition | 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. |
| Short Display | on | latched | off | ack |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAlert Presence Codes (Extensible) |
| Type | CodeableConcept |
| Summary | false |
| DeviceAlert.signal.annunciator | |
| Element Id | DeviceAlert.signal.annunciator |
| Definition | Signalling by the source device is local; signalling elsewhere is considered remote. A reference to the "top level" signalling device may also be present. |
| Short Display | Where the signal is being annunciated |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAlert Annunciation Codes (Required) |
| Type | CodeableReference(Device) |
| Summary | false |
| DeviceAlert.signal.manifestation | |
| Element Id | DeviceAlert.signal.manifestation |
| Definition | How the signal is being annunciated. |
| Short Display | How the signal is being annunciated |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAlert Manifestation Codes (Extensible) |
| Type | CodeableConcept |
| Summary | false |
| DeviceAlert.signal.type | |
| Element Id | DeviceAlert.signal.type |
| Definition | Details of the signal manifestation, such as a 1 meter visual indicator or a 4 meter visual indicator. |
| Short Display | Characteristics of the signal manifestation |
| Cardinality | 0..* |
| Terminology Binding | DeviceAlert Signal Type Codes (Example) |
| Type | CodeableConcept |
| Summary | false |
| DeviceAlert.signal.indication | |
| Element Id | DeviceAlert.signal.indication |
| Definition | The period during which the signal was being annunciated. If there is no indicated period end, the annunciation is on-going. |
| Short Display | When the signal was being annunciated |
| Cardinality | 0..1 |
| Type | Period |
| Summary | false |
| Comments | The indication period start when the signal presence is first on (or latched) and ends when the signal becomes off or acknowledged. |