Patent Description:
Today's patient monitoring environments are crowded with sophisticated electronic medical devices servicing a wide variety of monitoring and treatment endeavors for a given patient. Generally, many if not all of the devices are from differing manufactures, and many may be portable devices. The devices may not communicate with one another and each may include its own control, display, alarms, configurations and the like. Complicating matters, caregivers often desire to associate all types of measurement and use data from these devices to a specific patient. Thus, patient information entry often occurs at each device. Sometimes, the disparity in devices leads to a need to simply print and store paper from each device in a patient's file for caregiver review.

The result of such device disparity is often a caregiver environment scattered with multiple displays and alarms leading to a potentially chaotic experience. Such chaos can be detrimental to the patient, particularly in surgical environments where caregiver distraction can be deadly, and including recovery or monitoring environments where patient distraction or disturbance may increase recovery times and expense.

Various manufacturers produce multi-monitor devices or devices that modularly expand to increase the variety of monitoring or treatment endeavors a particular system can accomplish. However, as medical device technology expands, such multi-monitor devices often require specific hardware and size configurations and may be limited in the number of integrated monitors.

<CIT> discloses a first medical device which can receive a physiological parameter value from a second medical device. The second physiological parameter value may be formatted according to a protocol not used by the first medical device such that the first medical device is not able to process the second physiological parameter value to produce a displayable output value. The first medical device can pass the physiological parameter data from the first medical device to a separate translation module and receive translated parameter data from the translation module at the first medical device.

<CIT> discloses a method for acquiring several changing values and representing the acquired values on a monitoring screen, as well as to a device with a screen in order, on this, to represent changing values acquired during ventilation of the patient. The device comprises means for acquiring at least three changing values of different origin, and means for representing the values, which permit the acquired values to be qualitatively represented on the screen together in a single graphic element. This graphic element has a pictorial representation of a lung shape.

<CIT> discloses a device which obtains a series of measurements of a physiological parameter of a monitored patient when the device is operating within a monitoring workflow. The device displays a monitoring workflow home screen when the device is operating within the monitoring workflow. The monitoring workflow home screen contains a representation of the physiological parameter of the monitored patient. In addition, the device obtains a measurement of the physiological parameter of each patient in a series of patients when the device is operating within a non-monitoring workflow.

The present invention is defined by the features of the independent claim <NUM>. In particular, present invention relates to an improved screen display system for providing real-time and time-critical physiological parameters to a plurality of clinicians in a surgical care setting. The system comprises a display and one or more processors configured to pr present, in the display at a first time, a first layout area comprising a container slot at a first location, and allow a first user to drag a physiological parameter container from a selection area and to drop it in the container slot at the first location, wherein a setting interface element on the display allows adjusting the format of a dragged physiological parameter container, as defined in independent claim <NUM>.

For an understanding of the present invention, the present disclosure describes a host device that provides an improved, organized, uncluttered, and graphically-rich display for monitoring many physiological parameters of a patient. This display can be particularly useful in treatment settings, such as in a surgical setting during administration of anesthesia, where many physiological parameters can be monitored using multiple devices and all at the same time by multiple clinicians. The display can provide a real-time and intuitive set of information for clinicians that may be customized (for example, in the format or position of the presentation of data) for different clinical scenarios and assist clinicians with understanding relevant or significant physiological parameters in the different clinical scenarios. The display may include multiple concurrently-presented areas that can each provide different information intended to be more relevant to particular clinicians than other clinicians.

The host device can be part of a patient monitoring system and present an integrated display of real-time patient data and alarms from multiple integrated or non-integrated devices, such as patient monitors, ventilators, anesthesia gas machines, or intravenous (IV) pumps. The host device may provide a supplementary display for the patient data collected by the multiple devices and present information, such as comprehensive real-time patient status, historical trends, or alarm indicators, in an organized manner on one or more displays. The one or more displays can be central to a care team for a patient, and the care team can together simultaneously view and act upon the information presented. The host device can serve to reduce clinician cognitive overload and improve patient safety, as well as promote data sharing and team coordination among multiple clinicians, at least because physiological parameters may be presented by the host device in association with patient physiology or rather than the devices used to monitor the physiological parameters. This can facilitate a rapid understanding of patient needs, such as when an alarm condition arises during treatment, without clinicians having to consider one or more sources of sensor data used for determining the physiological parameters.

The host device can provide tailored, use-case-specific, or physiological-specific screen layouts (sometimes referred to as templates) that may optimize the presentation of advanced and integrated parameters, trend data, or waveforms for a variety of clinical scenarios, types of caregivers or users, or logical views. The host device may, for example, present one or more of (i) an overview layout for displaying patient monitoring data from most or all connected point-of-care or therapeutic devices including waveforms and alarms for an overview of patient status, (ii) a hemodynamics layout for displaying trend data for noninvasive hemoglobin (SpHb®), pleth variability index (PVi®), or pulse rate to aid in visualizing patient status over time, (iii) an oxygenation layout for displaying ventilator waveforms alongside noninvasive trended hemoglobin (SpHb®) and oxygen saturation (SpO2) to monitor a patient's oxygenation status, or (iv) a sedation layout for displaying electroencephalogram (EEG) waveforms, patient state index (PSi™), or anesthesia machine data to monitor a patient's sedation. Other potential layouts that may be presented by the host device can include a vital signs layout for displaying a collection of vital signs data from multiple devices, as well as a human body image layout for displaying values or magnitudes of parameters within or along a graphic of a human body that may be animated. Additionally, the host device can control one or more settings or other operations of the multiple devices or other additional components in a patient monitoring system.

For purposes of summarizing the disclosure, certain aspects, advantages and novel features are discussed herein. It is to be understood that not necessarily all such aspects, advantages or features will be embodied in any particular embodiment of the invention and an artisan would recognize from the disclosure herein a myriad of combinations of such aspects, advantages or features.

The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims.

The present disclosure relates to a host device for presenting an integrated display of patient data and alarms for a single patient. The patient data and alarms can be obtained from multiple devices, such as patient monitors, ventilators, anesthesia gas machines, or intravenous (IV) pumps that are used in monitoring the single patient. The host device can provide an additional, centralized display for patient data collected from the multiple devices and present information in tailored, use-case-specific screen, or physiological-specific layouts that optimizes the presentation for a variety of clinical scenarios. The host device can also control one or more settings or other operations of the multiple devices or other additional components in a patient monitoring system.

The host device can operate in coordination with a medical monitoring hub configured to be the center of monitoring activity for a given patient. The host device can be connected to the hub directly or indirectly through a network or a server. The host device can be associated with a display screen for projecting data received from the hub. The host device may, for example, be the television, a monitor, a cellphone, tablet, laptop or desktop computer, or one or more other devices having a hardware processor configured to execute a patient data display system. The hub may itself have a patient data display system installed and can cause a display external to the hub to present patient data. Because the hub may also have its own display, some patient data may be displayed both on the display of the hub and the external display.

The host device may communicate directly with point-of-care (POC) devices. A POC device may, for instance, be a portable patient monitor or another type of device that provides patient monitoring, such as bed-side to a patient. The host device may communicate with a server system to receive patient parameter data. The display associated with the host device can provide measurement data for a wide variety of monitored parameters for the patient under observation in numerical or graphic form and may be automatically configured based on the type of data and information being received at the host device. The host device is moveable, portable, or mountable so that it can be positioned to convenient areas within a caregiver environment. For example, the host device is collected within a singular housing.

