Name

datatype

cardinality

definition

DeviceAlert

DomainResource

identifier

Identifier

0..*

Brief: Instance identifier

Detailed:

Comments:

Brief: Instance resource status

Detailed:

Comments:

code

1..1

Brief: Identifies the specific meaning of the alert

Detailed:

Comments:

priority

code

0..1

Brief: Severity of the alert

Detailed:

Comments:

type

code

1..1

Brief: Whether the alert is physiological (about the patient) or technical (about the device)

Detailed:

Comments:

subject

Reference(Patient|Device)

1..1

1. Brief: Patient or device that the alert is about

Detailed:

Comments: How does this relate with DeviceAssociation? How about reference to a Device Metric? Where should it point in the DeviceHierarchy?

condition[x]
with choices
conditionDateTime
conditionPeriod

Brief: Time when condition started if not complete, period of time after condition ended

Detailed:

Comments:

Brief: Reason for absence of condition[x] (time of alert)

Detailed:

ValueSet: 

Comments: Improve the name?

Brief: Device Reference for MDS, VMD, Channel and DeviceMetric for individual Metric (e.g. HR in a HR HIGH Alarm).

Detailed:

Comments: In smart alarming, one device is calling the alert, though multiple devices may be providing inputs

Brief: Evidentiary data that is needed to interpret the condition or that is the reason why the condition is present

Detailed: 

Comments: Does it really need to reference a Device or DeviceMetric rather than the Observation actually containing the evidence. Future possible elaboration: Normally just one, but allowing for multiple sources to derive from (problem: what is the role of each, how do they relate to one another). 

alarmText

  type

  string

Brief: Short but informative description of the alert for limited-space presentation

Detailed:

Comments: Highly recommended to have what is displayed on the device, and a descriptive text. Should this be a BackboneElement to include an indication of what the meaning of the different instances of alarmText are (for short descriptor, longer descriptor, alternate languages etc.)

Brief: 

Detailed: 

Very Detailed: Documentation SafetyClassification allows POC MEDICAL DEVICE manufacturers to limit their responsibility for the provided objects that allow informational use or use in clinical functions. It reflects the quality of the respective data from the risk management perspective of the data provider.
Enumeration values prefixed with "Med" indicate that the manufacturer has considered a clinical function related to the object in its development process, particularly the risk management, software development, usability, and verification process. (BICEPS B.449 SafetyClassification)

ValueSet: Inf, MedA, MedB, MedC

Comments: