ethanjli
commented
3 years ago Since it looks like we will ship our HFNC-only release, we will need to implement pre-use tests before the first public release anyways, so then we might as well add pre-use tests to HFNC mode.
Right now, if a clinician wants to run pre-use tests from a paper checklist (because we are not shipping a software framework for pre-use tests in the first HFNC-only release), they must manually adjust alarm limits and settings to try to trigger and deactivate alarms. All of these would be recorded in the event log as regular patient events, with no information contextualizing these alarms/events as being generated in a manual pre-use checks procedure. As a temporary solution, we could add a button in the frontend (maybe the quick start screen) corresponding to a new boolean field in the ParametersRequest/Parameters service for "pre-use check" mode (or even in a new PreUseCheckRequest/PreUseCheck message). Then when ventilation is started with this field set to true, a low-priority alarm (no sound) is generated for this and an event is logged that pre-use check operation was started; and when ventilation is started with this field set to false, an event is logged indicating that pre-use check operation was stopped. This way, the event log will show context for actions performed during pre-use check phase.