user interface

Abstract

Customizable and intuitive user interfaces are provided for medical systems and devices, such as cardiopulmonary bypass systems, perfusion systems, extracorporeal circulation apparatus, and heart-lung machines, that allow easy access to critical patient data to facilitate blood perfusion, as well as monitoring and adjusting various physiological parameters of the patient and extracorporeal blood flow circuit during procedures such as cardiopulmonary bypass and extracorporeal membrane oxygenation (ECMO).

Description

[0001] This application is a divisional application of the application entitled "User Interface" filed on October 6, 2016, application number 201680071905.5.

[0002] This application claims priority to U.S. Provisional Patent Application No. 62 / 238,358, filed October 7, 2015, the disclosure of which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0003] The present disclosure relates to user interfaces for medical systems and devices, particularly for cardiopulmonary bypass systems, perfusion systems, extracorporeal circulation devices, and heart-lung machines, among others. The use of such user interfaces is particularly useful for facilitating blood perfusion during medical and / or surgical procedures, as well as monitoring and regulating various physiological parameters of a patient necessary to sustain life during medical and / or surgical procedures, such as cardiopulmonary bypass, extracorporeal membrane oxygenation (ECMO), and other extracorporeal circulation bypass surgical procedures. BACKGROUND

[0004] Conventional heart-lung machines have static button user interfaces that are hardwired into the machine and do not facilitate customization, ergonomics, ease of use, or allow for quick access to patient data and / or menus for monitoring, regulating, and / or adjusting patient parameters. These cumbersome interfaces are rigid in design and configuration and do not allow for customization of the interface for a particular clinical application for the user and / or flexibility for a particular patient and / or for the user's particular preferences. Furthermore, the typical multi-level nested menu layers employed by conventional heart-lung machine user interfaces can actually hinder quick access to critical patient data and impede access to such critical information due to the successive open-close steps required by the nested menus, which creates patient safety concerns.

[0005] Accordingly, conventional heart-lung machine user interfaces, such as those that use nested menus, create an obstacle to quick user access to certain data fields due to their design and disadvantageously prevent the user from unhindered quick access, adjustment, and continuous monitoring of critical patient data. These shortcomings can increase the likelihood of morbidity during complex medical and / or surgical procedures involving extracorporeal circulation, such as in the case of cardiopulmonary bypass surgery, where physiological parameters of the patient must be closely monitored and regulated to sustain the patient's life during the procedure.

[0006] Furthermore, conventional heart-lung machine user interfaces also lack or have poorly integrated alarm systems that are insufficient to timely notify, coordinate, and advise the user of system errors during cardiopulmonary bypass surgery.

[0007] In view of the deficiencies discussed above, there is a need to develop intuitive, ergonomic, customizable, and efficient user interface systems and displays for machines that provide extracorporeal bypass circulation, such as heart-lung machines and other cardiopulmonary bypass machines, to facilitate quick and continuous unobstructed access to critical patient data during extracorporeal bypass surgery. There is also a need to develop user interface systems and displays in this environment to facilitate monitoring, adjustment, and tuning of system parameters, and also to provide an integrated system-wide alarm mechanism to immediately notify the user of the cardiopulmonary bypass machine of any system error in a coordinated manner so that immediate corrective action can be taken, reducing patient morbidity and improving patient outcomes. SUMMARY

[0008] Accordingly, some embodiments of the present disclosure generally relate to user interfaces, such as can be used with cardiopulmonary bypass systems or other systems involving extracorporeal blood flow circuits. Such embodiments are structured to be customizable by one or more users, flexible, and have convenient modularity. Such embodiments can also be structured to have an intuitive design, be easy to use, and improve patient safety. In some such embodiments, the user interfaces are provided with tightly integrated alarms and other integrated safety measures to enhance safety during operation of the cardiopulmonary bypass systems or other systems involving extracorporeal blood flow circuits. The following summary of non-limiting illustrative embodiments of the present disclosure is provided to highlight certain features of some embodiments; however, this summary should not be interpreted as a comprehensive or exhaustive list of all features of the disclosure. In other words, this summary emphasizes various advantageous features of the device and method embodiments of the present disclosure; however, this summary should not be interpreted as a list of preferred embodiments.

[0009] According to a first non-limiting illustrative embodiment of the present disclosure, there is provided a cardiopulmonary bypass system comprising: (a) a processor; (b) a touch screen comprising a graphical user interface operably connected to provide user input to the processor and to display measurement data related to one or more parameters output from the processor, wherein the graphical user interface is provided with a central portion divided into a plurality of segments, wherein at least one segment displays a non-tabbed display page and at least one segment displays a plurality of tabbed display pages, wherein the non-tabbed display page comprises a plurality of sensor modules and at least one tabbed page comprises a plurality of sensor modules. According to a second non-limiting illustrative embodiment of the present disclosure, the first non-limiting embodiment is modified such that each sensor module of the non-tabbed page is individually selected from a group consisting of a pressure sensor module, a bubble detection sensor module, a level sensor module, a flow sensor module, a pressure delta data sensor module, and a temperature sensor module. According to a third non-limiting illustrative embodiment of the present disclosure, the first and second non-limiting embodiments are modified such that the non-tabbed page comprises at least one pressure sensor module, at least one bubble detection sensor module, and at least one level sensor module.

[0010] According to a fourth non-limiting illustrative embodiment of the present disclosure, the first, second, and third non-limiting embodiments are further modified such that each of the at least one pressure sensor module, the at least one bubble detection sensor module, and the at least one level sensor module is capable of displaying a plurality of alarm states selected from at least two of a high priority alarm state, a medium priority alarm state, and a low priority alarm state. According to a fifth non-limiting illustrative embodiment of the present disclosure, the first, second, third, and fourth non-limiting embodiments are further modified such that the at least one pressure sensor module comprises a pressure value data field and a touch or press activated intervention button, wherein the intervention button is activated by a touch or press to cause a temporary modification of the operation of the cardiopulmonary bypass system.

[0011] According to a sixth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, and fifth non-limiting embodiments are further modified such that the at least one bubble detection sensor module includes a bubble detection data field and a touch or press activated reset button, wherein the bubble detection data field displays bubble detection data obtained from the bubble detection sensor. According to a seventh non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, and seventh non-limiting embodiments are further modified such that when the bubble detection sensor detects a bubble that exceeds a preset bubble detection size value, the at least one bubble detection sensor module displays a high priority alarm status, and the bubble detection sensor module continues to display the high priority alarm status until the reset button is activated by a touch or press and simultaneously the bubble detected by the bubble detection sensor does not exceed the preset bubble detection size value. According to an eighth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, and seventh non-limiting embodiments are further modified such that the at least one bubble detection sensor module further includes a touch or press activated intervention button, wherein intervention is activated by a touch or press such that the operation of the pump of the heart-lung bypass system is temporarily modified.

[0012] According to a ninth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, and eighth non-limiting embodiments are further modified such that the at least one level sensor module includes a level data field and a touch or press activated intervention button, wherein the intervention button is only available when the blood level of the blood reservoir of the heart-lung bypass system is at or below a predetermined low blood level. According to a tenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, and ninth non-limiting embodiments are further modified such that the operation of the pump of the heart-lung bypass system is temporarily modified by activating the intervention button by a touch or press, thereby interrupting an automatic blood level correction mechanism initiated by the processor.

[0013] According to an eleventh non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, and tenth non-limiting embodiments are further modified such that each tabbed display page includes a tab, and wherein each tabbed display page is capable of being displayed in a display mode and an overlay mode. According to a twelfth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, and eleventh non-limiting embodiments are further modified such that when displayed in the display mode substantially all of the tabbed display pages are visible, and when displayed in the overlay mode only the tabs of the tabbed display pages are visible. According to a thirteenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, and twelfth non-limiting embodiments are further modified such that each time at least one segment of a plurality of tabbed display pages is displayed in the display mode only one tabbed display page of the plurality of tabbed display pages is displayed, and the remaining tabbed display pages are displayed in the overlay mode. According to a fourteenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, and thirteenth non-limiting embodiments are further modified such that each tab is capable of being activated by a user touching or pressing on the touchscreen, wherein activating a tab by touching or pressing causes the associated tabbed display page to be displayed in the display mode, and the remaining tabbed display pages to be displayed in the overlay mode. According to a fifteenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, and fourteenth non-limiting embodiments are further modified such that each tab is capable of transitioning to an alarm state, such that when the corresponding tabbed display page is displayed in the overlay mode and any sensor module of the corresponding tabbed display page transitions to an alarm state, the tab transitions to a visible alarm state.

[0014] According to a sixteenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, fourteenth, and fifteenth non-limiting embodiments are further modified such that the graphical user interface includes a header portion and a footer portion, wherein the central portion is disposed between the header portion and the footer portion. According to a seventeenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, fourteenth, fifteenth, and sixteenth non-limiting embodiments are further modified such that the cardiopulmonary bypass system further comprises (c) a plurality of sensors disposed to measure one or more parameters of the extracorporeal blood flow circuit, wherein the plurality of sensors are operably connected to input measured data related to the one or more parameters to the processor, and wherein each sensor is connected to one of the non-tabbed display pages or one of the sensor modules of the tabbed display pages, such that data measured by the sensor is displayed by the one sensor module.

[0015] According to an eighteenth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, fourteenth, fifteenth, sixteenth, and seventeenth non-limiting embodiments are further modified such that the plurality of tabbed display pages includes a patient monitor tabbed display page having a patient monitor configuration. According to a nineteenth non-limiting embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, fourteenth, fifteenth, sixteenth, seventeenth, and eighteenth non-limiting embodiments are further modified such that the cardiopulmonary bypass system further comprises (d) a third section and a fourth section, wherein the third section includes a simulator keypad tabbed display page having a simulator keypad configuration and the fourth section includes a simulator screen tabbed display page having a simulator screen configuration, wherein the patient monitor tabbed display page, the simulator keypad tabbed display page, and the simulator screen tabbed display page are operable together as a clinical parameter monitoring and simulation user interface when the patient monitor tabbed display page, the simulator keypad tabbed display page, and the simulator screen tabbed display page are displayed simultaneously. According to a twentieth non-limiting illustrative embodiment of the present disclosure, the first, second, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, thirteenth, fourteenth, fifteenth, sixteenth, seventeenth, eighteenth, and nineteenth non-limiting embodiments are further modified such that the patient monitor configuration includes a data value field that displays a blood lactate level, and optionally, the non-tabbed display pages include a timer module.

[0016] According to a twenty-first non-limiting illustrative embodiment of the present disclosure, there is provided a touch screen comprising a graphical user interface, wherein the graphical user interface comprises: (a) a header portion; and (b) a central portion adjacent to the header portion, wherein the central portion is divided into a plurality of segments, wherein at least one segment displays a non-tabbed page and at least one segment displays a plurality of tabbed pages, and wherein the non-tabbed page comprises a plurality of sensor modules, at least one tabbed page comprises a plurality of sensor modules. According to a twenty-second non-limiting illustrative embodiment of the present disclosure, the twenty-first non-limiting embodiment is modified such that each sensor module of the non-tabbed page is individually selected from a group consisting of a pressure sensor module, a bubble detection sensor module, a level sensor module, a flow sensor module, a pressure delta data sensor module, and a temperature sensor module. According to a twenty-third non-limiting illustrative embodiment of the present disclosure, the twenty-first and twenty-second non-limiting embodiments are further modified such that the non-tabbed page comprises at least one pressure sensor module, at least one bubble detection sensor module, and at least one level sensor module. According to a twenty-fourth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, and twenty-third non-limiting embodiments are further modified such that each of the at least one pressure sensor module, the at least one bubble detection sensor module, and the at least one level sensor module is capable of displaying a plurality of alarm states selected from at least two of a high priority alarm state, a medium priority alarm state, and a low priority alarm state.

[0017] According to a twenty-fifth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, and twenty-fourth non-limiting embodiments are further modified such that the at least one pressure sensor module includes a pressure value data field and a touch or press activated intervention button, wherein the intervention button is activated by touch or press causing the operation of the pump of the cardiopulmonary bypass system to be temporarily modified. According to a twenty-sixth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, and twenty-fifth non-limiting embodiments are further modified such that the at least one air bubble detection sensor module includes an air bubble detection data field and a touch or press activated reset button, wherein the air bubble detection data field displays air bubble detection data obtained from the air bubble detection sensor. According to a twenty-seventh non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, and twenty-sixth non-limiting embodiments are further modified such that when the air bubble detection sensor detects air bubbles exceeding a preset air bubble detection size value, the at least one air bubble detection sensor module displays a high priority alarm state, and the air bubble detection sensor module continues to display the high priority alarm state until the reset button is activated by touch or press and simultaneously air bubbles detected by the air bubble detection sensor do not exceed the preset air bubble detection size value. According to a twenty-eighth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, and twenty-seventh non-limiting embodiments are further modified such that the at least one air bubble detection sensor module further includes a touch or press activated intervention button, wherein the intervention button is activated by touch or press causing the operation of the pump of the cardiopulmonary bypass system to be temporarily modified.

[0018] According to a twenty-ninth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, and twenty-eighth non-limiting embodiments are further modified such that the at least one level sensor module includes a level data field and a touch or press activated intervention button, wherein the intervention button is only available when the blood level of the blood reservoir of the cardiopulmonary bypass system is at or below a predetermined low blood level. According to a thirtieth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, and twenty-eighth, and twenty-ninth non-limiting embodiments are further modified such that the intervention button is activated by touch or press causing the operation of the pump of the cardiopulmonary bypass system to be temporarily modified, thereby interrupting an automatic blood level correction mechanism initiated by the processor.

[0019] According to a thirty-first non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, and thirtieth non-limiting embodiments are further modified such that each tabbed page includes a tab, and wherein each tabbed page is displayable in a display mode and an overlay mode. According to a thirty-second non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, thirtieth, and thirty-first non-limiting embodiments are further modified such that substantially all of a tabbed page is visible when displayed in the display mode, and only the tab of a tabbed page is visible when displayed in the overlay mode. According to a thirty-third non-limiting embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, thirtieth, thirty-first, and thirty-second non-limiting embodiments are further modified such that only one tabbed page of a plurality of tabbed pages displaying at least one segment is displayed in the display mode at a time, and the remaining tabbed pages are displayed in the overlay mode. According to a thirty-fourth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, thirtieth, thirty-first, thirty-second, and thirty-third non-limiting embodiments are further modified such that each tab is activatable by a user touching or pressing on the touchscreen, wherein activating a tab by touching or pressing causes the associated tabbed page to be displayed in the display mode, and the remaining tabbed pages to be displayed in the overlay mode. According to a thirty-fifth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, thirtieth, thirty-first, thirty-second, thirty-third, and thirty-fourth non-limiting embodiments are further modified such that each tab is transitionable to an alarm state, such that when the corresponding tabbed page is displayed in the overlay mode and any sensor module of the corresponding tabbed page transitions to an alarm state, the tab transitions to a visible alarm state. According to a thirty-sixth non-limiting illustrative embodiment of the present disclosure, the twenty-first, twenty-second, twenty-third, twenty-fourth, twenty-fifth, twenty-sixth, twenty-seventh, twenty-eighth, twenty-ninth, thirtieth, thirty-first, thirty-second, thirty-third, thirty-fourth, and thirty-fifth non-limiting embodiments are further modified such that the graphical user interface includes a header portion and a footer portion, wherein the central portion is disposed between the header portion and the footer portion.

[0020] According to a thirty-seventh non-limiting illustrative embodiment of the present disclosure, there is provided a touch screen provided with a graphical user interface, wherein the graphical user interface includes a central portion divided into a plurality of segments, wherein one segment displays a non-tabbed display page and a plurality of other segments each display a plurality of tabbed display pages, wherein each tabbed display page is capable of being displayed in a display mode and an overlay mode, wherein only one tabbed display page of each other segment is capable of being displayed in the display mode at a time and each remaining tabbed display page is displayed in the overlay mode. According to a thirty-eighth non-limiting illustrative embodiment of the present disclosure, the thirty-seventh non-limiting embodiment is modified such that each tabbed display page includes a touch or pressure-activated tab such that a touch or press applied to the tab activates display of the tabbed display page in the display mode. According to a thirty-ninth non-limiting illustrative embodiment of the present disclosure, the thirty-seventh and thirty-eighth non-limiting embodiments are modified such that the plurality of other segments includes a first segment and a second segment, wherein a tabbed display page of the first segment is simultaneously displayed in the display mode with a tabbed display page of the second segment so as to form a theme user interface including a pair of tabbed display pages. According to a fortieth non-limiting illustrative embodiment of the present disclosure, the thirty-seventh, thirty-eighth and thirty-ninth non-limiting embodiments are further modified such that the plurality of other segments includes a first segment, a second segment and a third segment, wherein a tabbed display page of the first segment is simultaneously displayed in the display mode with one tabbed display page of the second segment or the third segment so as to form a theme user interface including a pair of tabbed display pages. According to a forty-first non-limiting illustrative embodiment of the present disclosure, the thirty-seventh, thirty-eighth, thirty-ninth and fortieth non-limiting embodiments are further modified such that the plurality of other segments includes a first segment, a second segment and a third segment, wherein a tabbed display page of the first segment is simultaneously displayed in the display mode with one tabbed display page of the second segment and one tabbed display page of the third segment so as to form a theme user interface including a triad of tabbed display pages.

[0021] According to a forty-second non-limiting illustrative embodiment of the present disclosure, the thirty-seventh, thirty-eighth, thirty-ninth, fortieth, and forty-first non-limiting embodiments are further modified such that the touch screen further comprises a header portion and a footer portion, wherein the central portion is adjacent to each of the header portion and the footer portion. According to a forty-third non-limiting illustrative embodiment of the present disclosure, a medical device is provided that comprises a touch screen according to any of the thirty-seventh, thirty-eighth, thirty-ninth, fortieth, forty-first, and forty-second non-limiting embodiments. According to a forty-fourth non-limiting illustrative embodiment of the present disclosure, the thirty-seventh, thirty-eighth, thirty-ninth, fortieth, forty-first, forty-second, and forty-third non-limiting embodiments are further modified such that the non-tabbed display pages comprise a plurality of sensor modules, and at least some of the tabbed display pages comprise a plurality of sensor modules. According to a forty-fifth non-limiting illustrative embodiment of the present disclosure, the thirty-seventh, thirty-eighth, thirty-ninth, fortieth, forty-first, forty-second, forty-third, and forty-fourth non-limiting embodiments are further modified such that the medical device is an apparatus selected from the group consisting of a heart-lung machine and a veno-venous extracorporeal membrane oxygenator.

[0022] According to a forty-sixth non-limiting illustrative embodiment of the present disclosure, there is provided a method of operating a graphical user interface of a medical device, the method comprising the steps of: (a) selectively configuring a plurality of sensor modules of a non-tabbed display page of the graphical user interface to display data collected by a first plurality of sensors and to display alarm status associated with the displayed data collected by the first plurality of sensors, wherein the first plurality of sensors are configured to collect data from an extracorporeal blood flow circuit; (b) selectively configuring a plurality of sensor modules of a plurality of tabbed display pages of the graphical user interface to display data collected by a second plurality of sensors and to display alarm status associated with the displayed data collected by the second plurality of sensors, wherein the second plurality of sensors are configured to collect data from the extracorporeal blood flow circuit. According to a forty-seventh non-limiting illustrative embodiment of the present disclosure, the forty-sixth non-limiting embodiment is modified such that the alarm status associated with the data displayed by the first plurality of sensors comprises two or more states selected from a group consisting of a low priority alarm state, a medium priority alarm state, and a high priority alarm state. According to a forty-eighth non-limiting illustrative embodiment of the present disclosure, the forty-sixth and forty-seventh non-limiting embodiments of the present disclosure are further modified such that the alarm status associated with the data displayed by the second plurality of sensors comprises two or more states selected from a group consisting of a low priority alarm state, a medium priority alarm state, and a high priority alarm state. According to a forty-ninth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, and forty-eighth non-limiting embodiments are further modified such that the plurality of sensor modules of the non-tabbed display page comprises at least one pressure sensor module, at least one air bubble detection sensor module, and at least one level sensor module.

[0023] According to a fiftieth non-limiting illustrative embodiment of the present disclosure, the method according to the forty-sixth, forty-seventh, forty-eighth, and forty-ninth non-limiting embodiments is further modified to further comprise the steps of: (c) displaying pressure data collected by the pressure sensor operably connected to the at least one pressure sensor module; (d) displaying a pressure high priority alert status when the displayed pressure data is equal to or exceeds a stop limit value. According to a fifty-first non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, and fiftieth non-limiting embodiments are further modified to include a step of displaying a pressure medium priority alert status when the pressure data is equal to or exceeds a threshold value and is below the stop limit value. According to a fifty-second non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, and fifty-first non-limiting embodiments are further modified to include a step of displaying a pressure low priority alert status when the pressure data is equal to or exceeds an alert limit value and is below the threshold value. According to a fifty-third non-limiting embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, and fifty-second non-limiting embodiments are further modified to include a step of activating a touch or press sensitive intervention button of the touch screen when the pressure high priority alert status is displayed, wherein activation of the touch or press sensitive intervention button reduces or interrupts operation of the blood pump.

[0024] According to a fifty-fourth non-limiting embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, and fifty-third non-limiting embodiments are further modified to include the steps of displaying bubble detection data collected by the bubble detection sensor operably connected to the at least one bubble detection sensor module; and displaying a bubble detection low-priority alarm state when the displayed bubble detection data indicates that a bubble in the extracorporeal blood flow circuit is detected and the detected bubble has a size that does not exceed a threshold size limit. According to a fifty-fifth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, and fifty-fourth non-limiting embodiments are further modified to include the steps of displaying a bubble detection high-priority alarm state when the displayed bubble detection data indicates that a bubble in the extracorporeal blood flow circuit is detected with a size that exceeds a threshold size limit, and continuing to display the bubble detection high-priority alarm state until the detected bubble size does not exceed the threshold size limit and a reset button has been activated. According to a fifty-sixth non-limiting embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, and fifty-fifth non-limiting embodiments are further modified to include the step of activating a touch or press sensitive intervention button of the touch screen while the bubble detection high-priority alarm state is displayed, wherein activation of the touch or press sensitive intervention button modifies operation of the blood pump for a set period of time.

[0025] According to a fifty-seventh non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, and fifty-sixth non-limiting embodiments are further modified to include the steps of displaying the level data collected by the level sensor operably connected to the at least one level sensor module; and displaying a low level priority alarm state when the displayed level data indicates that the blood level of the blood reservoir of the extracorporeal blood flow circuit is at or below the regulated level and exceeds an unacceptably low level. According to a fifty-eighth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, and fifty-seventh non-limiting embodiments are further modified to include the steps of displaying a high level priority alarm state when the displayed level data indicates that the blood level of the blood reservoir of the extracorporeal blood flow circuit is at or below an unacceptably low level. According to a fifty-ninth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, and fifty-eighth non-limiting embodiments are further modified to include the step of activating a touch or press sensitive intervention button of the touchscreen when the high level priority alarm state is displayed, wherein activation of the touch or press sensitive intervention button modifies operation of the arterial blood pump for a set period of time or modifies operation of the air removal pump for a set period of time.

[0026] According to a sixty-first non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, and sixty-first non-limiting embodiments are further modified to include the steps of: displaying pressure data collected by a pressure sensor operably connected to the pressure sensor module; and displaying a pressure high priority alert state when the displayed pressure data is equal to or exceeds a stop limit value. According to a sixty-second non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, and sixty-second non-limiting embodiments are further modified to include the step of: displaying a pressure medium priority alert state when the pressure data is equal to or exceeds a threshold value and is below a stop limit value. According to a sixty-third non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, and sixty-third non-limiting embodiments are further modified to include the step of: displaying a pressure low priority alert state when the pressure data is equal to or exceeds an alert limit value and is below a threshold value. According to a sixty-fourth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, and sixty-third non-limiting embodiments are further modified to include the step of: activating a touch or press sensitive intervention button of the touch screen while displaying the pressure high priority alert state, wherein activation of the touch or press sensitive intervention button reduces or interrupts operation of the blood pump.

[0027] According to a sixty-fifth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, and sixty-fifth non-limiting implementations are further modified to include the steps of displaying bubble detection data collected by a bubble detection sensor operably connected to the bubble detection sensor module; and displaying a bubble detection low-priority alarm state when the displayed bubble detection data indicates that a bubble in the extracorporeal blood flow circuit is detected and the size of the detected bubble does not exceed a threshold size limit. According to a sixty-sixth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, and sixty-fifth non-limiting implementations are further modified to include the steps of displaying a bubble detection high-priority alarm state when the displayed bubble detection data indicates that a bubble in the extracorporeal blood flow circuit is detected that exceeds a threshold size limit, and continuing to display the bubble detection high-priority alarm state until the detected bubble size does not exceed the threshold size limit and a reset button has been activated. According to a sixty-seventh non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, and sixty-sixth non-limiting embodiments are further modified to include the step of activating a touch or press sensitive intervention button of the touch screen while the bubble detection high-priority alarm state is displayed, wherein activation of the touch or press sensitive intervention button modifies operation of the blood pump for a set period of time.

[0028] According to a sixty-eighth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, and sixty-eighth non-limiting embodiments are further modified to include the steps of displaying the level data collected by the level sensor operably connected to the level sensor module; and displaying a low level priority alarm state when the displayed level data indicates that the level of blood of the blood reservoir of the extracorporeal blood flow circuit is at or below the regulated level and exceeds an unacceptably low level. According to a sixty-ninth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, and sixty-eighth non-limiting embodiments are further modified to include the steps of displaying a high level priority alarm state when the displayed level data indicates that the level of blood of the blood reservoir of the extracorporeal blood flow circuit is at or below an unacceptably low level. According to a seventieth non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, sixty-eighth, and sixty-ninth non-limiting embodiments are further modified to include the step of activating a touch or press sensitive intervention button of the touch screen when the high level priority alarm state is displayed, wherein activation of the touch or press sensitive intervention button modifies operation of the arterial blood pump for a set period of time or modifies operation of the outgas pump for a set period of time.

[0029] According to a seventy-first non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, sixty-eighth, sixty-ninth, and seventieth non-limiting embodiments are further modified such that the plurality of tabbed display pages are displayed within a first section of the graphical user interface, the non-tabbed display page is displayed within a second section of the graphical user interface, and each tabbed display page is capable of being displayed in a display mode and an overlay mode, and the method further comprises the steps of: activating a tab of a tabbed display page of the first section such that the tabbed display page is displayed in the display mode and such that each other tabbed display page of the first section is displayed in the overlay mode. According to a seventy-second non-limiting illustrative embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, sixty-eighth, sixty-ninth, seventieth, and seventy-first non-limiting embodiments are further modified such that substantially all of the tabbed display pages are displayed in the display mode and substantially only all of the tabs of the tabbed display pages are displayed in the overlay mode. According to a seventy-third non-limiting embodiment of the present disclosure, the forty-sixth, forty-seventh, forty-eighth, forty-ninth, fiftieth, fifty-first, fifty-second, fifty-third, fifty-fourth, fifty-fifth, fifty-sixth, fifty-seventh, fifty-eighth, fifty-ninth, sixtieth, sixty-first, sixty-second, sixty-third, sixty-fourth, sixty-fifth, sixty-sixth, sixty-seventh, sixty-eighth, sixty-ninth, seventieth, seventy-first, and seventy-second non-limiting embodiments are further modified such that, when displayed in the overlay mode, the alert status of the tabbed display page being overlaid is emitted by the tab of the tabbed display page being overlaid.

