Clément Ledoux

How to handle MaxTechnical/PhysiologicalParallelAlarms

Unit of Measure for Ranges in a LimitAlertCondition

There can be multiple use cases that one would like to support with this information: Clinical and operational reporting: Admission and discharge dates make it possible to accurately show when a patient was in the hospital, especially in retrospective or historical reports. Device-related events (for example, when monitoring data starts or stops) do not reliably indicate when a patient was admitted or discharged, as devices may be connected, disconnected, replaced, or reassigned for technical or...

How to provide a display range

APKP Discussion 2024-05-06: If we go this way, please include a note including examples for when a Provider should use the ActivationState = Off and Presence = True. The issue with this requirement is that we are providing information about the past and not anymore just about the actual state of the medical device.

In this case, should we remove R0216 also? R0216: For each pm:AlertSignalState, while @ActivationState = Off, a SERVICE PROVIDER SHALL set @Presence = Off. This was introduced via the Ticket #378. IMHO either we have the same requirement for Condition and Signals or none.

Prohibit any other state for AlertConditionState/@ActivationState = Off than Presence = false

Consider adding a requirement: While pm:AlertSignalState/@ActivationState = Psd, a SERVICE PROVIDER SHALL NOT set pm:AlertSignalState/@Presence = On. and: For each pm:AlertSignalState, while @ActivationState = On, a SERVICE PROVIDER SHALL set pm:AlertConditionState/@ActivationState = On for ALERT CONDITION referenced in the pm:AlertSignalState/@ConditionSignaled.