The host device or the hub may receive data from a portable patient monitor. Typical portable patient monitors, such as oximeters or co-oximeters can provide measurement data for a large number of physiological parameters derived from signals output from optical or acoustic sensors, electrodes, or the like. The physiological parameters include, but are not limited to oxygen saturation, carboxyhemoglobin, methemoglobin, total hemoglobin, glucose, pH, bilirubin, fractional saturation, pulse rate, respiration rate, components of a respiration cycle, indications of perfusion including perfusion index, signal quality or confidences, plethysmograph data, indications of wellness or wellness indexes or other combinations of measurement data, audio information responsive to respiration, ailment identification or diagnosis, blood pressure, patient or measurement site temperature, depth of sedation, organ or brain oxygenation, hydration, measurements responsive to metabolism, combinations of the same or the like, to name a few. The hub may output data sufficient to accomplish closed-loop drug administration in combination with infusion pumps or the like.

The hub communicates with other devices in a monitoring environment that are interacting with the patient in a number of ways. For example, the hub advantageously receives serial data from other devices (which may be POC devices) without necessitating their reprogramming or that of the hub. Such other devices include pumps, ventilators, all manner of monitors monitoring any combination of the foregoing parameters, ECG/EEG/EKG devices, electronic patient beds, and the like. Moreover, the hub advantageously receives channel data from other medical devices without necessitating their reprogramming or that of the hub. When a device communicates through channel data, the hub may advantageously alter the large display to include measurement information from that device. Additionally, the hub accesses nurse call systems to ensure that nurse call situations from the device are passed to the appropriate nurse call system.

The hub also communicates with hospital systems to advantageously associate incoming patient measurement and treatment data with the patient being monitored. For example, the hub may communicate wirelessly or otherwise to a multi-patient monitoring system, such as a server or collection of servers, which in turn may communicate with a caregiver's data management systems, such as, for example, an Admit, Discharge, Transfer ("ADT") system or an Electronic Medical Records ("EMR") system. The hub advantageously associates the data flowing through it with the patient being monitored thereby providing the electronic measurement and treatment information to be passed to the caregiver's data management systems without the caregiver associating each device in the environment with the patient.

The hub advantageously includes a reconfigurable and removable docking station. The docking station may dock additional layered docking stations to adapt to different patient monitoring devices. Additionally, the docking station itself is modularized so that it may be removed if the primary dockable portable patient monitor changes its form factor. Thus, the hub is flexible in how its docking station is configured.

The hub includes a large memory for storing some or all of the data it receives, processes, or associates with the patient, or communications it has with other devices and systems. Some or all of the memory may advantageously comprise removable SD memory.

The hub communicates with other devices through at least (<NUM>) the docking station to acquire data from a portable monitor, (<NUM>) innovative universal medical connectors to acquire channel data, (<NUM>) serial data connectors, such as RJ ports to acquire output data, (<NUM>) Ethernet, USB, and nurse call ports, (<NUM>) Wireless devices to acquire data from a portable monitor, (<NUM>) other wired or wireless communication mechanisms known to an artisan. The universal medical connectors advantageously provide optional electrically isolated power and communications, are designed to be smaller in cross section than isolation requirements. The connectors and the hub communicate to advantageously translate or configure data from other devices to be usable and displayable for the hub. A software developers kit ("SDK") is provided to a device manufacturer to establish or define the behavior and meaning of the data output from their device. When the output is defined, the definition is programmed into a memory residing in the cable side of the universal medical connector and supplied as an original equipment manufacturer ("OEM") to the device provider. When the cable is connected between the device and the hub, the hub understands the data and can use it for display and processing purposes without necessitating software upgrades to the device or the hub. The hub can negotiate the schema and even add additional compression or encryption. Through the use of the universal medical connectors, the hub organizes the measurement and treatment data into a single display and alarm system effectively and efficiently bringing order to the monitoring environment.

As the hub receives and tracks data from other devices according to a channel paradigm, the hub may advantageously provide processing to create virtual channels of patient measurement or treatment data. A virtual channel may comprise a non-measured parameter that is, for example, the result of processing data from various measured or other parameters. An example of such a parameter includes a wellness indicator derived from various measured parameters that give an overall indication of the wellbeing of the monitored patient. An example of a wellness parameter is disclosed in <CIT>, <CIT> and <CIT>, by the assignee of the present. By organizing data into channels and virtual channels, the hub may advantageously time-wise synchronize incoming data and virtual channel data.

The hub also receives serial data through serial communication ports, such as RJ connectors. The serial data is associated with the monitored patient and passed on to the multi-patient server systems or caregiver backend systems discussed above. Through receiving the serial data, the caregiver advantageously associates devices in the caregiver environment, often from varied manufactures, with a particular patient, avoiding a need to have each individual device associated with the patient and possible communicating with hospital systems. Such association is vital as it reduces caregiver time spent entering biographic and demographic information into each device about the patient. Moreover, through the SDK the device manufacturer may provide information associated with any measurement delay of their device, thereby further allowing the hub to advantageously time-wise synchronize serial incoming data and other data associated with the patient.

When a portable patient monitor is docked, and it includes its own display, the host device or hub effectively increases its display real estate. For example, the portable patient monitor may simply continue to display its measurement or treatment data, which may be now duplicated on the host device or hub display, or the display may alter its display to provide additional information. The display presents anatomical graphical data of, for example, the heart, lungs, organs, the brain, or other body parts being measured or treated. The graphical data may advantageously animate similar to and in concert with the measurement data. For example, lungs may inflate in approximate correlation to the measured respiration rate or the determined inspiration/expiration portions of a respiration cycle, the heart may beat according to the pulse rate, may beat generally along understood actual heart contraction patterns, the brain may change color or activity based on varying depths of sedation, or the like. When the measured parameters indicate a need to alert a caregiver, a changing severity in color may be associated with one or more displayed graphics, such as the heart, lungs, brain, organs, circulatory system or portions thereof, respiratory system or portions thereof, other body parts or the like. The body portions may include animations on where, when or how to attach measurement devices.

The host device or hub may also advantageously overlap parameter displays to provide additional visual information to the caregiver. Such overlapping may be user definable and configurable. The display may also incorporate analog-appearing icons or graphical indicia.

To facilitate a complete understanding of the disclosure, the remainder of the detailed description describes the disclosure with reference to the drawings, wherein like reference numbers are referenced with like numerals throughout.

<FIG> illustrates a perspective view of a medical monitoring hub <NUM> with a docked portable patient monitor <NUM>. The hub <NUM> includes a display <NUM>, and a docking station <NUM>, which is configured to mechanically and electrically mate with the portable patient monitor <NUM>, each housed in a movable, mountable and portable housing <NUM>. The housing <NUM> includes a generally upright inclined shape configured to rest on a horizontal flat surface, although the housing <NUM> can be affixed in a wide variety of positions and mountings and comprise a wide variety of shapes and sizes.

The display <NUM> may present a wide variety of measurement or treatment data in numerical, graphical, waveform, or other display indicia <NUM>. The display <NUM> occupies much of a front face of the housing <NUM>, although an artisan will appreciate the display <NUM> may comprise a tablet or tabletop horizontal configuration, a laptop-like configuration or the like. The display information and data may additionally or alternatively communicated to a table computer, smartphone, television, or any display system recognizable to an artisan. The upright inclined configuration of <FIG> presents display information to a caregiver in an easily viewable manner.