[0030] According to a seventy-fourth non-limiting illustrative embodiment of the present disclosure, there is provided a method of configuring a graphical user interface of a touch screen prior to operating in a clinical mode of operation, wherein the method comprises the steps of: a) displaying, in response to a first signal, a sensor module configuration menu interface associated with a tabbed display page of the graphical user interface displayed by the touch screen; and (b) setting, in response to a second signal, at least one alarm limit for a sensor module associated with the sensor module configuration menu interface associated with the tabbed display page. According to a seventy-fifth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth non-limiting embodiment is modified such that the first signal is generated as a result of activating a touchable or press-activated module settings menu button of the sensor module of the tabbed display page. According to a seventy-sixth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth and seventy-fifth non-limiting embodiments are modified such that the second signal is generated as a result of activating a touchable or press-activated button of the sensor module configuration menu interface of the tabbed display page. According to a seventy-seventh non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth and seventy-sixth non-limiting embodiments are further modified such that the method comprises the step of: overlaying, in response to a third signal, a pump association menu interface over a portion of the sensor module configuration menu interface of the tabbed display page so as to enable selective association of pump functions with the sensor module of the tabbed display page.

[0031] According to a seventy-eighth non-limiting embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, and seventy-seventh non-limiting embodiments are further modified so that, in response to a third signal, a sensor module configuration menu interface is displayed on a portion of the non-tabbed display page of the graphical user interface displayed by the touch screen; and, in response to a fourth signal, at least one alarm limit is set for a sensor module associated with the sensor module configuration menu interface associated with the non-tabbed display page. According to a seventy-ninth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, and seventy-eighth non-limiting embodiments are further modified so that the third signal is generated as a result of activating a touchable or pressable activated module settings menu button of the sensor module of the non-tabbed display page. According to an eightieth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-seventh, seventy-eighth, and seventy-ninth non-limiting embodiments are further modified so that the fourth signal is generated as a result of activating a touchable or pressable activated button of the sensor module configuration menu interface of the non-tabbed display page. According to an eighty-first non-limiting embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, and eightieth non-limiting embodiments are further modified to include the step of, in response to a fifth signal, overlaying a pump association menu interface on a portion of the sensor module configuration menu interface of the non-tabbed display page so as to enable selective association of a pump function with the sensor module of the non-tabbed display page.

[0032] According to an eighty-second non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, and eightieth, and eighty-first non-limiting embodiments are further modified such that the sensor module associated with the sensor module configuration menu interface is a pressure sensor module associated with a pressure sensor module configuration menu interface, or a bubble detection sensor module associated with a bubble detection sensor module configuration menu interface, or a level sensor module associated with a level sensor module configuration menu interface, or a temperature sensor module associated with a temperature sensor module configuration menu interface, or a flow sensor module associated with a flow sensor module configuration menu interface, or a pressure delta sensor module associated with a pressure delta sensor module configuration menu interface. According to an eighty-third non-limiting illustrative embodiment of the present disclosure, the seventy-eighth non-limiting embodiment is further modified such that each sensor module associated with a respective sensor module configuration menu interface is independently selected from the group consisting of a pressure sensor module associated with a pressure sensor module configuration menu interface, a bubble detection sensor module associated with a bubble detection sensor module configuration menu interface, a level sensor module associated with a level module configuration menu interface, a temperature sensor module associated with a temperature sensor module configuration menu interface, a flow sensor module associated with a flow sensor module configuration menu interface, and a pressure delta sensor module associated with a pressure delta sensor module configuration menu interface.

[0033] According to an eighty-fourth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, eightieth, eighty-first, eighty-second, eighty-third, and eighty-fourth non-limiting embodiments are further modified to include the step of activating a system configuration menu interface to select a predefined graphical user interface configuration, or to configure at least one selectable alarm setting selected from the group consisting of a brightness and an alarm volume, or to display an external device menu. According to an eighty-fifth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, eightieth, eighty-first, eighty-second, eighty-third, eighty-fourth, and eighty-fifth non-limiting embodiments are further modified to include the step of closing a sensor module configuration menu interface of a tabbed display page to accept and make available at least one alarm limit of a sensor module of the tabbed display page. According to an eighty-sixth non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, eightieth, eighty-first, eighty-second, eighty-third, eighty-fourth, eighty-fifth, and eighty-sixth non-limiting embodiments are further modified to include the step of closing a sensor module configuration menu interface of a non-tabbed display page to accept and make available at least one alarm limit of a sensor module of the non-tabbed display page. According to an eighty-seventh non-limiting illustrative embodiment of the present disclosure, the seventy-fourth, seventy-fifth, seventy-sixth, seventy-seventh, seventy-eighth, seventy-ninth, eightieth, eighty-first, eighty-second, eighty-third, eighty-fourth, eighty-fifth, eighty-sixth, and eighty-seventh non-limiting embodiments are further modified to include the step of closing a sensor module configuration menu interface of a tabbed display page to accept and make available at least one alarm limit of a sensor module of the tabbed display page. BRIEF DESCRIPTION OF DRAWINGS

[0034] The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.

[0035] Figure 1 is a perspective view of an exemplary heart-lung machine including an embodiment of the user interface system of the present disclosure.

[0036] FIG. 2a is a schematic diagram of a user interface system and its operative connection with various components of a heart-lung machine in accordance with an embodiment of the present disclosure. Figure 1

[0037] ​FIG. 2b is a schematic diagram of a cardiopulmonary bypass system incorporating a cardiopulmonary machine including a user interface system of the present disclosure.

[0038] FIGS. 3a and 3b, which can be collectively referred to as "FIG. 3," illustrate an exemplary, non-limiting configuration of a graphical user interface of a touch screen monitor in accordance with embodiments of the present disclosure.

[0039] Figure 4 An exemplary, non-limiting configuration of a header portion of the graphical user interface of FIG. 3 is illustrated.

[0040] FIGS. 5a, 5b, 5c, 5d, 5e, and 5f, which can be collectively referred to as "FIG. 5," illustrate various display states of a battery icon of a graphical user interface in accordance with embodiments of the present disclosure.

[0041] FIGS. 6a and 6b, which can be collectively referred to as "FIG. 6," illustrate various displays corresponding to different operational states of a lock screen button of a graphical user interface in accordance with embodiments of the present disclosure.

[0042] FIGS. 7a and 7b, which can be collectively referred to as "FIG. 7," illustrate various displays of a user configuration identifier of a graphical user interface in accordance with embodiments of the present disclosure.

[0043] FIGS. 8a and 8b, which can be collectively referred to as "FIG. 8," illustrate displays of a system settings menu button in a first operational mode as illustrated by the icon of FIG. 8a and a second operational mode as illustrated by the icon of FIG. 8b in accordance with embodiments of the present disclosure.

[0044] Figure 9 An exemplary, non-limiting configuration of a non-tabbed display page of a central monitoring portion of a graphical user interface in accordance with embodiments of the present disclosure is illustrated.

[0045] FIGS. 10a, 10b, 10c, 10d, 10e, 10f, 10g, and 10h, which can be collectively referred to as "FIG. 10," illustrate exemplary, non-limiting configurations of a pressure sensor module in accordance with embodiments of the present disclosure.

[0046] FIGS. 11a and 11b illustrate exemplary, non-limiting configurations of an intervention button of a pressure sensor module in accordance with embodiments of the present disclosure.

[0047] Figure 12 An exemplary, non-limiting configuration of a bubble detection sensor module in accordance with embodiments of the present disclosure is illustrated.

[0048] FIGS. 13a, 13b, 13c, and 13d, which can be collectively referred to as "FIG. 13," illustrate various bubble level icons in accordance with embodiments of the present disclosure.

[0049] FIGS. 14a, 14b, 14c, 14d, and 14e, which can be referred to collectively as“FIG. 14,” illustrate various alarm indication states of a bubble detection sensor module, in accordance with embodiments of the disclosure.

[0050] FIGS. 15a, 15b, and 15c, which can be referred to collectively as“FIG. 15,” illustrate exemplary, non-limiting configurations of a level sensor module including various liquid level detection states, in accordance with embodiments of the disclosure.

[0051] FIGS. 16a, 16b, 16c, and 16d, which can be referred to collectively as“FIG. 16,” illustrate various level icons representing the relative level of liquid in a relevant reservoir, in accordance with embodiments of the disclosure.

[0052] FIGS. 17a, 17b, 17c, and 17d, which can be referred to collectively as“FIG. 17,” illustrate exemplary, non-limiting configurations of a level sensor module including various liquid level detection states when a vacuum pump is connected to a blood reservoir, in accordance with embodiments of the disclosure.

[0053] FIGS. 18a, 18b, and 18c illustrate various alarm states of a level sensor module, in accordance with embodiments of the disclosure.

[0054] FIGS. 19a, 19b, 19c, 19d, 19e, 19f, and 19g illustrate several exemplary, non-limiting configurations of a temperature sensor module and / or alarm states thereof, in accordance with embodiments of the disclosure.

[0055] FIGS. 20a, 20b, 20c, 20d, 20e, and 20f illustrate several non-limiting configurations of a flow sensor module and / or alarm states thereof, in accordance with embodiments of the disclosure.

[0056] FIGS. 21a, 21b, 21c, and 21d illustrate several non-limiting configurations of a pressure delta sensor module and / or alarm states thereof, in accordance with embodiments of the disclosure.

[0057] FIGS. 22a and 22b, which can be referred to collectively as“FIG. 22,” illustrate exemplary, non-limiting examples of a tabbed display page of a user interface for a weight-based target flow calculator, in accordance with embodiments of the disclosure.

[0058] FIGS. 23a, 23b, 23c, and 23d, which can be referred to collectively as“FIG. 23,” illustrate exemplary, non-limiting examples of a tabbed display page of a user interface for a priming calculator, in accordance with embodiments of the disclosure.

[0059] Figure 24 FIGS. 24a, 24b, 24c, and 24d, which can be referred to collectively as“FIG. 24,” illustrate exemplary, non-limiting examples of a tabbed display page of a user interface for a patient monitor, in accordance with embodiments of the disclosure.

[0060] FIGS. 25a, 25b, 25c, and 25d, which can be collectively referred to as“FIG. 25,” illustrate exemplary, non-limiting embodiments of tabbed display pages of a remote heater-cooler unit user interface, in accordance with embodiments of the present disclosure.

[0061] Figure 26 Exemplary, non-limiting embodiments of tabbed display pages of a general purpose calculator, in accordance with embodiments of the present disclosure, are illustrated.

[0062] Figure 27 Exemplary, non-limiting embodiments of tabbed display pages of a pulse control user interface for an arterial pump, in accordance with embodiments of the present disclosure, are illustrated.

[0063] Figure 28 Exemplary, non-limiting embodiments of a clinical parameter monitor-analogue user interface, in accordance with embodiments of the present disclosure, are illustrated.

[0064] Figure 29 Exemplary, non-limiting embodiments of a tabbed display page of an emulator keyboard page for a clinical parameter monitor-analogue user interface, in accordance with embodiments of the present disclosure, are illustrated.

[0065] FIGS. 30a, 30b, 30c, and 30d, which can be collectively referred to as“FIG. 30,” illustrate exemplary, non-limiting embodiments of tabbed display pages of an emulator screen interface for a clinical parameter monitor-analogue user interface, in accordance with embodiments of the present disclosure.

[0066] Figure 31 Exemplary, non-limiting embodiments of a clinical parameter monitor-analogue user interface, in accordance with embodiments of the present disclosure, are illustrated.

[0067] Figure 32 Exemplary, non-limiting embodiments of a blood monitoring unit interface, in accordance with embodiments of the present disclosure, are illustrated.

[0068] Figure 33 Exemplary, non-limiting configurations of a footer portion of the graphical user interface of FIG. 3 are illustrated.

[0069] FIG. 34a illustrates an exemplary, non-limiting configuration of a system configuration menu interface, in accordance with embodiments of the present disclosure, and FIGS. 34b, 34c, 34d, 34e, 34f, and 34g illustrate various submenus of the system configuration menu interface.

[0070] FIG. 35a illustrates an exemplary, non-limiting configuration of a module configuration menu for a pressure sensor module, in accordance with embodiments of the present disclosure, and FIGS. 35b and 35c illustrate exemplary, non-limiting embodiments of associated submenu interfaces.

[0071] FIG. 36a illustrates an exemplary, non-limiting configuration of a module configuration menu for a bubble detection sensor module, and FIG. 36b illustrates an exemplary, non-limiting embodiment of an associated submenu interface, in accordance with embodiments of the present disclosure.

[0072] FIG. 37a illustrates an exemplary, non-limiting configuration of a module configuration menu for a level sensor module, and FIG. 37b illustrates an exemplary, non-limiting embodiment of an associated submenu interface, in accordance with embodiments of the present disclosure.

[0073] Figure 38 An exemplary, non-limiting configuration of a module configuration menu for a temperature sensor module is illustrated, in accordance with embodiments of the present disclosure.

[0074] FIG. 39a illustrates an exemplary, non-limiting configuration of a module configuration menu for a flow sensor module, and FIG. 39b illustrates an exemplary, non-limiting embodiment of an associated submenu interface, in accordance with embodiments of the present disclosure.

[0075] Figure 40 An exemplary, non-limiting configuration of a module configuration menu for a pressure delta sensor module is illustrated, in accordance with embodiments of the present disclosure.

[0076] FIGS. 41a and 41b illustrate exemplary, non-limiting configurations of a single alarm help screen and a multiple alarm help screen, respectively, in accordance with embodiments of the present disclosure. DETAILED DESCRIPTION

[0077] For purposes of explanation, the principles of the present disclosure are described by reference to various exemplary, non-limiting embodiments. Accordingly, although specific embodiments are described herein, one of ordinary skill in the art will readily recognize that the same principles are equally applicable to, and can be employed in, other systems and methods. Before the disclosed embodiments are explained, it is to be understood that the present disclosure is not limited in its application to the details of construction or the arrangements of components set forth in the following description. Additionally, the terminology used herein is for the purpose of description and not limitation. Furthermore, although certain methods are described herein as being performed in a certain order, in many instances, the steps can be performed in any order that is appreciated by one of ordinary skill in the art. Thus, the novel methods disclosed herein are not limited to the specific arrangements of steps disclosed herein.

[0078] For the purposes of this application, a "display field" as used herein refers to a field configured to display information on a user interface, and a "data field" as used herein refers to a field configured to both display information on a user interface and input information into a computer system through the user interface. The term "interface" according to the present disclosure should be interpreted to refer to a machine that is itself a machine. Thus, the term "interface" according to the present disclosure should not be interpreted as only a software application; however, it can be interpreted as a machine and associated nested software that operates as a machine. The term "mechanism" according to the present disclosure should be interpreted to refer to a machine, which can include electromechanical devices that are also machines and components thereof.

[0079] According to some embodiments of the present disclosure, the term "user interface" relates to a machine that includes at least two or more of the following features: (i) a set of scroll wheels, knobs, and / or touch or press operation buttons, (ii) operating system commands, (iii) graphical display formats, and (iv) other devices provided by the computer to allow the user to communicate with and use the computer or programs running on the computer. A graphical user interface (GUI) provides the user with a more or less "picture-oriented" way of interacting with computer technology.

[0080] The present disclosure is directed to a user interface system and display, a customization method, and uses thereof, configured for use in conjunction with medical devices and systems to facilitate blood perfusion and to monitor and / or regulate various physiological parameters of a patient. The user interface system can be part of, integrated in, used in conjunction with, and / or supported by the hardware of a cardiopulmonary bypass system, a perfusion system, an extracorporeal circulation device, or a heart-lung machine. In exemplary embodiments, the user interface is a flexible, ergonomic system that allows users, patients, and / or clinical applications, providing relevant customization in order to facilitate intuitive use and ease of use. The user interface system can further facilitate quick, efficient, and continuous unobstructed access to physiological data and system parameters, and to some extent, allow for quick and efficient monitoring, regulation, and / or adjustment of system parameters by minimizing and / or eliminating the nesting and nesting depth of menu layers that can obstruct data access. In contrast, the user interface system of the present disclosure provides unobstructed menu placement once opened, which minimizes patient safety risks resulting from obstructed data access. Furthermore, according to some embodiments, the user interface of the present disclosure can include an integrated alarm system with multiple corresponding alarm notifications that quickly direct the user's attention to system malfunctions and / or patient parameters that exceed threshold values and / or have reached dangerous values, without distracting or preventing the user from operating the medical device and system. According to the present disclosure, some embodiments also provide high-level and more detailed information about each alarm and a help menu for explaining and resolving the underlying situation that created the alarm and for helping with alarm prioritization.

[0081] To facilitate understanding of embodiments of the present disclosure, a graphical user interface of a user interface system is described, followed by a disclosure of customizable features of the user interface system.

[0082] Graphical user interface

[0083] According to the present disclosure, the graphical user interface 100 is a component of a display device 10 of a cardiopulmonary bypass machine 1, as shown in Figure 1 The graphical user interface 100 is also a component of a user interface system 20 of the cardiopulmonary bypass machine 1, as shown in FIG. 2a, which can be integrated with the display device 10. In other words, the display device 10 can incorporate some or all of the user interface system 20. However, other portions 22, 24 of the user interface system 20 can be remote from the display device 10. According to FIG. 2a, the user interface system 20 of the cardiopulmonary bypass machine 1 is operatively connected to send signal inputs to a processor 30 of the cardiopulmonary bypass machine 1 and to receive signal inputs from the processor 30. The processor 30 can preferably be an embedded system rather than a general purpose computer. Components of the cardiopulmonary bypass machine 1 and its extracorporeal blood flow circuit can be similar to those of the extracorporeal circulation system disclosed in U.S. Provisional Patent Application No. 62 / 160,689, filed May 13, 2015, the entire contents of which are incorporated herein by reference in their entirety.

[0084] FIG. 2b shows a graphical user interface 100 of the present disclosure integrated with components of a cardiopulmonary bypass system 2 that incorporates a cardiopulmonary bypass machine 1 and its extracorporeal blood flow circuit 3, which is typically comprised of various blood compatible tubing. FIG. 2b is a schematic diagram of more relevant portions of the cardiopulmonary bypass system 2, and thus less relevant portions of the system 2 are omitted from the figure. For a non-limiting example of a more detailed description of a cardiopulmonary bypass system, reference can be made to CARDIOPULMONARY BYPASS PRINCIPLES AND PRACTICE (3rd Ed.) 63-65 (Lippincott Williams & Wilkins 2008) by Glenn P. Gravlee et al.

[0085] As shown in Fig. 2b, venous blood is drawn from the vena cava or right atrium of the heart H through a venous catheter 32 into the extracorporeal blood flow circuit 3, through the circuit 3, and then through an arterial catheter 34 into the aorta. The venous blood travelling from the heart H through the extracorporeal blood flow circuit 3 passes through a venous blood reservoir 36 and is pumped via one or more venous blood pumps 37 to an oxygenator 52 connected to an oxygen source 54, which oxygenates the venous blood, and the oxygenated blood can be pumped by one or more arterial pumps 38 before being returned to the aorta through the arterial catheter 34 as oxygenated arterial blood. The extracorporeal blood flow circuit 3 can be provided with a plurality of sensors 50, 60, 70, 80, 90, sending data input to the processor 30. These sensors can include pressure sensors 50, bubble detection sensors 60, temperature sensors 80 and blood flow / pump sensors 90 located at various points along the extracorporeal blood flow circuit 3, such as for collecting pressure data, bubble detection data, temperature data and blood flow data. The venous blood reservoir 36 can be equipped with one or more level sensors 70 to measure the level of blood collected in the venous reservoir 36. The processor 30 can be connected to send control signals to various components of the heart-lung bypass machine 1, such as the blood pumps 37, 38 and the vacuum pump 39.

[0086] According to embodiments of the present disclosure, the processor 30 is optionally connected to receive data input from a venous blood gas sensor assembly 92 and an arterial blood gas sensor assembly 94, which provide data input regarding venous and arterial oxygen saturation (SvO2, SaO2) and corresponding arterial and venous partial pressure (PvO2, PaO2), respectively. The processor 30 can also be connected to receive HCT data input from an HCT sensor 95 and exhaled carbon dioxide data from a capnograph 96. The processor 30 can also be connected to send control signals to a vacuum pump 39, which is connected to draw a vacuum in the space above the blood level L of the blood reservoir 36.

[0087] The display device 10 includes a liquid crystal display (LCD) touchscreen monitor 15 and can employ a capacitive touchscreen system, a resistive touchscreen system, a surface acoustic touchscreen wave form system, or an infrared touchscreen system. As shown in Fig. 3, the graphical user interface 100 of the touchscreen monitor 15 is divided into a header portion 102, a footer portion 104, and a central monitor portion 106. Each of the portions 102, 104, and 106 can be framed by distinct borders 107 according to embodiments of the present disclosure, thus forming panels. However, according to other embodiments of the present disclosure, the portions 102, 104, and 106 can have borders that are not shown.

[0088] Header portion of graphical user interface

[0089] The header portion 102 displays various information in one or more display fields that are generally useful to those individuals monitoring the touch screen monitor 15 of the heart-lung bypass machine 1. According to embodiments of the present disclosure, as shown in Figure 4 The header portion 102 can include, as shown, a date and time display field 200 that continuously displays the current date and time. The header portion 102 also includes an audio alarm cancel icon 202 that, when displayed, indicates that some audio alarms of the heart-lung bypass machine 1 have been turned off or deactivated in some manner. The audio alarm cancel icon 202 has two states, i.e., displayed or blanked (i.e., not fully displayed). When the audio alarm cancel icon 202 is blanked (i.e., not fully visible), then the audio alarms of the heart-lung bypass machine 1 are not activated or otherwise compromised in any manner.

[0090] The header portion 102 can also include an alarm cancel icon 204 that, when displayed, indicates that some audiovisual alarms of the heart-lung bypass machine 1 have been turned off or deactivated in some manner. The alarm cancel icon 204 has two states, i.e., displayed or blanked (i.e., not fully displayed). When the alarm cancel icon 204 is blanked (i.e., not fully visible), then no visible non-audio alarms of the heart-lung bypass machine 1 are deactivated or otherwise compromised in any manner. The audiovisual alarms of the heart-lung bypass machine 1 have an optional mute mode in which the audio portion of the audiovisual alarms can be muted.

[0091] According to embodiments of the present disclosure, the header portion 102 includes a battery icon 206 that displays information regarding the power management system 40 of the heart-lung bypass machine 1. For example, the battery icon 206 can have substantially different display states corresponding to whether the battery 42 of the power management system 40 of the heart-lung bypass machine 1 is in the following states: (i) fully charged (Fig. 5a), (ii) charging via the battery charger 44 of the power management system 40, (iii) not charging and has an estimated remaining power sufficient to operate the heart-lung bypass machine 1 for more than 30 minutes (Fig. 5c), (iv) not charging and has an estimated remaining power sufficient to operate the heart-lung bypass machine 1 for more than 10 minutes and less than 30 minutes (Fig. 5d), (v) not charging and has an estimated remaining power sufficient to operate the heart-lung bypass machine 1 for less than 10 minutes (Fig. 5e), or (vi) not available (Fig. 5f).

[0092] According to embodiments of the present disclosure, the header portion 102 includes a lock screen button 208, which is a touch or press activated button of the touch screen 17. In its default mode, the lock screen button 208 indicates that the touch screen 17 of the touch screen monitor 15 is unlocked, meaning that the touch screen modality of the touch screen is operable and active. In this state, shown for example in FIG. 6a, the lock screen button 208 appears as a button displaying an unlocked padlock icon. However, by pressing the lock screen button 208 and holding for a predetermined period of time (e.g., at least 2 seconds), the touch screen 17 transitions into a "locked" state in which the keyboard mechanism is displayed in a "grayed out" mode and items displayed on such keyboard mechanism can be inoperative or otherwise not affected by touching the touch screen 17. While the touch screen 17 has been so locked, the lock screen button 208 can change its display mode to indicate the locked state of the touch screen 17, for example by displaying a locked padlock icon, as shown in FIG. 6b. In addition, during the locked state, the lock screen button 208 can be surrounded and abutted by an unlock screen key 209. Touching any portion of the unlock screen key 209 of the touch screen 17 immediately unlocks the touch screen, which transitions back into the unlocked state in which the touch screen is fully operational and active once again. The touch screen 17 also automatically unlocks and / or remains unlocked in the presence of any technical, high priority, medium priority, or low priority alerts. The touch screen 17 can also automatically transition into the locked state after a period of non-touch activation, as long as no alerts are present according to the automatic lock feature.

[0093] According to embodiments of the present disclosure, the header portion 102 can include a connection status indicator 210, which when possibly illuminated or glowing in a color such as green or some other suitable color, indicates the network connection status with respect to the system touch screen monitor 15 and the hospital information system / computer information system (HIS / CIS) network. When the connection status indicator 210 is not illuminated or glowing, or is illuminated or glowing in a different color (e.g., red), then it indicates that there is no network connection with the HIS / CIS network.

[0094] According to embodiments of the present disclosure, the header portion 102 can include a configuration identifier 212 that indicates a particular user configuration of the graphical user interface 100 that has been configured and / or selected by the user 15 of the touch screen monitor according to user preferences. For example, the touch screen monitor 15 can be operable to provide a plurality of different touch screen configurations that can be selected by the user according to user preferences and according to programmed graphical user interface options. For example, the touch screen monitor 15 can be operable to provide two, three, four, five, or six, etc. different selectable touch screen configurations that can be selected by the user. For example, FIG. 3a constitutes one non-limiting selectable touch screen configuration. For example, other non-limiting selectable touch screen configurations shown in FIG. 3b can be selectively arranged by the user of the graphical user interface 100 during a setup mode described later in the present disclosure.

[0095] FIG. 7a indicates that a second user configuration identified as "Adult Configuration #2" has been selected and is displayed as the configuration identifier 212. It should be understood that there is a first user configuration identified as "Adult Configuration #1" that can be selected but is not selected according to the non-limiting example. If selected, the configuration identifier 212 would display "Adult Configuration #1". By way of analogy, other user configurations such as a third user configuration would be identified as "Adult Configuration #3" if selected, and so on. If the second user configuration is modified after selection, which is possible according to the present disclosure, the configuration identifier 212 indicates the modification by the illuminated or glowing identifier, possibly yellow or other color, accompanied by the phrase "Configuration Changed" shown by FIG. 7b.

