Alarms to be implemented in FSM

[simeonedussoni]

Here we collect needed alarms to be implemented in the ventilator. Related signals, sensors etc. will be read by a dedicated FSM which will be in charge of generating the corresponding buzzer/light conditions as well as to pass infos to the controller. Many alarms are already discussed in several places.

[simeonedussoni]

Starting the list, anyone can contribute especially @claudiolorini @andreamerello @MarcoCrepaldi-iit

number	alarm	signal triggering	action performed	type	implemented
1	pressure drop alarm	pressure drop in the supply line, S7	sound, and light for immediate intervention	definitive	✔️
2	power supply alarm	the power supply from the wall outlet is down	sound and light for immediate intervention (within the battery duration)	definitive
3	breaking of pressure regulator in the supply line	huge pressure measured by S7	warning on incorrect status	definitive (see note 1)	✔️
4	overpressure alarm in inspiratory branch	high pressure sensed by S3, S1	sound, and light for signaling, ventilator stops inflating and resume if the pressure goes back	transitory	✔️
5	PEEP alarm	reading from S4 going below PEEP value	sound and light for signaling, ventilator continues inflating	transitory	✔️
6	Low Volume Alarm	the integral of input flow measured by S2 is below the limit for more than one respiratory act	sound and light for signaling, ventilator continues inflating	derived	✔️
7	Oxygen concentration	the oxygen concentration falls outside of user-defined limits or below 18% (safety level exceeded)	visual signaling, sound if safety level exceeded	transitory (definitive if safety level exceeded)

types of alarms:

• definitive: block the system and allow for atmospheric flow in fully passive mode, requires intervention from the user to solve problem and reset alarms.
• transitory: the ventilator can resume normal operation if the measured quantity falls back in the operating range, user must be aware of the alarm triggering which is used to identify possible problems
• derived: this is calculated from measured quantities, e.g. an alarm measuring the leakage from the mask as the difference from inspired and expired volumes.

notes

1. this evenience can be handled by the control at least in the simulated environment. We need to resume this situation anyway as it is a potential stress for the aparatus

[simeonedussoni]

please add alarms that I may have forgot.

[simeonedussoni]

alarms in ventilator SERVO-i VENTILATOR SYSTEM V6.0:

[simeonedussoni]

On the other side, the Spencer ventilator has only two alarms:

• low battery level
• low pressure of gas supply.

[simeonedussoni]

I propose to start working on the FSM using the alarms highlighted in our list, then we can test them. Upon tests we can also decide the urgency of each alarm i.e. check if the error condition blocks completely the patient breathing. Once we have a well-modulated structure for the FW we can easily think to add more alarms to the list taking them from existing devices or from the physician advise

cc @pattacini @vtikha @Nicogene @marcoaccame @maggia80

[pattacini]

I've created the Project Alarms Handling for tracking these activities. This issue can serve as a high-level wrapper. Thus, we could create ad-hoc issues to address specific alarms.

cc @simeonedussoni @Nicogene

[pattacini]

@simeonedussoni I agreed with @Nicogene that if you aim to extend the FSM in terms of alarm handling, you ought to work on your fork to avoid clashing (don't open PR though). I'll be then integrating any possible medications into the mainstream.

In the long term, we will be using the Model Comparison tool instead, to manage the model versioning.

[pattacini]

Implementation of single alarms is commented/provided in https://github.com/icub-tech-iit/ventilator-FI5/projects/9.

Bear in mind that from FSM standpoint there ain't any difference between transitory and derived alarms.

[simeonedussoni]

project closed, I close also the issue.