The portable patient monitor <NUM> of <FIG> may advantageously comprise an oximeter, co-oximeter, respiratory monitor, depth of sedation monitor, noninvasive blood pressure monitor, vital signs monitor or the like, such as those commercially available from Masimo Corporation of Irvine, CA, or disclosed in <CIT>, <CIT>, <CIT>, <CIT>, <CIT>; <CIT>, <CIT>, <CIT>, <CIT> and <CIT>,<CIT>, and the like. The monitor <NUM> may communicate with a variety of noninvasive or minimally invasive devices such as optical sensors with light emission and detection circuitry, acoustic sensors, devices that measure blood parameters from a finger prick, cuffs, ventilators, and the like. The monitor <NUM> may include its own display <NUM> presenting its own display indicia <NUM>. The display indicia may advantageously change based on a docking state of the monitor <NUM>. When undocked, the display indicia may include parameter information and may alter orientation based on, for example, a gravity sensor or accelerometer.

The docking station <NUM> of the hub <NUM> includes a mechanical latch <NUM>, or mechanically releasable catch to ensure that movement of the hub <NUM> doesn't mechanically detach the monitor <NUM> in a manner that could damage the same.

Although disclosed with reference to particular portable patient monitors <NUM>, an artisan will recognize from the disclosure herein a large number and wide variety of medical devices that may advantageously dock with the hub <NUM>. Moreover, the docking station <NUM> may advantageously electrically and not mechanically connect with the monitor <NUM>, or wirelessly communicate with the same.

Additional or alternative features of the hub <NUM>, its presentation of information, and its operating environment are described in <CIT>, titled "SYSTEM FOR DISPLAYING MEDICAL MONITORING DATA".

<FIG> illustrates a simplified block diagram of a monitoring environment <NUM> including the hub <NUM> of <FIG>. As shown in <FIG>, the environment may include the portable patient monitor <NUM> communicating with one or more patient sensors <NUM>, such as, for example, oximetry optical sensors, acoustic sensors, blood pressure sensors, respiration sensors or the like. Additional sensors, such as, for example, a NIBP sensor or system <NUM> and a temperature sensor or sensor system <NUM> may communicate directly with the hub <NUM>. The sensors <NUM>, <NUM> and <NUM> when in use are typically in proximity to the patient being monitored if not actually attached to the patient at a measurement site.

The portable patient monitor <NUM> may communicate with the hub <NUM> through the docking station <NUM> when docked and wirelessly when undocked, however, such undocked communication is not required. The hub <NUM> communicates with one or more multi-patient monitoring servers <NUM> or server systems, such as, for example, those disclosed with in <CIT>, <CIT>, and <CIT>.

In general, the server <NUM> communicates with caregiver backend systems <NUM> such as EMR or ADT systems. The server <NUM> may advantageously obtain through push, pull or combination technologies patient information entered at patient admission, such as demographical information, billing information, and the like. The hub <NUM> accesses this information to seamlessly associate the monitored patient with the caregiver backend systems <NUM>. Communication between the server <NUM> and the monitoring hub <NUM> may be any recognizable to an artisan from the disclosure herein, including wireless, wired, over mobile or other computing networks, or the like.

<FIG> also shows the hub <NUM> communicating through its serial data ports <NUM> and channel data ports <NUM>. As disclosed in the forgoing, the serial data ports <NUM> may provide data from a wide variety of patient medical devices, including electronic patient bed systems <NUM>, infusion pump systems <NUM> including closed loop control systems, ventilator systems <NUM>, blood pressure or other vital sign measurement systems <NUM>, or the like. Similarly, the channel data ports <NUM> may provide data from a wide variety of patient medical devices, including any of the foregoing, and other medical devices. For example, the channel data ports <NUM> may receive data from depth of consciousness monitors <NUM>, such as those commercially available from SedLine™, other brain or organ oximeter devices <NUM>, noninvasive blood pressure or acoustic devices <NUM>, capnography devices <NUM>, or the like. Channel device may include board-in-cable ("BIC") solutions where the processing algorithms and the signal processing devices that accomplish those algorithms are mounted to a board housed in a cable or cable connector, which may have no additional display technologies. The BIC solution outputs its measured parameter data to the channel port <NUM> to be displayed on the display <NUM> of hub <NUM>. The hub <NUM> may advantageously be entirely or partially formed as a BIC solution that communicates with other systems, such as, for example, tablets, smartphones, or other computing systems.

<FIG> illustrates a simplified patient data flow process. As shown, once a patient is admitted into the caregiver environment at step <NUM>, data about the patient is populated on the caregiver backend systems <NUM>. The server <NUM> may acquire or receive this information in step <NUM>, and then make it accessible to the hub <NUM>. When the caregiver at step <NUM> assigns the hub <NUM> to the patient, the caregiver simply looks at the presently available patient data and selects the particular patient being currently monitored. The hub <NUM> at step <NUM> then associates the measurement, monitoring and treatment data it receives and determines with that patient. The caregiver need not again associate another device with the patient so long as that device is communicating through the hub <NUM> by way of (<NUM>) the docking station, (<NUM>) the universal medical connectors, (<NUM>) the serial data connectors, or (<NUM>) other communication mechanisms. At step <NUM>, some or the entirety of the received, processed or determined data is passed to the server <NUM>.

<FIG> illustrates an example computing environment <NUM> in which patient data is acquired and processed. In the computing environment <NUM>, patient devices <NUM> connect with a medical network interface <NUM>, which provides network connection functionality for these devices by connecting to a hospital network <NUM>. The patient devices <NUM> may be PoC devices. Also connected to the hospital network <NUM> is a multi-patient monitoring server (MMS) <NUM>, a host device <NUM>, and other hospital devices <NUM>, such as nurses stations, kiosks, computers on wheels (COWs), and clinician devices (such as phones, pagers, tablets, and the like). The MMS <NUM> is also in communication with an external network <NUM> which may communicate with clinician devices or patient devices <NUM>, which can include, for instance, devices that may be remote from the hospital. The MMS <NUM> for also interfaces with EMR <NUM>. Thus, the medical network interface <NUM> may enable data from the patient devices <NUM> to be communicated to any of the other components shown in <FIG>, among possibly others.

The MMS <NUM> may route data to nurse stations (sometimes referred to as central stations). Data received from the patient devices <NUM> of the medical network interface <NUM> may be provided to their stations, central stations, and clinician devices, among others. The MMS <NUM> may perform clinician notification, for example, by routing alarms obtained from the patient devices <NUM> to the devices <NUM>, <NUM>. Further, the MMS <NUM> may perform analytics and journaling, for example, as disclosed in <CIT>, titled "Systems and Methods for Storing, Analyzing, Retrieving and Displaying Streaming Medical Data".

Further, the MMS <NUM> may include telepresence module that performs telepresence monitoring of patients by clinicians remotely, for example, as described in <CIT>, titled "Intelligent Medical Network Edge Router".

Further, the MMS <NUM>, like the MMS <NUM>, may be expandable and can supply data to other software engines and databases, including the EMR <NUM>.

The data obtained by the medical network interface <NUM> from the patient devices <NUM> (or from the hub <NUM>) may come in one or more of the following forms: waveform data, parameter data, or event data. Waveform data can include trend data, which may be high-frequency data. The medical network interface <NUM> or the MMS <NUM> may treat this data akin to video streaming data, such that if there are losses (for example, due to buffer overruns), those losses are ignored. Parameter data (for example, physiological parameter measurement such as oxygen saturation values), may come at a set frequency such as once every second (<NUM>). The medical network interface <NUM> may combine parameter data into a patient snapshot and provide this snapshot to the MMS <NUM> or to other devices shown. Event data can include event driven data, such as alarms (for example, parameter values going out of bounds) and alerts (for example, a progress fallen off or alarm settings were change on one of the patient devices <NUM>). Events may be supplied asynchronously, when they occur, and the medical network interface <NUM> may apply a time stamp to any events received from the patient devices <NUM> before supplying the event data to other devices on the network.