[0096] According to embodiments of the present disclosure, the header portion 102 can include a system settings menu button 214 for activating a system configuration menu interface 802. According to this embodiment, the system settings menu button 214 can be represented by the icon shown in FIG. 8a. The system configuration menu interface is used to configure the graphical user interface 100 of the heart-lung bypass machine 1 so as to configure it in an ergonomic manner according to the preferences of one or more particular users. The system configuration menu interface 802 will be described later in the present disclosure. When the system configuration menu interface is displayed upon activation of the system settings menu button 214 that can constitute a touch or press-activatable single activation button, the icon shown in FIG. 8a is replaced by the "Close Menu" button shown in FIG. 8b.

[0097] According to embodiments of the present disclosure, the header portion 102 can be provided with all of the above-described features 200, 202, 204, 206, 208, 210, 212, and 214, or just any combination of some of the features 200, 202, 204, 206, 208, 210, 212, and 214.

[0098] Central monitoring portion of the graphical user interface

[0099] The central monitoring portion 106 is divided into one or more segments 108 that are used to display information about one or more sensor modules and / or provide access to one or more functions (i.e., user modules) that operate or facilitate operation of the heart-lung bypass machine 1. For application to heart-lung machine environments or other heart-lung bypass machines, the central monitoring portion 106 is divided into four segments 108 that can be referred to as "quadrants," providing optimal space utilization efficiency and providing an ergonomic, user-centric, and configurable monitoring interface. However, for other applications, other numbers of segments 108 can be preferred. For example, the central monitoring portion can be divided into two portions, three portions, five portions, six portions, seven portions, or eight portions. Each segment of the central monitoring portion can be substantially symmetrical (i.e., have the same size and shape), or they can be asymmetrical (i.e., some segments can have different sizes and / or shapes than other segments).

[0100] Each segment 108 can be individually configurable to include one to four user-configurable tabbed display pages, or each segment 108 can constitute a single non-tabbed display page that is user-configurable. According to some embodiments of the present disclosure, some segments 108 include one to four user-configurable tabbed display pages, and some segments 108 constitute a single non-tabbed display page. According to embodiments of the present disclosure, the central monitoring portion 106 is provided with one non-tabbed display page for segment 108a and three segments 108b, 108c, and 108d that include multiple tabbed display pages.

[0101] A display page according to the present disclosure is a graphical image that is displayed within the boundaries of a segment 108, which is confined within the segment 108. The display page completely covers its segment or covers a substantial portion of the display space of its segment 108 when displayed. A display page according to the present disclosure is not a pop-up image, and it does not cover beyond one segment 108. Thus, a display page according to the present disclosure stays within the confines of its segment 108 boundaries 107, and does not encroach on any adjacent display pages located in another segment 108. The advantage of limiting display pages in this manner is that display pages from adjacent segments cannot overlap each other, and thus they cannot cover or obscure the images displayed by the display pages of another segment, including data and alarms. According to the present disclosure, a display page is configured as either a non-tabbed display page or a tabbed display page.

[0102] Unbound display pages

[0103] A non-tabbed display page, such as the display page 115 of segment 108a, does not have tabs. The non-tabbed display page 115 can include, for example, a graphical image that is displayed in its entirety within the boundaries of the segment 108. The non-tabbed display page 115 can include, for example, a graphical image that is displayed in its entirety within the boundaries of the segment 108.Figure 9 One or more sectors 122a, 122b, 122c, 122d, 122e, 122g, 122f, and 122h are shown. According to a non-limiting embodiment of this disclosure, the non-tabbed display page 115 is configured as a sensor module display page, primarily displaying sensor data and optionally other information related to the operation of the cardiopulmonary bypass machine 1. According to embodiments of this disclosure, the non-tabbed display page 115 displays time-sensitive information crucial to the operation of the cardiopulmonary bypass machine 1, displayed in a manner requiring continuous display so that the person operating the cardiopulmonary bypass machine 1 (e.g., a perfusion physician) can continuously monitor it. In this way, the person monitoring the graphical user interface 100 can continuously and directly visually access the information displayed by the non-tabbed display page 115.

[0104] from Figure 9 As is evident, those blocks on the non-tabbed display page 115 configured to display sensor data include their own module setting menu buttons 124. Each module setting menu button 124 is similar to the system setting menu button 214, except that each module setting menu button 124 is used to activate the module configuration menu interface. According to embodiments of this disclosure, the module setting menu button 124 may be represented by the icon shown in FIG. 8a. The module configuration menu interface is used to configure the corresponding modules of the blocks of the graphical user interface 100 such that they are configured to display sensor data according to the user's preferences, the user being the one who establishes the functionality of the modules and connects appropriate sensors to the blocks via the sensor modules, which are provided with information display units. Figure 9 Various non-limiting information display units 125a, 125b, 125c, 125d, 125f, and 125g are shown for corresponding sensor modules in their respective blocks. The configurations of various specific sensor module types will be described in more detail later in this disclosure.

[0105] Various module configuration menu interfaces will be described in more detail later in this disclosure. When the module configuration menu interface is displayed when the module setting menu button 124 (which may constitute a single touch or press-sensitive activation button) is activated, the module configuration menu interface remains displayed in its quadrant until it is turned off by activating the pressure or touch-sensitive button used to close the module configuration menu interface. In embodiments of this disclosure, when the module configuration menu interface is displayed, it covers the entire quadrant in which the module is located, but does not cover any portion of any other quadrant of the graphical user interface 100.

[0106] As is evident from Figure 3, according to embodiments of this disclosure, it is not necessary to utilize a non-tabbed display for each section of the page. Figure 9It is apparent that, according to embodiments of the present disclosure, each block of the non-tabbed display pages can be selectively utilized, but some blocks can be configured for use with sensor modules while some blocks can be configured for use with non-sensor modules. In Figure 9 In particular, for example, block 122h is configured to display non-sensor data provided by a non-sensor module provided with information display portion 125h.

[0107] Tabbed display pages

[0108] For example, tabbed display pages such as tabbed display pages 110, 111, 112, 114 of segment 108b of FIG. 3 are characterized as tabbed in that they each include a tab 110a, 111a, 112a, 114a extending from a portion of the display page. According to embodiments of the present disclosure, each tab 110a, 111a, 112a, 114a extends from the bottom of its display page 110, 111, 112, 114, respectively. However, according to other embodiments, the tabs can all extend from the right side of the display page, or they can all extend from the left side of the display page, or they can all extend laterally toward the side of the touch screen monitor 15, or they can all extend toward the inside of the touch screen 17, or they can all extend from the top of the display page.

[0109] The tabs 110a, 111a, 112a, 114a serve a variety of functions. First, the tabs allow the user to see how many display pages a segment 108 has. For example, in FIG. 3a, four segments 108 are shown in a non-limiting illustrative embodiment. In a clockwise direction, the four segments 108 include a top left segment 108a and a top right segment 108b, each abutting the header portion 102, and a bottom right segment 108c and a bottom left segment 108d, each abutting the footer portion 104. The top right segment 108b includes four tabbed display pages 110, 111, 112, and 114, each with a respective corresponding tab 110a, 111a, 112a, and 114a. The bottom left segment 108d includes three tabbed display pages 116, 118, and 120, whose respective tabs are tabs 116a, 118a, and 120a, respectively. The bottom right segment 108c includes two tabbed display pages 121 and 123, whose respective tabs are tabs 121a and 123a, respectively. The top left segment displays a single non-tabbed display page 115, as this display page has no tabs.

[0110] Second, each tab provides one or more graphical display icons that display information about the nature of the display page corresponding to the displayed icon. For example, in accordance with non-limiting embodiments of the present disclosure, tab 110a displays the abbreviation "CPL" identifying that the tabbed display page 110 displays module monitoring data specifically related to cardiopulmonary bypass, which involves the intentional and temporary interruption of a patient's heart activity on a heart-lung bypass machine during heart surgery. Thus, tab 110a can be referred to as a cardiopulmonary bypass tab, and tabbed display page 110 can be referred to as a cardiopulmonary bypass display page.

[0111] Tab 111a displays a clock icon identifying that the tabbed display page 111 displays timer data. Thus, tab 111a can be referred to as a timer tab, and tabbed display page 111 can be referred to as a timer display page.

[0112] Tab 112a displays a heart rate percentage icon identifying that the tabbed display page 112 displays a target flow calculator based on weight. For example, the target flow calculator can be used to calculate a target blood flow to a patient on a heart-lung bypass machine based on the patient's height, weight, and body surface area (BSA) using known BSA formulas of DuBois, Boyd, or Mosteller. Thus, tab 112a can be referred to as a target flow calculator tab, and tabbed display page 112 can be referred to as a target flow calculator display page.

[0113] Tab 114a displays a BSA calculator icon identifying that the tabbed display page 114 displays a perfusion calculator, for example, that can be used to calculate various perfusion parameters before and during a heart-lung bypass surgery. An example of a perfusion calculator that can be implemented by the embedded processor 30 is disclosed in U.S. Provisional Patent Application No. 62 / 160,689, filed May 13, 2015, the entire disclosure of which is incorporated herein by reference in its entirety. Tab 114a can be referred to as a perfusion calculator tab, and tabbed display page 114 can be referred to as a perfusion calculator page.

[0114] Tabs 116a and 121a display multiple icons, for example, for pressure measurements, temperature measurements, bubble detection, and reservoir fluid level measurements, identifying that the respective tabbed display pages 116 and 121 display data from selected sensor modules related to one or more types of sensors for pressure measurements, temperature measurements, bubble detection, and fluid level measurements for various portions of the extracorporeal blood flow circuit of the heart-lung bypass machine 1. Thus, tabs 116a and 121a can be referred to as sensor tabs, and tabbed display pages 116 and 121 can be referred to as sensor data display pages.

[0115] Tab 118a displays a sun and snowflake icon, identifying that the tabbed display page 118 is directed to remote monitoring and control of a separate heater-cooler unit 85 associated with the heart-lung bypass machine 1. The heater-cooler unit 85 is used to assist in monitoring and controlling the patient's body temperature during heart-lung bypass, and can be operatively connected to provide patient temperature data to the processor 30 and to receive control signals from the processor 30. Thus, the tab 118a can be referred to as a heater / cooler remote control tab, and the tabbed display page 118 can be referred to as a heater / cooler remote control page.

[0116] Tab 120a displays a calculator icon, identifying that the tabbed display page 120 is directed to a basic calculator, such as can be used to perform basic mathematical operations (e.g., addition, subtraction, multiplication, division). Thus, the tab 120a can be referred to as a calculator tab, and the tabbed display page 120 can be referred to as a calculator display page.

[0117] Tab 123a displays a pulsatile waveform icon, identifying that the tabbed display page 123 is directed to a pulsatile flow control module that functions when the heart-lung bypass machine 1 employs an optional arterial pump that is capable of producing a pulsatile flow in at least a portion of the extracorporeal blood flow circuit. Thus, the tab 123a can be referred to as a pulsatile flow tab, and the tabbed display page 123 can be referred to as a pulsatile flow control display page.

[0118] FIG. 3b illustrates a different configuration of the graphical user interface 100 than FIG. 3a. It should be understood that these two configurations represent only two possible configurations of a plurality of configurations available to the user of the graphical user interface 100. Each configuration can be selectively configured by the user of the graphical user interface 100 using available setup functions, enabling the user to customize the graphical user interface 100 according to the user's personal preferences.

[0119] FIG. 3b illustrates two additional tabs 127a that are provided with another unique icon representing the function of the respective tabbed display page 127. In this case, the tabbed display page 127 constitutes a blood monitoring unit (BMU) interface display page, and the tab 127a constitutes a BMU interface tab. It should be understood that other icons can be used to represent the function of the corresponding tabbed display page. In other words, the scope of the present disclosure should not be interpreted as being limited to the particular icons and tabbed display pages explicitly disclosed herein.

[0120] When a user touches or presses a tab on the touchscreen 17 of the touchscreen monitor 15, each tab performs a selection function. This feature is apparent by comparing Figures 3a and 3b. In Figure 3a, the displayed tabbed display page of section 108b is tabbed display page 111, which is the case because the user must have previously pressed tab 111a on the touchscreen 17. Pressing tab 111a on the touchscreen 17 causes the processor 30 to cause the touchscreen monitor 15 to display tabbed page 111 (which is a timer display page), so it first appears in section 108b of the graphical user interface 100. The other tabbed display pages 110, 112, 114 are not visible except for their respective tabs 110a, 112a, 114a. This creates a visual effect in which the displayed tabbed display page 111 appears to cover the invisible tabbed display pages 110, 112, and 114.

[0121] For the purposes of this disclosure, a tabbed display page can be said to be in a display mode when it is displayed first in its section. A tabbed display page that appears to be covered by a tabbed display page that is in a display mode is considered to be in a covered mode. Thus, with respect to section 108b of Figure 3a, tabbed display page 111 is in a display mode and tabbed display pages 110, 112, and 114 are in a covered mode. According to embodiments of the present disclosure, multiple tabbed display pages within a section can be initialized to display the leftmost tabbed display page in a display mode and the remaining tabbed display pages in a covered mode by default.

[0122] In Figure 3b, the displayed tabbed display page of section 108b is tabbed display page 110, which is the case because the user must have previously pressed tab 110a on the touchscreen 17 or section 108b has just been initialized. Pressing tab 110a on the touchscreen 17 causes the processor 30 to cause the touchscreen monitor 15 to display tabbed page 110 (which is a cardiac arrest display page), so it appears first in section 108b of the graphical user interface 100. The other tabbed display pages 111, 112, 114 are not visible except for their respective tabs 111a, 112a, 114a. This creates a visual effect in which the displayed tabbed display page 110 appears to cover the invisible display pages 111, 112, and 114. Thus, with respect to section 108b of Figure 3b, tabbed display page 110 is in a display mode and tabbed display pages 111, 112, and 114 are in a covered mode.

[0123] Although not explicitly shown in the drawings, it should be understood that by analogy, a touch or press on tab 112a on touch screen 17 will cause processor 30 to cause touch screen monitor 15 to display tabbed display page 112 (which is the Target Flow Calculator display page) via graphical user interface 100, thus causing it to appear in the forefront (i.e., in display mode) in section 108b, while the other tabbed display pages 110, 111 and 114 appear overlaid (i.e., in overlay mode) and are not visible except for their respective tabs 110a, 111a and 114a. Similarly, a touch or press on tab 114a on touch screen 17 will cause processor 30 to cause touch screen monitor 15 to display tabbed display page 114 (which is the Perfusion Calculator page) via graphical user interface 100, thus causing it to appear in the forefront (i.e., in display mode) in section 108b, while the other tabbed display pages 110, 111 and 112 appear overlaid (i.e., in overlay mode) and are not visible except for their respective tabs 110a, 111a and 112a.

[0124] This tab functionality of the tabs and tabbed display pages with respect to the display mode and the overlay mode allows the user to visually move from one tabbed display page to another without having to move through a nested layer-like page structure. In the structure of section 108b, the tab of a respective tabbed display page can be activated by a touch or press to convert the respective tabbed display page to the display mode while converting the remaining tabbed display pages to the overlay mode, this structure of section 108b being characterized by a tab-selectable page structure which is quite different from conventional nested layer-like page structures such as those disclosed in U.S. Patent 4,712,191, which is incorporated herein by reference in its entirety. As should be understood from Figures 3a and 3b, sections 108b, 108c and 108d each have their own tab-selectable page structure.

[0125] An advantage of the tab-selectable page structure is that a user can move directly from any one tabbed display page within the section to any other tabbed display page within the same section with only one touch or press of the appropriate tab. For example, a user can move directly from tabbed display page 111 to tabbed display page 110 by activating tab 110a, or from tabbed display page 111 to tabbed display page 112 by activating tab 112a, or from tabbed display page 111 to tabbed display page 114 by activating tab 114a. Thus, the tab-selectable page structure allows for flexibility in moving from one tabbed display page to another, which is not possible with a nested page structure. For example, a user can move from tabbed display page 112 to tabbed display page 110 and then to tabbed display page 114 by first activating tab 110a, activating tab 114a after tabbed display page 110 is in the display mode, and then activating tab 112a. The examples illustrating the flexibility in moving between tabbed display pages are non-limiting and for illustrative purposes only, as any permutation of sequential movement between tabbed display pages within a section is within the scope of the present disclosure.

[0126] Another advantage of the tab-selectable page structure is that the tabs can be used to alert a user of alarm status of various modules, which can be configured as part of each tabbed display page. For example, according to embodiments of the present disclosure, whenever a tabbed display page is in the overlay mode and any sensor module or any non-sensor module that is a component of the tabbed display page being overlaid transitions to an alarm status, the corresponding tab of the tabbed display page being overlaid can transition to an alarm mode and flash or blink, and possibly change color, in order to draw attention to the alarm status. In this way, the alarm tab can notify the user to check the tabbed display page being overlaid for its alarm module. According to embodiments of the present disclosure, the alarm mode includes flashing between a normal color and an alarm color at a specific rate in accordance with medical device standards.

[0127] As a non-limiting example, segment 108b of FIG. 3b includes a pressure sensor module 129 that is displayed when the tabbed display pages are in display mode while tabbed display pages 111, 112, and 114 are in overlay mode. In FIG. 3a, tabbed display page 110 of segment 108b is in overlay mode, and the tabbed display pages are in display mode. When in this state, the user will not be able to directly see alarms as a part of pressure sensor module 129, which will be described later in this disclosure. Such alarms can be triggered when a measured pressure in a portion of an extracorporeal blood flow circuit exceeds a maximum threshold measured pressure or falls below a minimum threshold measured pressure.

[0128] Tab 110a can provide a notification of an alarm pressure sensor module 129 because it is still visible even though tabbed display page 110 is in overlay mode in FIG. 3a. According to embodiments of the present disclosure, when pressure sensor module 129 should alarm and tabbed display page 110 is in overlay mode, processor 30 transitions tab 110a into an alarm mode in which tab 110a can flash and change color. According to embodiments of the present disclosure, the alarm mode for each tab involves flashing between its background color and an appropriate alarm color, such as yellow for a medium priority alarm, red for a high priority alarm.

[0129] Based on how the tabs flash and / or change color, the alarm tabs can inform the user about the nature of the alarm, such as whether it constitutes a high priority alarm, a medium priority alarm, or a low priority alarm. For example, according to embodiments of the present disclosure, a yellow flashing tab can indicate a medium priority alarm, and a red flashing tab can indicate a high priority alarm. According to embodiments of the present disclosure, a low priority alarm constitutes a color change from the background color of the tab to a blue or yellow color without an additional flash. Thus, for example, a tab that transitions from its background color to a steady blue or steady yellow color represents a low priority alarm state. On the other hand, a tab that starts yellow flashing represents a medium priority alarm state, and a tab that starts red flashing represents a high priority alarm state. The rate of flashing can also correspond to the priority of the alarm. For example, the rate of yellow flashing according to a medium priority alarm can be lower than the rate of red flashing according to a high priority alarm. However, a low priority alarm, whether blue or yellow, maintains a steady, non-flashing display of the alarm color.

[0130] Accordingly, in embodiments of the present disclosure, the alarm tab can transform into a colored state that indicates the severity of the alarm module of the tabbed display page that is being overlaid. For example, the alarm tab can transform into a red color all the time or only on a portion of the tab in order to notify a high priority alert, while the alarm tab can transform into a yellow color all the time or only on a portion of the tab in order to notify a medium or low priority alert. The alarm tab can also transform into a cyan color all the time or only on a portion of the tab in order to notify a low priority alert. The alarm color scheme used in the present disclosure conforms to the standard color scheme of medical devices. Other color schemes can be employed when the graphical user interface 100 is used with non-medical devices only.

[0131] Accordingly, in embodiments of the present disclosure, the alarm tab can transform into a colored state that indicates the severity of the alarm module of the tabbed display page that is being overlaid. For example, the alarm tab can transform into a red color all the time or only on a portion of the tab in order to notify a high priority alert, while the alarm tab can transform into a yellow color all the time or only on a portion of the tab in order to notify a medium or low priority alert. The alarm tab can also transform into a cyan color all the time or only on a portion of the tab in order to notify a low priority alert. The alarm color scheme used in the present disclosure conforms to the standard color scheme of medical devices. Other color schemes can be employed when the graphical user interface 100 is used with non-medical devices only.

[0132] Having described the general structure of the graphical user interface, i.e., the non-tabbed display page 100 and, as well as the tab selectable page structure of the tabbed display pages, various sensor modules and non-sensor modules that can be used as building blocks of the non-tabbed display page and / or the tabbed display pages are described below.

[0133] Pressure Sensor Module

[0134] The heart-lung bypass system 1 is typically equipped with one or more pressure sensors 50 that are provided to measure pressure at various desired points on the extracorporeal blood flow circuit 3 and to input pressure data to the processor 30, which can process the pressure data before outputting the pressure data to the graphical user interface 100 for display. Data from each pressure sensor 50 is displayed by a corresponding unique pressure sensor module 152, as shown in FIGS. 10a and 10b. FIG. 10a is similar to FIG. 10b, except that FIG. 10a displays pressure data in mmHg, while FIG. 10b displays pressure data in kPa. Each pressure sensor module 152 is a display module that can be displayed in any of the four quadrants 108, either as a component of a non-tabbed display page, or as a component of a tabbed sensor display page, or as a component of a tabbed cardiopulmonary bypass display page, depending on the application and the preferences of each user. As a non-limiting example, the pressure sensor modules are illustrated as components of the non-tabbed display page 115 and as components of the tabbed cardiopulmonary bypass display page 110, as shown in FIG. 3b.

[0135] As shown in FIG. 10a, each unique pressure sensor module 152 includes a header field 154 that is an alphanumeric field that displays a unique identifier that pertains to the pressure sensor 50 from which the displayed data is obtained. The unique identifier can have the form "Px-," where x is a number that corresponds to the particular pressure sensor, followed by a sensor name, such as can indicate a location along the extracorporeal blood flow circuit. The sensor names shown in FIG. 10a are merely exemplary for illustrative purposes and are not meant to be limiting.

[0136] Each pressure sensor module 152 also includes a pressure value data field 156 that is a numeric field that displays the value of the pressure data measured by the pressure sensor 50 and a pressure value units field 157 that is an alphanumeric field that displays the units of the pressure data measured by the pressure sensor 50. Each pressure sensor module 152 can further include an intervention button 158 that can connect or disconnect the pump 38 interaction of the heart-lung bypass machine 1, as described in greater detail below. As noted above, each pressure sensor module 152 also includes the module settings menu button 124.

[0137] Each pressure sensor module 152 can further include a plurality of alarm indication states as shown in FIGS. 10c, 10d, 10e, 10f, and 10g. For example, as shown in FIG. 10c, when the pressure sensor 50 measures a pressure in the extracorporeal blood flow circuit that reaches and / or exceeds a stop limit value, the pressure sensor module 152 switches to a pressure high-priority alarm state. The pressure high-priority alarm state can be configured in various ways. In one non-limiting embodiment, the pressure high-priority alarm state includes displaying a warning symbol (e.g., triangle) with three exclamation marks, and a red banner that flashes at a defined rate consistent with medical device industry standards (i.e., a flash rate of 1.4 Hz to 2.8 Hz; a duty cycle of 20% to 60%). In another embodiment of the present disclosure, in addition to or as an alternative to the visual components of the pressure high-priority alarm state disclosed above, the pressure high-priority alarm state can include an audible alarm that includes a sound that pulses at a predetermined cadence (e.g., a high-pitched beeping sound).

[0138] As shown in FIG. 10d, when the pressure sensor 50 measures a pressure in the extracorporeal blood flow circuit that reaches and / or exceeds a threshold limit value that is substantially lower than the stop limit value, the pressure sensor module 152 switches to a pressure medium-priority alarm state. The pressure medium-priority alarm state can be configured in various ways. In one non-limiting embodiment, the pressure medium-priority alarm state includes displaying a warning symbol (e.g., triangle) with two exclamation marks, and a yellow banner that flashes at another predetermined rate (i.e., a flash rate of 0.4 Hz to 0.8 Hz, a duty cycle of 20% to 60%, for example). In another embodiment of the present disclosure, in addition to or as an alternative to the visual components of the pressure medium-priority alarm state disclosed above, the pressure medium-priority alarm state can include an audible alarm that includes a sound that pulses at another predetermined cadence (e.g., a beeping sound that is substantially lower in pitch than the high-pitched beeping sound of the high-priority alarm state).

[0139] As shown in FIG. 10e, when the pressure sensor 50 measures a pressure in the extracorporeal blood flow circuit 3 that reaches and / or exceeds an alarm limit value that is substantially lower than the threshold limit value, the pressure sensor module 152 switches to a pressure low-priority alarm state. The pressure low-priority alarm state can be configured in various ways. In one non-limiting embodiment, the pressure low-priority alarm state includes displaying a warning symbol (e.g., triangle) with a single exclamation mark, and a cyan banner that is presented in a non-flashing manner (i.e., a duty cycle of 100%). In another embodiment of the present disclosure, in addition to or as an alternative to the visual components of the pressure low-priority alarm state disclosed above, the pressure low-priority alarm state can include an audible alarm that includes a sound that pulses at another predetermined cadence (e.g., a beeping sound that is substantially lower in pitch than the medium-pitched beeping sound of the medium-priority alarm state).

[0140] Thus, according to the above example, the pressure value of the stop limit value is greater than the pressure value of the threshold limit value, which is greater than the pressure value of the alarm limit value. Moreover, according to industry standards for medical devices, a specific color scheme for pressure measurements has been described, i.e. red, yellow and cyan, for high, medium and low priority alarm banners, respectively. However, when the graphical user interface 100 is used in a non-medical environment, other color schemes can be employed.

[0141] In case the pressure high priority alarm state has been activated, the pressure measured by the pressure sensor 50 has reached and / or exceeded the stop limit value, which means that the pressure needs to be reduced immediately at least in the part of the extracorporeal blood flow circuit 3 whose pressure is monitored by the pressure sensor 50. One way to achieve this immediate reduction of pressure is to provide an automatic pressure correction algorithm which reduces the pump activity to reduce the pressure. Once the pressure has dropped below a set threshold value, the related pump will automatically resume activity according to the automatic pressure correction algorithm. However, an intervention button 158 can be provided which, when activated by the user touching or pressing it, overrides the automatic pressure correction algorithm which would otherwise affect the operation of the specific blood pump 38.

[0142] As a non-limiting example, according to Fig. 10a, the intervention button 158 indicates an operable connection to a specific pump, i.e. the arterial pump 38. When the pressure exceeds the stop limit value, the automatic pressure correction algorithm is activated so that the processor 30 controls to some extent the operation of the arterial pump 38 to reduce the pressure (i.e. the pump 38 is completely or partially shut down to reduce the pressure). However, by manually activating the intervention button 158 by the user, the automatic pressure correction algorithm can be selectively overridden for two seconds.

[0143] In case no intervention mechanism has been associated with the pump, the intervention button 158 is as shown in Fig. 11a so as to indicate that there is no connection between the pump and the intervention button 158, e.g. the automatic pressure correction algorithm can be overridden. When the intervention button 158 is in the state shown in Fig. 11a, the user cannot manually override the operation of the automatic pressure correction algorithm of the pump 38 due to the lack of association between the intervention button 158 and the pump 38. However, when the intervention button 158 is as shown in Fig. 1 lb, then a fault or other unintentional functional disconnection between the intervention button 158 and the pump 38 is detected, which prevents the intervention button 158 from overriding the operation of the automatic pressure correction algorithm.

[0144] Other pressure alarm conditions that can be displayed by the pressure sensor module 152 include the conditions shown in FIGS. 10f, 10g and 10h. In FIG. 10f, the pressure sensor module 152 indicates a condition in which the pressure sensor 50 is disconnected from the processor 30, such as can occur when the pressure sensor 50 is disconnected from the sensor panel. In FIG. 10g, the pressure sensor module 152 indicates a condition in which the pressure sensor 50 is malfunctioning. In FIG. 10h, the pressure sensor module 152 indicates a condition in which the pressure sensor 50 is unavailable, such as when the pressure sensor 50 is in an "off" configuration.

[0145] Bubble detection sensor module

[0146] The cardiopulmonary bypass system 1 is typically equipped with one or more bubble detection sensors 60, which are provided to measure bubbles in the blood flow at various desired points on the extracorporeal blood flow circuit 3 and to input bubble detection data to the processor 30, which can process the bubble detection data before outputting the bubble detection data to the graphical user interface 100 for display. The data from each bubble detection sensor 60 is displayed by a corresponding unique bubble detection sensor module 162, as shown in FIG. 3a. Each bubble detection sensor module 162 is a display module that can be displayed in any of the four quadrants 108, either as a component of a non-tabbed display page, or as a component of a tabbed sensor display page, or as a component of a tabbed cardiopulmonary arrest display page, depending on the application and the preferences of each user. As a non-limiting example, as shown in FIG. 3b, the bubble detection sensor module is illustrated as a component of a non-tabbed display page 115 and as a component of a tabbed cardiopulmonary arrest display page 110. Figure 12

[0147] As shown in FIG. 3a, each unique bubble detection sensor module 162 includes a header field 164, which is an alphanumeric field that displays a unique identifier that pertains to the bubble detection sensor 60 from which the data is obtained. The unique identifier can have the form "Bx-," where x is a number that corresponds to the particular bubble detection sensor, followed by a sensor name, such as can indicate the location along the extracorporeal blood flow circuit. Figure 12 Figure 12 The sensor names shown in FIG. 3a are merely exemplary, for illustrative purposes, and are not meant to be limiting.

[0148] ​​Each bubble detection sensor module 162 also includes a bubble detection data field 166, which is a graphical field that displays bubble detection data obtained by the bubble detection sensor 60 via a bubble level icon, and a reset button 167 that is activated by a touch or press to reset the detected bubble size when the bubble detection module 162 is in a bubble detection high priority alarm state. When the bubble detection module 162 is in a high priority alarm state, it indicates that a bubble has been detected that exceeds a predetermined threshold value, and that the blood flow in the extracorporeal blood flow circuit 3 needs to be reduced and the bubble removed before it is input to the patient. Therefore, when the bubble detection sensor module 162 enters the bubble detection high priority alarm state, the perfusionist or other operator of the heart-lung bypass machine 1 must ensure that corrective action has been taken to remove the detected bubble.

[0149] The bubble detection high priority alarm state then needs to persist until corrective action has been taken to remove the large detected bubble. Therefore, the reset button 167 is not available for selection when the bubble detection module 162 is not in the bubble detection high priority alarm state. Once the bubble detection sensor module 162 has entered the bubble detection high priority alarm state, the reset button 167 becomes available for selection. However, when the sensor 60 is detecting a bubble that is larger than the bubble size threshold corresponding to the bubble detection high priority alarm state, a touch or press activation of the reset button 167 will not reset the alarm state of the bubble detection sensor module 162.

[0150] In the event that the bubble detection high priority alarm state is activated, the detected bubble needs to be removed from the extracorporeal blood flow circuit 3. One way to begin removing these large bubbles is to provide an automatic debubbling algorithm that reduces the blood flow through the extracorporeal blood flow circuit 3 by changing the pump activity of the heart-lung bypass machine 1. Each bubble detection sensor module 162 can further include an intervention button 168 that, when activated by a user touch or press, overrides the automatic debubbling algorithm, which otherwise affects the operation of one or more blood pumps. As explained in more detail below, activation of the intervention button 168 initiates a two second override of the automatic debubbling algorithm. As noted above, each bubble detection sensor module 162 also includes the module settings menu button 124.

[0151] The bubble level icon of the bubble detection data field 166 is described with reference to FIGS. 13a, 13b, 13c, and 13d. The bubble level icon can display a plurality of levels of a predetermined detectable bubble size. The user selected bubble detection size is displayed as a circle around the selected bubble size, as shown by the white circle. Although the illustrated embodiment employs a white circle, other colored circles can be employed as long as the user of the bubble detection sensor module 62 easily understands. As is apparent from FIG. 13b, each circle of the bubble level icon is filled with a color that indicates a bubble detection medium priority alert status starting with the leftmost circle and ending before the circle that represents the selected bubble detection size (i.e., the circle surrounded by the white circle) to indicate that a smaller bubble than the selected trigger was detected (i.e., microbubble activity was detected). In this case, the bubble detection medium priority alert color can be yellow as it is the same as the pressure medium priority alert status.

[0152] When the current bubble detection activity is greater than or equal to the selected bubble detection size, as shown in FIG. 13c, the bubble detection high priority alert color (such as the red color used for the pressure high priority alert status) is filled from the smallest detected bubble size to the largest detected bubble size. The color of the high priority alert is selected in accordance with industry standards for medical devices. The selection of a color other than red indicates that the high priority alert belongs to an embodiment that is only for non-medical device applications.

[0153] FIG. 13d shows a situation in which the bubble detection sensor module 162 is configured to be on; however, no bubble detection sensor 60 is operatively connected to the bubble detection sensor module 162. In this case, all of the bubble size identifiers of the bubble detection icon are filled with black instead of the background color of the bubble detection sensor module 162. As is the case with all color selections of this disclosure, other colors besides black can be used to indicate that no bubble detection sensor 60 is operatively connected to the bubble detection sensor module 162 when the environment applied to is only for non-medical devices.

[0154] Each bubble detection sensor module 162 can also include a plurality of alarm indication states, as shown in FIGS. 14a, 14b, 14c, 14d, and 14e. For example, as shown in FIG. 14a, when the bubble detection sensor 60 detects a bubble in the extracorporeal blood flow circuit that reaches and / or exceeds a selected bubble detection size value, the bubble detection sensor module 162 switches to a bubble detection high priority alarm state. The bubble detection high priority alarm state can be configured in various ways. In one non-limiting embodiment, the bubble detection high priority alarm state includes displaying a warning symbol (e.g., triangle) with three exclamation marks, and a red banner that flashes at a predetermined rate that complies with industry standards for medical devices (i.e., a flash rate of 1.4 Hz to 2.8 Hz; a duty cycle of 20% to 60%). Additionally, the selected bubble size, as indicated by the bubble detection size identifier corresponding to the detected maximum bubble size and the smaller bubble size identifier, is also filled in red. In another embodiment of the present disclosure, in addition to the visual components of the bubble detection high priority alarm state disclosed above, the bubble detection high priority alarm state can include an audible alarm that includes a sound that pulses at a predetermined cadence (e.g., a high-pitched beeping sound) that complies with industry standards for medical devices.

[0155] As shown in FIG. 14b, when the bubble detection sensor 60 measures a bubble in the extracorporeal blood flow circuit 3 that reaches and / or is less than a threshold limit value of a stop limit value (i.e., detection of microbubbles that are less than the selected bubble detection size threshold), the bubble detection sensor module 162 switches to a bubble detection medium priority alarm state. The bubble detection medium priority alarm state can be configured in various ways. In one non-limiting embodiment, the bubble detection medium priority alarm state includes displaying a warning symbol (e.g., triangle) with one exclamation mark, and a yellow banner that flashes at another predetermined rate (i.e., a flash rate that is substantially lower than the flash rate of the bubble detection high priority alarm state, and selected from a flash rate of 0.4 Hz to 0.8 Hz, a duty cycle of 20% to 60%, that complies with industry standards for medical devices). In another embodiment of the present disclosure, in addition to the visual components of the bubble detection medium priority alarm state disclosed above, the bubble detection medium priority alarm state can include an audible alarm that includes a sound that pulses at a predetermined cadence (e.g., a beeping sound that is substantially lower in pitch than the high-pitched beeping sound of the high priority alarm state).

[0156] According to industry standards for medical devices, a specific color scheme for bubble detection has been described for the high and medium priority alarm banners, namely red and yellow, respectively. However, when the graphical user interface 100 is used in a non-medical environment, other color schemes can be employed.

[0157] Once the bubble detection sensor module 162 enters the bubble detection high priority alarm state, the bubble detection sensor module 162 will remain in that state until the reset button 167 has been activated (i.e., pressed or touch activated) and the bubble detection sensor 60 no longer detects a bubble equal to or greater than the bubble size detection limit set for the bubble detection sensor module 162. In other words, once the bubble detection sensor module 162 has entered the bubble detection high priority alarm state, it does not transition back to the no alarm state or the bubble detection medium priority alarm state until the bubble detection sensor module 162 has been reset using the reset button 167 (and at the same time the bubble detection sensor 60 is not currently detecting a bubble of a size equal to or greater than the bubble size detection threshold used to set the high priority alarm).

[0158] When the bubble detection sensor module 162 enters the bubble detection medium priority alarm state, the bubble detection sensor module 162 can exit that state without the need to activate the reset button 167. In fact, the reset button 167 is only activatable when the bubble detection sensor module 162 is in the bubble detection high priority alarm state, but not when the bubble detection sensor module 162 is in the bubble detection medium priority alarm state. According to embodiments of the present disclosure, the bubble detection sensor module 162 can spontaneously transition from the bubble detection medium priority alarm state to the no bubble detection state, as shown in FIG. 13a, or to the bubble detection high priority alarm state, as shown in FIG. 14a, depending on whether the bubble size decreases below the detectable limit (i.e., there is no detectable bubble at all) or the bubble size increases to trigger a transition to the bubble detection high priority alarm state. Figure 12

[0159] In the event that the bubble detection high priority alarm state has been activated, one or more bubbles detected by the bubble detection sensor 60 have reached and / or exceeded the selected threshold bubble detection size, which means that blood flow needs to be stopped immediately in at least that portion of the extracorporeal blood circulation circuit in which the unacceptable large bubbles are detected by the bubble detection sensor 60. One way to achieve this immediate stop in blood flow is to provide the system with an automatic bubble correction algorithm that automatically adjusts one or more pumps of the heart-lung bypass machine in response to the bubble detection high priority alarm state, thereby reducing or stopping blood flow in at least the relevant portion of the extracorporeal blood flow circuit 3. In this way, the system can automatically respond to the bubble detection high priority state and thus facilitate the process of purging the unacceptable large bubbles detected in the extracorporeal blood flow circuit 3 performed by the perfusionist or other healthcare personnel.

[0160] ​The bubble detection sensor module 162 can be provided with an intervention button 168 that, when activated by a user by touch or press, overrides the automatic bubble correction algorithm such that it ceases to influence the operation of the particular pump 38 for a predetermined period of time, such as two seconds. As a non-limiting example, according to Figure 14a, the intervention button 158 indicates an operable connection to the particular pump, i.e. the arterial pump 38. When a bubble is detected that exceeds the bubble detection threshold limit, the automatic bubble correction algorithm is activated such that the processor 30 controls the operation of the arterial 38 to some extent to reduce or stop blood flow at least in the relevant portion of the extracorporeal blood circuit 3. However, by manually activating the intervention button 168 by the user, the automatic pressure correction algorithm can be selectively overridden for two seconds.

[0161] The bubble detection sensor module 162 is capable of transitioning to several other alarm states. For example, as shown in Figure 14c, in the event that the bubble detection sensor 60 is disconnected from the sensor panel, the bubble detection sensor module 62 transitions to a bubble detection disconnected high priority alarm state. The bubble detection disconnected high priority alarm state can be configured in various ways. In one non-limiting embodiment, the bubble detection disconnected high priority alarm state includes a warning symbol (e.g. triangle) with three exclamation marks, and a red banner that flashes at a predetermined rate. However, unlike the bubble detection high priority alarm state, in the bubble detection disconnected high priority alarm state, none of the bubble size identifiers of the bubble detection data field 166 are filled in red, but rather in black to indicate disconnection. In another embodiment of the present disclosure, in addition to the visual components of the bubble detection disconnected high priority alarm state disclosed above, the bubble detection disconnected high priority alarm state can include an audible alarm that includes a pulsing sound (e.g. high pitched beeping sound) at a predetermined cadence.

[0162] As shown in FIG. 14d, when the bubble detection sensor 60 is available but somehow fails so as to return a fault state, the bubble detection sensor module 162 transitions to a bubble sensor fault alarm state. The bubble sensor fault alarm state can be configured in various ways. In one non-limiting embodiment, the bubble sensor fault alarm state includes displaying a warning symbol (e.g., triangle) with three exclamation marks, and a red banner that flashes at a predetermined rate. However, unlike the bubble detection high priority alarm state, in the bubble sensor fault alarm state, none of the bubble size identifiers of the bubble detection data field 166 are filled with red, but are filled with the background color, and a large red "X" is overlaid on the bubble detection data field 166. In another embodiment of the present disclosure, in addition to the visual components of the bubble sensor fault alarm state disclosed above, the bubble sensor fault alarm state can include an audible alarm that includes a pulsing sound (e.g., high-pitched beeping sound) at a predetermined cadence. According to embodiments of the present disclosure, the reset button 167 is not available when the bubble detection sensor module 162 is in the bubble sensor fault alarm state.

[0163] As shown in FIG. 14e, when the bubble detection sensor 60 is configured to an off state, the bubble detection sensor module 162 transitions to a bubble detection sensor unavailable state. The bubble detection sensor unavailable alarm state can be configured in various ways. In one non-limiting embodiment, the bubble detection sensor unavailable state includes displaying a black banner and a dimmed bubble detection data field 166. When in the bubble detection sensor unavailable state, the module settings menu button 124 is available, although the reset button 167 and the intervention button 168 are not. According to embodiments of the present disclosure, the reset button 167 and the intervention button 168 are displayed in a dimmed mode to indicate that they are not activatable (available) during the bubble detection sensor unavailable state, as shown in FIG. 14e. However, the module settings menu button 124 is displayed in an illuminated mode, as shown in FIG. 14e, to indicate its activatable (available) state.

[0164] Horizontal sensor module

[0165] The heart-lung bypass system can be provided with one or more level sensors 70 arranged to detect the level of liquid in a blood reservoir (typically a venous reservoir) that constitutes a component of the extracorporeal blood flow circuit 3 of the heart-lung bypass system 1. Each level sensor 70 is operatively connected to input liquid level data to the processor 30, which can process the liquid level data before outputting the liquid level data to the graphical user interface 100 for display. Data from the level sensors 70 can be displayed by a respective unique level sensor module 172, such as shown in Figure 15a. Each level sensor module 172 is a display module that can be displayed in any of the four quadrants 108, either as a component of a non-tabbed display page, or as a component of a tabbed sensor display page, or as a component of a tabbed cardiopulmonary bypass display page, depending on the application and the preference settings of each user. As a non-limiting example, the level sensor module is shown as a component of a non-tabbed display page 115 as shown in Figure 3b.

[0166] As shown in Figure 15a, each unique level sensor module 172 includes a header field 174, which is an alphanumeric field, that displays a unique identifier that pertains to the level sensor 70 from which the displayed data is obtained. The unique identifier can have the form of "Lx- ", where x is a number that corresponds to the particular level sensor, followed by a sensor name, such as can indicate the location along the extracorporeal blood flow circuit. The sensor names shown in Figure 15a are merely exemplary, for illustrative purposes, and are not meant to be limiting.

[0167] Each level sensor module 172 also includes a level data field 176, which is a graphical field, that displays the relevant level data obtained by the level sensor 70 via a level icon. More specifically, the level data obtained by the level sensor 70 pertains to the location of the level sensor 70. Each level sensor module 172 can further include an intervention button 178, which can be activated, where appropriate, to override an automatic level correction algorithm that automatically adjusts the level of blood in the blood reservoir 70 by operation of the blood pump 37 of the heart-lung bypass machine 1, as will be described in greater detail below. The pump 37 that is operatively connected to the intervention button 178 is a type that pumps blood from the blood reservoir 70. Each level sensor module 172 also includes the module settings menu button 124 as described above.

[0168] Referring to FIGS. 16a, 16b, 16c, and 16d, the low level icons of the low level field 176 are described. Each low level icon graphically represents the relative level of liquid in the associated reservoir. For example, the low level icon of FIG. 16a graphically represents an acceptable level of liquid within the blood reservoir (i.e., a level above the regulated level). The illustrated embodiment employs a green triangle in accordance with industry standards for medical devices. However, when the graphical user interface 100 is used as a component of a non-medical system, other colors and shapes can be employed to represent an acceptable relative level so long as they are readily understood by the user of the level sensor module 172 in this manner. The green triangle icon also has two horizontal white dashed lines that represent other important relative levels as described below with respect to other low level icons.

[0169] FIG. 16b graphically represents a level of liquid within the blood reservoir that is lower than the level of liquid illustrated by the low level icon of FIG. 16a. In fact, the level of liquid graphically represented by the low level icon of FIG. 16b is at or below the regulated limit represented by the upper horizontal dashed line and above the level of the level sensor 70 represented by the horizontal dashed line. Although the level of liquid illustrated by FIG. 16b is still an acceptable level of liquid, it represents a level of liquid that warrants closer attention in accordance with the low level priority alert status as represented by FIG. 15. This low level priority alert status can be configured in various ways. For example, as shown in FIG. 15b, the coloring of the graphical representation of the level of liquid can change from green to yellow and the yellow banner can be provided with a triangular warning icon and two exclamation marks that remain in a steady, non-flashing state when activated. In another embodiment of the present disclosure, in addition to the visual components of the low level priority alert status, the low level priority alert status can include an audible alert that includes a pulsing sound (i.e., a low or medium pitch sound) at a predetermined cadence that indicates the low level priority alert status.

[0170] The horizontal icon of Fig. 16c graphically represents a liquid level within the blood reservoir that is lower than the liquid level illustrated by the horizontal icon of Fig. 16b and corresponds to a liquid level that is at or below the level of the horizontal sensor 70, as indicated by the horizontal dashed line. The liquid level graphically represented by Fig. 16c is not an acceptable liquid level because there is a risk associated with the blood reservoir running dry, so it corresponds to a high priority alarm state, as illustrated by Fig. 15c. This horizontal high priority alarm state can be configured in various ways. For example, the coloring of the graphical representation of the liquid level can be changed to red, a red banner can be provided along with a triangular warning icon and three exclamation marks, and the horizontal icon can be made to flash at a predetermined rate that indicates the horizontal high priority alarm state. In another embodiment of the present disclosure, in addition to the visual components of the horizontal high priority alarm state, the horizontal high priority alarm state can include an audible alarm that includes a pulsing sound (i.e., a high-pitched sound) that indicates the horizontal high priority alarm state.

[0171] When the horizontal data field 176 displays the horizontal icon of Fig. 16c, thereby indicating the horizontal high priority alarm state, it is imperative that the low liquid level in the blood reservoir be corrected. In this case, the processor 30 initiates an automatic horizontal correction algorithm that includes adjusting the operation of the blood pump 38 or some other blood pump so that blood accumulates in the blood reservoir 36, thereby raising the blood level. In these cases, the intervention button 178 becomes activatable so that the user can activate the intervention button 178 by pressing or touching it on the touchscreen 17 and override the automatic horizontal correction algorithm for a period of two seconds. Such an override interrupts the automatic horizontal correction algorithm so that the blood pump 38 resumes its previous state of operation prior to the activation of the automatic horizontal correction algorithm.

[0172] When the displayed horizontal icon is the icon of Fig. 16b, the horizontal sensor module 172 can display the configuration shown in Fig. 15b, in which the pump operatively associated with the horizontal sensor module and the intervention button 178 is the arterial blood pump 38. When the displayed horizontal icon is the icon of Fig. 16c, the horizontal sensor module 172 can display the configuration shown in Fig. 15c, in which the pump operatively associated with the horizontal sensor module and the intervention button 178 is the arterial blood pump 38.

[0173] The state graphically represented by Fig. 16d corresponds to a situation in which the particular blood reservoir sensor level data cannot be obtained. The horizontal icon displayed by the horizontal data field 176 of the horizontal sensor module 172 can automatically transition between any of the states represented by Figs. 16a, 16b, 16c and 16d as appropriate. In this way, the horizontal sensor module 172 can indicate the liquid level in the liquid reservoir without requiring the user to perform any reset functions.

[0174] The illustrated embodiments of the horizontal icons of FIGS. 16a, 16b, 16c and 16d are non-limiting; however, they are in compliance with industry standards for medical devices. When the graphical user interface 100 is used in non-medical systems, other shapes and / or colors can be employed to graphically depict the various relative liquid levels of the respective blood reservoirs, as long as the various relative liquid levels are readily understood by the user of the horizontal sensor module 172 in this manner.

[0175] In some cases, the horizontal sensor 70 can be associated with a horizontal sensor module 172 that is operatively connected with the intervention button 178 and connected to the air removal pump 39 (i.e., vacuum pump) instead of the blood pumps 37 or 38. In such cases, during the automatic level correction algorithm, the processor 30 manipulates the operation of the air removal pump 39 to increase the flow of blood into the blood reservoir 36, thereby increasing the level of blood in the blood reservoir 36. In these cases, activation of the intervention button 178 is possible. Activation of the intervention button 178 by touching or pressing overrides the automatic level correction algorithm for a period of two seconds, and during the override, the air removal pump 39 operates as it did prior to the start of the automatic level correction algorithm.

[0176] As shown in FIGS. 17a, 17b and 17c, the liquid level sensor module 172 can assume various states. According to the present disclosure, a blood pump is a pump that is connected to the blood reservoir 36 and to the extracorporeal blood flow circuit 3 of the heart-lung bypass system, and is primarily used to pump blood through the extracorporeal blood flow circuit. While such blood can contain a trivial amount of air in the form of microbubbles, the majority of what is pumped by the blood pump is blood. According to the present disclosure, an air removal pump is a pump that is connected to the blood reservoir 36 to remove air from the blood reservoir. While such removed air can contain some blood, the majority of what is pumped by the air removal pump is substantially air.

[0177] When the horizontal sensor module 172 is operatively connected to the air removal pump 39 with the intervention button 178 and the blood in the blood reservoir is at an acceptable level (i.e., above the adjusted level), then the horizontal sensor module 172 will appear as shown in FIG. 17a. Substantially similar to FIG. 15a, FIG. 17a possesses the header field 174, the level data field 176, the intervention button 178 and the module settings menu button 124. However, the intervention button 178 of FIG. 17a identifies "ARP" (air removal pump) instead of "ART" (arterial side blood pump).

[0178] While the blood level in the blood reservoir is at an acceptable level, the level sensor module 172 as shown in Fig. 17a, the deaeration pump can be disengaged, meaning that it is not operating to draw a vacuum against the air pocket that is normally present in the blood reservoir. When the liquid level within the blood reservoir is below the liquid level illustrated by the level icon of Fig. 17a, the liquid level is at or below the regulated limit (indicated by the upper horizontal dashed line), but above the level of the level sensor 70 (indicated by the lower horizontal dashed line), the level sensor module 172 will be as shown in Fig. 17b. This state corresponds to a high priority state with respect to the deaeration pump, and can be configured in various ways. For example, the color of the graphical representation of the liquid level can change from green to yellow, and a red banner with a triangular warning icon and three exclamation marks can be provided, and the level icon can be made to flash at a predetermined rate in accordance with this high priority state. In another embodiment of the disclosure, in addition to the visual components of the high priority alarm state of the level, the high priority alarm state of the level can include an audible alarm comprising a sound pulsed at a rhythm (i.e., a medium or high pitched sound) indicating the level of the high priority alarm state.

[0179] When the level sensor module 172 displays the high priority alarm state of the level of Fig. 17b, the deaeration pump is automatically engaged due to the available automatic level correction algorithm, so as to exert a vacuum on the air pocket within the blood reservoir 36. This vacuum helps to draw blood from the extracorporeal blood flow circuit of the heart-lung bypass machine 1 into the blood reservoir. At the same time, the intervention button 178 is activatable by the user by touch or press. When the user activates the intervention button 178 by touch or press under these conditions, the automatic level correction algorithm is temporarily overridden for a period of two seconds, so that the deaeration pump temporarily resumes its operational state that existed when the automatic level correction algorithm was activated.

[0180] The level icon of Fig. 17c graphically represents the liquid level within the blood reservoir, which is lower than the liquid level illustrated by the level icon of Fig. 17b, and corresponds to a liquid level at or below the level of the level sensor 70, as indicated by the lower horizontal dashed line. This state also corresponds to a high priority alarm state of the level, and is similar to Fig. 17b, in that it displays a similar banner and warning signs as Fig. 17b, namely a red banner, a triangular warning icon, and three exclamation marks, and the level icon can be made to flash at a predetermined rate corresponding to this high priority alarm state of the level. According to this high priority alarm state of the level, the color of the graphical representation of the liquid level can change from yellow to red. In another embodiment of the disclosure, in addition to the visual components of this high priority alarm state of the level, the high priority alarm state of the level can include an audible alarm comprising a sound pulsed at a rhythm matching the degree of this high priority alarm state of the level (i.e., a high pitched sound).

[0181] When the level sensor module 172 displays the level high priority alarm state of Fig. 17c, according to the automatic level correction algorithm the air pump is automatically engaged or continues to be automatically engaged to apply a vacuum to the air bladder within the blood reservoir in order to assist in drawing blood from the extracorporeal blood flow circuit into the blood reservoir. At the same time, the intervention button 178 is activatable in order for a user to touch or press to activate. When a user activates the intervention button 178 under these conditions, the automatic level correction algorithm is temporarily overridden for a period of two seconds so that the air pump resumes its active state at the time of activation of the automatic level correction algorithm.

[0182] When the level sensor module 172 has displayed the level high priority alarm state, e.g. corresponding to 17b or 17c, it then in turn displays a state corresponding to Fig. 17d, i.e. the case where the blood level in the blood reservoir is at an acceptable level. The air pump initially remains active in order to apply a vacuum to the air bladder of the blood reservoir according to the automatic level correction algorithm for the duration of a lag period. During this lag period, the level sensor module 172 displays the level high priority alarm state as shown in Fig. 17d, and the intervention button 178 remains activatable. According to the alarm state shown in Fig. 17d, the level data field 176 displays the level icon of Fig. 16a, thereby indicating an acceptable level of blood in the blood reservoir. However, the banner is still red, continuing to display the triangular warning icon and three exclamation marks to inform the user that the air pump is still engaged and drawing a vacuum.