The host device <NUM>, the patient devices <NUM>, the MMS <NUM> may be connected to the hospital network <NUM>. The hub <NUM> can be connected to the host device <NUM> directly or via the hospital network <NUM>. The hospital network <NUM> can support wireless or hard wired network communications. The patient devices <NUM> can include devices that provide bedside patient monitoring.

The host device <NUM> can include a display <NUM> configured to present patient information. In one example, the host device <NUM> may be a television, monitor, cellphone, tablet, laptop or desktop computer and include a patient data display system <NUM>, which may be installed on a memory of the host device <NUM>. The patient data display system <NUM> can be configured to communicate with the MMS <NUM>, the patient devices <NUM>, the hub <NUM>, the medical network interface <NUM>, alone or in combination, to receive patient data or provide control instructions. In one implementation, the host device <NUM> executes an Android™ operating system, and the patient data display system <NUM> is a program loaded and that runs on the Android™ operating system.

The patient data display system <NUM> can, for example, group data based on the parameters being monitored, a source of the data, a patient physiology, or a use-case-specific manner. The patient parameters may be prioritized for display. The prioritization may be associated with parameters within the patient devices <NUM>. For example, where one of the patient devices <NUM> provides data from three parameters, the three parameters may be prioritized among themselves. Parameters may also be prioritized depending on the patient devices <NUM> connected, such as to the hub <NUM>, and the display layout selected for the host device <NUM>. For example, in one screen layout, such as for a sedation clinical scenario, the sedation layout (shown in <FIG>) may cause one set of parameters to be prioritized for display, whereas in another screen layout, such as for an overview scenario, the overview layout (shown in <FIG>) may cause a different set of parameters to be prioritized.

As will further be described with reference to <FIG>, <FIG>, and <FIG>, the patient data display system <NUM> can include alarm features, and the patient data display system <NUM> can allow a user to adjust the alarm limit of one or more of the patient devices <NUM> via the host device <NUM>. The host device <NUM> can accordingly send the adjusted alarm limit to the patient devices <NUM> or another device (such as, the medical network interface <NUM> or the MMS <NUM>) for implementation by the patient devices <NUM>. The host device <NUM> may not itself generate or manage alarms but instead provide an interface through which alarms may be presented, grouped, and acted on.

The patient data display system <NUM> can provide animations associated with anatomical features of a patient, such as shown in the examples described with reference to <FIG>. The anatomical features of the patient may, for instance, be animated at the rate of associated parameters. Similar animations may be provided on the hub <NUM>.

<FIG> illustrates a simplified hardware block diagram of the host device <NUM> of <FIG>. The host device <NUM> can include a housing <NUM>, a processor <NUM>, a memory <NUM>, a display <NUM>, and an input/output (I/O) interface <NUM>. The housing <NUM> can support or enclose one or more of the other components of the host device <NUM>. The processor <NUM>, the memory <NUM>, the display <NUM>, and the input/output (I/O) interface <NUM> can communicate with one another via wired or wireless communication. The processor <NUM> can control operations of the host device <NUM> according at least to instructions stored on the memory <NUM>. The memory can, for example, store the patient data display system <NUM>. The processor <NUM> can present information on the display <NUM>, such as by presenting one or more of the screens or user interfaces described herein. The input/output interface <NUM> can be used by the processor <NUM> to receive or transmit data, such as patient data, from or to one or more other electronic devices via wired or wireless communication.

<FIG> illustrates displays of measurement data on a display of a host device, such as the display <NUM>, or another display described herein. The measurement data may be organized by source electronic devices or channels. As shown in <FIG>, the parameters received from a particular source electronic device or channel or computed from the particular source electronic device or channel can be grouped together and presented in a dedicated area on the display corresponding to the particular source electronic device or channel.

The screen layout shown in <FIG> may be an overview screen <NUM>. The overview screen <NUM> may be a default layout screen displayed after a patient is selected. The identifier for the patient can be provided at a patient identifier area <NUM>, and a room in a physical treatment facility in which the patient is being treated can be identified at a patient room area <NUM>. The patient may be selected after the patient has been admitted as described with respect to <FIG>.

The overview screen <NUM> can include one or more of the dedicated areas (sometimes referred to as windows for purposes of illustration, but may take forms other than windows), such as an anesthesia/vent window 522A, EEG window 524A, regional oximeter forehead right window 524B, regional oximeter forehead left window 524C, monitor window 522C, blood gas window <NUM>, and infusion pump window 522B, among others. More or fewer windows may alternatively be shown on the overview screen <NUM>. For example, the overview screen <NUM> can additionally or alternatively include a window for capnography.

The anesthesia/vent window 522A can display data from an anesthesia or ventilator device. A first-connected or a last-connected anesthesia or ventilator device may have a highest priority and its data will be displayed. The anesthesia/vent window 522A can display data for a variety of parameters, such as, for example, PEEP, Ppeak, Pmean, PLAT, Vte, Ve, EtO<NUM>, FiO<NUM>. The anesthesia/vent window 522A can also display waveforms, such as, for example, pressure, volume, and flow waveforms.

The size of the anesthesia/vent window 522A may change depending on whether one or more associated devices are disconnected or connected, such as from or to the hub <NUM>. For example, the anesthesia/vent window 522A may expand when one or more capnography or pump devices is disconnected or powered off. Because the size of the anesthesia/vent window 522A can change, no waveforms may be visible, for instance, if a capnography device is connected or all three waveforms may be visible if the capnography device is not connected. The pressure waveform may be visible if a pump device is connected and a capnography device is disconnected.

Although not shown in <FIG>, the overview screen <NUM> can also display data from a capnography device. For example, the overview screen <NUM> can include a window for displaying parameters such as EtCO<NUM>, FiCO<NUM>, RR, or CO<NUM> waveform. The window for a capnography device can be visible when the capnography is connected, such as to the hub <NUM>.

The infusion pump window 522B can display parameters related to fluid delivery, such as INVTB, INV, INRT, and INRMT. The infusion pump window 522B may, for instance, be visible when an infusion pump device is connected, such as to the hub <NUM>.

The EEG window 524A can display data received from a EEG monitoring device, such as the EEG monitor marketed under the name SedLine® and sold by Masimo Corporation of Irvine, CA. The EEG window 524A can display parameters indicative of brain activity, such as PSi™, EMG, SR, SEFL, SEFR, ARTF. The EEG window 524A can also display the EEG waveform. The EEG window 524A may change size as one or more regional oximeter devices is connected or disconnected, such as to or from the hub <NUM>.

The regional oximeter forehead right and left windows 524B and 524C can display regional oximeter sensor data from regional oximeter sensors. One such regional oximeter sensor is marketed under the name O3® and sold by Masimo Corporation of Irvine, CA. For example, the regional oximeter forehead right and left windows 524B and 524C can display data for parameters indicative of cerebral oxygenation, such as rSO<NUM>, Delta Baseline (Δbase), Delta SpO<NUM> (ΔSpO<NUM>).

The monitor window 522C can display data from third-party monitoring devices, such as devices other than those provided or manufactured by someone other than a provider or manufacturer of the hub <NUM> or the host device <NUM>. For example, the monitor window 522C can display data related to one or more of the following parameters: Temperature, NiBP Systolic, NiBP Diastolic, ECG HR, PVC, CVP, ST aVL, ST aVR. The monitor window 522C may be visible when at least one of the third-party monitoring devices is connected, such as to the hub <NUM>.