[0183] After the lag period has expired, and the blood level of the blood reservoir remains acceptable as detected by the level sensor 70, the level sensor module 172 transitions to display the image according to Fig. 17a. At this point, with the automatic level correction algorithm stopped, the manipulation of the air pump under the automatic level correction algorithm stops, and the intervention button 178 transitions to a state in which it cannot be activated by touch or pressing.

[0184] The illustrated embodiments of the level icons of 17a, 17b, 17c and 17d are non-limiting; however, they are in accordance with industry standards for medical devices. When the graphical user interface 100 is used as a component of a non-medical system, other shapes and / or colors can be used to graphically illustrate the various relative liquid levels of the respective blood reservoirs as long as the various relative liquid levels are readily understood by the user of the level sensor module 172 as such.

[0185] The level sensor module 172 can transition to several other alarm states. For example, as shown in FIG. 18a, in the event that the level sensor 70 is disconnected from the sensor panel, the level sensor module 172 transitions to a level disconnected high priority alarm state. The level disconnected high priority alarm state can be configured in various ways. In one non-limiting embodiment, the level disconnected high priority alarm state includes displaying a warning symbol (e.g., triangle) with three exclamation marks, and a red banner that flashes at a predetermined rate. However, unlike the other level high priority alarm states, when in the level disconnected high priority alarm state, the level icon of the level data field 176 is filled in with black so as to not indicate a level. In another embodiment of the disclosure, in addition to the above-mentioned visual components of the level disconnected high priority alarm state, the level disconnected high priority alarm state can include an audible alarm that includes a pulsing sound (e.g., high-pitched beeping sound) at a predetermined cadence, indicating the level disconnected high priority alarm state.

[0186] When the level sensor 70 is available but has malfunctioned in some way so as to return to a fault state, the level sensor module 172 transitions to a level fault alarm state, as shown in FIG. 18b. The level fault alarm state can be configured in various ways. In one non-limiting embodiment, the level fault alarm state includes displaying a warning symbol (e.g., triangle) with three exclamation marks, and a red banner that flashes at a predetermined rate. Additionally, when in the level fault alarm state, the level icon of the level data field 176 is filled in with black, and a large red "X" is overlaid on the level data field 176. In another embodiment of the disclosure, in addition to the above-mentioned visual components of the level fault alarm state, the level fault alarm state can include an audible alarm that includes a pulsing sound (e.g., high-pitched beeping sound) at a predetermined cadence, indicating the level fault alarm state.

[0187] When the level sensor 70 is configured to an off state, the level sensor module 172 transitions to a level sensor unavailable state, as shown in FIG. 18c. The level sensor unavailable state can be configured in various ways. In one non-limiting embodiment, the level sensor unavailable state includes displaying a black banner and a subdued level data field 176, which can also be filled in with black. When in the level sensor unavailable state, the intervening button 178 is not activatable, although the module settings menu button 124 is activatable by touch or press.

[0188] Temperature sensor module

[0189] The heart-lung bypass system 1 is typically equipped with one or more temperature sensors 80 that are arranged to measure the temperature at various desired points on the extracorporeal blood flow circuit 3, and / or to measure the temperature of the patient, and / or to measure the temperature of the heart during cardioplegia, and to input the temperature data to the processor 30, which can process the temperature data before outputting the temperature data to the graphical user interface 100 display. The data from each temperature sensor 80 is displayed by a respective unique temperature sensor module 182, as shown in Figures 19a, 19f and 19g. Figure 19a is similar to Figures 19f and 19g, except that Figures 19f and 19g include icon fields 188 and 189, respectively, that display information associated with the cardioplegia fluid circuit. More specifically, the icon field 188 indicates that the temperature sensor 80 is associated with the cardioplegia fluid heating-cooling unit, and measures the temperature of the blood of the extracorporeal blood flow circuit 3. This association is indicated graphically by the sun and snowflake symbols, and the body symbol. The icon field 189 indicates that the temperature sensor 80 is associated with the cardioplegia fluid heating-cooling unit, and measures the temperature of the cardioplegia fluid solution. This association is indicated graphically by the sun and snowflake symbols, and the heart symbol.

[0190] The temperature sensor module 182 is a display module that can be displayed in any one of the four quadrants 108, as a non-tabbed display page component, as a tabbed sensor display page component, or as a tabbed cardioplegia display page component, as appropriate, depending on the application and the preferences of each user. By way of non-limiting example, the temperature sensor module is shown as a component of the tabbed display pages 116 and 121, and as a component of the tabbed cardioplegia display page 110, as shown in Figure 3b.

[0191] As shown in Figure 19a, each unique temperature sensor module 182 includes a header field 184 that is an alphanumeric field that displays a unique identifier that pertains to the temperature sensor 80 from which the displayed data is obtained. The unique identifier can have the form "Tx-", where x is a number that corresponds to the particular temperature sensor, followed by a sensor name that can indicate, for example, a location along the extracorporeal blood flow circuit 3. The sensor names shown in Figure 19a are merely exemplary, for illustrative purposes, and are not meant to be limiting.

[0192] Each temperature sensor module 182 also includes a temperature value data field 186, which is a numeric field, displaying the value of the temperature data measured by the temperature sensor 80, and a temperature value unit field 187, which is an alphanumeric field, displaying the units of the temperature data measured by the temperature sensor 80. The temperature value unit field 187 can display temperature units in Celsius or Fahrenheit. According to embodiments of the present disclosure, the temperature value data field 186 and the temperature value unit field 187 can be integrated together as a single field. As described above, each temperature sensor module 182 also includes a module settings menu button 124.

[0193] Each temperature sensor module 182 can further include a plurality of alarm indication states as shown in FIGS. 19b, 19c, and 19d. For example, as shown in FIG. 19b, when the temperature sensor 80 measures a temperature in the extracorporeal blood flow circuit that reaches and / or exceeds an upper limit value or reaches and / or falls below a lower limit value, then the temperature sensor module 182 switches to a temperature medium priority alarm state. The temperature medium priority alarm state can be configured in a variety of ways. In one non-limiting embodiment, the temperature medium priority alarm state includes displaying a warning symbol (such as a triangle) with a pair of exclamation marks and a yellow banner that can flash at a predetermined rate to indicate the medium priority alarm state. In another embodiment of the present disclosure, in addition to the visual components of the temperature medium priority alarm state described above, the temperature medium priority alarm state can include an audible alarm that includes a sound that pulses at a rhythm (e.g., a medium-pitched beeping sound) to indicate the temperature medium priority alarm state.

[0194] A particular color scheme for the medium priority alarm banner regarding temperature measurements has been described, namely a yellow banner, in line with industry standards for medical devices. According to various alternative embodiments of the present disclosure, other color schemes can also be employed when the graphical user interface 100 is used with non-medical devices only.

[0195] The temperature sensor module 182 is capable of transitioning to several other alarm states. In FIG. 19c, the temperature sensor module 182 indicates a state in which the temperature sensor 80 is disconnected from the processor 30, such as can occur when the temperature sensor 80 is disconnected from the sensor panel. In FIG. 19d, the temperature sensor module 182 indicates a state in which the temperature sensor 80 is malfunctioning. In FIG. 19e, the temperature sensor module 182 indicates a state in which the temperature sensor 80 is unavailable, such as when the temperature sensor 80 is in an “off’ configuration.

[0196] Flow sensor module

[0197] The heart-lung bypass system 1 is typically equipped with one or more blood flow sensors 90 arranged to measure blood flow at various desired points on the extracorporeal blood flow circuit 3 and to input blood flow data to the processor 30, which can process the blood flow data before outputting the blood flow data to the graphical user interface 100 display. Data from each flow sensor 90 is displayed by a corresponding unique flow sensor module 192, as shown in FIG. 20a. The flow sensor module 192 is a display module that can be displayed in any one of the four quadrants 108, as a component of a non-tabbed display page, or as a component of a tabbed sensor display page, or as a component of a tabbed group stop display page, as appropriate, depending on the application and the preferences of each user. As a non-limiting example, the flow sensor module is illustrated as a component of a non-tabbed display page 115, and as a component of a tabbed display page 116, as shown in FIG. 3b.

[0198] As shown in FIG. 20a, each unique flow sensor module 192 includes a header field 194, which is an alphanumeric field, displaying a unique identifier belonging to the flow sensor 90 from which the displayed data is obtained. The unique identifier can have the form of “Fx-”, where x is a number corresponding to the particular flow sensor, followed by a sensor name, such as can indicate a location along the extracorporeal blood flow circuit. The sensor names shown in FIG. 20a are merely exemplary for illustrative purposes and are not meant to be limiting.

[0199] Each flow sensor module 192 also includes a flow value data field 196, which is a numeric field, displaying the value of the flow data measured by the flow sensor 90, and a flow value units field 197, which is an alphanumeric field, displaying the units of the flow data measured by the flow sensor 90. For example, the displayed units can be liters per minute (LPM). According to embodiments of the present disclosure, the flow value data field 196 and the flow value units field 197 can be integrated together as a single field. As noted above, each flow sensor module 192 also includes a module settings menu button 124.

[0200] Each flow sensor module 192 can also include a plurality of alarm indication states, as shown in FIGS. 20b, 20c, 20d, and 20e. For example, as shown in FIG. 20b, when the flow sensor 90 measures a negative blood flow in the extracorporeal blood flow circuit 3 (i.e., reverse flow is present), the flow sensor module 192 switches to a flow medium priority alarm state. The medium priority alarm state can be configured in various ways. In one non-limiting embodiment, the flow medium priority alarm state includes displaying a warning symbol (e.g., triangle) with two exclamation marks and a yellow banner that flashes at a predetermined rate corresponding to the flow medium priority alarm state. In another embodiment of the present disclosure, in addition to the visual components of the flow medium priority alarm state described above, the flow medium priority alarm state can include an audible alarm that includes a sound (e.g., a medium-pitched beeping sound) indicating the flow medium priority alarm state.

[0201] As shown in FIG. 20c, when the flow sensor 90 measures a blood flow in the extracorporeal blood flow circuit 3 that reaches and / or exceeds an upper limit value, the flow sensor module 192 switches to a flow medium priority alarm state. The flow medium priority alarm state is configured similarly to the medium priority alarm state provided when the flow is negative.

[0202] The specific color scheme for the flow high priority alarm banner and the flow medium priority alarm banner with respect to blood flow measurements, i.e., a red banner for high priority and a yellow banner for medium priority, has been described and complies with industry standards for medical devices. Other color schemes can be employed when the graphical user interface 100 is employed in a strictly non-medical monitoring environment in accordance with various embodiments of the present disclosure in which non-medical devices are not used.

[0203] The flow sensor module 192 is capable of transitioning to several other alarm states. In FIG. 20d, the flow sensor module 192 indicates an alarm state in which the flow sensor 90 is disconnected from the processor 30, such as can occur when the flow sensor 90 is disconnected from the sensor panel. In FIG. 20e, the flow sensor module 192 indicates an alarm state in which the flow sensor 90 is malfunctioning. In FIG. 20f, the pressure sensor module 192 indicates a notification state in which the pressure sensor 90 is not available, such as when the flow sensor 90 is in an “off’ configuration.

[0204] Pressure Delta Module

[0205] The segment 108 of the graphical user interface of the heart-lung bypass system 1 can employ one or more pressure delta sensor modules 252 that are operatively connected to at least two pressure sensors 50 that are disposed to measure pressure at respective desired points on the extracorporeal blood flow circuit 3 for the purpose of comparison and to input the two pressure data sources to the processor 30 that can process the pressure data to generate pressure delta data before outputting the pressure delta data to the graphical user interface 100 display. Such generated pressure delta data from pairs of pressure sensors 50 computed by the processor 30 are displayed by corresponding unique pressure delta sensor modules 252 as shown in FIGS. 21a and 21b. FIG. 21a is similar to FIG. 21b except that FIG. 21a displays the pressure delta data in mmHg units and FIG. 21b displays the pressure delta data in kPa units. The pressure delta data sensor modules 252 are display modules that can be displayed in any one of the four quadrants 108 as appropriate, as a constituent of a non-tabbed display page, or as a constituent of a tabbed sensor display page, or as a constituent of a tabbed cardioplegia display page, depending on the application and the preference settings of each user. By way of non-limiting examples, the pressure delta data sensor modules are shown as a constituent of the non-tabbed display page 115 of FIG. 3b, and as a constituent of the tabbed display page 116 as shown in FIG. 3a.

[0206] As shown in FIG. 21a, each unique pressure delta data sensor module 252 includes a header field 254 that is an alphanumeric field that displays a unique identifier that pertains to the pair of pressure sensors 50 from which the displayed data is obtained. The unique identifier can have the form of “pressure delta Py-Px”, where x is a number that corresponds to a particular first pressure sensor and y is a number that corresponds to a particular second pressure sensor that is paired with the first pressure sensor for the purpose of computing pressure delta. The header example shown in FIG. 20a is merely exemplary for illustrative purposes and is not meant to be limiting.

[0207] Each pressure delta data sensor module 252 also includes a pressure delta value data field 256 that is a numeric field that displays the value of the pressure delta data computed from the measured pressure by the pair of pressure sensors 50, and a pressure delta data value units field 257 that is an alphanumeric field that displays the units of the pressure delta data computed from the measured pressure data provided by the pair of pressure sensors 50. According to embodiments of the present disclosure, the pressure delta value data field 256 and the pressure delta value units field 257 can be integrated together as a single field. As mentioned above, each pressure delta data sensor module 252 also includes a module settings menu button 124.

[0208] Each pressure delta data sensor module 252 can further include an alarm indication state as shown in FIG. 21c. When the calculated pressure delta data value reaches and / or exceeds a threshold limit value, then the pressure sensor module 252 switches to a pressure delta medium priority alarm state as shown in FIG. 21c. The pressure delta medium priority alarm state can be configured in various ways. In one non-limiting embodiment, the pressure delta medium priority alarm state includes displaying a warning symbol (e.g., triangle) with two exclamation marks, and a yellow banner that flashes at a predetermined rate to indicate the medium priority alarm state. In another embodiment of the present disclosure, in addition to the visual components of the pressure delta medium priority alarm state disclosed above, the pressure delta medium priority alarm state can include an audible alarm that includes a sound that pulses at a predetermined cadence (e.g., a medium-pitched beeping sound) to indicate the pressure delta medium priority alarm state.

[0209] According to industry standards for medical devices, a particular color scheme for medium priority alarm banners has been described for pressure delta determinations (i.e., yellow). However, when the graphical user interface 100 is used in a strict non-medical monitoring environment and is not associated with any medical device, other color schemes can be employed in accordance with various embodiments of the present disclosure.

[0210] In FIG. 21d, the pressure delta data sensor module 252 indicates a notification state in which one or both of the paired pressure sensors is unavailable. This can occur when one or both of the pressure sensors 50 is in an "off' configuration.

[0211] In addition to the various sensor modules discussed above, the tabbed and non-tabbed display pages can be equipped with components selected from various non-sensor modules. For example, the non-tabbed display page 116 employs a non-sensor module in zone block 122h as shown. This non-sensor module displays timer data, such as time for a cardiopulmonary bypass procedure for perfusion, and time for cross-clamping and reperfusion for different portions of a cardiopulmonary bypass procedure. This example of a non-sensor module should be interpreted as merely exemplary, and thus non-limiting. Figure 9

[0212] Non-limiting examples of non-tabbed and tabbed display pages

[0213] ​Having described a number of non-limiting illustrative examples of sensor modules and non-sensor modules, e.g., various non-tabbed display pages and tabbed display pages that can be employed by a user to selectively construct the graphical user interface 100, a few non-limiting illustrative examples of non-tabbed display pages and tabbed display pages are described in order to highlight the modular structure of the non-tabbed display pages and tabbed display pages and the flexibility and customization provided by the optionalities associated with that modular structure.

[0214] Non-limiting illustrative non-tabbed display page configurations

[0215] The non-tabbed display page of segment 108a of FIG. 3a includes two pressure sensor modules (i.e., PI -pre-membrane and P2 -pre-membrane), two bubble detection sensor modules (i.e., B1 -pre-membrane and B2 -pre-membrane), and two level sensor modules (i.e., LI -reservoir and L2). One of the pressure sensor modules (i.e., P2 -pre-membrane) is operatively connected to an arterial pump, such that activation of its intervention button will affect operation of the arterial pump so connected; however, the other pressure sensor module (i.e., PI -pre-membrane) is not connected to any pump, as can be seen from the broken link icon with an X mark overlaying the broken link. One of the bubble detection sensor modules (B1 -pre-membrane) is operatively connected to an arterial pump, such that activation of its intervention button will affect operation of the arterial pump. The other bubble detection sensor module (B2 -pre-membrane) is operatively connected to an auxiliary pump, such that activation of its intervention button will affect operation of the connected auxiliary pump. One of the level sensor modules (i.e., L2) is operatively connected to an auxiliary pump, such that activation of its intervention button will affect operation of the auxiliary pump. The other level sensor module (i.e., LI -reservoir) is not connected to any pump, as it is in the "off" state, as indicated by the icon.

[0216] The non-tabbed display page of segment 108a of FIG. 3b shows a different configuration than that of segment 108a of FIG. 3a. FIG. 3b shows two pressure sensor modules (i.e., PI - pre-membrane and P2 - post-membrane), one pressure delta sensor module (i.e., pressure delta P2 - PI), one bubble detection sensor module (i.e., B2 - post-membrane), two level sensor modules (i.e., LI - reservoir and L2), and one flow sensor module (i.e., FI - pre-membrane). One of the pressure sensor modules (i.e., PI - pre-membrane) is not connected to a pump, as can be seen from the outline-disconnected icon of the intervention button, so its intervention button does not affect the operation of any pump, as it is in a non-connected state. The other pressure sensor module (i.e., P2 - post-membrane) is operatively connected to an arterial pump, as can be seen from the non-outline-fully-connected icon corresponding to the intervention button, so activation of the intervention button of that pressure sensor will at least temporarily affect the operation of the connected arterial pump. The bubble detection sensor module (B2 - post-membrane) is operatively connected to an arterial pump, so that activation of the intervention button of that bubble sensor detection module will affect the operation of the arterial pump. One of the level sensor modules (i.e., LI - reservoir) is operatively connected to an air purge pump (“ARP”) that is a vacuum pump, so that activation of its intervention button will temporarily affect the operation of the air purge pump. The other level sensor module (i.e., L2) is operatively connected to an arterial pump, so that activation of the intervention button of that sensor module will temporarily affect the operation of the arterial pump.

[0217] Figure 9 The non-tabbed display page of segment 108a of FIG. 3b shows a different configuration than that of segment 108a of FIG. 3a. FIG. 3b shows two pressure sensor modules (i.e., PI - pre-membrane and P2 - post-membrane), one pressure delta sensor module (i.e., pressure delta P2 - PI), one bubble detection sensor module (i.e., B2 - post-membrane), two level sensor modules (i.e., LI - reservoir and L2), and one flow sensor module (i.e., FI - pre-membrane). One of the pressure sensor modules (i.e., PI - pre-membrane) is not connected to a pump, as can be seen from the outline-disconnected icon of the intervention button, so its intervention button does not affect the operation of any pump, as it is in a non-connected state. The other pressure sensor module (i.e., P2 - post-membrane) is operatively connected to an arterial pump, as can be seen from the non-outline-fully-connected icon corresponding to the intervention button, so activation of the intervention button of that pressure sensor will at least temporarily affect the operation of the connected arterial pump. The bubble detection sensor module (B2 - post-membrane) is operatively connected to an arterial pump, so that activation of the intervention button of that bubble sensor detection module will affect the operation of the arterial pump. One of the level sensor modules (i.e., LI - reservoir) is operatively connected to an air purge pump (“ARP”) that is a vacuum pump, so that activation of its intervention button will temporarily affect the operation of the air purge pump. The other level sensor module (i.e., L2) is operatively connected to an arterial pump, so that activation of the intervention button of that sensor module will temporarily affect the operation of the arterial pump.

[0218] Non-sensor module 125h is an information display related to various timers useful during the extracorporeal circulation process, such as timers that record perfusion duration, cross-clamp duration, and reperfusion duration. Non-sensor module 125h does not include a module settings menu button.

[0219] The configurations of FIGS. 3a, 3b, and 9 constitute non-limiting examples only to demonstrate the flexible and reconfigurable nature of the non-tabbed display pages. In one embodiment of the present disclosure, the central monitoring section 106 includes only one non-tabbed display page and one, two, or three tabbed display pages, and the non-tabbed display page is divided into a plurality of blocks, and each block can be configured with a module selected from the group consisting of a pressure sensor module, a bubble detection sensor module, a level sensor module, a temperature sensor module, a flow sensor module, and a timer module (i.e., a non-sensor module).

[0220] Non-limiting illustrative tabbed display page configurations for cardioplegia

[0221] The tabbed display pages of section 108b of FIGS. 3a and 3b are related to a cardioplegia display interface, such as can be related to sensor data, pumps, and other components of a cardiopulmonary bypass machine used to perform cardioplegia during a cardiopulmonary bypass surgery. For example, tabbed display page 110, as shown in FIG. 3b, whose tab 110a is only a portion of the tabbed display page 110 visible in FIG. 3a, can be configured to include a pressure sensor module (i.e., P3 - Cardioplegia), a temperature sensor module (i.e., Tl - Cardioplegia), and a bubble detection sensor module (i.e., B2 - Cardioplegia). Both the pressure sensor module and the bubble detection sensor module are operatively connected to the same cardioplegia ("CPL") pump, such that activation of the intervention button of either the P3 - Cardioplegia pressure sensor module or the B2 - Cardioplegia bubble detection module temporarily affects the operation of the cardioplegia pump. The tabbed display page also includes a non-sensor module (i.e., Total Cardioplegia Volume), which is used to manually keep track of the amount of fluid volume administered to the patient as the cardioplegia process progresses. The tabbed display pages of section 108b, as shown in FIG. 3b, also include a timer module related to tracking cardioplegia time and a cardioplegia delivery module. The tabbed display page 110 has a reset button labeled "Reset Actual Cardioplegia" that, when activated by being touched or pressed for at least two seconds, resets the page.

[0222] As shown in Fig. 3a, the tabbed display page 111 is a timer display page, the tab 111a of which is the only visible portion of Fig. 3b. The tabbed display page 111 includes non-sensor timer modules that display various timers used during cardiopulmonary bypass surgery to record the duration of perfusion, cross-clamp, and reperfusion during cardiopulmonary bypass. These non-sensor modules related to timed perfusion, cross-clamp, and reperfusion do not include a module settings menu button. The tabbed display page 111 also includes non-sensor timer modules that include a crystal delivery timer and an infusion timer that can be operatively connected to a crystal delivery pump and an infusion delivery pump, as is apparent from the module settings menu button. The tabbed display page 111 can also include non-sensor up and down timer modules that include an up timer and a down timer. Each of the timers in the tabbed display page 111 can be selectively reset by holding down the corresponding timer reset field for at least two seconds.

[0223] Non-limiting illustrative tabbed display page calculator configurations

[0224] The tabbed display page 112, shown in Figs. 22a and 22b, relates to a body weight based target flow calculator user interface according to embodiments of the present disclosure. The tabbed display page 112 includes a body surface area formula selection module 300 having three formula selection buttons 302, 304, 306, depending on whether the user of the interface wishes to employ the DuBois formula, the Boyd formula, or the Mosteller formula, respectively, to calculate the body surface area (BSA) in metric units based on the height and weight of the patient, using touch or press sensitive keyboard 312 to input the height and weight into data fields 308 and 310, respectively. The calculated BSA is displayed in data field 314. The tabbed display page 112 also includes a target flow module 316 that allows the user to calculate the target flow of the extracorporeal blood flow circuit 3 to be equal to the product of the calculated BSA of the patient and a target flow index entered in data field 320 (Fig. 22a), or equal to the product of the superscripted patient weight and a target flow index entered in data field 320 (Fig. 22b). The user can select which target flow calculation to perform by activating the BSA based target flow calculation button 322 or the weight based target flow calculation button 324. The result of the target flow calculation is displayed in data field 326. All of the above calculations are performed by the processor 30.

[0225] A tabbed display page 114 is shown in FIGS. 23a, 23b, 23c and 23d, which relates to a perfusion calculator user interface according to embodiments of the present disclosure. The tabbed display page 114 includes a perfusion parameter selection module 330 having four touch or press sensitive selection buttons 332, 334, 336, 338, respectively, for selecting modules that allow the user to input patient parameters, calculate intra-CPB, calculate a heparin dose for the patient, or calculate the patient's index oxygen delivery DO2I and index oxygen consumption VO2I, and optionally their ratio, which are useful clinical parameters in monitoring a patient, as disclosed in U.S. Patent Application Publication No. US 2006 / 0257283 Al, the entire disclosure of which is incorporated herein by reference. In view of the touch or press sensitive selection buttons 332, 334, 336, 338, the tabbed display page 114 has a non-nested sublayer structure, which is substantially different from a nested structure. The tabbed display page 114 also includes a keypad 340 for entering data into data fields for data entry.

[0226] When the "patient statistics" button 332 has been touched or pressed active, the tabbed display page 114 displays a patient statistics data entry user interface, as shown in FIG. 23a, having data entry fields 350 and data output fields 342, 344, 346, 348, 352, 354 and 356. The data output field 342 has a height data field that is automatically populated with the patient's height as entered into the data entry field 308 of the tabbed display page 112. The data output field 344 has a weight data field that is automatically populated with the patient's weight as entered into the data entry field 310 of the tabbed display page 112. The data output field 346 has a body surface area (BSA) data field for outputting the patient's BSA that is calculated by the processor 30 using one of the BSA formulas that can be selected with the tabbed display page 112. The data output field 348 has a body mass index (BMI) data field for outputting the patient's BMI that is calculated by the processor 30 using a known formula and the height and weight data automatically populated into the data output fields 342 and 344. The data entry field 350 has a volume / kg data field for entering an estimated intravascular blood flow volume per unit weight for use in other calculations using the keypad 340. The data output field 352 has a pre-CPB volume data field for outputting an estimated pre-CPB blood volume of the patient that is calculated by the processor 30 based on a known formula and the data displayed by the data output fields 342, 344 and the data entry field 350. The data output field 354 has a data field for displaying the selected BSA formula (i.e., DuBois, Boyd or Mosteller) used to calculate the patient's BSA as selected from the body surface area formula selection module 300 of the tabbed display page 112. The data output field 356 has a weight classification field for outputting a weight classification (i.e., underweight, normal, overweight, obese) selected by the processor 30 based on the BMI calculated by the processor 30 and commonly used weight classification paradigms.

[0227] When the "Intra-CPB Fluids" button 334 has been touched or pressed activated, the tabbed display page 114 displays an intra-CPB fluids data entry user interface, as shown in FIG. 23b, having data entry fields 360, 362, 364, 366, 368, 372 and data output fields 370 and 374. The keypad 340 is used to enter data into the data entry fields. The data entry field 360 has an initial volume data field for entering the initial volume required to prime the heart-lung bypass system 2. The data entry field 362 has a pRBC volume data field for entering the volume of packed red blood cells (pRBC) infused into the patient during the CPB procedure. The data entry field 364 has a pRBC Hct data field for entering the hematocrit (Hct) of the pRBC at the medical facility where the CPB procedure is performed. The data entry field 366 has an IV fluids data field for entering the volume of intravenous fluids (i.e., crystalloids, saline, platelets, fresh frozen plasma, etc.) infused into the patient up to that point during the CPB procedure. The data entry field 368 has an initial shut down volume data field for entering the initial shut down volume removed from the extracorporeal blood flow circuit 3 at the beginning of the CPB procedure. The data output field 370 has an intra-CPB volume data field for displaying the patient's intra-CPB volume, which is calculated by the processor 30 using known formulas with the input data from the data entry fields 360, 362, 364, 366, 368, such as disclosed in U.S. Provisional Patent Application No. 62 / 160,689, filed May 13, 2015, which is incorporated herein by reference. The data entry field 372 has a pre-CPB-Hct data field for entering the patient's Hct measured prior to starting the CPB procedure. The data output field 374 has an estimated CPB Hct data field for displaying the patient's estimated hematocrit during the CPB procedure, which is calculated by the processor 30 according to known formulas using the input data. See, e.g., U.S. Provisional Patent Application No. 62 / 160,689, filed May 13, 2015.

[0228] When the "Heparin Dose" button 336 has been touched or pressed activated, the tabbed display page 114 displays a heparin dose table, as shown in FIG. 23c, having a per weight unit heparin dose column 380 and a heparin calculated dose column 382, which is calculated by the processor 30 and automatically populated with the heparin dose calculated based on the data displayed in column 380 and the patient's weight entered into the data field 308 of the tab display page 112. As is apparent from columns 380 and 382, each row pairs the heparin dose per weight unit from column 380 with its calculated heparin dose from column 382. For example, for a patient weighing 80 kg, a calculated heparin dose of 24,000 units corresponds to a dose of 300 units / kg.

[0229] When the "DO2 / VO2 Index" button 338 has been touched or pressed, the tabbed display page 114 displays a clinical data entry user interface, as shown in FIG. 23d, having data entry fields 390, 392, 394, 396, 398, 400 and data output fields 402 and 404. The keypad 340 is used to enter data into the data entry fields. The data entry field 390 has a hemoglobin (Hb) data field for entering hemoglobin data for the patient. The data entry field 392 has an arterial oxygen saturation (SaO2) data field for entering arterial oxygen saturation data for the patient. The data entry field 394 has an arterial partial pressure oxygen (PaO2) data field for entering arterial partial pressure oxygen data for the patient. The data entry field 396 has a pump flow data field for entering pump flow (CO) data from the extracorporeal blood flow circuit 3. The data entry field 398 has a venous oxygen saturation (SvO2) data field for entering venous oxygen saturation data for the patient. The data entry field 400 has a venous partial pressure oxygen (PvO2) data field for entering venous partial pressure oxygen data for the patient. The data output field 402 has an index delivered oxygen (DO2I) data field for displaying the index delivered oxygen (DO2I) value calculated by the processor 30 from known equations using the data entered into the input data fields 390, 392, 394, 396, 398, 400. The data output field 404 has an index consumed oxygen (VO2I) data field for displaying the index consumed oxygen (VO2I) value calculated by the processor 30 from known equations using the data entered into the input data fields 390, 392, 394, 396, 398, 400. Non-limiting illustrative tabbed display page patient monitor configuration

[0230] According to embodiments of the present disclosure, the tabbed display page 117 can replace the tabbed display page 114. The tabbed display page 117, as shown in FIG. 23e, includes a perfusion parameter selection module 410 having four touch or press sensitive selection buttons 332, 334, 336, 412, respectively, for selecting to allow the user to enter patient parameters, to calculate intracardiac pulmonary fluid (intra-CPB), to calculate a heparin dose for the patient, or to monitor clinical parameters useful in monitoring the patient. The touch or press sensitive selection buttons 332, 334, and 336 activate substantially the same user interfaces shown in FIGS. 23a, 23b, and 23c, respectively, with the exception that the monitor button 412 replaces the "DO2 / VO2 Index" button 338 and activates a different user interface. The tabbed display page 117 has its own unique tab 117a. The tabbed display page 117 has a non-nested subhierarchy provided by the touch or press sensitive selection buttons 332, 334, 336, 412. Figure 24 the touch or press sensitive selection buttons 332, 334, and 336 activate substantially the same user interfaces shown in FIGS. 23a, 23b, and 23c, respectively, with the exception that the monitor button 412 replaces the "DO2 / VO2 Index" button 338 and activates a different user interface. The tabbed display page 117 has its own unique tab 117a. The tabbed display page 117 has a non-nested subhierarchy provided by the touch or press sensitive selection buttons 332, 334, 336, 412.

[0231] When the "Monitor" button 412 is activated by being touched or pressed, the tabbed display page 117 shows the clinical parameter monitoring interface, such as... Figure 24 As shown, it has data output fields 414, 416, 418, 419, 420, 422, 424, 425, 426, 428, 430, and 432. Data output fields 414, 416, 418, 420, 422, and 424 constitute sensor output fields and include a field setting menu button 434. This button is used to connect each field to a suitable data sensor and can be used to set alarms (i.e., high-priority alarm, medium-priority alarm, low-priority alarm) in a manner similar to module setting menu button 124. Data output fields 426, 428, 430, and 432 constitute calculated output fields and include a field setting menu button 435 for setting alarms, such as selecting one or more alarms from a group consisting of high-priority alarms, medium-priority alarms, and low-priority alarms.

[0232] For example, data output field 414 has a hemoglobin (Hb) data field for continuously displaying patient hemoglobin data derived from HCT sensor 95. In another embodiment of this disclosure, data output field 414 may display hematocrit data from a hematocrit data field instead of hemoglobin data from a hemoglobin data field, or the sensor may be a hemoglobin sensor. Since hemoglobin and hematocrit are generally related to the formula Hct = 3·(Hb), for the purposes of this disclosure, hemoglobin and hematocrit are considered equivalent and interchangeable. When the field setting menu button 434 of field 414 is touched or pressed, the field setting menu is activated and becomes visible, allowing the user to connect HCT sensor 95 to field 414 to display measured Hb or HCT data in field 414, and allowing the user to set any desired Hb / HCT high, medium, and / or low priority alarms for field 414. The graphical display of Hb / HCT high, medium, and low priority alarms can mimic the color scheme and configuration used for temperature sensor module 182 or flow sensor module 192.

[0233] The data output field 416 has an arterial blood oxygen saturation (Sa02) data field for displaying arterial blood oxygen saturation data of the patient derived from the arterial blood gas sensor assembly 94 that measures Sa02 in a continuous manner. When the field setup menu button 434 of the field 416 is touched or pressed activated, the field setup menu is activated and made visible so that the user can connect the arterial blood gas sensor assembly 94 to the field 416 for displaying the Sa02 data in the field 416, and so that the user can set any desired high, medium, and / or low priority alarms for Sa02 for the field 416.

[0234] The data output field 418 has an arterial partial pressure oxygen (Pa02) data field for displaying arterial blood oxygen partial pressure data of the patient derived from the arterial blood gas sensor assembly 94 that measures Pa02 in a continuous manner. When the field setup menu button 434 of the field 418 is touched or pressed activated, the field setup menu is activated and made visible so that the user can connect the arterial blood gas sensor assembly 94 to the field 418 for displaying the Pa02 data in the field 418, and so that the user can set any desired high, medium, and / or low priority alarms for Pa02 for the field 418.

[0235] The data output field 419 has an expiratory partial pressure of carbon dioxide (expCO2) data field for displaying expiratory carbon dioxide data of the patient derived from the carbon dioxide analyzer 96 that measures expCO2 in a continuous manner. When the field setup menu button 434 of the field 419 is touched or pressed activated, the field setup menu is activated and made visible so that the user can connect the carbon dioxide analyzer 96 to the field 419 for displaying the expCO2 data in the field 419, and so that the user can set any desired high, medium, and / or low priority alarms for expCO2 for the field 419.

[0236] The data output field 420 has a pump flow data field for entering pump flow (CO) data from the extracorporeal blood flow circuit that is obtained in a continuous manner by the pumped blood flow sensor 90. When the field setup menu button 434 of the field 420 is touched or pressed activated, the field setup menu is activated and made visible so that the user can connect the blood flow sensor 90 to the field 420 for displaying the blood flow data in the field 420, and so that the user can set any desired high, medium, and / or low priority alarms for blood flow for the field 420.

[0237] Data output field 422 has a venous oxygen saturation (Sv02) data field for displaying patient venous oxygen saturation data derived from venous blood gas sensor assembly 92 which measures Sv02 in a continuous manner. When field setting menu button 434 of field 422 is touched or pressed to activate, the field setting menu is activated and made visible so that the user can connect venous blood gas sensor assembly 92 to field 422 for display of Sv02 data in field 422, and so that the user can set any desired Sv02 high, medium and / or low priority alarms for field 422.

[0238] Data output field 424 has a venous partial pressure oxygen (Pv02) data field for displaying the venous partial pressure of oxygen data of a patient derived from venous blood gas sensor assembly 92 which measures Pv02 in a continuous manner. When field setting menu button 434 of field 424 is touched or pressed to activate, the field setting menu is activated and made visible so that the user can connect venous blood gas sensor assembly 92 to field 424 for display of Pv02 data in field 424, and so that the user can set any desired Pv02 high, medium and / or low priority alarms for field 424.

[0239] Data output field 425 has a blood lactate data field for displaying patient blood lactate data derived from on-line blood lactate sensor 99 which measures blood lactate levels in a continuous manner. When field setting menu button 434 of field 425 is touched or pressed to activate, the field setting menu is activated and made visible so that the user can connect blood lactate sensor 99 to field 425 for display of blood lactate data in field 425, and so that the user can set any desired blood lactate high, medium and / or low priority alarms for field 425.

[0240] Data output field 426 has an index delivered oxygen (D02I) data field for displaying the index delivered oxygen (D02I) value calculated by processor 30 for the patient from the BSA calculated using data input from HCT sensor 95, pumped blood flow sensor 90 and arterial blood gas sensor assembly 94 in accordance with a known formula, and using data input via tabbed display page 112. When field setting menu button 435 of field 426 is touched or pressed to activate, the field setting menu is activated and made visible so that the user can set desired D02I high, medium and / or low priority alarms for field 426.

[0241] The data output field 428 has an index consumption oxygen (VO2I) data field for displaying the index consumption oxygen (VO2I) value calculated by the processor 30 from data input from the HCT sensor 95, the pumped blood flow sensor 90, the arterial blood gas sensor assembly 92 and the venous blood gas sensor assembly 94, and the patient's BSA calculated using data input via the tabbed display page 112 according to known formulas. When the field settings menu button 435 of the field 428 is touched or pressed active, the field settings menu is activated and visible so that the user can set the desired VO2I high, medium, and / or low priority alarms for the field 426.

[0242] The data output field 430 has a (DO2I) / (VO2I) ratio data field for displaying the ratio of the index oxygen delivery (DO2I) to the index consumption oxygen (VO2I) value calculated by the processor 30 according to known formulas. When the field settings menu button 435 of the field 430 is touched or pressed active, the field settings menu is activated and visible so that the user can set the desired (DO2I) / (VO2I) ratio high, medium, and / or low priority alarms for the field 430.

[0243] The data output field 432 has a (DO2I) / (VCO2I) ratio data field for displaying the ratio of the index oxygen delivery (DO2I) to the index carbon dioxide generation (VCO2I) value calculated by the processor 30 according to known formulas using data input from the HCT sensor 95, the pumped blood flow sensor 90, the arterial blood gas sensor assembly 92 and the carbon dioxide analyzer 96. When the field settings menu button 435 of the field 432 is touched or pressed active, the field settings menu is activated and visible so that the user can set the desired (DO2I) / (VCO2I) ratio high, medium, and / or low priority alarms for the field 432.

[0244] According to an embodiment of the present disclosure, a non-tabbed display page having the same patient monitoring configuration as the tabbed display page 117 can be implemented to replace the tabbed display page 117. In this embodiment, the provided non-tabbed display page has the patient monitoring configuration, essentially having the same data output fields and functions as the tabbed display page 117, except that it does not have tabs and is displayed continuously in its own segment 108. In such an embodiment, this non-tabbed patient monitoring display page provides a continuous patient monitoring display page in addition to the non-tabbed display page 115, such that the central monitoring portion 106 is provided with two non-tabbed display pages, each within its own segment 108, with the remaining segments 108 of the central monitoring portion 106 each being provided with one or more tabbed display pages. According to another embodiment of the present disclosure, one segment 108 of the central monitoring portion 106 is provided with a single non-tabbed display page, i.e. a non-tabbed patient monitoring display page, and the remaining segments 108 of the central monitoring portion 106 are populated with one or more tabbed display pages (preferably one to four tabbed display pages per segment).

[0245] Non-limiting illustrative tabbed display page configurations for additional sensors

[0246] The tabbed display page 116 of segment 108d, as well as the tabbed display page 122 of segment 108c, constitute a sensor page through which various additional sensors desired by the user are connected to the graphical user interface 100, and thus monitored by the user. Accordingly, in such an additional sensor page of segments 108c and 108d, any additional pressure sensor module, bubble detection sensor module, level sensor module, temperature sensor module, flow sensor module, pressure delta sensor module, etc. can be configured in any order. The examples shown in Figures 3a and 3b are merely exemplary, and should not be construed as limiting examples and / or preferred examples.

[0247] Non-limiting illustrative tabbed display page configurations for remotely controlling heater / cooler units

[0248] A tabbed display page 118, such as can be located in segment 108c or segment 108d, constitutes a heater / cooler remote control user interface, such as can be used to remotely control the heating-cooling of a patient using the heater-cooler unit 85 during a cardiopulmonary bypass surgery and / or to remotely control the heating-cooling during a cardioplegia. As shown in Fig. 25a, the tabbed display page 118 includes a screen selection module 440 for selecting the configuration of the screen 441 of the tabbed display page 118. The screen selection module 440 includes a home button 442, a screen settings button 444, a heater-cooler unit function button 446 and a heater-cooler unit alarm button 448, all of which are touch or press activated. Activation of the home button 442 causes the display of the screen configuration according to Fig. 25a. Activation of the screen settings button 444 causes the display of the screen configuration according to Fig. 25b, which is used to set temperature parameters, such as temperature set points for the patient's body and the cardioplegia fluid and temperature gradients used in the warming and / or cooling. Activation of the heater-cooler unit function button 446 causes the display of the screen configuration according to Fig. 25c, which is used to manage the operation of the compressor of the heater-cooler unit 85 and to initiate the venting of the patient and / or cardioplegia fluid heating-cooling circuit and to initiate the evacuation of the patient and / or cardioplegia fluid heating-cooling catheter. Activation of the heater-cooler unit alarm button 448 causes the display of the screen configuration according to Fig. 25d, which is used to view messages related to any alarm status related to the heater-cooler unit 85. In Figs. 25a and 25d, the icon and / or color scheme of the heater-cooler unit alarm button 444 can switch from a normal state (i.e., no alarm) to a high priority alarm state (i.e., alarm with three exclamation marks), thereby notifying the user to activate the heater-cooler unit alarm button 444 in order to view additional information related to the alarm status.

[0249] The screen of Fig. 25a is described in more detail below. The screen according to Fig. 25a includes heater-cooler temperature modules 450, 452, 454 and 456. Each of these temperature modules includes a temperature value field 458 for displaying temperature data obtained by a temperature sensor. The temperature module 450 includes a header field 460 including the term "T Out " associated with a patient icon, which indicates that this module displays the actual output temperature of the patient circuit of the heater-cooler unit 85. The temperature module 452 includes a header field 462 including the term "T Out " associated with a heart icon, which indicates that this module displays the actual output temperature of the cardioplegia fluid circuit of the heater-cooler unit 85. The temperature module 454 includes the term "T SetButton 464, associated with a patient icon, indicates that the button 464 is activated by touching or pressing a menu screen used to set the set temperature of the patient circuit of the heater-cooler unit 85. Temperature module 456 includes a "T" button. Set Button 466, which is associated with a heart icon, indicates that after being touched or pressed, a menu screen is activated for setting the set temperature of the cardiac arrest fluid circuit of the heater-cooler unit 85.

[0250] The screen in Figure 25a also includes a patient circuit module 470 and a cardiac pacing fluid circuit module. The patient circuit module 470 includes a patient circuit control button 474 for selecting from multiple patient circuit control states. The patient circuit module 470 further includes a patient warming button 478 and a patient cooling button 480. When activated by touch or press, the patient warming button 478 causes a screen to be displayed for confirming or canceling the patient warming temperature setpoint and the patient warming temperature gradient. When activated by touch or press, the patient cooling button 480 causes a screen to be displayed for confirming or canceling the patient cooling temperature setpoint and the patient cooling temperature gradient.

[0251] The pacing fluid circuit module 472 includes a pacing fluid circuit control button 476 for selecting from multiple pacing fluid circuit control states. The pacing fluid circuit module 472 also includes a pacing fluid warming button 482 and a pacing fluid cooling button 484. When activated by touch or press, the pacing fluid warming button 482 causes a screen to be displayed for confirming or canceling the pacing fluid warming temperature setpoint and pacing fluid warming temperature gradient. When activated by touch or press, the pacing fluid cooling button 484 causes a screen to be displayed for confirming or canceling the pacing fluid cooling temperature setpoint and pacing fluid cooling temperature gradient.

[0252] Non-restrictive descriptive tabbed display page configuration for general-purpose calculators

[0253] like Figure 26 As shown, tabbed display page 120 is configured as a general-purpose calculator with standard arithmetic functions such as addition, subtraction, multiplication, division, and inverse functions. The general-purpose calculator also provides several unit conversion functions, such as pounds to kilograms, kilograms to pounds, inches to centimeters, and centimeters to inches.

[0254] Non-restrictive illustrative tabbed display page configuration for pulsatile blood flow control

[0255] Tabbed display of page 123 Figure 27As shown in FIG. 12, a pulsatile control user interface is involved, such as when arterial pump 38 is operating in circuit 3, for controlling the pulsatile characteristics of the blood flowing through extracorporeal blood flow circuit 3 in accordance with embodiments of the present disclosure. Such pulsatile control advantageously provides a more physiological pulsatile blood flow in extracorporeal blood flow circuit 3, and thus can yield perfusion advantages not achievable with non-pulsatile blood flow.

[0256] Tabbed display page 123 includes a pulsatile control module 490, a maximum flow module 491, a start time module 492, a stop time module 494, a pulse rate and frequency module 496, and a base flow module 498. Pulsatile control module 490 includes a fixed header field 500, a pulsatile delivery settings menu button 502, and a pulsatile control button 504. Activation of pulsatile delivery settings menu button 502 by touch or press causes a pulsatile delivery settings menu screen to become visible, which constitutes a graphical user interface screen for inputting control parameters displayed in other modules 491, 492, 494, 496, and 498 of tabbed display page 123. Activation of pulsatile control button 504 by successive touch or press for at least two seconds causes arterial pump 38 to be operatively connected to tabbed display page 123, and thus to operate in a pulsatile flow mode having characteristics defined as follows.

[0257] Maximum flow module 491 includes a fixed maximum flow header field 506, a fixed units field 508, and a maximum flow value field 510. Maximum flow value field 510 displays the maximum flow value that can be reached by the pulsatile flow when using the pulsatile delivery settings menu settings.

[0258] Start time module 492 includes a fixed start time header field 512 and a start time value field 514, which displays the time taken for the pump pressure to reach its maximum value during a pump cycle as a percentage of the cardiac cycle. Stop time module 494 includes a fixed stop time header field 516 and a stop time value field 518, which displays the time taken for the pump pressure to reach its baseline minimum value during a pump cycle as a percentage of the cardiac cycle.

[0259] Pulse rate and frequency module 496 includes a fixed header field 520 for pulse rate and pulsatile frequency, a fixed units field 522, and a pulse rate and pulse value field 524, which displays the pulse rate of pump 38 in beats per minute (bpm) and the ratio of pump cycles to cardiac cycles. In this case, the displayed 1:1 ratio means that there is one pump cycle per cardiac cycle.

[0260] The base flow module 498 includes a fixed base flow header field 526 and a base flow value field 528 that displays the base flow as a percentage of the target flow of the arterial pump 38. The target flow of the arterial pump 38 is displayed elsewhere as part of another portion 24 of the user interface system 20.

[0261] Non-limiting illustrative tabbed display page configurations for a clinical parameter monitor-simulator

[0262] According to embodiments of the present disclosure, the graphical user interface 100 can include a clinical parameter monitor-simulator user interface 598. The clinical parameter monitor-simulator user interface 598 is formed by the simultaneous display of a combination of the tabbed display pages 117, 600 and 602, which occurs when the activation tabs 117a, 600a and 602a are simultaneously touched or pressed by the user, so that the tabbed display pages 117, 600 and 602 together are in a display mode, as shown in Figure 28 In other words, as shown in Figure 28 When the tabbed display pages 117, 600 and 602 are simultaneously displayed in the three different segments 108 (e.g., segments 108b, 108c and 108d, respectively), the three tabbed display pages can operate together to form a unified clinical parameter monitor-simulator graphical interface, as shown in

[0263] The tabbed display page 117 is described above as displaying a patient monitor configuration when the touch or press sensitive monitor button 412 has been activated (see Figure 24 ). The tabbed display page 600 constitutes a simulator page, and the tabbed display page 602 constitutes a simulator keyboard page, which together provide a graphical user interface for entering and manipulating clinical data of a clinical simulator in order to test a plurality of hypothetical clinical scenarios in real-time, in situ, according to actual clinical data of a patient. Thus, for example, the unified clinical parameter monitor-simulator graphical interface can be operable to provide timely guidance to a clinician regarding the management of a patient during a cardiopulmonary bypass surgery.

[0264] As shown in Figure 29As shown, the tabbed display page 602 includes a touch or press sensitive tab 602a. Activation of the tab 602a by touch or press causes the tabbed display page 602 to be displayed in display mode, and then the remaining tabbed display pages of the corresponding section to be displayed in overlay mode. The tabbed display page 602 includes a quick button 610, a repeat button 612, a calculate button 614, an all clear button 616, and a keypad 618, all of which are touch or press activated on the touch screen 17. The quick button is operable by touch or press to effect transfer of monitored patient data displayed by the patient monitor of the tabbed display page 117 to the data field array of the simulator screen of the tabbed display page 600. The repeat button is operable by touch or press to effect repeated transfer of monitored patient data into a second or third data field array of the simulator screen. The calculate button is operable by touch or press to effect one or more calculations based on patient data in one, two, or three data field arrays of the tabbed display page 600. The all clear button is operable by touch or press, preferably requiring a two second hold, to clear all monitored patient data displayed in the data field array of the simulator screen, and to clear all calculated clinical parameters contained in the calculation field array of the simulator screen.

[0265] The keypad 618 includes a plurality of number and punctuation keys 620, such as are known for keypads, and an up arrow key 622, a down arrow key 624, a backspace key 626, a clear key 628, and an enter key 630. The various keys are used to manipulate data in one or more data field arrays of the simulator screen of the tabbed display page 600. The up arrow key 622 and the down arrow key 624 are used to move the cursor array up and down in the data fields. The backspace key 626 is used to delete one number at a time in the data fields. The clear key 628 is used to clear all data in a single data field. The enter key 630 can be used to move the cursor from one data field array to another.

[0266] FIG. 30a shows a tabbed display page 600 that includes a touch or press activated tab 600a that, when activated by touch or press, causes the tabbed display page 600 to be displayed in its quadrant. The tabbed display page 600 constitutes a simulation screen that includes three clinical data field arrays 640, 642, 644 and corresponding three calculated data field arrays 650, 652, 654, respectively, that are labeled as scenario numbers 1, 2, and 3, respectively. Each of the clinical data field arrays includes a plurality of data entry fields that are data fields into which clinical data values are entered and selectively manipulated using the keypad 618 of the tabbed display page 602. The data entry fields, such as those forming the data field arrays 640, 642, 644 can include IV fluid data entry fields 646 into which IV fluid volume data is entered, pRBC data entry fields 648 into which volume of pRBC transfused is entered, expCO2 data entry fields 670 into which patient exhaled carbon dioxide data is entered, flow data entry fields 672 into which blood flow data from a pump and / or extracorporeal blood flow circuit is entered, SaO2 data entry fields 674 into which patient arterial blood oxygen saturation data is entered, PaO2 data entry fields 676 into which patient arterial oxygen tension data is entered, SvO2 data entry fields 678 into which patient venous oxygen saturation data is entered, and PvO2 data entry fields 680 into which patient venous oxygen tension data is entered.

[0267] By pressing the quick button 610 of the tabbed display page 602, the tabbed display page 117 Figure 24) and / or the patient clinical data values displayed in the corresponding data fields in the tabbed display pages 114 (Fig. 23b) are used to instantaneously automatically populate the data entry fields of the first clinical data field array 640. This is the case as shown in Fig. 30a which shows the first clinical data field array 640 populated with patient clinical data values which have been automatically populated when the quick button 610 was activated at time to. If the user presses the quick button 610 again at some later time tl, then the second clinical data field array 642 will be automatically populated at the later time tl with the patient clinical values from the corresponding data fields in the tabbed display pages 114, 117. If the user subsequently presses the quick button again at some later time t2, then the third clinical data field array 644 will be automatically populated at the corresponding later time t2 with the patient clinical values from the corresponding data fields in the tabbed display pages 114, 117. For example, once the three clinical data field arrays 640, 642, 644 are populated with data, the activation of the quick button 610 will not have an effect until the data in the clinical data field arrays 640, 642, 644 has been cleared by activating the clear all button 616. In one embodiment of the present disclosure, touching or pressing activation in the clear all button 616 stores the data from the clinical data field arrays 640, 642, and 644 in a memory device associated with the processor 30 while clearing the clinical data field arrays 640, 642, 644. According to embodiments of the present disclosure, the memory device is a hardware device.

[0268] Each of the calculated data field arrays 650, 652, 644 includes a plurality of data display fields which are data fields that display calculated clinical data values using known formulas such as those disclosed in U.S. Provisional Patent Application No. 62 / 160,689 filed May 13, 2015 and / or U.S. Patent Application Publication No. US 2006 / 0257283 Al, the entireties of which are incorporated herein by reference. Data display fields such as those forming the calculated data field arrays 650, 652, 644 can include a calculated hemoglobin data display field 655 which displays a calculated hemoglobin value, an index delivered oxygen (DO2I) data display field 656 which displays a calculated index delivered oxygen value, an index consumed oxygen (VO2I) data display field 658 which displays a calculated index consumed oxygen value, a calculated ratio of index delivered oxygen to index consumed oxygen (DO2I / VO2I) data display field 660 which displays a calculated ratio of index delivered oxygen to index consumed oxygen, and a calculated ratio of index delivered oxygen to index produced carbon dioxide (DO2I / VCO2I) data display field 662 which displays a calculated ratio of index delivered oxygen to index produced carbon dioxide.