The blood gas window <NUM> can display measurement data from native sensors, such as, for example, sensors that are compatible with the hub <NUM> or sensors that can be directly connected to the hub <NUM> or are provided or manufactured by a provider or manufacturer of the hub <NUM>. One such blood gas sensor is marketed under the name Rainbow and sold by Masimo Corporation of Irvine, CA. The size of the blood gas window <NUM> may change, for example, depending on whether a third-party monitoring device is connected or disconnected, such as to or from the hub <NUM>. For example, the blood gas window <NUM> may expand (for example, to also include the area corresponding to the monitor window 522C) when the third-party monitoring device is disconnected, such as from the hub <NUM>, or powered off. The blood gas window <NUM> can display one or more parameters indicative of pH, oxygen level, or carbon dioxide level, such as SpO2% PVi%, etc. The blood gas window <NUM> can also display Pleth, Signal I. ®, and Respiration Envelope waveforms.

The display shown in <FIG> may not be able to fit in all patient parameters that are being monitored. As a result, the windows displayed may be displayed based on priority, or the parameters may be displayed within individual windows based on priority. For example, the monitor window 522C may be hidden if the monitor window 522C is considered to be a relatively lower priority, and the blood gas window <NUM> may display the first <NUM> parameters that have a highest priority but not one more or additional parameters that may other be displayed.

The display illustrated in <FIG> can present a graphic of an upper portion of a person. The graphic can include a lung <NUM>, a brain <NUM>, and a heart <NUM>. Each of the lung <NUM>, the brain <NUM>, and the heart <NUM> can be colored green or red where green indicates an alarm inactive and red indicates an alarm active for the organ depicted by the red graphic. An area around a particular parameter may additionally turn red to indicate an alarm active associated with the particular parameter, and a portion of a dedicated area in which the particular parameter is shown may also turn red. For instance, an area <NUM> around the displayed SpO2% value or another area in the blood gas window <NUM> can be red indicating an alarm condition. A menu element <NUM> can enable a user to transition from displaying <FIG> to displaying an alternative interface, such as an option configuration interface for adjusting one or more of enabling/disabling alarm status visualizer animations, viewing patient data for a different patient, disconnecting from a patient monitoring device or system, or viewing a current version of the software for the patient data display system <NUM>.

The display depicted in <FIG> can include a shading (not shown), such as a gray shading in an area similar to the area <NUM>, which may indicate that a window or a parameter presents input information rather than output information. The output information may, for example, include information measured by one or more sensors monitoring a patient while the input information can include information used to control treatment of the patient. The shading can thus provide a quick and accessible indication to a caregiver whether information on the display may be input or output information. The display can include a highlighting (not shown) of particular parameters or windows. The highlighting can be used to attract attention of a user to the particular parameters or windows so assist the user with processing presented information. One or more parameters or windows can be automatically hidden from display when the parameters may be within a safe or acceptable range to reduce the amount of information that may be presented at one time.

<FIG>, <FIG>, and <FIG> illustrate displays of measurement data on the display of a host device, such as the display <NUM>, or another display described herein. The displays of measurement data can, for instance, be presented or organized according to a physiological system of a patient, clinical scenarios, or various use cases. The displays of <FIG>, <FIG>, and <FIG> may contrast with the displays of <FIG>, which instead may present or organize measurement data according to source electronic devices or channels. Accordingly, the displays of <FIG>, <FIG>, and <FIG> can be usable for assessing the status of particular physiology or a particular physiological system of the patient as a whole (for example, cardiac status, pulmonary status, neurological status, or the like) without concern for the source of the measurement data that is being shown. The measurement data can be presented in the form of parameters, trends, waveforms, or the like in the displays.

<FIG> illustrates the display of measurement data presented or organized according to hemodynamics for a patient (this display arrangement may be referred to as a hemodynamics screen). An area <NUM> can denote that the provided measurement data relates to hemodynamics of the patient. <FIG> may be presented on the display in response to receipt of a user input, such as via selection of and in a dropdown menu selectable at the area <NUM> or selection of an organ (for example, the heart) of the graphic of the upper portion of the person corresponding to hemodynamics. The hemodynamics screen may display parameter data from multiple channels such as, for example, third-party monitoring, anesthesia/ventilator, or capnography. This screen can additionally or alternatively display, for example, pleth wavefrom, pressure waveform, flow waveform, or CO<NUM> waveform.

<FIG> illustrates the display of measurement data presented or organized according to oxygenation for a patient (this display arrangement may be referred to as an oxygenation screen). An area <NUM> can denote that the provided measurement data relates to oxygenation of the patient. <FIG> may be presented on the display in response to receipt of a user input, such as via selection of and in a dropdown menu selectable at the area <NUM> or selection of an organ (for example, the lungs) of the graphic of the upper portion of the person corresponding to oxygenation. The oxygenation screen can display parameter data from one or more the following channels: third-party monitoring, anesthesia/ventilator, or capnography. The oxygenation screen can additionally or alternatively display for example, Pleth waveform, pressure waveform, flow waveform, or CO<NUM> waveform. Although some screens, such as the hemodynamics screen and the oxygenation screen, display the similar parameters or waveforms, the layout (for example, the location or size) of some of the waveform data or parameter data may be different between two screen layouts, which can show the different emphasis of each screen layout.

<FIG> illustrates the display of measurement data presented or organized according to sedation for a patient (this display arrangement may be referred to as a sedation screen). An area <NUM> can denote that the provided measurement data relates to sedation of the patient usable to monitor a depth of anesthesia for the patient. <FIG> may be presented on the display in response to receipt of a user input, such as via selection of and in a dropdown menu selectable at the area <NUM> or selection of an organ (for example, the brain) of the graphic of the upper portion of the person corresponding to sedation. The sedation screen can display parameter data from one or more the following channels: third-party monitoring devices, anesthesia/ventilator, capnography, EEG monitoring, or region brain oximetry. The sedation screen can additionally or alternatively display waveforms generated based on data from a EEG monitoring device.

The areas <NUM>, <NUM>, and <NUM> can be used to cause one of the individual displays of <FIG>, <FIG>, and <FIG> to be presented in place of another of the individual displays of <FIG>, <FIG>, and <FIG>. In addition, although <FIG>, <FIG>, and <FIG> depict measurement data presented or organized according to a care scenario such as hemodynamics, oxygenation, and sedation, the measurement data may additionally or alternatively be presented or organized according to other physiological systems or care scenarios tailored for certain groups care providers. For example, possible care scenarios used for selecting for presentation or organizing the measurement data can include circulation, blood oxygenation and ventilation, brain function and oxygenation, and organ/tissue oxygenation, and possible physiological systems used for selecting for presentation or organizing the measurement data can include organs (such as heart, brain, lungs, pharynx, larynx, lymph nodes, arteries, muscles, spleen, bone marrow, stomach, veins, arteries, pancreas, urinary bladder, kidney, skeleton, intestines, gallbladder, or liver) or organ systems (such as, respiratory system, digestive system, nervous system, muscular system, urinary system, reproductive system, endocrine system, integumentary system, immune system, or circulatory system), among other possibilities.

Further examples of displays and communications in a patient monitoring system are disclosed in <CIT>, titled "SYSTEM FOR DISPLAYING MEDICAL MONITORING DATA".

Such displays or features of such displays, for instance, may be presented by the host device <NUM>.

The host device <NUM> may present a user interface which allows a user to adjust a setting of one or more of the patient devices <NUM>, where a patient parameter data acquired by the patient devices <NUM> is displayed on a display associated with the host device. For example, the user interface can allow a user to adjust alarm limits of devices that are connected to the hub <NUM> or to the host device <NUM> directly via wired or wireless communications.

For example, sliders could be provided as user interface controls on the display of the host device <NUM>, which allow a user to adjust alarm limits or other settings of the one or more of the patient devices <NUM>. Upon receipt of an updated setting, the host device can communicate this setting update to the one or more of the patient devices <NUM> (for example, over a cable, a network, etc., or via the hub <NUM>). The one or more of the patient devices <NUM> can know how to read the setting update because the one or more of the patient devices <NUM> can include code that can interpret the settings update (for example, because the setting update can be formatted in a way, such as by the host device <NUM>, the hub <NUM>, or another device in the computing environment <NUM>, that the one or more of the patient devices <NUM> can understand it).

The host device <NUM> can receive an alarm from the one or more of the patient devices <NUM>, the hub <NUM> (if the host device is connected to the hub directly or via a computer network), or another device in the computing environment <NUM>. The host device <NUM> can, for example, communicate alarm settings to the hub <NUM>. Based on the alarm settings, the hub <NUM> can be configured to generate an alert based on the data received from its connected medical devices or sensors and communicate the alert to the display of a host device.

The displays shown in <FIG>, <FIG>, and <FIG> can include parameter or window shading (not shown) in gray, parameter or window highlighting (not shown), or parameter or window hiding as described with respect to the display of <FIG> so that a caregiver may quickly understand and focus on important information collected and presented by the displays. Moreover, a user may transition between the display depicted in <FIG> and one or more of the displays shown in <FIG>, <FIG>, and <FIG> and vice versa responsive to a user input, such as via a user selection on one of the displays.

<FIG> illustrates controls on a display of a host device, such as the display <NUM>, for adjusting alarm limit ranges of source electronic devices. Tabs <NUM>, <NUM>, <NUM> can respectively be used to switch between viewing and adjusting alarm limits for the blood gas device, EEG monitoring device, or regional oximetry device. As shown by <FIG>, when the tab <NUM> corresponding to the blood gas device may be selected, multiple parameters monitored by the blood gas device can be presented along with corresponding upper and lower ranges for each of the parameters with some upper or lower ranges being unavailable as indicated by "--". The lines and dots, such as a line <NUM> and a dot <NUM>, can form sliders that are movable by user input to increase the upper and lower alarm limits for the parameters within ranges and may cause generation and transmission of instructions to the blood gas device to appropriately adjust the corresponding alarm limits. To diminish clutter on the display, a value corresponding to a position of a particular slider, such as the slider composed of the line <NUM> and the dot <NUM>, may not be indicated on the display other than by a value displayed alongside the particular slider, such as at area <NUM>.

Although the display may be shown as being longer than wider, the display instead may have other dimensions like being wider than longer, such as would fit the displays of <FIG>, <FIG>, <FIG>, <FIG>, and <FIG> or such as those on a mobile device.

A user can adjust the setting of a medical device on the hub <NUM>. For example, the hub <NUM> can present user interface element(s), such as, for example, slider bars to adjust alarm limits of connected medical device. Additional examples of adjusting the setting of a medical device on the hub are also described in <CIT>, entitled "SYSTEM FOR DISPLAYING MEDICAL MONITORING DATA".

The user interface controls shown herein are merely illustrative examples and can be varied. For instance, any of the user interface controls shown may be substituted with other types of user interface controls that provide the same or similar functionality. Some examples of user interface controls that may be used include buttons, dropdown boxes, select boxes, text boxes or text fields, checkboxes, radio buttons, toggles, breadcrumbs (for example, identifying a page or interface that is displayed), sliders, search fields, pagination controls, tags, icons, tooltips, progress bars, notifications, message boxes, image carousels, modal windows (such as pop-ups), date or time pickers, accordions (for example, a vertically stacked list with show/hide functionality), and the like. Additional user interface controls not listed here may be used.

Further, user interface controls may be combined or divided into other sets of user interface controls such that similar functionality or the same functionality may be provided with very different looking user interfaces. Moreover, each of the user interface controls may be selected by a user using one or more input options, such as a mouse, touch screen input (for example, finger or pen), remote control, or keyboard input, among other user interface input options.

<FIG> depicts an area <NUM> around a displayed EEG parameter value, such as PSi™ value, that can be red indicating an alarm condition for the EEG parameter value, and the brain <NUM> and an area <NUM> in a dedicated area labeled EEG monitoring which includes the displayed EEG parameter value can further be red. In addition, an audible alarm may be presented concurrently by the hub <NUM> or a EEG monitoring device used for monitoring brain activity with presentation of the red on the brain <NUM>, the area <NUM>, and the area <NUM>.

A user of the host device <NUM> can provide a user input to the host device <NUM> that causes an audible or visual alarm presented by the host device <NUM>, a source device (for example, one of the patient devices <NUM>), or the hub <NUM> to be silenced. The host device <NUM> may moreover silence alarms on any and all devices to which the host device <NUM> is connected or communicating. When silencing an audible or visual alarm of a source device, an instruction can be generated and transmitted to the source device that causes the source device to silence the audible alarm. For example, the user can provide a user input via selection of an area <NUM> on the display that causes the audible alarm presented by the hub <NUM> to be silenced or that an instruction to be generated and sent to the EEG monitoring device to silence the audible alarm.

<FIG> illustrates a EEG monitoring alarm display <NUM> where an alarm is presented by the host device <NUM>. In this example, the alarming parameter may not be viewable on the overview screen <NUM>, which may be because the priority of the alarming parameter is relatively lower compared to that of the other parameters being displayed. The EEG monitoring alarm display <NUM> shows an alarm icon <NUM> (which may be in red) when an alarm for a parameter is a triggered. In addition to the alarm icon <NUM>, the EEG monitoring alarm display <NUM> also shows a pill-shaped message <NUM> at the top-center of the screen indicating the source of the alarming parameter (for example, EEG monitoring) and the parameter that has passed the alarm limit (for example, PSi™). If more than one parameter is alarming, the parameters may be shuffled in the pill-shaped message. The display may provide other visual indications, such as, for example, a red glow pulse behind the pill-shaped message <NUM> to emphasize the alarm. The EEG monitoring alarm display <NUM> can also include the organ <NUM> corresponding to the alarming parameter. For example, the display can change show a red color for an image of the organ <NUM>.

In situations where the alarming parameter is viewable in a screen layout, the display may change the font color of the alarming parameter.

The patient data display system <NUM> can include an alarm status visualizer which can be configured to show a 3D image of a human body. The 3D image may be present on multiple layout screens, such as those shown in <FIG>, <FIG>, <FIG>, <FIG>, and <FIG>. The 3D image can display organ animations and can be color coded for alarm conditions. The animations can be updated based on as the host device <NUM> receives the values of relevant patient parameters.

<FIG> illustrates a display of 3D images, such as on the display <NUM>, where certain organs are color coded to represent the status of monitoring and alarm conditions. In this example, the lungs and hearts are highlighted in the views 900B and 900D. The lungs and heart can be animated, for example, based on data collected from sensors associated with the lungs or heart or parameters associated with the lungs or heart. For example, the lungs and heart can be animated based on parameter values, such as those shown in the blood gas window <NUM> in <FIG>. The lungs can be animated based on RRa® and RRp® parameter values, and the heart can be animated based on pulse rate (PR) parameter values.