[0269] When the respective data field array 640 has been completely filled with data and subsequently the compute button 614 of the tabbed display page 602 is activated by touch or press, the processor 30 computes the computed data values that will fill the data display fields of the computed data field array, e.g. the computed data field array 650. The same operations described above for the pair of clinical and computed data field arrays 640 and 650, respectively, apply to the pair of clinical and computed data field arrays 642 and 652 and the pair of clinical and computed data field arrays 644 and 654, respectively.

[0270] Fig. 30b shows the effect of the repeat button 612 of the tabbed display page 602. By activating the repeat button 612 by touch or press, the data in the data input fields of the clinical data field array to the left is automatically filled into the data input fields of the clinical data field array to the right. Thus, when the clinical data field array 640 is filled with data as shown in Fig. 30a, the activation of the repeat button 612 causes the clinical data field array 642 to be filled with the same data as the clinical data field array 640 shown in Fig. 30b. If the repeat button 612 is activated again, the empty clinical data field array 644 will be automatically filled with the same data that filled the clinical data field array 642. The purpose of the repeat button 612 is to facilitate copying the same data to more than one clinical data field array for subsequent processing before computing the computed data values based on the hypothetical clinical intervention to compute hypothetical data values so that different scenario simulations can be compared.

[0271] The activation of the repeat button 612 does not work when the clinical data field arrays 640 and 642 are empty. The activation of the repeat button 612 also does not work when the three clinical data field arrays are filled with data.

[0272] It should be understood that when the clinical data field arrays 640, 642, 644 are empty, three consecutive activations of the quick button 610 can cause the clinical data field arrays 640, 642, 644 to be filled with different information because each snapshot occurs at a different time to, ti, t2and since most of the captured data is constantly monitored, it is constantly changing. On the other hand, two activations of the repeat button 612 after the activation of the quick button 610 will cause the clinical data field arrays 640, 642, 644 to be filled with the same data.

[0273] Fig. 30c illustrates a non-limiting example of how simulations can be used to facilitate patient care using the clinical parameter monitor-simulator user interface 598. In this example, the clinician can explore how inputting various amounts of pRBC (e.g., 250 cc, 500 cc, or 750 cc) can affect hemoglobin levels and other clinical parameters, such as DO2I, VO2I, DO2I / VO2I, and DO2I / VCO2I, if all other parameters remain constant. In this example, the clinician uses the keypad 618 to selectively change the previously provided auto-populated data entry by activating the quick button 610 (or first activating the quick button 610 and then activating the repeat button 612). After inputting the simulated data, the clinician activates the calculate button 614, and thus the calculated data fields array 650, 652, 654 are populated with the calculated data.

[0274] This example of changing the amount of transfused blood is merely exemplary and should not be construed as limiting, as other simulations can be performed that change other parameters, such as, for example, total IV fluids administered and / or changing carbon dioxide production (expCO2). Simulations can be performed that change only one parameter at a time while all other variables remain constant. Simulations can be performed that change multiple parameters at a time while all other variables remain constant. Simulations can also include estimates and extrapolations as to how a variable changes as a result of a hypothetical change in one or more other variables.

[0275] Fig. 30d illustrates a non-limiting example of a simulation that employs estimates or extrapolations. According to the present disclosure, an estimate constitutes a hypothetical data point that is based on another calculation or based on historical data about the patient, which can be used as a factual basis to generate estimated data for use in a simulation. On the other hand, according to the present disclosure, an extrapolation constitutes a hypothetical data point that is not based on a fact per se, but it can be based on intuition. For example, if it is believed that a patient's carbon dioxide production can increase by 10% with a 10 degree Fahrenheit increase in body temperature during rewarming, an extrapolation for a simulation can include, for example, that the patient's carbon dioxide production expCO2may go up by 10%. Thus, in this case, if a 10% increase in the patient's body temperature is planned, the patient's expCO2may enter the simulator with a 10% extrapolation above the previous baseline.

[0276] According to the simulation of FIG. 30d, the clinical data field array 640 is populated with snapshot data, i.e., the automatically populated data of the tabbed display pages 114 and 117 resulting from the activation of the quick button 610. The clinical data field array 642 is populated with data repeated from the clinical data field array 640 using the repeat button, with some of the data fields subsequently modified to include hypothetical data using the keypad 618. More specifically, the clinical data field array 640 corresponds to a patient who has received 250 cc of IV fluid and 500 cc of pRBCs up to the time of activation of the quick button 610 during a cardiopulmonary bypass procedure, and the patient has measured values of expCO2 of 32.1 mmHg, flow of 5.00 l / min, SaO2 of 99%, PaO2 of 250 mmHg, SvO2 of 73%, and PvO2 of 36 mmHg. According to the simulation, hypothetical data was added to the simulation for pRBCs, SVO2 and PvO2 based on the assumption that the input of blood would increase the patient's SvO2 and PvO2, with the data reflecting an estimated or presumed value of SvO2 and PvO2 of 81 and 40, respectively, for an additional 250 cc of pRBC transfusion given to the patient. Activation of the calculate button 614 then caused the calculation data to populate the calculation data fields 650 and 652, which provided the clinician with an idea of how the planned intervention could affect the patient's clinical status based on known, calculable clinical parameters such as hemoglobin, index oxygen delivery (DO2I), oxygen consumption index (VO2I), and various ratios known or believed to be associated with clinical outcomes. For example, according to M. Rannuci et al., Anaerobic Metabolism During Cardiopulmonary Bypass: Predictive Value of Carbon Dioxide Derived Parameters, 81 ANNALS THORACIC SURGERY 2189-2195 (2006), a DO2I / VCO2I ratio of 5 or greater is associated with improved clinical outcomes.

[0277] According to embodiments of the present disclosure, the graphical user interface 100 can include a clinical parameter monitor-simulator user interface 698 formed by the concurrent display of a combination of tabbed display pages 700 and 702, which occurs when the user touches or presses the tabs 700a and 702a concurrently, such that the tabbed display pages 700 and 702 are together in a display mode, as shown in FIG. 30e. Figure 31 In other words, as shown in FIG. 30f, the user can touch or press the tabs 700a and 702a concurrently to cause the display of the combination of tabbed display pages 700 and 702, and then touch or press the tabs 700a and 702a individually to cause the display of the individual tabbed display pages 700 and 702, respectively. Figure 31As shown, when tabbed display pages 700 and 702 are simultaneously displayed in two different segments 108 (e.g., segments 108c and 108d), respectively, the two tabbed display pages can operate together to form a unified clinical parameter monitor-simulator graphical interface 698. In accordance with the present disclosure, such a subject user interface formed from two operatively connected tabbed display pages can be characterized as a dual set pair tabbed display page. In accordance with embodiments of the present disclosure, a clinical parameter monitor-simulator user interface can be formed from a single tabbed display page (i.e., a single tabbed display page) that incorporates both a patient monitor and a simulator.

[0278] Tabbed display page 700 constitutes a patient monitor page and is similar to tabbed display page 117; however, tabbed display page 700 is activatable in a display mode only by touching or pressing the active tab 700a. Tabbed display page 702 constitutes a simulator screen 704 and a simulator keypad 706 that provide a graphical user interface for entering and manipulating clinical data for a clinical simulator to test a plurality of hypothetical clinical scenarios in real-time and in situ based on actual clinical data of a patient in order to provide timely guidance to a clinician regarding management of the patient, for example, during a cardiopulmonary bypass surgery.

[0279] Tabbed display page 702 includes a quick button, a repeat button, a calculate button, an all clear button, and a keypad 706, all of which are touch or press activated on touchscreen 17. The quick button is operable by touch or press to effect transfer of monitored patient data displayed by the patient monitor of tabbed display page 700 to the data field arrays of simulator screen 704 of tabbed display page 702. The repeat button is operable by touch or press to effect repeated transfer of monitored patient data into a second or third data field array of simulator screen 704. The calculate button is operable by touch or press to effect one or more calculations based on patient data in one, two, or three data field arrays of tabbed display page 702. The all clear button (CLR ALL) is operable by touch or press (preferably requiring a two second hold) to effect clearing of all monitored patient data displayed by the data field arrays of the simulator screen and clearing of all calculated clinical parameters contained in the calculation field arrays of the simulator screen. The operation of simulator screen 704 and keypad 706 is substantially the same as the operation of tabbed display pages 600 and 602. The all clear button of tabbed display page 702 can effect a save operation in which the data in the data field arrays is saved to a memory device associated with processor 30 while the data field arrays are cleared of data.

[0280] The dual clinical parameter monitor-simulator user interface 698 has the advantage over the triple clinical parameter monitor-simulator user interface 598 that the dual user interface 698 takes up less space than the triple user interface 598. The triple user interface 598 has the advantage over the dual user interface 698 that the triple user interface 598 can be used to monitor and simulate more clinical parameters than the dual user interface 698 because it has more space for monitoring and simulation.

[0281] Non-limiting illustrative tabbed display page configurations for interfaces with blood monitoring units

[0282] According to embodiments of the present disclosure, as shown in Figure 32 The graphical user interface 100 can include a blood monitoring user interface 710, which is a tabbed display page for interfacing with a blood monitoring unit 800, such as a blood monitoring unit BMU 40 (MAQUET), which can be operably connected to the processor 30 of the heart-lung bypass machine 1. The blood monitoring unit (BMU) 800 is an online monitoring device for continuously measuring vital blood parameters during extracorporeal blood circulation and can contain sensors to monitor partial pressure of oxygen and temperature on the arterial side of the extracorporeal blood flow circuit 3, as well as oxygen saturation, hemoglobin, hematocrit, and temperature on the venous side of the extracorporeal blood flow circuit.

[0283] The blood monitoring unit interface 710 includes a tabbed display page 712 with a tab 712a, such as can be disposed in any one of the blocks 108 of the graphical user interface 100 for tabbed display pages. Figure 32 A non-limiting embodiment of the blood monitoring unit interface 710 is shown, which can include a venous oxygen saturation sensor module 714, a venous temperature module 716, a hemoglobin sensor module 718, a hematocrit sensor module 720, and a snapshot mechanism 722.

[0284] The venous blood oxygen saturation sensor module 714 includes a fixed alpha-numeric title field 724 and a venous blood oxygen saturation value field 726 that displays a measured value of venous blood oxygen saturation. The venous oxygen saturation value field 726 is associated with an appropriate units field (%) 728. The venous oxygen saturation sensor module 714 also includes a module settings menu button 124.

[0285] The venous temperature sensor module 716 includes a fixed alpha-numeric title field 730 and a venous temperature value field 732 that displays a measured value of venous temperature. The venous temperature value field 732 is associated with an appropriate units field (°C) 734. The venous temperature sensor module 716 also includes a module settings menu button 124.

[0286] The hemoglobin sensor module 718 includes a fixed alphanumeric heading field 736 and a hemoglobin value field 738 that displays the measured value of the blood hemoglobin. The hemoglobin value field 738 is associated with an appropriate units field (g / dl) 740. The hemoglobin sensor module 718 also includes the module settings menu button 124.

[0287] The hematocrit sensor module 720 includes a fixed alphanumeric heading field 742 and a hematocrit value field 744 that displays the measured value of the blood hematocrit. The hematocrit value field 744 is associated with an appropriate units field (%) 746. The hematocrit sensor module 720 also includes the module settings menu button 124.

[0288] The snapshot mechanism 722 constitutes a touch or press-activated button on the touchscreen that, when activated by being touched or pressed, saves venous oxygen saturation (Sv02), venous temperature (Tven), hemoglobin (Hb), and hematocrit (Hct) into a storage device (i.e., a hardware storage device) operatively associated with the processor 30 for storage and subsequent retrieval. The associated storage device can be operatively connected with the processor 30 as an external device or as a component of the processor 30.

[0289] Footer portion of the graphical user interface

[0290] The footer portion 104 displays alphanumeric error messages primarily in a display area 750 that is provided with scroll features. The footer portion 104 is provided with an up scroll button 752 and a down scroll button, both of which are touch or press-activated. Activating the up scroll button 752 causes the display field 750 to scroll up through the display field, and activating the down scroll button 754 causes the display field 750 to scroll down through the display field. The error messages displayed by the display field 750 include messages regarding faults, error connections, disconnections, and alarm states. The footer portion 104 can also be provided with a variable alarm message icon 756 and a help screen available button 758. The alarm message icon 756 is configured to change to different colors corresponding to various high-priority alarm states, medium-priority alarm states, and low-priority alarm states, and to display indicia and flash, as described above.

[0291] For example, when a high priority alarm is present, the alarm message icon 756 can display red and flash at a rate indicative of a high priority alarm status while displaying a triangle with three exclamation marks. On the other hand, when a medium priority alarm is present, the alarm message icon 756 can display yellow and flash at a rate indicative of a medium priority alarm status while displaying a triangle with two exclamation marks. When a low priority alarm is present, the alarm message icon 756 can display cyan without flashing and display a triangle with one exclamation mark. If more than one alarm is triggered at the same time, the alarm message icon 756 will transition to the state indicative of the highest level alarm currently active.

[0292] The help screen available button 758 is a touch or press activated button that becomes available on the touchscreen 17 whenever one or more alarms have been triggered. Thus, according to embodiments of the present disclosure, the help screen available button 758 is only available (i.e. only displayed) when there is an active alarm. Activating the help screen available button 758 causes the footer section 104 to display a single alarm help screen as shown in Figure 41a when only a single alarm has been activated, or a multiple alarm help screen as shown in Figure 41b when multiple alarms have been triggered. The single alarm help screen of Figure 41a and the multiple alarm help screen of Figure 41b are merely exemplary and should not be construed as limiting.

[0293] Mechanism for establishing a graphical user interface system

[0294] The header 102 of the graphical user interface 100 includes a system settings menu button 214 for activating a system configuration menu interface 802 as shown in Figure 34a. The system configuration menu interface 802 can have a nested structure that is different from those portions of the graphical user interface 100 that do not involve the establishment mechanism and are not nested structures. In other words, according to embodiments of the present disclosure, the system and module configuration menu interfaces can have a nested structure because they are related to the establishment mechanism, while the clinical operation portions of the graphical user interface have a tab selectable page structure that is not nested structures at all.

[0295] The system settings menu button 214 is touch or press activated. Touch or press activating the system settings menu button 214 causes the system configuration menu interface 802 to be displayed by the graphical user interface 100. The system configuration menu interface 802 includes a load configuration button 804, an alarm history button 806, a general settings button 808, a system information button 810, an external devices button 812, a service mode button 814, and a close menu button 816. Each of the buttons 804, 806, 808, 810, 812, 814, and 816 is touch or press activatable.

[0296] Activation of the load configuration button 804 by touch or press causes a menu 820 of selectable predefined graphical user interface configurations to be displayed in the display field 818 of the system configuration menu interface 802, as shown in Figure 34b. The user can then select one of the predefined graphical user interface configurations for display by the graphical user interface 100.

[0297] Activation of the alarm history button 806 by touch or press causes a log 822 of alarm messages to be displayed in the display field 818 of the system configuration menu interface 802, as shown in Figure 34c. The log 820 of alarm messages includes the time and date of each message, and the alarm messages can be color coded according to their priority level, such as red for high priority alarm messages, yellow for medium priority alarm messages, cyan for low priority messages, and white for messages that have not been assigned a priority.

[0298] Activation of the general settings button 808 by touch or press causes a menu 824 of selectable settings buttons to be displayed in the display field 818 of the system configuration menu interface 802, as shown in Figure 34d. The menu 824 of selectable settings buttons can include settings buttons for display brightness 826, alarm volume 828, data and time settings 830, screen lock settings 832, and timer format settings 834. Each of these settings buttons is touch or press activated to display selectable settings corresponding to the selected category.

[0299] Activation of the system information button 810 by touch or press causes various system information 836 to be displayed in the display field 818 of the system configuration menu interface 802, as shown in Figure 34e. The system information 836 displayed in the display field 818 can include information such as system total time data, system software revision data, last system maintenance date data, next system maintenance due data, battery test due date data, and battery replacement date data.

[0300] Activation of the external devices button 812 by touch or press causes an external devices menu 838 to be displayed in the display field 818 of the system configuration menu interface 802, as shown in Figure 34f. The external devices menu 838 is used to enable or disable communication between the graphical user interface 100 and external devices, such as the heater-cooler unit 85 or the blood monitoring unit 800.

[0301] Activation of the service mode button 814 by touch or press causes instructions 840 to be displayed in the display area 818 of the system configuration menu interface 802 detailing how to exit the clinical mode of operation to enter the service mode of operation and vice versa. Activation of the service mode button 814 also causes the enter service mode button 842 to become available. The enter service mode button 842 is a touch or press activated button that must be pressed for at least two seconds before the processor 30 enters the service mode. The service mode is the mode of operation used by service technicians to perform diagnostics and / or provide programming updates and / or revisions to the processor 30.

[0302] Module settings mechanism for the graphical user interface

[0303] The various sensor modules and non-sensor modules described above can be equipped with a module settings menu button 124 which is a touch screen touch or press activated button. Activation of the module settings menu button 124 of a sensor module or non-sensor module will cause the settings menu interface for that module to be displayed. The various settings menu interfaces are described below.

[0304] Pressure sensor module configuration menu interface

[0305] Figure 35a illustrates a settings menu interface for the pressure sensor module 152. Activation of the module settings menu button 124 by touch or press of the pressure sensor module 152 causes the pressure sensor module configuration menu interface 902 to be displayed by the graphical user interface. The pressure sensor module configuration menu interface 902 can include an alpha-numeric title field 903 that matches the title field 154 of the associated pressure sensor module 152. The pressure sensor configuration menu interface 902 includes a keypad 904 for entering values into the various settings fields 906, 908 of the menu 902. The pressure sensor configuration menu interface 902 includes a pressure stop limit field 906, a pressure adjustment limit field 908, an alarm limit button 910, a zero pressure button 912, a calibration pressure button 914, a sensor on button 916, a sensor off button 918, a pump association button 920, a settings cancel button 922 and a settings activate button 924. Each of the buttons 910, 912, 914, 916, 918, 920, 922 and 924 are activated by touch or press. The pressure sensor configuration menu interface 902 can optionally be provided with a pressure display area 926 which can display the actual pressure measured by the pressure sensor 50 connected to the pressure sensor module 152.

[0306] The pressure sensor module configuration menu interface 902 of Figure 35a is configured to display pressure in mmHg. However, the pressure sensor module configuration menu interface can also be configured to display pressure in KPa.

[0307] The pressure stop limit field 906 and the pressure regulation limit field 908 are used to set the pressure stop limit value and the pressure threshold limit value, respectively, used by the pressure sensor module 152 to activate the various pressure priority alert states as described above. An alert limit button 910 is provided to enable and disable the setting of the pressure alert limit value. The pressure stop limit field 906, the pressure regulation limit field 908, and the alert limit button 910 are associated with the audio buttons 928, 930, 932, respectively. The audio buttons 928, 930, and 932 are touch or press activated buttons that are activated by touching or pressing for at least two seconds. These buttons 928, 930, 932 are used to disable and enable the audio alert associated with the respective threshold value. As shown in FIG. 35, the buttons 928 and 930 are displayed by the pressure sensor module configuration menu interface 902 as darker and grayer than the button 932, which indicates that the audio alert associated with the buttons 928 and 930 is disabled, while the audio alert associated with the button 932 is enabled.

[0308] The zero pressure button 912 is a touch or press activated button that zeros the pressure channel when activated by pressing and holding for at least two seconds. The calibration pressure button 914 is a touch or press activated single action button that, when activated, causes the pressure calibration menu interface 936 to be displayed as a pop-up window overlaying a portion of the pressure sensor module configuration menu interface 902, as shown in FIG. 35b. The pressure calibration menu interface 936 allows the user to calibrate the connected pressure sensor after the pressure channel has been zeroed using the zero pressure button 912. The pressure calibration menu interface 936 can be equipped with a keypad 937 for entering a target calibration pressure value into a target calibration pressure data field. The pressure calibration menu interface 936 can include a pressure display field 940, which can display the actual pressure measured by the pressure sensor 50 connected to the pressure sensor module 152. The pressure calibration menu interface 936 includes a settings cancel button 941 and a settings activate button 942, which are two touch or pressure activated single action buttons. Activating the settings cancel button 941 closes the pressure calibration menu interface 936 without accepting any new changes to the target calibration pressure. Activating the settings activate button 942 closes the pressure calibration menu interface 936 while accepting and enabling any new changes to the target calibration pressure made using the pressure calibration menu interface 902.

[0309] The sensor on button 916 and the sensor off button 918 are two touch or press activated single action buttons. Activation of the sensor on button 916 enables the connected pressure sensor 50, and activation of the sensor off button 918 disables the connected pressure sensor 50.

[0310] The pump association button 920 is a single action button that is touch or press activated that, when activated, causes the pressure sensor pump association menu interface 944 to be displayed as a pop-up window overlaying a portion of the pressure sensor module configuration menu interface 902. The pressure sensor pump association menu interface 944 allows the user to select a pump of the cardiopulmonary bypass system 1 and connect it to the pressure sensor module 152 so that activation of the intervention button 158 by the user will affect the operation of the connected pump (i.e., the associated pump). Thus, the pressure sensor pump association menu interface 944 includes a plurality of available single action pump buttons 945, 946, 947, 948, 949 corresponding to pumps that can be associated with the pressure sensor module 152. For example, the pressure sensor pump association menu interface 944 can include single action pump buttons that are not available, which are related to those pumps that cannot be associated with the pressure sensor module 152, such as an air removal pump (“ARP”). The pressure sensor pump association menu interface 944 can be provided with a “none” button that can be selected when no pump is associated with the pressure sensor module 152. When a pump has been selected by activating the corresponding pump button, then the pump button displays a check icon, such as shown for the pump button 945 in the non-limiting example of FIG. 35c, where an arterial blood pump has been associated with the pressure sensor module 152.

[0311] The pressure sensor pump association menu interface 944 includes a settings cancel button 950 and a settings activate button 951, which are two single action buttons that are touch or press activated. Activating the settings cancel button 950 closes the pressure sensor pump association menu interface 944 without accepting any new changes to the pump associated with the pressure sensor module 152. Activating the settings activate button 951 closes the pressure sensor pump association menu interface 944 while accepting and making available any new changes to the pump associated with the pressure sensor module 152 made using the pressure sensor pump association menu interface 944.

[0312] The settings cancel button 922 and the settings activate button 924 of the pressure sensor module configuration menu interface 902 are two single action buttons that are touch or press activated. Activating the settings cancel button 922 closes the pressure sensor module configuration menu interface 902 without accepting any new changes to the pressure sensor module configuration. Activating the settings activate button 924 closes the pressure sensor module configuration menu interface 902 while accepting and making available any new changes to the pressure sensor module configuration made using the pressure sensor module configuration menu interface 902.

[0313] Bubble detection sensor module configuration menu interface

[0314] FIG. 36a illustrates a settings menu interface for a bubble detection sensor module 162. The module settings menu button 124 is activated by touching or pressing the bubble detection sensor module 162, causing the bubble detection sensor module configuration menu interface 952 to be displayed by the graphical user interface 100. The bubble detection sensor module configuration menu interface 952 can include an alpha-numeric title field 953 that matches the alpha-numeric title field 164 of the associated bubble detection sensor module 162, and it can include an alpha-numeric bubble detection sensor type field 954 that indicates the particular type of bubble detection sensor that is being used and connected to the bubble detection sensor module 162. The bubble detection sensor module configuration menu interface 952 includes a bubble sensitivity detection array 956 provided with a plurality of bubble detection level buttons 957, 958, 959, 960, and a microbubble audio alarm button 962, a sensor on button 964, a sensor off button 966, a pump association button 968, a settings cancel button 970, and a settings activate button 972. Each of the buttons 957, 958, 959, 960, 962, 964, 966, 968, 970, and 972 can be activated by touching or pressing.

[0315] The bubble sensitivity detection array 956 allows the user to set the alarm sensitivity of the bubble detection of the associated bubble detection sensor module 162 by activating one of the bubble detection level buttons 957, 958, 959, 960. Each of the bubble detection level buttons 957, 958, 959, 960 is a single action button that is activated by touching or pressing, which sets the bubble detection size alarm threshold that is used by the bubble detection sensor module 162 to activate the various bubble detection priority alarm states described above. The bubble sensitivity detection array 956 sets the alarm state, but it does not change the bubble size that is detected by the associated bubble detection sensor 60. The bubble detection level button 957 corresponds to the detection alarm threshold for the smallest size bubble (i.e., the highest bubble detection sensitivity), the bubble detection level button 960 corresponds to the detection alarm threshold for the largest size bubble (i.e., the lowest bubble detection sensitivity), and the bubble detection level buttons 958 and 959 set alarm thresholds between the alarm thresholds that can be set using the bubble detection level buttons 957 and 960.

[0316] A microbubble audio alert button 962 is provided to enable and disable the setting of the microbubble audio alert. The microbubble audio alert button 962 is activated by touching or pressing such that the state of the audio alert toggles between the enabled state and the disabled state. For example, if the microbubble audio alert is engaged, activating the microbubble audio alert button 962 disengages the audio alert and this disengaged state is indicated by the disengaged icon (i.e., a red "X" over the active speaker icon). If the microbubble audio alert is disengaged, activating the microbubble audio alert button 962 engages the audio alert and this engaged state is indicated by the engaged icon (i.e., the active speaker icon).

[0317] The sensor on button 964 and the sensor off button 966 are two touch or press activated buttons, although the sensor on button 964 is a single action button and the sensor off button 966 must be pressed and held for at least two seconds to activate. Activation of the sensor on button 964 enables the connected bubble detection sensor 60 and activation of the sensor off button 966 disables the connected bubble detection sensor 60.

[0318] The pump association button 968 is a single action button that is touch or press activated that, when activated, causes the bubble sensor pump association menu interface 974 to be displayed as an overlay over a portion of the bubble detection sensor module configuration menu interface 952 pop-up window, as shown in FIG. 36b. The bubble sensor pump association menu interface 974 allows the user to select a pump of the heart-lung bypass system 1 and connect it to the bubble detection sensor module 162 such that activation of the intervention button 168 by the user will affect the operation of the connected pump (i.e., the associated pump).

[0319] The bubble sensor pump association menu interface 974 includes a plurality of available single action pump buttons 975, 976, 977, 978, 979 corresponding to pumps that can be associated with the bubble detection sensor module 162. The bubble sensor pump association menu interface 974 can include single action pump buttons that are not available, which relate to pumps that cannot be associated with the bubble detection sensor module 162, such as an air purge pump ("ARP"). The bubble sensor pump association menu interface 974 can be provided with a "none" button that can be selected when no pump is associated with the bubble detection sensor module 162. When a pump is selected by activating the corresponding pump button, then the pump button is displayed with a check icon, as shown for the pump button 975 in the non-limiting example of FIG. 36b.