In <FIG>, four views 900A, 900B, 900C, and 900D are illustrated for different points in time during a monitoring process. In the view 900A, the color of the lungs and the heart is shown in gray, which represents there is no monitoring because the corresponding one or more patient devices <NUM> is disconnected. The view 900B shows the color of the lungs and the heart in green indicating the successful connection to the one or more patient devices <NUM> and that the parameters being monitored are in the normal range. The view 900C shows the color of the lungs and the heart in yellow indicating that the statues, notifications, modifiers, notification devices have not been linked to a patient although the one or more patient devices <NUM> is connected. The view 900D shows the color of the lungs and the heart in red indicating that the parameter is in the alarm range while the one or more patient devices <NUM> is connected.

Fig. 10A illustrates a process <NUM> of adjusting a setting of a PoC device, such as one of the patient devices <NUM>, via a host device, such as the host device <NUM>. The process <NUM> may be performed, for instance, by the host device host device <NUM> or another device described herein. The process <NUM> can be programmed as part of the patient data display system <NUM>.

At block <NUM>, a connection can be established between a PoC device and a host device. For example, one of the patient devices <NUM> can be connected to the host device <NUM> directly or via the hub <NUM>.

At block <NUM>, the host device can monitor user inputs. For example, the host device <NUM> can determine whether a user has actuated a display of the host device <NUM>, such as the display <NUM>, or another user input device associated with the host device <NUM>.

At block <NUM>, the host device can determine whether the host device has received a user input for adjusting a setting of the PoC device. For example, a user can adjust a slider bar on the user interface presented by the host device <NUM> to adjust conditions for triggering an alarm of a patient parameter (for example, whether the value of the patient parameter is above or below a threshold condition). The user interface for adjusting the alarm may be presented in response to a user actuating an user interface element on a patient monitoring screen. As an example, the user can select the menu element <NUM> on the display <NUM> to cause the host device <NUM> to show the user interface screen for adjusting alarm limits for one or more parameters being monitored or for one or more of the patient devices <NUM> monitored by the host device <NUM>.

If the user input is not received, the process <NUM> goes back to the block <NUM> where user inputs on the host device are continuously monitored. If the user input is received, at block <NUM>, the host device can cause the PoC device to update in accordance with the adjusted setting. For example, where an alarm limit is adjust by the user, the one of the patient devices <NUM> can communicate the adjusted limit to the PoC device (either directly or through the hub <NUM>) which will cause the one of the patient devices <NUM> to generate an alarm of the associated patient parameter(s) based on the adjusted limit.

<FIG> illustrates a process <NUM> of presenting patient measurement data on a display associated with a host device. The process <NUM> can, for instance, be performed by the host device <NUM> or another device described herein and be programmed as part of the patient data display system <NUM>.

At block <NUM>, the host device can receive first measurement data gathered by a first PoC device, such as one of the patient devices <NUM>.

At block <NUM>, the host device can receive second measurement data gathered by a second PoC device, such as another of the patient devices <NUM>. The host device <NUM> can communicate with the first PoC device or the second PoC device directly (for example, via wired or wireless communications) or indirectly (such as, for example, through the hub <NUM> or another device disclosed herein).

At block <NUM>, a screen for the host device can be selected for presenting the first measurement data and second measurement data. The screen may be selected based on the types of devices being connected to the host device <NUM> for display, the types of parameters being displayed, or the priorities of types of measurement data, etc..

At block <NUM>, the host device can present the first measurement data in the first region of the display and present the second measurement data in the second region of the display. As a result, the host device <NUM> can group data based on a clinical scenario, use-case, or physiological system for a patient.

At block <NUM>, the host device can update an animation of a 3D image of a patient based at least on the first measurement data or the second measurement data. For example, the 3D image may include a portion of the user's brain or lungs. The animations of the brain or lungs may change color from green to red in response to a determination that an alarm is triggered based on the first or second data.

The layouts of the displays described herein can be customized by users, such as clinicians or other non-clinician users. The layouts, for instance, can be populated in part or fully with user-selected data presentation modules (sometimes referred to as containers or display elements) that together cover part or all of a particular layout of the display. The populated layout may then receive measurement data from one or more devices and present or animate based on measurement data. In this way, the presentation of information by the displays can be tailored for types of caregivers, procedures being performed, user preferences, or the like.

<FIG> illustrates an empty screen <NUM> on a display of a host device, such as the display <NUM>, for presenting information. The empty screen <NUM> can be divided into two areas including a footer <NUM> and a canvas <NUM>. As shown in the examples of <FIG>, <FIG>, <FIG>, and <FIG> and elsewhere herein, the footer <NUM> can include an identifier for a patient, an identifier for a room in a physical treatment facility in which the patient is being treated, or an identifier for a physiological system or a template corresponding to the display of information on the canvas <NUM>, among other information or interface controls. The canvas <NUM> can present various measurement data as, for instance, shown in <FIG>, <FIG>, <FIG>, and <FIG> or elsewhere herein, among other information or interface controls.

In one example, the canvas <NUM> can be divided into <NUM> rows of squares where each square may have a height of around <NUM>% of a height of the canvas <NUM>. The canvas <NUM> can include <NUM> squares per row with each square's width being around <NUM>% of a width of the canvas <NUM>. For a resolution of <NUM> x <NUM>, each square may be <NUM> x <NUM> pixels. In other examples, the canvas <NUM> can be divided into a different number of rows, a different size of squares or other shapes, or a different number of squares per row. One or more outer rows or columns may or may not include measurement data or user interface controls.

<FIG> illustrates a bounding box screen <NUM> on a display of a host device, such as the display <NUM>. The bounding box screen <NUM> can include bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM> that are positioned around numerical values, gauges, or trends for particular measurement data, as well as include an identifier that indicates a parameter associated with the measurement data displayed by a particular one of the bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. The bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can be moved around by on the display by a user (for example, by a drag and drop action), aligned by the display to the gridlines on the bounding box screen <NUM>, and non-overlapping with one another so that the bounding box screen <NUM> is arranged and organized. The bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be permitted to overlap in some instances. The bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be moved in a configuration mode (for example, a mode when not presenting measurement data of a patient) but not an operation mode (for example, a mode when presenting measurement data of a patient) or may be moved in any mode. Although SpO2% may be shown as the associated parameter for all of the bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, this is merely for illustrative purposes and other parameters described herein or yet other parameters may be presented via the bounding boxes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>.

<FIG> illustrates a parameter container screen <NUM> on a display of a host device, such as the display <NUM>. The parameter container screen <NUM> can include parameter containers that are various sizes, such as small, medium, large, or extra-large. The parameter containers can present measurement data in various different forms or in various different formats. The spacing between certain elements of the parameter container screen <NUM> is shown as a percentage of a particular parameter container. The size of certain elements of the parameter container screen <NUM> is shown as a number of squares of the background grid. The parameter containers can each be surrounded by a bounding box as described with respect to <FIG> and may be moved around a layout of the display by a user.

<FIG> and <FIG> illustrate trend container screens 1500A, 1500B on a display of a host device, such as the display <NUM>. The trend container screens 1500A, 1500B can include trend containers that are various sizes, such as extra-small tall or short, small tall or short, medium tall or short, large tall or short, or extra-large tall or short. The parameter containers can present measurement data in various different forms or in various different formats. The spacing between or size of certain elements of the trend container screens 1500A, 1500B is shown as a percentage of a particular parameter container. The size of certain elements of the trend container screens 1500A, 1500B is shown as a number of squares of the background grid. The trend containers can each be surrounded by a bounding box as described with respect to <FIG> and may be moved around a layout of the display by a user.