[0320] The bubble sensor pump association menu interface 974 includes a settings cancel button 980 and a settings activate button 981, which are two touch or press activated single action buttons. Activating the settings cancel button 980 closes the bubble sensor pump association menu interface 974 without accepting any new changes to the pump associated with the bubble detection sensor module 162. Activating the settings activate button 981 closes the bubble sensor pump association menu interface 974 while accepting and making available any new changes to the pump associated with the bubble detection sensor module 162 made using the bubble sensor pump association menu interface 974.

[0321] The settings cancel button 970 and the settings activate button 972 of the bubble detection sensor module configuration menu interface 952 are two touch or press activated single action buttons. Activating the settings cancel button 970 closes the bubble detection sensor module configuration menu interface 952 without accepting any new changes to the bubble detection sensor module configuration. Activating the settings activate button 972 closes the bubble detection sensor module configuration menu interface 952 while accepting and making available any new changes to the bubble detection sensor module configuration made using the bubble detection sensor module configuration menu interface 952.

[0322] Horizontal sensor module configuration menu interface

[0323] FIG. 37a illustrates a settings menu interface for the horizontal sensor module 172. The module settings menu button 124 is activated by touching or pressing the horizontal sensor module 172, causing the horizontal sensor module configuration menu interface 992 to be displayed by the graphical user interface 100. The horizontal sensor module configuration menu interface 992 can include an alphanumeric title field 993 that matches the title field 174 of the associated horizontal sensor module 172. The horizontal sensor module configuration menu interface 992 includes a regulation interface 994 provided with a regulation on button 996 and a regulation off button 998. The regulation on button 996 and the regulation off button 998 are each touch or press activated buttons; however, the regulation on button 996 is a single action button and the regulation off button 998 must be pressed and held for at least two seconds to activate. Activation of the regulation on button 996 causes automatic horizontal regulation to be implemented by operating the associated gas removal pump 39 when a low level is detected by the horizontal sensor 70, and activation of the regulation off button 998 disables this automatic horizontal regulation mechanism.

[0324] The horizontal sensor module configuration menu interface 992 can also be equipped with a horizontal sensor activation interface 1000 including a sensor on button 1002 and a sensor off button 1004. The sensor on button 1002 and the sensor off button 1004 are both touch or press activated buttons; however, the sensor on button 1002 is a single action button and the sensor off button 1004 must be pressed and held for at least two seconds to activate. Activation of the sensor on button 1002 makes the connected reservoir liquid level sensor 70 available and activation of the sensor off button 1004 makes the connected reservoir liquid level sensor 70 unavailable.

[0325] The horizontal sensor module configuration menu interface 992 can also be provided with a pump association button 1006, which is a touch or press activated single action button that when activated causes a horizontal sensor pump association menu interface 1012 to be displayed as a pop-up window overlaying a portion of the horizontal sensor module configuration menu interface 992, as shown in FIG. 37b. The horizontal sensor pump association menu interface 1012 allows the user to select a pump of the cardiopulmonary bypass system 1 and connect it to the horizontal sensor module 172 so that activation of the intervention button 178 by the user will affect the operation of the associated pump (i.e., the associated pump), which can be a blood pump 37, 38 or a gas pump 39.

[0326] The horizontal sensor pump association menu interface 1012 includes a plurality of available single action pump buttons 1013, 1014, 1015, 1016, 1017, 1018 corresponding to pumps that can be associated with the horizontal sensor module 172. The horizontal sensor pump association menu interface 1012 can include single action pump buttons that are not available, which are those that belong to pumps that cannot be associated with the horizontal sensor module 172. The horizontal sensor pump association menu interface 1012 can be provided with a “none” button that can be selected when no pump is associated with the horizontal sensor module 172. When a pump is selected by activating the corresponding pump button, the pump button displays a check icon, as shown in the non-limiting example of the pump button 1018 in FIG. 37b, where the pump associated with the horizontal sensor module 172 is the gas pump.

[0327] The horizontal sensor pump association menu interface 1012 includes a settings cancel button 1019 and a settings activate button 1020, which are both touch or press activated single action buttons. Activation of the settings cancel button 1019 closes the horizontal sensor pump association menu interface 1012 without accepting any new changes to the pump associated with the horizontal sensor module 172. Activation of the settings activate button 1020 closes the horizontal sensor pump association menu interface 1012 while accepting and making available any new changes to the pump associated with the horizontal sensor module 172 made using the horizontal sensor pump association menu interface 1012.

[0328] The horizontal sensor module configuration menu interface 992 can also be provided with a settings cancel button 1008 and a settings activate button 1010, which are two single action buttons that are touch or press activated. Activation of the settings cancel button 1008 closes the horizontal sensor module configuration menu interface 992 without accepting any new changes to the horizontal sensor module configuration. Activation of the settings activate button 1010 closes the horizontal sensor module configuration menu interface 992 while accepting and making available any new changes to the horizontal sensor module configuration made using the horizontal sensor module configuration menu interface 992.

[0329] Temperature sensor module configuration menu interface

[0330] Figure 38 A settings menu interface for the temperature sensor module 182 is shown. The module settings menu button 124 is activated by touching or pressing the temperature sensor module 182, causing the temperature sensor module configuration menu interface 1022 to be displayed by the graphical user interface 100. The temperature sensor module configuration menu interface 1022 can include an alphanumeric title field 1023 that matches the title field 184 of the associated temperature sensor module 182.

[0331] The temperature sensor configuration menu interface 1022 includes a keypad 1024 for entering values into the various settings fields 1026, 1028 of the menu 1022. The temperature sensor configuration menu interface 1022 includes a temperature upper limit field 1026, an audio button 1025 corresponding to the upper limit, a temperature lower limit field 1028, an audio button 1030 corresponding to the lower limit, a heat-cool unit association button 1034, a temperature sensor activation interface 1036 including a sensor on button 1038 and a sensor off button 1040, and a settings cancel button 1042 and a settings activate button 1044. Each of the buttons 1025, 1030, 1034, 1038, 1040, 1042, and 1044 are activatable by touching or pressing. The temperature sensor configuration menu interface 1022 can optionally be provided with a temperature display field 1032 that can display the actual temperature measured by the temperature sensor 80 connected to the temperature sensor module 182.

[0332] Figure 38 The temperature sensor module configuration menu interface 1022 is configured to display temperatures in Celsius. However, the temperature sensor module configuration menu interface can also be configured to display temperatures in Fahrenheit.

[0333] The upper temperature limit field 1026 and the lower temperature limit field 1028 are used to set the upper temperature limit value and the lower temperature limit value, respectively, used by the temperature sensor module 182 to activate the various temperature priority alarm states as described above. An audio button 1025 is provided to enable and disable the audio alarm corresponding to the upper temperature alarm limit value, and an audio button 1030 is provided to enable and disable the audio alarm corresponding to the lower temperature alarm limit value. The audio button 1025 is a touch or press activated button that is activated to disable the corresponding audio alarm when pressed for a period of at least two seconds, while the audio button 1030 is a touch or press activated single action button. In embodiments of the present disclosure, the audio button 1025 is configured as a single action button when it is used to enable the corresponding audio alarm and requires activation for a period of at least two seconds in order to disable the audio alarm.

[0334] The heater-cooler unit association button 1034 is a touch or press activated single action button that, when activated, causes a heater-cooler unit association menu interface to be displayed as a pop-up window overlaying a portion of the temperature sensor module configuration menu interface 1022. The heater-cooler unit association menu interface allows the user to properly connect the heater-cooler unit 85 of the cardiopulmonary bypass system 1 with the temperature sensor 80 when the temperature sensor 80 is arranged to measure the heater-cooler unit patient circuit external temperature or the cardioplegia circuit external temperature, or to specify when there is no association between the temperature sensor 80 and the heater-cooler unit 85, when the association menu interface 1022 is displayed.

[0335] The sensor on button 1038 is a single action touch or press activated button, and the sensor off button 1040 is a touch or press activated button that must be pressed for at least two seconds to activate. Activation of the sensor on button 1038 causes the connected temperature sensor 80 to be enabled, and activation of the sensor off button 1040 causes the connected temperature sensor 80 to be disabled.

[0336] The settings cancel button 1042 and the settings activate button 1044 are two touch or press activated single action buttons. Activation of the settings cancel button 1042 closes the temperature sensor module configuration menu interface 1022 without accepting any new changes to the temperature sensor module configuration. Activation of the settings activate button 1044 closes the temperature sensor module configuration menu interface 1022 while accepting and enabling any new changes to the temperature sensor module configuration made using the temperature sensor module configuration menu interface 1022.

[0337] Flow sensor module configuration menu interface

[0338] FIG. 39a illustrates a settings menu interface for a flow sensor module 192. The module settings menu button 124 is activated by touching or pressing the flow sensor module 192, causing the flow sensor module configuration menu interface 1052 to be displayed by the graphical user interface 100. The flow sensor module configuration menu interface 1052 can include an alphanumeric title field 1053 that matches the title field 194 of the associated flow sensor module 192. The flow sensor configuration menu interface 1052 includes a keypad 1054 for entering values into various settings fields 1056, 1058 of the menu interface 1052. The flow sensor configuration menu interface 1052 includes a flow upper limit field 1056, an audio button 1057 corresponding to the upper limit, a flow lower limit field 1058, an audio button 1060 corresponding to the lower limit, a zero flow button 1064, a flow sensor activation interface 1068 including a sensor on button 1070 and a sensor off button 1072, a pump association button 1066, a settings cancel button 1074, and a settings activate button 1076. Each of the buttons 1057, 1060, 1064, 1066, 1070, 1072, 1074, and 1076 is activatable by touch or pressure. The flow sensor configuration menu interface 1052 can optionally be provided with a flow display area 1062 that displays the actual flow measured by the flow sensor 90 connected to the flow sensor module 192.

[0339] The flow upper limit field 1056 and the flow lower limit field 1058 are used to set the flow upper limit value and the flow lower limit value, respectively, that the flow sensor module 192 uses to activate the various flow priority alert states as described above. The audio button 1057 is provided to enable and disable the audio alert corresponding to the upper flow alert limit value, and the audio button 1060 is provided to enable and disable the audio alert corresponding to the lower flow alert limit value. The audio button 1057 is a touch or pressure button that activates to disable the corresponding audio alert when pressed for a period of at least two seconds, but the audio button 1057 can be configured as a single action button to enable the corresponding audio alert, while the lower limit disable button 1060 is a touch or press activated single action button to enable and disable its corresponding audio alert.

[0340] The zero flow button 1064 is a touch or press activated button that, when activated by pressing and holding for a period of at least two seconds, clears the flow sensor to zero. The pump association button 1066 is a touch or press activated single action button that, when activated, causes the horizontal sensor pump association menu interface 1100 to be displayed as a pop-up window overlaying a portion of the flow sensor module configuration menu interface 1052, as shown in FIG. 39b. The horizontal sensor pump association menu interface 1100 allows the user to select a centrifugal pump of the cardiopulmonary bypass system 1 and connect it to the flow sensor module 192.

[0341] The flow sensor pump association menu interface 1100 includes a plurality of single action pump buttons 1101, 1102, 1103, 1104, 1105 corresponding to the available pumps that can be associated with the flow sensor module 192. The flow sensor pump association menu interface 1100 can include single action pump buttons that are not available, which are those pumps that cannot be associated with the flow sensor module 192. The flow sensor pump association menu interface 1100 can be provided with a "none" button that can be selected when no pump is associated with the flow sensor module 192. When a pump has been selected by activating a corresponding pump button, the pump button displays a check icon, as shown in the non-limiting example of pump button 1101 in FIG. 39b, where the pump associated with the flow sensor module 192 can be a centrifugal blood pump.

[0342] The flow sensor pump association menu interface 1100 includes a settings cancel button 1106 and a settings activate button 1107, which are two single action buttons that are touch or press activated. Activation of the settings cancel button 1106 closes the flow sensor pump association menu interface 1100 without accepting any new changes to the pumps associated with the flow sensor module 192. Activation of the settings activate button 1107 closes the flow sensor pump association menu interface 1100 while accepting and making available any new changes to the pumps associated with the flow sensor module 192 made using the flow sensor pump association menu interface 1100.

[0343] The sensor on button 1070 is a single action touch or press activated button, and the sensor off button 1072 is a touch or press activated button that must be pressed for at least two seconds to activate. Activation of the sensor on button 1070 makes the associated flow sensor 90 available, and activation of the sensor off button 1072 makes the associated flow sensor 90 unavailable.

[0344] The settings cancel button 1074 and the settings activate button 1076 are two single action touch or press activated buttons of the flow sensor module configuration menu interface 1052. Activation of the settings cancel button 1074 closes the flow sensor module configuration menu interface 1052 without accepting any new changes to the flow sensor module configuration. Activation of the settings activate button 1076 closes the flow sensor module configuration menu interface 1052 while accepting and making available any new changes to the flow sensor module configuration made using the flow sensor module configuration menu interface 1052.

[0345] Pressure delta sensor module configuration menu interface

[0346] Figure 40A settings menu interface for the pressure delta sensor module 252 is shown. The module settings menu button 124 is activated by touching or pressing the pressure delta sensor module 252, causing the pressure delta sensor module configuration menu interface 1082 to be displayed by the graphical user interface 100. The pressure delta sensor module configuration menu interface 1082 can include an alphanumeric title field 1083 that matches the title field 254 of the associated pressure delta sensor module 252. The pressure delta sensor configuration menu interface 1082 includes a keypad 1084 for entering values into various settings fields 1086, 1088 of the configuration menu interface 1082. The pressure delta sensor configuration menu interface 1082 includes a pressure delta upper limit field 1086, an audio button 1087 corresponding to the upper limit, a pressure delta lower limit field 1088, an audio button 1090 corresponding to the lower limit, a settings cancel button 1094, and a settings activate button 1096. Each of the buttons 1087, 1090, 1094, and 1096 is activatable by touch or press. The pressure sensor configuration menu interface 1082 can optionally be provided with a pressure delta display field 1092 that displays the actual pressure delta derived from measured pressure values from at least two pressure sensors 50 associated with the pressure delta sensor module 252.

[0347] Figure 40 The pressure delta sensor module configuration menu interface 1082 is configured to display pressure delta values in mmHg. However, the pressure delta sensor module configuration menu interface can also be configured to display pressure delta values in KPa.

[0348] The pressure delta upper limit field 1086 and the pressure delta lower limit field 1088 are used to set the pressure delta upper limit value and the pressure delta lower limit value, respectively, for use by the pressure delta sensor module 252 to activate various pressure delta priority alert states as described above. The audio button 1087 is provided to enable and disable the audio alert corresponding to the upper pressure delta alarm limit value. For example, when the audio alert is in the enabled state, a touch or press on the audio button 1087 for at least two seconds will cause the audio alert to transition to the disabled state. When the audio alert corresponding to the upper limit is disabled, then a single action touch or press on the audio button 1087 will cause the audio alert to transition back to the enabled state.

[0349] The audio button 1090 is provided to enable and disable the audio alert corresponding to the lower pressure delta alarm limit value. The audio button 1090 is a single action button that is activatable by touch or press, so a single touch or press transitions the audio alert between the enabled state and the disabled state and the disabled state and the enabled state.

[0350] The set cancel button 1094 and the set active button 1096 are two touchably or pressably activated single action buttons. Activation of the set cancel button 1094 closes the pressure delta sensor module configuration menu interface 1082 without accepting any new changes to the pressure delta sensor module configuration. Activation of the set active button 1096 closes the pressure delta sensor module configuration menu interface 1082 while accepting and making available any new changes to the pressure delta sensor module configuration made using the pressure delta sensor module configuration menu interface 1082.

[0351] Method embodiments for user interface setup

[0352] According to the present disclosure, there is provided a method of configuring a graphical user interface of a touch screen prior to operating in a clinical mode of operation, wherein the method comprises the steps of: (a) in response to a first signal, displaying a sensor module configuration menu interface associated with a tabbed display page of the graphical user interface displayed by the touch screen; and (b) in response to a second signal, setting at least one alarm limit for a sensor module associated with the sensor module configuration menu interface associated with the tabbed display page. In this case, the clinical mode of operation of the touch screen is the mode of operation used when the graphical user interface has been configured and is operated to display and monitor data input from a plurality of sensors associated with a plurality of sensor modules. According to an embodiment of the method, the first signal is generated as a result of activation of a touchably or pressably activated module settings menu button of the sensor module of the tabbed display page. According to an embodiment of the method, the second signal is generated as a result of activation of a touchably or pressably activated button of the sensor module configuration menu interface associated with the tabbed display page. According to an embodiment of the present disclosure, the method can further comprise the step of: (c) in response to a third signal, overlaying a pump association menu interface on a portion of the sensor module configuration menu interface of the tabbed display page so as to enable selective association of a pump with the sensor module of the tabbed display page. According to an embodiment of the present disclosure, the third signal is generated as a result of activation of a touchably or pressably activated pump association button of the sensor module configuration menu interface.

[0353] According to embodiments of the present disclosure, the method can include a step (c) of displaying, in response to a third signal, a sensor module configuration menu interface on a non-tabbed display page of a portion of the graphical user interface displayed by the touch screen, and (d) setting, in response to a fourth signal, at least one alarm limit for a sensor module associated with the sensor module configuration menu interface associated with the non-tabbed display page. According to embodiments of the present disclosure, the third signal can be generated as a result of activating a touchable or press-activated module settings menu button of a sensor module of the non-tabbed display page. According to embodiments of the present disclosure, the fourth signal can be generated as a result of activating a touchable or activated button of the sensor module configuration menu interface of the non-tabbed display page. According to embodiments of the present disclosure, the method can further include a step (e) of overlaying, in response to a fifth signal, a pump association menu interface on the sensor module configuration menu interface of a portion of the non-tabbed display page in order to enable selective association of a pump with a sensor module of the non-tabbed display page. According to embodiments of the present disclosure, the fifth signal can be generated upon activating a touchable or press-activated pump association button of the sensor module configuration menu interface.

[0354] According to embodiments of the present disclosure, each sensor module associated with its corresponding sensor module configuration menu interface can be independently selected from the group consisting of a pressure sensor module associated with a pressure sensor module configuration menu interface, a bubble detection sensor module associated with a bubble detection sensor module configuration menu interface, a level sensor module associated with a level sensor module configuration menu interface, a temperature sensor module associated with a temperature sensor module configuration menu interface, a flow sensor module associated with a flow sensor module configuration menu interface, and a pressure delta sensor module associated with a pressure delta sensor module configuration menu interface. According to embodiments of the present disclosure, the method can include a step of activating a system configuration menu interface in order to select a predefined graphical user interface configuration, or to configure at least one selectable alarm setting selected from the group consisting of brightness and alarm volume, or to display an external device menu. However, the system configuration menu interface can be equipped with other options available for configuring the system.

[0355] According to embodiments of the present disclosure, the method can include a step of closing the sensor module configuration menu interface of the tabbed display page in order to accept and make available at least one alarm limit of the tabbed sensor module, and / or it can further include a step of closing the sensor module configuration menu interface of the non-tabbed display page in order to accept and make available at least one alarm limit of the non-tabbed display page sensor module.

[0356] Miscellaneous

[0357] Thus, in accordance with the present disclosure, a graphical user interface providing convenient customization, flexible configuration, and modular structure has been described, which employs an intuitive design, thereby facilitating ease of use and safety of use. Also in accordance with the present disclosure, a graphical user interface with integrated alerts has been described, which enhances safety in using the graphical user interface. In accordance with the present disclosure, the graphical user interface is provided with various hierarchical setting mechanisms for setting system settings as well as for setting various sensor modules and non-sensor modules configured within at least one non-tabbed display page and a plurality of tabbed display pages.

[0358] The foregoing description of the present disclosure has been presented for the purposes of illustration and description only and is not intended to be construed as limitations on the scope of the application. The scope of the application is to be determined by the appended claims.

Claims

1. A touch screen comprising a graphical user interface, wherein the graphical user interface comprises: a header portion; and a central portion adjacent to the header portion, wherein the central portion is divided into a plurality of segments, wherein at least one segment displays a non-tabbed page and at least one segment displays a plurality of tabbed pages, and wherein the non-tabbed page comprises a plurality of sensor modules, at least one tabbed page comprises a plurality of sensor modules, wherein each segment is customizable by an operator of a cardiopulmonary bypass system to include selected modules, and at least one tabbed page comprises a plurality of sensor modules customizable by an operator of a cardiopulmonary bypass system to include selected modules, and at least one tabbed display page comprises a plurality of cardioplegia modules, wherein the at least one tabbed display page comprising the plurality of sensor modules and the at least one tabbed display page comprising the plurality of cardioplegia modules are located within different segments of the central portion; wherein each tabbed display page comprises a contiguous tab attached thereto, wherein each tabbed display page is displayable in a display mode and an overlay mode, such that the graphical user interface is operable to simultaneously display the non-tabbed display page and three tabbed display pages in the display mode, wherein all tabbed display pages are visible when displayed in the display mode, and only the contiguous tab of a tabbed display page is visible when displayed in the overlay mode, wherein each contiguous tab is convertible to an alarm state, such that the contiguous tab is convertible to a visual alarm state when the corresponding tabbed display page is displayed in the overlay mode and any sensor module of the corresponding tabbed display page is converted to an alarm state, wherein at least the non-tabbed display page comprises a plurality of segments, and at least one segment of the plurality of segments has a sensor module settings menu button for activating a module configuration menu interface for configuring the at least one segment to display information related to a different sensor module than a current sensor module being displayed. Each sensor module of the non-tabbed page is individually selected from a group consisting of a pressure sensor module, a bubble detection sensor module, a level sensor module, a flow sensor module, a pressure delta data sensor module, and a temperature sensor module.

2. The touch screen of claim 1, wherein, The non-tabbed page comprises at least one pressure sensor module, at least one bubble detection sensor module, and at least one level sensor module.

3. The touch screen of claim 1, wherein, Each of the at least one pressure sensor module, the at least one bubble detection sensor module, and the at least one level sensor module is displayable in a plurality of alarm states selected from at least two of a high priority alarm state, a medium priority alarm state, and a low priority alarm state.

4. The touch screen of claim 3, wherein, 5. The touch screen of claim 3, wherein the at least one pressure sensor module comprises a pressure value data field and a touch or press activated intervention button, wherein the intervention button is activated by a touch or press to temporarily modify operation of a pump of the cardiopulmonary bypass system. ​ 6. The touch screen of claim 3, wherein the at least one bubble detection sensor module includes a bubble detection data field and a touch or press activated reset button, wherein the bubble detection data field displays bubble detection data obtained from the bubble detection sensor.

7. A method of configuring a graphical user interface of a touch screen prior to operating in a clinical mode of operation, the touch screen being the touch screen of any of the preceding claims 1-6, wherein the method comprises the steps of: in response to a first signal, displaying a sensor module configuration menu interface associated with a tabbed display page of the graphical user interface displayed by the touch screen, wherein the first signal is generated as a result of activating a touch or press activated module settings menu button of the sensor module of the tabbed display page; in response to a second signal, setting at least one alarm limit for a sensor module associated with the sensor module configuration menu interface associated with the tabbed display page, wherein the second signal is generated as a result of activating a touch or press activated button of the sensor module configuration menu interface of the tabbed display page; in response to a third signal, overlaying a pump association menu interface on a portion of the sensor module configuration menu interface of the tabbed display page, wherein the pump association menu interface enables selection of a pump function to be associated with the sensor module of the tabbed display page, wherein the third signal is generated as a result of activating a touch or press activated module settings menu button of the sensor module configuration menu interface of the tabbed display page; in response to a fourth signal, displaying a sensor module configuration menu interface on a portion of a non-tabbed display page of the graphical user interface displayed by the touch screen, wherein the fourth signal is generated as a result of activating a touch or press activated module settings menu button of the sensor module of the non-tabbed display page; in response to a fifth signal, setting at least one alarm limit for a sensor module associated with the sensor module configuration menu interface associated with the non-tabbed display page, wherein the fifth signal is generated as a result of activating a touch or press activated button of the sensor module configuration menu interface of the non-tabbed display page.

8. The method of claim 7, further comprising the steps of: in response to a sixth signal, overlaying a pump association menu interface on a portion of the sensor module configuration menu interface of the non-tabbed display page, wherein the pump association menu interface enables selection of a pump function to be associated with the sensor module of the non-tabbed display page, wherein the sixth signal is generated as a result of activating a touch or press activated pump association button of the sensor module configuration menu interface of the non-tabbed display page.

9. The method of claim 7, wherein, The sensor module associated with the sensor module configuration menu interface is either a pressure sensor module associated with the pressure sensor module configuration menu interface, or a bubble detection sensor module associated with the bubble detection sensor module configuration menu interface, or a temperature sensor module associated with the temperature sensor module configuration menu interface, or a flow sensor module associated with the flow sensor module configuration menu interface, or a pressure delta sensor module associated with the pressure delta sensor module configuration menu interface.

10. The method of claim 8, wherein, Each sensor module associated with the respective sensor module configuration menu interface is independently selected from the group consisting of: a pressure sensor module associated with the pressure sensor module configuration menu interface, a bubble detection sensor module associated with the bubble detection sensor module configuration menu interface, a temperature sensor module associated with the temperature sensor module configuration menu interface, a flow sensor module associated with the flow sensor module configuration menu interface, and a pressure delta sensor module associated with the pressure delta sensor module configuration menu interface.

11. The method of claim 7, further comprising the steps of: activating the system configuration menu interface to select a predefined graphical user interface configuration, or to configure at least one selectable alarm setting selected from the group consisting of a brightness and an alarm volume, or to display an external device menu.

12. The method of claim 7, further comprising the steps of: deactivating the non-tabbed display page sensor module configuration menu interface to accept and make available at least one alarm limit of the non-tabbed display page sensor module.

13. The method of claim 7, further comprising the steps of: deactivating the non-tabbed display page sensor module configuration menu interface to accept and make available at least one alarm limit of the non-tabbed display page sensor module.

14. The method of claim 13, further comprising the steps of: deactivating the tabbed display page sensor module configuration menu interface to accept and make available at least one alarm limit of the tabbed display page sensor module.

15. The method of claim 7, wherein the touch screen is an integral part of a heart-lung bypass machine, and the clinical operating mode is an operation of an extracorporeal blood flow circuit.

16. A heart-lung bypass system, comprising: a processor; a touch screen according to any one of claims 1 to 6; and a plurality of sensors arranged to measure one or more parameters of an extracorporeal blood flow circuit of the heart-lung bypass system, wherein the plurality of sensors are operatively connected to input measurement data related to the one or more parameters to the processor, and wherein each sensor is connected to one of a non-tabbed display page or a sensor module of a tabbed display page, such that the data measured by each sensor module is displayable by the graphical user interface. ​

Images