<FIG> illustrates a waveform container screen <NUM> on a display of a host device, such as the display <NUM>. The waveform container screen <NUM> can include waveform containers that are various sizes, such as small tall or short, medium tall or short, or large tall or short. The waveform containers can present measurement data in various different forms or in various different formats. The size of certain elements of the waveform container screen <NUM> is shown as a number of squares of the background grid. The waveform containers can each be surrounded by a bounding box as described with respect to <FIG> and may be moved around a layout of the display by a user.

<FIG> illustrates a human body image container screen <NUM> on a display of a host device, such as the display <NUM>. The human body image container screen <NUM> can include human body image containers that are various sizes, such as small, medium, large, or extra-large. The human body image containers can present measurement data or alarms in various different forms or in various different formats, such as is described elsewhere herein. The size of certain elements of the human body image container screen <NUM> is shown as a number of squares of the background grid. The human body image containers can each be surrounded by a bounding box as described with respect to <FIG> and may be moved around a layout of the display by a user.

<FIG> illustrates a template selection screen 1800A for selection of a template for presentation on a display of a host device, such as the display <NUM>. The template selection screen 1800A can include templates <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. As can be seen, the template <NUM> can be selected in <FIG> and displayed in the area above the templates <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. The templates <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> can include different numbers or types of containers from one another and may have different formats or organizations from one another.

<FIG> illustrates a layout screen 1800B for configuration of a display of a host device, such as the display <NUM>. The layout screen 1800B can include a vital signs tab <NUM>, a hemodynamics tab <NUM>, a oxygenation tab <NUM>, a sedation tab <NUM>, a human body image tab <NUM>, a parameter selection area <NUM>, and a search area <NUM>. The vital signs tab <NUM>, the hemodynamics tab <NUM>, the oxygenation tab <NUM>, the sedation tab <NUM>, and the human body image tab <NUM> can permit a user to adjust the parameters or measurement data that are displayed for the corresponding screens by selection from the parameter selection area <NUM> or parameter searching via the search area <NUM>.

<FIG> illustrates a layout construction screen 1800C for configuration of a display of a host device, such as the display <NUM>. The layout construction screen 1800C can include a pulse rate container <NUM> and a container slot <NUM>. As illustrated, a user can drag the pulse rate container <NUM> from a pulse rate selection area <NUM> and drop pulse rate container <NUM> in the container slot <NUM> to include the pulse rate container <NUM> as part of the layout of the screen at the container slot <NUM>.

<FIG> illustrates a setting modification screen 1800D for configuration of a display of a host device, such as the display <NUM>. The setting modification screen 1800D can include settings interface elements <NUM> for adjusting format settings associated with presentation measurement data in an added pulse rate container <NUM>. The settings interface elements <NUM> can include a numeric change element (for example, to select a formatting of a number presented by the added pulse container ), a small change element (for example, to select a size of data presented by the added pulse rate container), a color change element (for example, to select a size of information presented by the added pulse rate container), a details display element (for example, to select or configure a source, priority, or order of data presented by the added pulse rate container), and a remove element (for example, to delete the added pulse rate container from the current layout). The details display element can, in one implementation, be used to prefer one manufacturer or source of data over other so that, for instance, PR derived from oximeter data is preferred to PR derived from acoustic data and accordingly presented first if available or determined to be of a sufficient quality level. The settings interface elements <NUM> can be similarly presented and used to configure other added containers on the current layout.

<FIG> illustrates a selection search screen 1800E for configuration of a display of a host device, such as the display <NUM>. The selection search screen 1800E can include a search control area <NUM> for searching for parameters that may be displayed as part of a particular screen or template. The selection search screen 1800E can, for example, appear upon selection of the search area <NUM> of the layout screen 1800B.

<FIG> illustrates another layout construction screen <NUM> for configuration of a display of a host device, such as the display <NUM>. The another layout construction screen <NUM> can include a pulse rate container <NUM> and a container slot <NUM>. As illustrated, a user can drag the pulse rate container <NUM> from a pulse rate selection area <NUM> and drop pulse rate container <NUM> in the container slot <NUM> to include the pulse rate container <NUM> as part of the layout of the screen at the container slot <NUM>. The container slot <NUM> can be presented in an empty background template, such as by selection of the template <NUM> on the template selection screen 1800A.

<FIG> illustrates a layout saving screen <NUM> for saving a configuration of a display of a host device, such as the display <NUM>. The layout saving screen <NUM> can include a layout name area <NUM> where a user may input a template name (for example, "untitled layout 2018_05_18") for a custom layout that may be assigned and saved and then used to retrieve or share the custom layout. The custom layout can be saved locally to the host device or may be saved or shared with other devices, such as a server like the MMS <NUM> or a computer like the hub <NUM>, and in turn used by the other devices to also share or similarly display measurement data.

<FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and <FIG> illustrate example templates for presenting information including measurement data as described herein. The different templates can be usable or desirable for different care conditions, use cases, or patient treatments. The different templates can moreover serve as a starting point for a user for constructing a layout and be further customized to include or exclude particular measurement data or interface controls or present data from different sources, in a revised priority or order, or with different formatting.

The term "plethysmograph" includes it ordinary broad meaning known in the art which includes data responsive to changes in volume within an organ or whole body (usually resulting from fluctuations in the amount of blood or air it contains).

The following description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure. Although various specific parameter measurements are described herein, the specific parameter measurements may be merely illustrative of measurements that can be associated with various windows, sensors, or monitors. Additional or alternative specific parameter measurements may be used or provided.

As used herein, the term module may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC); an electronic circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; other suitable components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip. The term module may include memory (shared, dedicated, or group) that stores code executed by the processor.

The term code, as used above, may include software, firmware, or microcode, and may refer to programs, routines, functions, classes, or objects. The term shared, as used above, means that some or all code from multiple modules may be executed using a single (shared) processor. In addition, some or all code from multiple modules may be stored by a single (shared) memory. The term group, as used above, means that some or all code from a single module may be executed using a group of processors. In addition, some or all code from a single module may be stored using a group of memories.

The apparatuses and methods described herein may be implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on a non-transitory tangible computer readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage. Although the foregoing has been described in terms of certain preferred embodiments, other embodiments will be apparent to those of ordinary skill in the art from the disclosure herein. Additionally, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. Accordingly, the present disclosure is not intended to be limited by the reaction of the preferred embodiments, but is to be defined by reference to claims.

Claim 1:
An improved screen display system for providing real-time and time-critical physiological parameters to a plurality of clinicians in a surgical care setting, the improved screen display system comprising:
a display (<NUM>); and
one or more processors (<NUM>) configured to:
present, in the display (<NUM>) at a first time, a first layout area comprising a container slot (<NUM>) at a first location,
allow a first user to drag a physiological parameter container (<NUM>) from a selection area (<NUM>) and to drop it in the container slot (<NUM>) at the first location, wherein a setting interface element (<NUM>) on the display (<NUM>) allows adjusting the format of a dragged physiological parameter container (<NUM>),
wherein a measurement value of a physiological parameter may be derived from one source of data or another source of data,
wherein the setting interface element comprises a details display element which allows a user to prefer the one source of data over the another source of data by selecting measurement values derived from a preferred source of data to be displayed;
present, in the display (<NUM>) at a second time, a plurality of display areas comprising measurement values for a plurality of physiological parameters monitored for a patient, the plurality of display areas further comprising a first display area and a second display area,
wherein the first display area corresponds to the first layout area, wherein the first display area comprises (i) the measurement values for a first set of the plurality of physiological parameters corresponding to a first physiological system for the patient and (ii) a first display element corresponding to the physiological parameter container at the first location, and
wherein the second display area comprises the measurement values for a second set of the plurality of physiological parameters corresponding to a second physiological system for the patient different from the first physiological system.