Patent Grant
11270792
Certain embodiments disclosed herein relate generally to monitoring physiological parameters of a patient, and specifically to a patient monitor configured to monitor parameters of a patient.
In many healthcare settings, especially in the care of seriously afflicted cardiac patients, it is desirable or necessary for a healthcare practitioner to be able to monitor generally continuous information about a patient's physiology, such as a patient's cardiac performance or a patient's blood characteristics. Hemodynamic monitoring is typically performed to ensure tissue oxygenation in critically ill patients in different settings. A pulmonary artery catheter (PAC) can generally be used for this task in order to assess cardiac output, a primary determinant of oxygen delivery. Additionally, a variety of minimally invasive hemodynamic monitors are available to provide information of systemic flow and cardiac performance as well as intravascular fluid status. Patient monitoring devices typically include a user interface screen for displaying data acquired about the patient via sensors in communication with the patient monitoring device and with the patient.
The systems, methods and devices of the disclosure each have innovative aspects, no single one of which is indispensable or solely responsible for the desirable attributes disclosed herein. Some of the advantageous features of some embodiments will now be summarized.
The embodiments disclosed herein describe a patient monitor configured to receive patient-information electrical signals from an invasive patient sensor and a minimally invasive patient sensor, the patient monitor including a base unit and a detachable user interface unit for displaying hemodynamic parameters determined by the base unit. Embodiments of the base unit and user interface unit can be docked together, tethered together through a cabled connection, or physically separated from one another using wireless communication to transmit and receive information. Embodiments of the patient monitor can be configured to switch between invasive and minimally invasive monitoring of hemodynamic parameters of a patient, using invasive measurements to calibrate minimally invasive measurements.
The embodiments disclosed herein describe various features of the patient monitor. For example, the patient monitor can be configured to switch between invasive and minimally invasive monitoring of hemodynamic parameters of a patient and adjust the display of hemodynamic parameters accordingly. As another example, the patient monitor can include a base unit and a detachable user interface unit, where the base unit determines hemodynamic parameters using measurements received from various sensors and the detachable user interface unit displays various user interfaces. Such user interfaces can include a user interface that displays trend data for one or more hemodynamic parameters, a user interface that displays a physiological schematic with corresponding hemodynamic parameter values, a user interface that displays current and historical hemodynamic parameter values in a table, a user interface that displays a bi-variant plot of two hemodynamic parameters, a user interface that displays a hemodynamic calculator for determining output parameter values given a set of input parameter values, and/or a user interface that displays a Bolus cardiac output graph. Because a location may include multiple base units and detachable user interface units, the base unit and the detachable user interface unit can implement a pairing process at startup or when the detachable user interface unit connects or disconnects from the base unit to link a particular base unit to a particular detachable user interface unit. The pairing process can be implemented using a wired or wireless connection source between the base unit and the detachable user interface unit. As another example, the detachable user interface unit is pole-mountable and can communicate with the base unit via a wired or wireless connection. If a connection between the base unit and the user interface unit is lost, the base unit can automatically indicate whether an alarm condition has occurred without the use of the user interface unit and can automatically lower the power of a heater coupled to the base unit if the heater is active. As another example, the base unit can prioritize data sources for heart rate and mean arterial pressure calculations. Such prioritization can include prioritizing sensors coupled to the base unit via an analog input over sensors coupled to the base unit via a digital input.
One aspect of the disclosure provides a patient monitor configured to receive patient-information electrical signals from an invasive patient sensor and a minimally invasive patient sensor. The patient monitor includes a base unit having a housing forming a docking base and a front plate, the docking base including a base unit connector; a plurality of sensor input connectors on an exterior portion of the housing, at least one sensor input connector configured to receive electrical signals from an invasive patient sensor and at least one sensor input connector configured to receive electrical signals from a minimally invasive patient sensor; a wireless communication system comprising an antenna and a transceiver enclosed within the housing; and a latch attached to the housing. The patient monitor further includes a user interface unit having a housing with a bottom portion and a rear portion; a display on a front portion of the user interface unit, the display configured to display hemodynamic parameters determined by the base unit based on the received patient-information electrical signals; a wireless communication system enclosed within the housing; and a user interface connector on the bottom portion of the housing, the user interface connector configured to mate with the base unit connector. In a docked configuration, the user interface connector is configured to directly couple to the base unit connector and the bottom portion of the housing of the user interface unit is configured to contact the docking base of the base unit and at least a portion of the rear portion of the housing of the user interface unit is configured to contact the front plate of the housing of the base unit, and the latch is configured to secure the user interface unit to the base unit. In a tethered configuration, the user interface connector is electrically coupled to the base unit connector using a cable, the cable conducting electrical power and electrical signals between the base unit and the user interface unit. In a detached configuration, the wireless communication system of the user interface unit is configured to wirelessly communicate with the wireless communication system of the base unit.
The patient monitor of the preceding paragraph can include any sub-combination of the following features: where the minimally invasive patient sensor comprises at least one pressure sensor configured to be in fluid communication with a patient's blood vessel through a fluid-receiving region in the pressure sensor and configured to be in electrical communication with the base unit, the pressure sensor being configured to sense a pressure wave in the patient's vasculature and being configured to transmit at least one patient-information electrical signal to the base unit that indicates a hemodynamic parameter of a patient; where the base unit is configured to determine a hemodynamic parameter of a patient based on the patient-information electrical signals received from the invasive patient sensor during a first time period and to determine the hemodynamic parameter of the patient based on the patient-information electrical signals received from the minimally invasive patient sensor during a second time period after the first time period, wherein the hemodynamic parameter based on the patient-information electrical signals received from the minimally invasive patient sensor is calibrated using the patient-information electrical signals received from the invasive patient sensor; where the patient monitor is configured to switch between determining the hemodynamic parameter of the patient based on the patient-information electrical signals received from the invasive patient sensor and determining the hemodynamic parameter of the patient based on the patient-information electrical signals received from the minimally invasive patient sensor; where the docking base is sloped so that liquid flows off of the docking base when the user interface unit is docked on the base unit; where the patient monitor further includes a plurality of analog signal input connectors configured to receive an analog input signal from an external patient monitor system; where the base unit is configured to automatically convert received signals to a physiological parameter based on a maximum expected value of the physiological parameter and a received maximum analog signal from the external patient monitor system; where the user interface unit receives an indication of the maximum expected value of the physiological parameter through an interaction of a user with the display; where the base unit further comprises a conducting portion configured to act as a ground plane for the antenna of the wireless communication system so that a resulting radiation pattern of the antenna preferentially transmits electromagnetic energy in a forward direction relative to the base unit; where the docking base and base unit connector are configured so that the user interface unit cannot be docked on the base unit with the display portion adjacent to the front plate; and where the user interface unit and the base unit are configured such that, in the tethered configuration, the user interface unit cannot be seated in the docking base so that the latch secures the user interface unit in place on the base unit.
Another aspect of the disclosure provides a method for providing an alarm for a patient monitoring system comprising a base unit and a detachable user interface unit when the detachable user interface unit is not electrically coupled to the base unit through a cable or connector. The method includes determining a presence of one or more alarm conditions based at least in part on a value of a hemodynamic parameter of a patient based on patient-information electrical signals received from an invasive patient sensor or a minimally invasive patient sensor. The method includes determining whether the user interface unit is in wireless communication with the base unit. The method includes signaling an alarm on the base unit if there is at least one alarm condition and there is no wireless communication between the user interface unit and the base unit. The method includes signaling an alarm on the user interface unit if there is at least one alarm condition and the user interface unit is wirelessly communicating with the base unit.
The method of the preceding paragraph can include any sub-combination of the following features: where the at least one alarm condition comprises an alarm indicating that at least one hemodynamic parameter is outside a tailored range of accepted values; where the method further includes not signaling the alarm on the base unit if there is at least one alarm condition and the user interface unit is wirelessly communicating with the base unit; where signaling the alarm comprises providing a visual indication of the alarm; and where signaling the alarm comprises providing an audible indication of the alarm.
Another aspect of the disclosure provides a method for controlling a heater coupled to a patient sensor for a patient monitoring system comprising a base unit and a detachable user interface unit when the detachable user interface unit is not electrically coupled to the base unit through a cable or connector. The method includes iteratively commanding the heater to be in a low power state for a first period of time and to be in a high power state for a second period of time. The method includes determining whether the user interface unit is in wireless communication with the base unit. The method includes monitoring a length of time where there is no wireless communication between the user interface unit and the base unit. The method includes setting the power of the heater to be in the low power state if the length of time exceeds a time threshold.
The method of the preceding paragraph can include any sub-combination of the following features: where the length of time is less than or equal to about 2 minutes; where the first period of time is less than or equal to about 20 seconds; where the first period of time is the same duration as the second period of time; where the low power state comprises providing less than or equal to about 200 mW of power to the heater; and where the high power state comprises providing at least about 7.5 W of power to the heater.
The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the disclosure. Throughout the drawings, reference numbers may be re-used to indicate general correspondence between referenced elements.
Various aspects of the disclosure will now be described with regard to certain examples and embodiments, which are intended to illustrate but not to limit the disclosure. Nothing in this disclosure is intended to imply that any particular feature or characteristic of the disclosed embodiments is essential. The scope of protection of certain inventions is defined by the claims.
Example Critical-Care Patient Monitoring System
As illustrated in the example of
As a patient's heart beats, a pressure wave is transmitted through the patient's interconnected system of blood vessels (e.g., veins and arteries). The pressure wave provides information about the patient's cardiac performance, which can be electrically transmitted from the patient sensor 120 to the patient monitor 110, such as by way of a wired connection 160 or a wireless connection. The information about the patient's cardiac performance can be derived or calculated through a mathematical analysis performed by the patient monitor 110 (e.g., through the base unit 115) of the shape of the pressure wave, the ways in which the pressure wave changes over time, and/or the like. As shown, the patient sensor 120 can be positioned on a suitable holding structure 140, such as a pole stand or other holder, and the patient sensor 120 can be in fluid communication with a liquid source 170.
The patient sensor 120, such as a cardiac monitoring sensor, can be configured to transform mechanical motion into electrical energy, such as a pressure sensor that produces an electrical signal that changes over time in response to changes in fluid pressure. The patient sensor 120 can comprise a fluid channel that is in communication with the transducer. The fluid channel can form part of, or be attached to, or otherwise be positioned in fluid communication with, the medical catheter 150 or other tubing or device in fluid communication with a patient's vessel. A distal end of the medical catheter can be inserted into a patient's blood vessel, in contact with the patient's blood, in a conventional manner.
The medical catheter 150 can contain a column of biocompatible fluid, such as saline and/or blood, that interfaces with the blood flowing inside of a patient's blood vessel (e.g., a vein or an artery). The column of fluid can be provided by a liquid source 170, such as an IV bag, that is pressurized or that is gravity-fed into the patient sensor 120, which can be disposed in fluid communication with the patient sensor 120. As the pressure wave from the patient's beating heart is transmitted through the patient's blood vessel, the wave is communicated through fluid interaction with the blood into the column of fluid inside the medical catheter 150 at or near the transducer, where the fluid pressure wave can be converted into a cardiac monitoring electrical signal and transmitted by an electrical wire 160 or wirelessly to the patient monitor 110. The patient monitor 110 can be programmed to analyze the cardiac monitoring electrical signal to provide physiological information about the patient, such as cardiac performance information (e.g., pulse rate, blood pressure such as systolic pressure and/or diastolic pressure, cardiac output, etc.).
In addition to, or instead of, providing cardiac performance information, a blood parameter sensor can be provided with a medical catheter configured to convey information about one or more blood parameters, such as one or more of: a blood gas level (e.g., oxygen and/or carbon dioxide, etc.), a pH level, a hemoglobin level, a hematocrit level, a glucose level, a blood temperature, etc. In some embodiments, one or more blood parameters can be determined by measuring characteristics of light waves that are transmitted into and/or reflected from the blood or another substance in communication with the blood, such as through a system of one or more fiber optic light-transmitting and/or light-receiving cables. In some embodiments, one or more blood parameters can be determined by placing one or more sensors in close communication with the blood, such as a temperature-sensing thermistor suspended in the blood or positioned near the blood.
The patient sensor 120, whether a cardiac-monitoring sensor and/or a blood-parameter sensor, or some other form of patient sensor, can be structured, positioned, and/or oriented in a variety of different ways. The patient monitoring system 100 can be configured to switch, for example, from monitoring hemodynamic parameters derived from data provided by a patient sensor at a pulmonary artery catheter, to monitoring hemodynamic parameters derived from data provided by a patient sensor in a peripheral venous line or a peripheral arterial line. For example, cardiac output of a patient can be measured where an arterial blood pressure waveform of the patient is obtained from a blood pressure monitoring device over a period of time to determine the pulsatility and heart rate of the patient. The nominal stroke volume can then be calculated from the pulsatility and the heart rate. In some embodiments, the hemodynamic parameters derived using minimally invasive techniques (e.g., a sensor in a peripheral venous or arterial line), such as the nominal stroke value, can be calibrated based on the hemodynamic parameters derived using invasive techniques (e.g., thermodilution). Advantageously, this can allow the same patient monitor 110 to obtain, store, and apply calibration factors when switching from monitoring a patient using invasive techniques to minimally-invasive techniques. This can provide the benefit of the patient monitor 110 being able to display hemodynamic parameters obtained through minimally invasive techniques that are calibrated to more accurate measurements obtained using invasive techniques.
For example, the patient monitor 110 can be configured to acquire, derive, and display continuous cardiac output (CCO) and cardiac output derived from pulsatility data. Using the Stewart-Hamilton equation, the patient monitor 110 can calculate cardiac output by the use of an intravascular indicator (e.g., saline) injected into a central or peripheral vein and measured in a peripheral artery using a specialized sensor probe attached to the pressure line (referred to herein as lithium dilution). The patient monitor 110 can use the cardiac output obtained with lithium dilution to calibrate a nominal stroke volume value derived from the arterial blood pressure waveform using a PULSECO algorithm. Alternatively or in addition, the patient monitor 110 can measure cardiac output by implementing other techniques, such as by implementing the cardiac output measurement techniques provided in U.S. Pat. No. 6,071,244 to Band et al., and in U.S. Pat. No. 6,216,094 to Fox Linton et al., each of which is incorporated by reference herein in its entirety. The PULSECO algorithm method is based at least in part on the principles of conservation of mass and power. The patient monitor 110 can calculate stroke volume from an analysis of the stroke volume induced pulsatile change in the arterial blood pressure waveform. The PULSECO algorithm transforms the arterial blood pressure waveform from pressure to a volume equivalent through a compliance and aortic volume correction maneuver. For example, using a lookup table that maps arterial blood pressure values to arterial volume values and that is stored in memory of the patient monitor 110, the patient monitor 110 can use the arterial blood pressure waveform as the basis for calculating a continuous curve describing the general form of the arterial volume changes with every cardiac cycle for which arterial blood pressure is available. The patient monitor 110 can autocorrelate the volume waveform to derive the beat period (e.g., heart rate) and input pulsatile volume change (e.g., stroke volume). The patient monitor 110 can then determine cardiac output by multiplying the stroke volume by the heart rate.
The cardiac output determined by the patient monitor 110 based on the stroke volume and heart rate may be referred to as a pre-calibration cardiac output (COpre). The patient monitor 110 may use a calibration factor, C, to calibrate the stroke volume values derived from the autocorrelation of the volume waveform and, therefore, to calibrate the calculated pre-calibration cardiac output. The calibration factor, C, can be obtained by entering a known cardiac output, COk, such as a cardiac output obtained through invasive techniques (e.g., thermodilution) or lithium dilution. The calibration factor, C, can then be: C=COk/COpre. The calibration factor, C, may also be determined using a nomogram, which calculates the calibration factor using, at least in part, the patient's age, height, gender, and weight. The cardiac output displayed by the patient monitor 110, then, can be CO=C*COpre.
In some embodiments, when switching from determining cardiac output using invasive patient sensors (e.g., pulmonary artery catheters, central venous oximetry catheters, etc.) to determining cardiac output using minimally invasive patient sensors (e.g., CARDIOFLO™ cardiac output sensors, oximetry catheters, etc.), the patient monitor 110 can use the last measurement or a recent measurement of cardiac output determined using the invasive patient sensors to calibrate the cardiac output determined using the minimally invasive patient sensors. In some embodiments, the patient monitor 110 can display the cardiac output determined using the minimally invasive patient sensors as a trend without being calibrated. The display of the uncalibrated trend information can continue until calibration occurs, at which time the patient monitor 110 can adjust the display of the cardiac output to display calibrated cardiac output information. In certain implementations, the cardiac output measurements derived from minimally invasive patient sensors can be calibrated manually (e.g., the patient monitor 110 can receive a calibration factor from a user of the patient monitor 110, such as through the user interface unit 117).
In some embodiments, when switching from invasive to minimally invasive cardiac output monitoring, the patient monitor 110 uses parameters derived from invasive cardiac monitoring to calibrate the parameters derived from the minimally invasive cardiac monitoring. In certain implementations, the patient monitor 110 can update more frequently (e.g., from beat to beat of the heart, every 10 seconds, etc.) one or more of the parameters derived using minimally invasive patient sensors than one or more parameters derived using invasive patient sensors (e.g., which may be updated about every 2 minutes). For example, continuous cardiac output calculated using an invasive patient sensor can take about 2 minutes to acquire. This calculated cardiac output, however, can be a calibrated and accurate measurement of cardiac output. In comparison, cardiac output calculated using data from a minimally invasive patient sensor (e.g., a CARDIOFLO™ cardiac output sensor) can be updated from beat to beat of the heart, but is uncalibrated. In some embodiments, before switching between displaying calibrated and uncalibrated hemodynamic parameters, the patient monitor 110 can be configured to wait at least a predetermined period of time. In some embodiments, the predetermined period of time is about 2 minutes, at least about 4 minutes, or at least about 6 minutes.
In some embodiments, the patient monitor 110 can be configured to operate based on data from invasive patient sensors when an invasive patient sensor is connected to the patient monitor 110, excluding operations based on data and/or discarding data from minimally invasive patient sensors until the invasive patient sensor is disconnected. In some embodiments, the patient monitor 110 can display information derived from the invasive patient sensor after switching to a minimally invasive patient sensor until the parameters derived from the minimally invasive patient sensor are calibrated and/or after a tailored period of time (e.g., about 2 minutes, about 4 minutes, about 8 minutes, etc.). This can reduce potentially misleading changes in displayed hemodynamic parameters when switching between invasive patient sensors and minimally invasive patient sensors. In some embodiments, the patient monitor 110 can be configured to operate based on data from invasive patient sensors when the patient monitor 110 is operating in a mode that utilizes invasive patient sensors, excluding operations based on data and/or discarding data from minimally invasive patient sensors until the patient monitor 110 is operating in a mode that utilizes minimally invasive patient sensors. In some embodiments, the patient monitor 110 can be configured to display on the user interface unit 117 options for selecting which monitoring techniques are to be employed (e.g., choosing between measurements based on invasive or minimally invasive patient sensors).
The user interface unit 117 can be implemented with or without embedded processing capabilities and is releasably attached to the base unit 115.
As illustrated in
As illustrated in
As illustrated in
The patient monitor 110 of the critical-care patient monitoring system 100 can comprise a computer processor housed in the base unit 115, memory housed in the base unit 115 that stores hemodynamic parameters determined for a current patient and one or more (e.g., 3, 4, 5, etc.) previous patients, wherein the base unit 115 can be configured to determine one or more hemodynamic parameters based at least in part on information obtained from the patient sensor 120, a user interface unit 117 configured to display physiological information about the patient (including one or any combination of any of the physiological information that the base unit 115 is configured to determine), a power source (such as a battery or a power cord), and one or more electrical connectors, 270, 240 configured to establish an electrical connection with the patient sensor 120, such as by way of an attachment with one or more electrical connectors 240 that form part of the patient sensor 120. The base unit 115 of the patient monitor 110 can be configured to receive one or more patient-information electrical signals that convey information about a patient's physiological conditions. The user interface unit 117 is detachable from the base unit 115. The base unit 115 includes the one or more processors and other electrical circuitry used in processing the signals to determine the monitored hemodynamic parameters. In certain implementations, the user interface unit 117 does not calculate any of the monitored hemodynamic parameters that it displays.
In some healthcare settings, the distance between the transducer portion of the patient sensor 120 and the patient monitor 110 can be significant, such as when the transducer is positioned on a pole stand 140 or in some other location relatively close to the entry point of the medical catheter into the patient's body (such as into the patient's arm 130 or some other location) and the patient monitor 110 is located on a stand in a hospital room several feet away from the entry point. A fluid catheter 145 attached to the patient can be connected to the fluid line 150 from the sensor 120 by way of a pair of fluid connectors, such as corresponding male and female fluid connectors 155, 175. The detachable user interface unit 117 can advantageously allow the user interface unit 117 to be mounted at a convenient location for hospital personnel, such as when the position of the base unit 115 is dictated or influenced by the patient sensor 120, geometry of the patient's room, access to power cords, or the like. This allows the healthcare professional to mount the user interface unit 117 somewhere more convenient or to leave the user interface unit 117 detached and unmounted (e.g., portable).
In some embodiments, the electrical connection with the patient sensor 120 is achieved by attaching an electrical connection portion 240 of the patient sensor 120 to a proximal electrical connection portion of the non-disposable cable, and then attaching a distal connection portion of the non-disposable cable 270 to an electrical connection portion of the computer monitor.
The electrical information can be conveyed in some embodiments wirelessly, such as by way of an electromagnetic short-range signal, such as over a Wi-Fi network or by way of a BLUETOOTH or ZigBee signal, or by some other wireless protocol that is acceptable or utilized in a healthcare setting. Any description or illustration in this specification of an electrical wire 160, 250, or electrical connection 240 can be accomplished in a wireless manner and such descriptions or illustrations of wires or electrical connections should be understood to also refer to and encompass wireless connections.
Example Base Unit of a Patient Monitor
The base unit 315 includes a latch 306 configured to secure the user interface unit 117 in place when docked on the base unit 315. The latch 306 can be configured to be actuated to alternately secure and release the user interface unit 117. When docked with the base unit 315, the latch 306 can be configured to sufficiently secure the user interface unit 117 to the base unit 315 so that a user can move the base unit 315 without having to independently secure or hold the user interface unit 117 against the base unit 315. In some embodiments, the latch 306 is configured to sufficiently secure the user interface unit 117 against the base unit 315 so that the units can be treated as a unitary patient monitor. For ease of handling, a handle 312 can be provided on the base unit 315. The handle 312 can be stowed in a first position so as to be substantially aligned with a top portion of the housing 301, and can be raised in a second position, raising above the top portion of the housing 301, to facilitate carrying and moving the base unit 315. The handle 312 can be configured to allow a user to carry the base unit 315 with one hand while the user interface unit 117 is docked on the base unit 315.
The docking base 302 can be configured to be generally tilted with respect to horizontal so that liquid tends to run off the docking base 302 rather than pooling. In addition, in some embodiments, the docking base 302 can generally slope from the exterior edges towards a central or mid-point so that liquids generally tend to run towards the mid-point and flow off of the docking base 302. For example, when the user interface unit 117 is docked on the base unit 315, the connectors of the units can mate and any liquid can run off the docking base 302 rather than pooling around and/or damaging the connector 303 or the electrical contacts of the connector 303 or the connector on the user interface unit 117.
Example Base Unit and User Interface Unit of a Patient Monitor
The user interface unit 317 can include a connector 323 configured to mate with the connector 303 on the base unit 315 when the user interface unit 317 is seated against the docking base 302. The connector 323 and connector 303 can be configured to mate together in one configuration so that the display 319 of the user interface unit 317 faces outward, away from the front plate 304 of the base unit 315. In some embodiments, the housing 301 of the base unit 315 includes one or more features that prevents the user interface unit 317 from being docked on the base unit 315 so that the display 319 faces the face portion 304 of the base unit 315. In some embodiments, the user interface unit 317 includes one or more features that prevents the user interface unit 317 from being docked on the base unit 315 so that the display 319 faces the face portion 304 of the base unit 315.
The connector 323 of the user interface unit 317 and the connector 303 of the base unit 315 can be configured to be electrically coupled using a cable that connects to both of the connectors. This configuration can be referred to as tethered, or the user interface unit 317 is tethered to the base unit 315 when the connectors are coupled using a cabled connection. When tethered, the configuration of the connectors can be such that the user interface unit 317 cannot be docked on the base unit 315 when tethered. For example, to dock the user interface unit 317 to the base unit 315 after being tethered, the cable coupling the connectors should be removed to allow the user interface unit 317 to seat correctly in the docking base 302 so that the connectors mate.
Example Wireless Communication System of a Base Unit
The wireless communication system 421 can include an omni-directional antenna 420 configured to send and receive wireless communication from the user interface unit, for example. In certain implementations, the antenna 420 can interact with the ground plane 423 to provide a directional wireless signal. For example, the ground plane 423 can act to reduce electromagnetic waves produced by the antenna 420 that exit the housing 401 out of the rear of the housing 401. Similarly, the ground plane 423 can effectively act as an electromagnetic reflector for the antenna 420, redirecting radiated energy in a forward direction relative to the base unit 415. This can allow the effective radiation pattern of the antenna 420 to appear to be directional even though the antenna 420 is omni-directional. This can advantageously increase wireless range forward of the base unit 415, potentially allowing the user interface unit 317 to be used from farther away than if there were no ground plane configured to increase forward projection of radio frequency energy emitted by the antenna 420. This can also be advantageous because it is generally more likely that the user interface unit 317 is to be used while the user interface unit 317 is in front of the base unit 415 rather than when the user interface unit 317 is behind the base unit 415.
In some embodiments, the design of the wireless communication system 421 and/or antenna 420 is configured to transfer energy to the housing 401 so the housing 401 acts as a transmitter or acts to enhance the transmission and reception capabilities of the antenna 420. This may occur due at least in part to the proximity of the antenna 420 to the housing 401, the housing including one or more electrically conducting plates. In this way, the housing 401 can act to enhance the way radio frequency energy is radiated by effectively reflecting the RF signal produced by the antenna 420. In some embodiments, the antenna 420 is a stamped metal antenna having a ground plane on a printed circuit board. The housing 401 of the base unit 415 can at least partially be a metal housing. The metal housing, in some implementations, can increase the effective size of the ground plane which thereby increases the reflective properties of the housing 401 and antenna 420, thereby increasing radiation strength.
Using a Detachable User Interface Unit Separated from a Base Unit
In some embodiments, the base unit 515 can use the strength or presence of the wireless signal from the user interface unit 517 as a proxy for a proximity sensor. For example, when the base unit 515 detects a wireless signal from the user interface unit 517, the base unit 515 can indicate that a compatible or suitable user interface unit 517 is sufficiently close to the base unit 515 to function properly or adequately.
In some embodiments, when the base unit 515 determines that the user interface unit 517 is too far from the base unit 515 (e.g., because no wireless signal is detected or a wireless signal below a threshold strength is detected), one or more alarms can be provided at the base unit 515. In addition, in such circumstances, specialized control functions can be implemented to increase safety of the patient. Examples of processes or methods related to the relative positions of the base unit 515 and the user interface unit 517 are described in greater detail herein with reference to
Example Features of a Base Unit
The analog signal inputs 626 can be configured to receive an analog signal from one or more external monitoring systems. The base unit 615 can be configured to receive the analog signals for conversion into an appropriate parameter for display. For example, an external monitor system can be configured to measure end-systolic volume in mL. The external monitor system can include an analog output that outputs an analog voltage signal correlated to the measured end-systolic volume. When coupling the analog output from the external monitor system to the base unit 615, the base unit 615 can be configured to expect a max voltage signal corresponding to a maximum voltage that may be put out by the external monitor unit. A user can use the user interface unit 517 to input a maximum measured value (e.g., 150 mL for the end-systolic volume) corresponding to the maximum voltage sent by the external monitor system. The base unit 615 can use this information to subsequently scale the received analog voltage to map it to an appropriate value for the measured parameter, as measured by the external monitoring system. As a particular example, if the user inputs that the maximum measured value is 150 mL, and the external monitor sent a 10 V signal to indicate the maximum output voltage corresponding to the maximum measured voltage, the base unit 615 can be configured to multiply the received analog voltage by 15 mL/V to convert the analog signal into the appropriate measured value for display. This can allow the base unit 615 to incorporate measurements from external systems for display on the user interface unit 517. In some embodiments, the base unit 615 can include 2 analog inputs, 2 or more analog inputs, 3 or more analog inputs, 4 or more analog inputs, 5 or more analog inputs, or 6 or more analog inputs. In some embodiments, the base unit 615 can be configured to receive both a high signal and a low signal to indicate the upper and lower bounds of potential signals on the analog signal inputs 625.
In some embodiments, the base unit 615 can be configured to read a sufficiently large dynamic range of input voltages at the analog signal inputs 626 so that an expected voltage range does not need to be entered into the base unit 615. Rather, the base unit 615 can be configured to receive input indicating a largest (and smallest) expected measured value and that value can be correlated with analog input signal(s) received from an external monitor system, wherein the received analog signal(s) corresponds to a maximum (minimum) analog voltage corresponding to the largest (smallest) expected measured value.
In some embodiments, not shown, the base unit 615 includes one or more digital inputs and/or one or more serial inputs in place of the one or more analog inputs 626 or in addition to the one or more analog inputs 626. The base unit 615 may prioritize data sources if more than one sensor is coupled to the base unit 615. For example, if a cardiac output sensor (e.g., a CARDIOFLO™ sensor) is coupled to the base unit 615, a second sensor is coupled to an analog input, and/or a third sensor is coupled to a digital input, the base unit 615 may process data received via the cardiac output sensor first, process data received via the analog input 626 second, and process data received via the digital input third. In some embodiments, the base unit 615 ignores or discards data received via the analog input 626 and the digital input while data continues to be received from the cardiac output sensor. If an error occurs and/or data is no longer received from the cardiac output sensor (e.g., the cardiac output sensor malfunctions or is disconnected), then the base unit 615 may begin to process data received via the analog input 626 and ignore or discard data received via the digital input. If an error occurs and/or data is no longer received from the cardiac output sensor and the analog input 626 (e.g., the cardiac output sensor and/or the sensor coupled to the analog input 626 malfunction or are disconnected), then the base unit 615 may begin to process data received via the digital input. As another example, if a thermal coil cable (e.g., to perform thermodilution) and a cardiac output sensor are both coupled to the base unit 615, the base unit 615 may cause the user interface unit 517 to display a user interface requesting a practitioner to select either the PA catheter cables or the cardiac output sensor cable for use in determining the hemodynamic parameter values. Thus, in some embodiments, the base unit 615 can allow the user to elect fully or minimally invasive measurements. Once elected, the base unit 615 may further require the unelected input to be disconnected from the base unit 615 (e.g., via a prompt presented on the user interface unit 517).
In some embodiments, when the base unit 615 loses a wireless connection with the user interface unit 517, the display screen 605 of the base unit 615 can be activated and/or configured to display this information. In some embodiments, such as where the user interface unit 517 is separated and no longer in wireless communication with the base unit 615, the display screen 605 can be configured to display alarm statuses or current alarms. This can be advantageous where a user interface unit 517 is misplaced, broken, or otherwise unavailable so that the healthcare professionals can sufficiently monitor the patient.
The display screen 605 of the base unit 615 can be configured to indicate a state of a heater used in patient monitoring (e.g., power state, power level, etc.). The display screen 605 can be configured to indicate a connection state between the base unit 615 and the user interface unit 517. The display screen 605 can be configured to provide a reduced or minimal display for selected, predetermined, and/or critical hemodynamic parameters.
Example Method for Providing Alarms in a Patient Monitor with a Detachable Display
In block 705, the base unit monitors incoming patient sensor electrical information for potential alarm conditions. The base unit can also monitor other communication channels, such as a network channel, or analog signal channels, to determine if an alarm, warning, or other alert is to be provided on the patient monitor. For example, the base unit can be configured to calculate one or more hemodynamic parameters from the received information (e.g., from patient sensors and/or external monitor systems). The determined values can be compared to alarm conditions set on the base unit, where the alarm conditions can be automatically calculated, set, or determined and/or manually set.
In block 710, the base unit monitors a wireless signal from the user interface unit. The base unit can be configured to determine whether the user interface unit is still in communication with the base unit. For example, the base unit can send a request for acknowledgement to the user interface unit. If no reply is received within a tailored period of time, then the base unit decides that the user interface is not in communication with the base unit. Other methods of determining wireless connection can be used as well. For example, the user interface unit can be configured to periodically ping the base unit, and if the base unit determines that it has missed one or more pings from the user interface unit, then the base unit can decide that the user interface is not in communication with the base unit.
In block 715, the base unit determines whether an alarm condition exists. An alarm condition exists, for example, if one or more determined hemodynamic parameters, or a combination of parameters, triggers a selected, predetermined, or tailored alarm condition. An alarm condition may also exist where a peripheral device signals an alarm to the patient monitor. An alarm condition may also exist where a hospital communication network initiates an alarm condition through a network connection with the base unit. If no alarm condition exists, then the base unit can return to block 705 to monitor alarm conditions. If an alarm condition exists, then the base unit can proceed to block 720 to determine whether a wireless signal exists between the base unit and the user interface module.
If wireless communications are established and continuing between the base unit and the user interface unit as determined in block 720, then the base unit proceeds to block 730 where the base unit sends the alarm condition(s) to the user interface unit for display. If no wireless communications are currently established, then the base unit proceeds to block 725 to display and/or sound an alarm. For example, the base unit can include a speaker and/or a display or lights to indicate audibly and/or visually that an alarm condition has occurred. In this way, the patient monitor system can be configured to preferably alarm on the user interface unit and to fall back to the base unit where the user interface unit is out of communication with the base unit. This redundancy can ensure that alarms are signaled when they occur, regardless of whether the user interface unit is present in the room, on, or functioning. This can also reduce alarm fatigue, which may occur where users hear multiple alarms and/or frequent alarms to the point where the user begins to ignore the alarms.
In some embodiments, the base unit can be configured to track one or more alarms when the user interface unit is disconnected. Upon re-establishing a connection, the base unit can send the one or more alarms to the user interface unit.
Example Method for Controlling a Heater in a Patient Monitor with a Detachable Display
In block 805, the patient monitor sets the heater to a low power setting. For example, the low power setting can be less than or equal to about 150 mW, less than or equal to about 200 mW less than or equal to about 300 mW, or less than or equal to about 500 mW. This low power can be clinically safe to the patient even if the heater were to remain at this power for an extended period of time.
In block 810, the base unit monitors a wireless signal from the user interface unit. The base unit can be configured to determine whether the user interface unit is still in communication with the base unit. For example, the base unit can send a request for acknowledgement to the user interface unit. If no reply is received within a tailored period of time, then the base unit decides that the user interface is not in communication with the base unit. Other methods of determining wireless connection can be used as well. For example, the user interface unit can be configured to periodically ping the base unit, and if the base unit determines that it has missed one or more pings from the user interface unit, then the base unit can decide that the user interface is not in communication with the base unit.
In block 815, the base unit monitors a timer to determine the amount of time that the heater has been in a particular state (e.g., at a particular power level) and/or to determine the amount of time since the last wireless communication with the user interface unit.
If wireless communications are established and continuing between the base unit and the user interface unit as determined in block 820, then the base unit proceeds to block 825 to control the heater. To control the heater, the base unit can command the heater to turn on to a high setting (e.g., about 12 W) for a period of time (e.g., about 20 s) followed by turning the heater to a low setting (e.g., about 150 mW) for the same period of time (e.g., about 20 s). The amount of times that the heater is in the high setting and/or the low setting can vary and can be varied during operation to achieve targeted goals. For example, the high setting can comprise providing at least about 8 W of power to the heater, at least about 7.5 W of power to the heater, at least about 10 W of power to the heater, at least about 12 W of power to the heater, or at least about 15 W of power to the heater. The low power setting time can be different from the high power setting. The low power setting or the high power setting can be applied for at least about 10 s, at least about 15 s, at least about 20 s, at least about 30 s, or at least about 60 s.
If wireless communications have been determined to be down for longer than a threshold period of time, as determined in block 820, then the base unit proceeds to block 830 to set the heater to a low setting to reduce the chances of injury to the patient. In addition, the patient monitor can be configured to mark or label data acquired during this period as faulty or bad data. For example, the displayed trends or values on the user interface unit can be displayed with an asterisk, with a particular color, or the like to show that the data is unreliable and/or that there may be a problem with the communication between the user interface unit and the base unit. In some embodiments, the threshold period of time is at least about 40 s, at least about 60 s, at least about 80 s, at least about 100 s, at least about 120 s, or at least about 140 s. In some embodiments, the threshold period of time is at least about 40 s and/or less than about 140 s. In some embodiments, if wireless communications have not been reestablished before the timer indicates the threshold period of time has run, then the heater is set to low. If, however, wireless communications are re-established, then the heater can continue to be controlled in the same manner as before.
Example User Interfaces Displayed by the User Interface Unit
When the patient monitor 110 is initialized, the user interface unit 117 may display a user interface or screen requesting a practitioner or user to identify (e.g., via a touch screen input) whether a new patient is being monitored by the patient monitor 110, whether a previously entered patient (e.g., a current patient) is being monitored by the patient monitor 110, or whether a patient is being transferred to another area of a hospital (e.g., from an operating room to an intensive care unit). If the practitioner identifies that a current patient is being monitored, then the base unit 115 resumes monitoring the patient. If the practitioner identifies that a patient is being transferred, then the base unit 115 may transfer information associated with the patient to another base unit 115 (e.g., a base unit located in the area where the patient is being transferred) via a wired and/or wireless network. Otherwise, if the practitioner identifies that the patient is new, then the user interface unit 117 may display a user interface that allows the practitioner to input via a touch screen or external input device (e.g., a mouse, a keyboard, a stylus, etc.) patient information (e.g., patient ID, gender, height, weight, age, hemodynamic parameter values, etc.).
Once the patient information is entered or the current patient option is selected, the user interface unit 117 can display a main menu from which one of several user interfaces can be accessed. For example, the user interfaces can include various hemodynamic parameter monitoring user interfaces, an arterial waveform setup and calibration user interface, an oximetry calibration user interface, a hemodynamic calculator user interface, and/or a system configuration user interface. The main menu user interface displayed by the user interface unit 117 allows a practitioner to view entered patient information; perform a pre-insertion calibration, light intensity baseline, and/or in vivo calibration of a light intensity signal received from a cable; enter lab results; inspect, zero, and/or calibrate an arterial blood pressure waveform; mark events on a trend plot of hemodynamic parameter values; export hemodynamic parameter values stored in memory of the base unit 115 (e.g., hemodynamic parameter values for a current patient and/or one or more previous patients) via a wireless connection, a base unit 115 port (e.g., a universal serial bus (USB) port), and/or the like; and/or configure the patient monitor 110.
One or more of the hemodynamic parameters may be associated with a symbol or shape and/or a specific color. For example, hemodynamic parameter P1 is associated with a circle, hemodynamic parameter P2 is associated with a square, hemodynamic parameter P3 is associated with a triangle, hemodynamic parameter P4 is associated with an upside-down triangle, and each of the hemodynamic parameters P1-P4 is associated with a different color. Given that graph 910 depicted in the user interface 900 displays the historical trends for each of the hemodynamic parameters P1-P4, the symbols and/or colors can be used to differentiate between the different historical trends (e.g., the historical trend line can be a color associated with the appropriate hemodynamic parameter and/or the historical trend line can be shaded a color associated with the appropriate hemodynamic parameter).
In an embodiment, the historical trend for a hemodynamic parameter can be temporarily hidden from the user interface 900 via a selection (e.g., a touch screen selection) of the y-axis of the respective hemodynamic parameter. For example, if the practitioner would like to hide historical trend 920, which corresponds with hemodynamic parameter P3, the practitioner can select the y-axis corresponding to hemodynamic parameter P3.
The user interface 900 may also numerically indicate upper and/or lower limits for one or more of the hemodynamic parameters P1-P4. If the value of a hemodynamic parameter P1-P4 falls below a lower limit or exceeds an upper limit, then the base unit 115 may generate an alarm for display in the user interface 900 and/or for output via a speaker. For example, the upper limit for hemodynamic parameter P4 is 1200 and the lower limit for hemodynamic parameter P4 is 800 as shown in box 930. As depicted in
Within the graph 910, a practitioner can pan or scroll through various hemodynamic parameter P1-P4 values. For example, the practitioner can select a pan or scroll mode. Selection of the pan or scroll mode may cause a movable vertical marker to appear in the graph 910. Thus, the vertical marker may correspond with various times depending on the location of the vertical marker. The value for one or more of the hemodynamic parameters P1-P4 that correspond to the time at which the vertical marker is located may be displayed in the graph 910. As the practitioner adjusts the location of the vertical marker (e.g., as the practitioner moves the vertical marker left or right), the hemodynamic parameter P1-P4 values may update accordingly.
Optionally, the user interface unit 117 displays a user interface that provides a practitioner with an option to pause or resume hemodynamic parameter monitoring. Pausing hemodynamic parameter monitoring may cause the user interface unit 117 to stop displaying hemodynamic parameter values and/or may cause the base unit 115 to stop generating alarms or notifications.
In further embodiments, the practitioner can adjust the time scale in the user interface 900 (e.g., the scale of the x-axis of the graph 910) by selecting the x-axis. Adjusting the time scale causes the graph 910 to display additional historical hemodynamic parameter values (e.g., if the time scale is increased) or fewer historical hemodynamic parameter values (e.g., if the time scale is decreased).
Optionally, the practitioner can add events to the graph 910. For example, the user interface unit 117 can generate and display a screen that allows the practitioner to select an event and a time that the event occurred. Events can include blood gas, drug titration, electrosurgical procedure, fluid challenge, miscellaneous, nursing maneuver, respirator/ventilator change, suction, x-ray/radiology, and/or the like. An event can be displayed as a vertical line or other symbol in the graph 910 at a time that the event occurred. The vertical line or symbol may be marked with another symbol or character that identifies the type of event that occurred at the time.
One or more hemodynamic parameters may be indicated at various locations within the physiological schematic 1010. For example, the indicated hemodynamic parameters can include stroke volume variation (SVV), SV, heart rate (HR), CCO, mean arterial pressure (MAP), systemic vascular resistance (SVR), central venous pressure (CVP), end-diastolic volume (EDV), right ventricular ejection fraction (RVEF), mixed venous oxygen saturation (SvO2), and/or other such parameters. Hemodynamic parameters for which live values are available can be lightly shaded (e.g., SVV, SV, HR, CCO, MAP, and SVR) and hemodynamic parameters for which no live values are available can be darkly shaded (e.g., CVP, EDV, RVEF, and SvO2).
As described above with respect to
Below the hemodynamic parameter value matrix 1110 are bars 1120-1126 that indicate the signal quality of the wireless or wired connection between the base unit 115 and the user interface unit 117 over the period of time identified in the hemodynamic parameter value matrix 1110. For example, the length of the darkly shaded bar in the bars 1120-1126 indicates the signal quality level.
In an embodiment, the base unit 115 may determine one or more hemodynamic parameter values in time intervals shorter than the time intervals between entries in the hemodynamic value matrix 1110. For example, the base unit 115 may determine values for hemodynamic parameter P1 every second. The hemodynamic parameter value matrix 1110, however, displays a value for hemodynamic parameter P1 every 10 seconds. Thus, the base unit 115 can aggregate the determined values that fall within each time interval of the hemodynamic parameter value matrix 1110 (e.g., determine an average the 10 values that fall within each 10 second time interval, determine a medium of the 10 values that fall within each 10 second time interval, determine a mode of the 10 values that fall within each 10 second time interval, etc.) and transmit the aggregate value to the user interface unit 117 for display in the hemodynamic parameter value matrix 1110.
The bi-variant plot 1210 may also depict an optimal range represented by a shape, such as rectangle 1220 (or a circle, square, trapezoid, etc.). If the plotted values fall outside the optimal range, then the base unit 115 may generate a notification 1240 for display. A practitioner can set the limits that define the optimal range and the limits may only affect the bi-variant plot 1210 or may determine when the base unit 115 generates an alarm or notification. In some embodiments, the alarm limits (e.g., limits that, if exceeded, cause the base unit 115 to generate a notification) and the optimal range limits can be the same or different. The notification 1240 may indicate which of the hemodynamic parameter values caused the plotted value to fall outside the optimal range and/or a reason why the hemodynamic parameter value caused the plotted value to fall outside the optimal range. For example, as shown in
In an embodiment, the user interface unit 117 generates and displays a user interface that allows a practitioner to configure a catheter and injectate volume to be used when performing Bolus CO measurements (e.g., set a catheter type, an injectate volume, an injectate temperature, a type of injectate probe, etc.). Some settings, such as injectate temperature and injectate probe type, may be automatically determined by the base unit 115.
Once the settings are determined, the user interface unit 117 can display a Bolus CO measurement user interface.
As Bolus CO values are determined by the base unit 115, the determined Bolus CO values are displayed below the Bolus CO graph 1310 under the corresponding curve number in boxes 1320. A practitioner can select button 1330 to cause the boxes 1320 to instead display Bolus cardiac index (CI) values that are also determined by the base unit 115. The user interface 1300 can also display an average Bolus CO (or average Bolus CI) and/or a solution/IV temperature below the Bolus CO graph 1310.
In some embodiments, not shown, the user interface 1300 can numerically display current and/or historical Bolus CO and/or CI values. Along with the current and/or historical Bolus CO and/or CI values, the user interface 1300 can display the Bolus volume at different times.
As illustrated in
When a practitioner navigates to the user interface 1400, current patient information (e.g., determined hemodynamic parameter values and/or patient information like weight and height) may be automatically imported for use as input parameters. Input parameter values can be manually entered (either via the user interface unit 117 or by selecting import button 1420) and/or changed by selecting a parameter in the hemodynamic calculator 1410. A marking, such as an asterisk, may appear next to an input parameter that has a value that has been manually entered. The date and/or time of the latest update may be displayed at the top of the hemodynamic calculator 1410.
Base Unit and User Interface Unit Pairing Process
In an embodiment, the base unit 115 and the user interface unit 117 implement a pairing process such that the user interface unit 117 can display data generated by the base unit 115 and/or any one user interface unit 117 can display data generated by a specific base unit 115 (in situations, for example, in which multiple patient monitors 110 are present).
At block 1502, the base unit may enter a listening state, waiting for the user interface unit to request a connection. The user interface unit may transmit a connection request to the base unit at some time after the user interface unit starts up. For example, the user interface unit 117 may transmit a connection request at startup or after being disconnected from the base unit. In some embodiments, the user interface unit 117 broadcasts the connection request using a wired or wireless transmission protocol, such as the user datagram protocol (UDP).
At block 1504, the base unit determines whether a connection has been requested by a user interface unit. If a connection has not been requested, then the method 1500 reverts back to block 1502 and the base unit returns to the listening state to wait for another connection request. Otherwise, if a connection has been requested, then the method 1500 proceeds to block 1506.
At block 1506, the base unit begins attempts to connect with the user interface unit. In some embodiments, the connection attempt includes the base unit and/or the user interface unit transmitting authentication, association, and/or other like messages to each other using a wired or wireless transmission protocol, such as transmission control protocol (TCP).
At bock 1508, the base unit determines whether a connection is successfully established with the user interface unit. If the attempt to connect with the user interface unit fails, then the method 1500 reverts back to block 1502 and the base unit returns to the listening state to wait for another connection request. Otherwise, if the connection attempt succeeds, then the method 1500 proceeds to block 1510.
At block 1510, the base unit can set up send and/or receive message handlers and/or various other connection listeners. The send and/or receive message handlers and/or the various other connection listeners may allow the base unit to transmit data to, receive data from, and/or process data received from the user interface unit.
At block 1512, the base unit transmits an acknowledgement message to the user interface unit confirming that the connection attempt succeeded. After transmitting the acknowledgement message, the executing thread may transmit a message to one or more applications executing on the base unit indicating that the base unit has successfully paired with the user interface unit.
At block 1602, the base unit creates a wireless hotspot (e.g., WIFI, BLUETOOTH, etc.) at startup of the base unit. The wireless hotspot may be created to allow the user interface unit to connect to the wireless hotspot. A name of the hotspot may be determined by a service set identifier (SSID) listed in a configuration file stored on the base unit or may be auto-generated if a SSID is not stored. Whether creation of the hotspot succeeds or fails, the method 1600 proceeds to block 1604 (e.g., because a wireless connection may not be necessary for the base unit and the user interface unit to communicate).
At block 1604, the base unit starts listening for a broadcast pairing ID. The base unit may start listening for the broadcast pairing ID after a wireless hotspot is created upon startup or after the user interface unit is disconnected from the base unit.
At block 1606, the base unit determines whether a broadcast pairing ID transmitted by a user interface unit is detected. If a broadcast pairing ID is not detected, then the method 1600 reverts back to block 1604 and the base unit continues to listen for a broadcast pairing ID. Otherwise, if a broadcast pairing ID is detected, then the method 1600 proceeds to block 1608 and the base unit determines whether wired (e.g., local area network (LAN) created via Ethernet or another cable) or wireless communications should be used to establish the connection with the user interface unit. In some embodiments, a wired connection source takes priority over a wireless connection source if both are available.
At block 1608, the base unit determines whether a wired connection source exists. If a wired connection source exists, then the method 1600 proceeds to block 1610. Otherwise, if a wired connection source does not exist, then the method 1600 proceeds to block 1622.
At block 1610, the base unit uses the wired connection source to establish the connection with the user interface unit. After block 1610 is complete, the method 1600 proceeds to block 1612.
At block 1612, the base unit determines whether the base unit and the user interface unit were previously paired. For example, the base unit and the user interface unit may have previously paired if the pairing key of the user interface unit matches the pairing key of the base unit. The pairing key of the user interface unit may have been included in or be equivalent to the transmitted broadcast pairing ID. If the base unit and the user interface unit were previously paired, then the method 1600 proceeds to block 1620. Otherwise, if the base unit and the user interface unit were not previously paired, then the method 1600 proceeds to block 1614.
At block 1614, the base unit generates a new pairing key for eventual transmission to the user interface unit. For example, the new pairing key can be a guaranteed unique ID. After block 1614 is complete, the method 1600 proceeds to block 1616.
At block 1616, the base unit determines whether the base unit was previously wirelessly connected to a user interface unit. If the base unit was previously wirelessly connected to a user interface unit, then the method 1600 proceeds to block 1618. Otherwise, if the base unit was not previously wirelessly connected to a user interface unit, then the method 1600 proceeds to block 1620.
At block 1618, the base unit creates a new wireless hotspot. The base unit may create a new wireless hotspot to disallow a previously connected user interface unit from communicating with the base unit.
At block 1620, the base unit transmits pairing information to the user interface unit. The pairing information can include the pairing key (e.g., a previous pairing key or the new pairing key generated at block 1614), the hotspot SSID, a version of the base unit, a wired address of the base unit if a wired connection source is available (e.g., a LAN internet protocol (IP) address), and/or a wireless address of the base unit if a wireless connection source is available (e.g., a wireless IP address). After block 1620 is complete, the method 1600 reverts back to block 1604 and the base unit continues to listen for a broadcast pairing ID.
At block 1622, the base unit determines whether a wireless connection source is available. If a wireless connection source is not available, then an error may have occurred. Otherwise, if a wireless connection source is available, then the method 1600 proceeds to block 1624.
At block 1624, the base unit uses the wireless connection source to establish a connection with the user interface unit. After block 1624 is complete, the method 1600 proceeds to block 1626.
At block 1626, the base unit determines whether the pairing key of the user interface unit matches the pairing key of the base unit. If the pairing keys do not match, then the method 1600 reverts back to block 1604 and the base unit continues to listen for a broadcast pairing ID. Otherwise, if the pairing keys do match, then the method 1600 proceeds to block 1620.
At block 1702, the user interface unit determines whether a valid wireless hotspot exists and whether the user interface is not currently connected to a wireless hotspot. The user interface unit may make this determination after startup of the user interface unit or after a network disconnection (e.g., a disconnection from the base unit). If a valid wireless hotspot exists and the user interface unit is not currently connected to a wireless hotspot, then the method 1700 proceeds to block 1704. Otherwise, the method 1700 proceeds to block 1706.
At block 1704, the user interface unit attempts to connect to the wireless hotspot. After block 1704 is complete, the method 1700 proceeds to block 1706.
At block 1706, the user interface unit broadcast a pairing ID. The user interface unit may broadcast the pairing ID over all available connections (e.g., wired and wireless connections).
At block 1708, the user interface unit determines whether a broadcast response is received from the base unit. For example, the broadcast response may be an acknowledgment that the broadcasted pairing ID was received. If a broadcast response is not received, the method 1700 reverts back to block 1706 and the user interface unit continues to broadcast the pairing ID. Otherwise, if a broadcast response is received, the method 1700 proceeds to block 1710.
At block 1710, the user interface unit starts listening for pairing information transmitted by the base unit. If no pairing information has been received after a threshold period of time (e.g., a timeout period, such as 5 seconds or any like time period) expires, then the method 1700 reverts back to block 1706 and the user interface unit again broadcasts the pairing ID.
At block 1712, the user interface unit determines whether the pairing information is received from the base unit before the threshold period of time expires. If the pairing information is not received and the threshold period of time has not expired, then the method 1700 reverts back to block 1710 and the user interface unit continues to listen for the pairing information. If the pairing information is received before the threshold period of time expires, then the method 1700 proceeds to block 1714.
At block 1714, the user interface unit notifies other threads or applications executed by the processor housed in the user interface unit that a base unit has been found and a connection attempt should be made. After block 1714 is complete, the method 1600 proceeds to block 1716.
At block 1716, the user interface unit determines whether the user interface unit previously paired with the base unit or whether a pairing with the base unit has been confirmed (e.g., by selection of a confirm button by a user). For example, the user interface may determine whether the user interface unit has previously paired with the base unit by comparing the pairing key of the user interface unit with the pairing key of the base unit received as part of the pairing information. The user interface unit and the base unit previously paired if the pairing keys match. If the user interface unit and the base unit were not previously paired and a pairing has not been confirmed, then the method 1700 proceeds to block 1718. Otherwise, if the user interface unit and the base unit were previously paired or a pairing has been confirmed, then the method 1700 proceeds to block 1722.
At block 1718, the user interface unit determines whether a wired connection source is available. If a wired connection source is not available, then the user interface unit does not proceed with a connection and the method 1700 may revert back to block 1702 or 1706. Otherwise, if a wired connection source is available, then the method 1700 proceeds to block 1720.
At block 1720, the user interface unit displays a confirm button. The user can select the confirm button to verify that the user interface unit and the base unit should pair. After block 1720 is complete, the method 1700 either proceeds to block 1722 (e.g., if the confirm button is selected before a timeout period, such as 5 seconds or any like time period) or reverts back to block 1706 and the user interface unit can broadcast the pairing ID to ensure that the base unit remains available for pairing while the user interface unit waits for the user to select the confirm button. If the confirm button is selected after the timeout period, the user interface unit may complete blocks 1706 through 1714 again before proceeding to block 1722 because the pairing has been confirmed.
At block 1722, the user interface unit initializes send and/or receive message handlers to handle communications transmitted to or received from the base unit. After block 1722 is complete, the method 1700 proceeds to block 1724.
At block 1724, the user interface unit decides whether to use a wired connection source or a wireless connection source. In some embodiments, a wired connection source supersedes a wireless connection source such that the user interface unit uses the wired connection source to establish a connection with the base unit if both a wired and wireless connection source are available.
At block 1726, the user interface unit attempts to connect with the base unit using the chosen connection source and determines whether a connection with the base unit is successful. If the connection with the base unit is unsuccessful, then the method 1700 proceeds to block 1732. Otherwise, if the connection with the base unit is successful, then the method 1700 proceeds to block 1728.
At block 1728, the user interface unit waits for an acknowledgment to be transmitted by the base unit. The user interface unit may wait for a timeout period, such as 7 seconds (or any other like time period). A connection may not be considered complete until the acknowledgement is received.
At block 1730, the user interface unit determines whether the acknowledgement has been received from the base unit. If the acknowledgment has not been received or has not been received before the timeout period expires, then the method 1700 proceeds to block 1732. Otherwise, if the acknowledgment has been received (e.g., before the timeout period expires), then the method 1700 proceeds to block 1734.
At block 1732, the user interface unit handles a connection failure. After block 1732 is complete, the method 1700 reverts to block 1706 and the user interface unit starts over by broadcasting the pairing ID.
At block 1734, the user interface unit confirms that a connection with the base unit is established. The user interface unit may then begin displaying data received from the base unit.
At startup, such as when the user interface unit 117 is turned on, the screen 1840 may display a pairing screen. The screen 1840 may then instruct the broadcaster 1850 to listen and broadcast a pairing ID at 1861. Similarly, at startup, such as when the base unit 115 is turned on, the program 1810 may launch a wireless host so as to create a wireless hotspot at 1862. The program 1810 may then instruct the thread 1830 to start listening for a broadcast pairing ID at 1863. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 1864. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 1865.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 1866. After some time, the broadcaster 1850 may also transmit the pairing ID at 1867. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 1868 as described above. Here, the receiver 1820 selected the wired connection source. Once this is determined, the receiver 1820 can transmit a response over the wired connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 1869.
The broadcaster 1850 can then begin to listen for the pairing information at 1870. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 1871. At 1872, the broadcaster 1850 notifies the screen 1840 that a connection is detected, which causes the screen 1840 to start a connection detected function that causes the screen 1840 to display the pairing information at 1873. In addition, the screen 1840 may display the confirm button. The broadcaster 1850 may continue to broadcast the pairing ID until the confirm button is selected to ensure that the base unit 115 is still available for a connection. Once the confirm button is selected, then the screen 1840 notifies the manager 1860 at 1874 and the manager 1860 initializes the send and/or receive message handlers at 1875.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 1876 and the client 1890 determines whether to use a wired or wireless connection source at 1877. Here, the client 1890 uses the wired connection source. After the determination is made, the client 1890 transmits a connection request over the wired connection source to the thread 1830 at 1878. At 1879, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 1880. Before or after message 1880, the thread 1830 initializes send and/or receive message handlers to handle the connection at 1881 and instructs the receiver 1820 to stop listening for pairing IDs at 1882. After receiving the connection acceptance at 1880, the manager 1860 starts listening for the acknowledgment message at 1883. At 1884, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit a notification to the screen 1840 that the connection is successful at 1885. The screen 1840 may then instruct the broadcaster 1850 to stop broadcasting the pairing ID at 1886.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the screen 1840 may instruct the broadcaster 1850 (e.g., on any screen) to listen and broadcast a pairing ID at 1961. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 1963. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 1964. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 1965.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 1966. After some time, the broadcaster 1850 may also transmit the pairing ID at 1967. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 1968 as described above. Here, the receiver 1820 selected the wired connection source. Once this is determined, the receiver 1820 can transmit a response over the wired connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 1969.
The broadcaster 1850 can then begin to listen for the pairing information at 1970. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 1971. At 1972, the broadcaster 1850 notifies the screen 1840 that a connection is detected, which causes the screen 1840 to start a connection detected function at 1973. The screen 1840 then notifies the manager 1860 at 1974 to connect and the manager 1860 initializes the send and/or receive message handlers at 1975.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 1976 and the client 1890 determines whether to use a wired or wireless connection source at 1977. Here, the client 1890 uses the wired connection source. After the determination is made, the client 1890 transmits a connection request over the wired connection source to the thread 1830 at 1978. At 1979, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 1980. Before or after message 1980, the thread 1830 initializes send and/or receive message handlers to handle the connection at 1981 and instructs the receiver 1820 to stop listening for pairing IDs at 1982. After receiving the connection acceptance at 1980, the manager 1860 starts listening for the acknowledgment message at 1983. At 1984, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit a notification to the screen 1840 that the connection is successful at 1985. The screen 1840 may then instruct the broadcaster 1850 to stop broadcasting the pairing ID at 1986.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the manager 1860 may instruct the broadcaster 1850 to listen and broadcast a pairing ID at 2061. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 2063. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2064. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2065.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2066. After some time, the broadcaster 1850 may also transmit the pairing ID at 2067. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2068 as described above. Here, the receiver 1820 selected the wired connection source. Once this is determined, the receiver 1820 can transmit a response over the wired connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2069.
The broadcaster 1850 can then begin to listen for the pairing information at 2070. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2071. At 2072, the broadcaster 1850 notifies the manager 1860 that a connection is detected, which causes the manager 1860 to start a connection detected function at 2073. The manager 1860 then instructs the screen 1840 to show the pairing screen at 2074, where the pairing screen includes the confirm button. Once the confirm button is selected, the screen 1840 notifies the manager 1860 accordingly at 2075. Selection of the confirm button causes the manager 1860 at 2076 to connect and initialize the send and/or receive message handlers.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2077 and the client 1890 determines whether to use a wired or wireless connection source at 2078. Here, the client 1890 uses the wired connection source. After the determination is made, the client 1890 transmits a connection request over the wired connection source to the thread 1830 at 2079. At 2080, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2081. Before or after message 2081, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2082 and instructs the receiver 1820 to stop listening for pairing IDs at 2083. After receiving the connection acceptance at 2081, the manager 1860 starts listening for the acknowledgment message at 2084. At 2085, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit an instruction to the screen 1840 to close the pairing screen at 2086 and an instruction to the broadcaster 1850 to stop broadcasting the pairing ID at 2087.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the manager 1860 may instruct the broadcaster 1850 to listen and broadcast a pairing ID at 2161. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 2163. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2164. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2165.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2166. After some time, the broadcaster 1850 may also transmit the pairing ID at 2167. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2168 as described above. Here, the receiver 1820 selected the wired connection source. Once this is determined, the receiver 1820 can transmit a response over the wired connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2169.
The broadcaster 1850 can then begin to listen for the pairing information at 2170. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2171. At 2172, the broadcaster 1850 notifies the manager 1860 that a connection is detected, which causes the manager 1860 to start a connection detected function at 2173. The manager 1860 at 2174 then connects and initializes the send and/or receive message handlers.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2175 and the client 1890 determines whether to use a wired or wireless connection source at 2176. Here, the client 1890 uses the wired connection source. After the determination is made, the client 1890 transmits a connection request over the wired connection source to the thread 1830 at 2177. At 2178, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2179. Before or after message 2179, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2180 and instructs the receiver 1820 to stop listening for pairing IDs at 2181. After receiving the connection acceptance at 2179, the manager 1860 starts listening for the acknowledgment message at 2182. At 2183, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit an instruction to the broadcaster 1850 to stop broadcasting the pairing ID at 2184.
At startup, such as when the user interface unit 117 is turned on, the screen 1840 may display a pairing screen. The screen 1840 may then instruct the broadcaster 1850 to listen and broadcast a pairing ID at 2261. Similarly, at startup, such as when the base unit 115 is turned on, the program 1810 may launch a wireless host so as to create a wireless hotspot at 2262. The program 1810 may then instruct the thread 1830 to start listening for a broadcast pairing ID at 2263. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2264. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2265.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2266. After some time, the broadcaster 1850 may also transmit the pairing ID at 2267. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection if the pairing ID of the user interface unit 117 matches the pairing ID of the base unit 115. Otherwise, if the pairing IDs do not match, then the receiver 1820 may not send an acknowledgment.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2268 as described above. Here, the receiver 1820 selected the wireless connection source. Once this is determined, the receiver 1820 can check to ensure that the pairing IDs match. If the pairing IDs match, then the receiver 1820 can transmit a response over the wireless connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2269. If the pairing IDs do not match, then the receiver 1820 does not transmit a response and the remaining messages described below are not transmitted. Rather, the broadcaster 1850 resumes broadcasting the pairing ID.
The broadcaster 1850 can then begin to listen for the pairing information at 2270. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2271. At 2272, the broadcaster 1850 notifies the screen 1840 that a connection is detected, which causes the screen 1840 to start a connection detected function that causes the screen 1840 to display the pairing information at 2273. In addition, the screen 1840 may display the confirm button. The broadcaster 1850 may continue to broadcast the pairing ID until the confirm button is selected to ensure that the base unit 115 is still available for a connection. Once the confirm button is selected, then the screen 1840 notifies the manager 1860 at 2274 and the manager 1860 initializes the send and/or receive message handlers at 2275.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2276 and the client 1890 determines whether to use a wired or wireless connection source at 2277. Here, the client 1890 uses the wireless connection source. After the determination is made, the client 1890 transmits a connection request over the wireless connection source to the thread 1830 at 2278. At 2279, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2280. Before or after message 1880, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2281 and instructs the receiver 1820 to stop listening for pairing IDs at 2282. After receiving the connection acceptance at 2280, the manager 1860 starts listening for the acknowledgment message at 2283. At 2284, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit a notification to the screen 1840 that the connection is successful at 2285. The screen 1840 may then instruct the broadcaster 1850 to stop broadcasting the pairing ID at 2286.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the screen 1840 may instruct the broadcaster 1850 (e.g., on any screen) to listen and broadcast a pairing ID at 2361. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may launch a wireless host so as to create a wireless hotspot at 2362 and the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 2363. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2364. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2365.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2366. After some time, the broadcaster 1850 may also transmit the pairing ID at 2367. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection if the pairing ID of the user interface unit 117 matches the pairing ID of the base unit 115. Otherwise, if the pairing IDs do not match, then the receiver 1820 may not send an acknowledgment.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2368 as described above. Here, the receiver 1820 selected the wireless connection source. Once this is determined, the receiver 1820 can check to ensure that the pairing IDs match. If the pairing IDs match, then the receiver 1820 can transmit a response over the wireless connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2369. If the pairing IDs do not match, then the receiver 1820 does not transmit a response and the remaining messages described below are not transmitted. Rather, the broadcaster 1850 resumes broadcasting the pairing ID.
The broadcaster 1850 can then begin to listen for the pairing information at 2370. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2371. At 2372, the broadcaster 1850 notifies the screen 1840 that a connection is detected, which causes the screen 1840 to start a connection detected function at 2373. The screen 1840 then notifies the manager 1860 at 2374 to connect and the manager 1860 initializes the send and/or receive message handlers at 2375.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2376 and the client 1890 determines whether to use a wired or wireless connection source at 2377. Here, the client 1890 uses the wireless connection source. After the determination is made, the client 1890 transmits a connection request over the wireless connection source to the thread 1830 at 2378. At 2379, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2380. Before or after message 2380, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2381 and instructs the receiver 1820 to stop listening for pairing IDs at 2382. After receiving the connection acceptance at 2380, the manager 1860 starts listening for the acknowledgment message at 2383. At 2384, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit a notification to the screen 1840 that the connection is successful at 2385. The screen 1840 may then instruct the broadcaster 1850 to stop broadcasting the pairing ID at 2386.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the manager 1860 may instruct the broadcaster 1850 to listen and broadcast a pairing ID at 2461. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 2463. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2464. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2465.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2466. After some time, the broadcaster 1850 may also transmit the pairing ID at 2467. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection if the pairing ID of the user interface unit 117 matches the pairing ID of the base unit 115. Otherwise, if the pairing IDs do not match, then the receiver 1820 may not send an acknowledgment.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2468 as described above. Here, the receiver 1820 selected the wireless connection source. Once this is determined, the receiver 1820 can check to ensure that the pairing IDs match. If the pairing IDs match, then the receiver 1820 can transmit a response over the wireless connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2469. If the pairing IDs do not match, then the receiver 1820 does not transmit a response and the remaining messages described below are not transmitted. Rather, the broadcaster 1850 resumes broadcasting the pairing ID.
The broadcaster 1850 can then begin to listen for the pairing information at 2470. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2471. At 2472, the broadcaster 1850 notifies the manager 1860 that a connection is detected, which causes the manager 1860 to start a connection detected function at 2473. The manager 1860 then instructs the screen 1840 to show the pairing screen at 2474, where the pairing screen includes the confirm button. Once the confirm button is selected, the screen 1840 notifies the manager 1860 accordingly at 2475. Selection of the confirm button causes the manager 1860 at 2476 to connect and initialize the send and/or receive message handlers.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2477 and the client 1890 determines whether to use a wired or wireless connection source at 2478. Here, the client 1890 uses the wireless connection source. After the determination is made, the client 1890 transmits a connection request over the wireless connection source to the thread 1830 at 2479. At 2480, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2481. Before or after message 2481, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2482 and instructs the receiver 1820 to stop listening for pairing IDs at 2483. After receiving the connection acceptance at 2481, the manager 1860 starts listening for the acknowledgment message at 2484. At 2485, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit an instruction to the screen 1840 to close the pairing screen at 2486 and an instruction to the broadcaster 1850 to stop broadcasting the pairing ID at 2487.
After the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the manager 1860 may instruct the broadcaster 1850 to listen and broadcast a pairing ID at 2561. Similarly, after the user interface unit 117 is removed from a dock or tether connecting the user interface unit 117 with the base unit 115, the program 1810 may instruct the thread 1830 to start listening for a broadcast pairing ID at 2563. Receipt of the instruction may cause the thread 1830 to create a listener (e.g., a TCP listener) at 2564. The program 1810 may also instruct the receiver 1820 to start listening for a broadcast pairing ID at 2565.
The broadcaster 1850 may attempt to connect to the wireless hotspot at 2566. After some time, the broadcaster 1850 may also transmit the pairing ID at 2567. For example, the broadcaster 1850 may broadcast the pairing ID. The broadcaster 1850 may periodically transmit the pairing ID (e.g., every 3 seconds or other like time period) until pairing information is received from the base unit 115. Receipt of the pairing ID may cause the receiver 1820 to transmit a response acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection if the pairing ID of the user interface unit 117 matches the pairing ID of the base unit 115. Otherwise, if the pairing IDs do not match, then the receiver 1820 may not send an acknowledgment.
After receiving the pairing ID, the receiver 1820 can determine whether to use a wired or wireless connection source at 2568 as described above. Here, the receiver 1820 selected the wireless connection source. Once this is determined, the receiver 1820 can check to ensure that the pairing IDs match. If the pairing IDs match, then the receiver 1820 can transmit a response over the wireless connection source acknowledging that the pairing ID was received and/or indicating that the base unit 115 is attempting a connection at 2569. If the pairing IDs do not match, then the receiver 1820 does not transmit a response and the remaining messages described below are not transmitted. Rather, the broadcaster 1850 resumes broadcasting the pairing ID.
The broadcaster 1850 can then begin to listen for the pairing information at 2570. The broadcaster 1850 may listen for a timeout period (e.g., 5 seconds or other like time periods). If the pairing information is not received before the timeout period expires, then the broadcaster 1850 may again broadcast the pairing ID. Here, the receiver 1820 transmits the pairing information before the timeout period expires at 2571. At 2572, the broadcaster 1850 notifies the manager 1860 that a connection is detected, which causes the manager 1860 to start a connection detected function at 2573. The manager 1860 at 2574 then connects and initializes the send and/or receive message handlers.
The manager 1860 then notifies the client 1890 that the message handlers are initialized at 2575 and the client 1890 determines whether to use a wired or wireless connection source at 2576. Here, the client 1890 uses the wireless connection source. After the determination is made, the client 1890 transmits a connection request over the wireless connection source to the thread 1830 at 2577. At 2578, the thread 1830 sends a message to the client 1890 accepting the connection. The client 1890 then notifies the manager 1860 of the connection acceptance at 2579. Before or after message 2579, the thread 1830 initializes send and/or receive message handlers to handle the connection at 2580 and instructs the receiver 1820 to stop listening for pairing IDs at 2581. After receiving the connection acceptance at 2579, the manager 1860 starts listening for the acknowledgment message at 2582. At 2583, the thread 1830 transmits the acknowledgment message to the manager 1860. This may cause the manager 1860 to transmit an instruction to the broadcaster 1850 to stop broadcasting the pairing ID at 2584.
Terminology
Many variations on the patient monitoring systems and methods described above are possible. For example, the user interface unit can be implemented using different design aesthetics as well as different physical elements for docking with a compatible base unit. In addition, the base unit can be configured to receive information and send it directly to the user interface unit for further processing prior to display (e.g., determining a measured hemodynamic parameter from patient sensor electrical information).
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more specialized or dedicated computers, computer processors, or machines configured to execute specialized computer instructions. The code modules may be implemented using a combination of hardware (e.g., programmable logic circuits, application specific integrated circuits, microprocessors, etc.) and software stored on any type of non-transitory computer-readable medium or tangible computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (e.g., as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (e.g., as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, e.g., volatile or non-volatile storage.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described tasks or events may be performed in an order other than that specifically disclosed, or multiple may be combined in a single block or state. The example tasks or events may be performed in serial, in parallel, or in some other manner. Tasks or events may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, is not generally intended to imply that features, elements and/or steps are required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to convey that an item, term, etc. may be either X, Y or Z. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present. The terms “about” or “approximate” and the like are synonymous and are used to indicate that the value modified by the term has an understood range associated with it, where the range can be ±20%, ±15%, ±10%, ±5%, or ±1%. The term “substantially” is used to indicate that a result (e.g., measurement value) is close to a targeted value, where close can mean, for example, the result is within 80% of the value, within 90% of the value, within 95% of the value, or within 99% of the value.
While certain example embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions disclosed herein. Thus, nothing in the foregoing description is intended to imply that any particular feature, characteristic, step, module, or block is necessary or indispensable. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the inventions disclosed herein.
This application is a continuation of International Application No. PCT/US2016/057553, entitled “HEMODYNAMIC MONITORING SYSTEM WITH DETACHABLE DISPLAY UNIT” and on filed Oct. 18, 2016, which claims the benefit of U.S. Provisional Patent Application No. 62/243,555, entitled “HEMODYNAMIC MONITORING SYSTEM WITH DETACHABLE DISPLAY UNIT” and filed on Oct. 19, 2015. The entire contents of each of the above-identified patent applications are hereby incorporated by referenced herein and made a part of this specification.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3618592 | Stewart | Nov 1971 | A |
| 3868679 | Arneson | Feb 1975 | A |
| 4465075 | Swartz | Aug 1984 | A |
| 4501531 | Bilstad et al. | Feb 1985 | A |
| 4550611 | Czarnocki | Nov 1985 | A |
| 4557269 | Reynolds et al. | Dec 1985 | A |
| 4581940 | Merrick et al. | Apr 1986 | A |
| 4611601 | Bowman | Sep 1986 | A |
| 4659235 | Gilmore, Jr. et al. | Apr 1987 | A |
| 4679567 | Hanlon et al. | Jul 1987 | A |
| 4683894 | Kodama et al. | Aug 1987 | A |
| 4685469 | Keller | Aug 1987 | A |
| 4817022 | Jomod et al. | Mar 1989 | A |
| 4825876 | Beard | May 1989 | A |
| 4883992 | Koglin et al. | Nov 1989 | A |
| 4926674 | Fossum et al. | May 1990 | A |
| 4950235 | Slate et al. | Aug 1990 | A |
| 5135002 | Kirchner et al. | Aug 1992 | A |
| 5269311 | Kirchner et al. | Dec 1993 | A |
| 5400793 | Wesseling | Mar 1995 | A |
| 5526817 | Pfeiffer et al. | Jun 1996 | A |
| 5579771 | Bonnefous | Dec 1996 | A |
| 5623925 | Swenson et al. | Apr 1997 | A |
| 5640953 | Bishop et al. | Jun 1997 | A |
| 5685314 | Geheb et al. | Nov 1997 | A |
| 5712795 | Layman et al. | Jan 1998 | A |
| 5713856 | Eggers et al. | Feb 1998 | A |
| 5746698 | Bos et al. | May 1998 | A |
| 5781442 | Engleson et al. | Jul 1998 | A |
| 5800387 | Duffy et al. | Sep 1998 | A |
| 5803917 | Butterfield et al. | Sep 1998 | A |
| 5822185 | Cavello | Oct 1998 | A |
| 5827223 | Butterfield et al. | Oct 1998 | A |
| 5836910 | Duffy et al. | Nov 1998 | A |
| 5848988 | Davis | Dec 1998 | A |
| 5904708 | Goedeke | May 1999 | A |
| 5908027 | Butterfield et al. | Jun 1999 | A |
| 5941846 | Duffy et al. | Aug 1999 | A |
| 5954641 | Kehr et al. | Sep 1999 | A |
| 5957885 | Bollish et al. | Sep 1999 | A |
| 5961487 | Davis | Oct 1999 | A |
| 6045512 | Roteliuk et al. | Apr 2000 | A |
| 6050951 | Friedman et al. | Apr 2000 | A |
| 6071244 | Band et al. | Jun 2000 | A |
| 6085752 | Kehr et al. | Jul 2000 | A |
| 6102855 | Kehr et al. | Aug 2000 | A |
| 6113543 | Bonnefous | Sep 2000 | A |
| 6158965 | Butterfield et al. | Dec 2000 | A |
| 6159151 | Bonnefous | Dec 2000 | A |
| 6181549 | Mills et al. | Jan 2001 | B1 |
| 6183417 | Geheb et al. | Feb 2001 | B1 |
| 6185095 | Helot et al. | Feb 2001 | B1 |
| 6200301 | Pfeiffer et al. | Mar 2001 | B1 |
| 6213972 | Butterfield et al. | Apr 2001 | B1 |
| 6224585 | Pfeiffer | May 2001 | B1 |
| 6231498 | Pfeiffer et al. | May 2001 | B1 |
| 6270252 | Siefert | Aug 2001 | B1 |
| 6290650 | Butterfield et al. | Sep 2001 | B1 |
| 6315735 | Joeken et al. | Nov 2001 | B1 |
| 6348777 | Brown et al. | Feb 2002 | B1 |
| 6358213 | Friedman et al. | Mar 2002 | B1 |
| 6358225 | Butterfield | Mar 2002 | B1 |
| 6394961 | Pfeiffer et al. | May 2002 | B1 |
| 6416291 | Butterfield et al. | Jul 2002 | B1 |
| 6485431 | Campbell | Nov 2002 | B1 |
| 6485481 | Pfeiffer | Nov 2002 | B1 |
| 6506163 | Farrell et al. | Jan 2003 | B1 |
| 6532381 | Bayer et al. | Mar 2003 | B2 |
| 6537214 | Hood et al. | Mar 2003 | B1 |
| 6562012 | Brown et al. | May 2003 | B1 |
| 6570758 | Maeda | May 2003 | B1 |
| 6575901 | Stoycos et al. | Jun 2003 | B2 |
| 6582370 | Jibiki | Jun 2003 | B2 |
| 6583985 | Nguyen et al. | Jun 2003 | B2 |
| 6584336 | Ali et al. | Jun 2003 | B1 |
| 6589264 | Barbut et al. | Jul 2003 | B1 |
| 6591135 | Palmer et al. | Jul 2003 | B2 |
| 6592546 | Barbut | Jul 2003 | B1 |
| 6594146 | Frangesch et al. | Jul 2003 | B2 |
| 6602191 | Quy | Aug 2003 | B2 |
| 6609023 | Fischell et al. | Aug 2003 | B1 |
| 6611206 | Eshelman et al. | Aug 2003 | B2 |
| 6645177 | Shearn | Nov 2003 | B1 |
| 6648828 | Friedman et al. | Nov 2003 | B2 |
| 6671547 | Lyster et al. | Dec 2003 | B2 |
| 6671563 | Engelson et al. | Dec 2003 | B1 |
| 6673018 | Friedman | Jan 2004 | B2 |
| 6698921 | Siefert | Mar 2004 | B2 |
| 6699203 | Starr et al. | Mar 2004 | B2 |
| 6705992 | Gatzke | Mar 2004 | B2 |
| 6731973 | Voith | May 2004 | B2 |
| 6731989 | Engleson et al. | May 2004 | B2 |
| 6736782 | Pfeiffer et al. | May 2004 | B2 |
| 6746431 | Pfeiffer et al. | Jun 2004 | B2 |
| 6758822 | Romano | Jul 2004 | B2 |
| 6801802 | Sitzman et al. | Oct 2004 | B2 |
| 6829501 | Nielsen et al. | Dec 2004 | B2 |
| 6840904 | Goldberg | Jan 2005 | B2 |
| 6862472 | Mikula et al. | Mar 2005 | B2 |
| 6870475 | Fitch et al. | Mar 2005 | B2 |
| 6904306 | Wu et al. | Jun 2005 | B1 |
| 6915170 | Engleson et al. | Jul 2005 | B2 |
| 6997877 | Band et al. | Feb 2006 | B2 |
| 7011672 | Barbut et al. | Mar 2006 | B2 |
| 7022322 | Koll et al. | Apr 2006 | B2 |
| 7054679 | Hirsh | May 2006 | B2 |
| 7074205 | Duffy et al. | Jul 2006 | B1 |
| 7092751 | Erkkila | Aug 2006 | B2 |
| 7209780 | Pfeiffer et al. | Apr 2007 | B2 |
| 7220230 | Roteliuk et al. | May 2007 | B2 |
| D552741 | Zhou et al. | Oct 2007 | S |
| 7280864 | Jenkins | Oct 2007 | B2 |
| 7297129 | Kinouchi et al. | Nov 2007 | B2 |
| 7298613 | Yin et al. | Nov 2007 | B2 |
| 7306575 | Barbut et al. | Dec 2007 | B2 |
| 7314449 | Pfeiffer et al. | Jan 2008 | B2 |
| 7319894 | Higgins | Jan 2008 | B2 |
| 7344551 | Barbut et al. | Mar 2008 | B2 |
| 7384410 | Eggers et al. | Jun 2008 | B2 |
| 7390302 | Friedman et al. | Jun 2008 | B2 |
| 7407486 | Huiku et al. | Aug 2008 | B2 |
| 7422562 | Hatib et al. | Sep 2008 | B2 |
| 7452333 | Roteliuk | Nov 2008 | B2 |
| 7465273 | Friedman | Dec 2008 | B2 |
| 7468035 | Bonan et al. | Dec 2008 | B2 |
| 7468038 | Ye et al. | Dec 2008 | B2 |
| 7507208 | Bennett et al. | Mar 2009 | B2 |
| 7542795 | Brodnick | Jun 2009 | B2 |
| 7553291 | Duffy et al. | Jun 2009 | B2 |
| 7559896 | Torp | Jul 2009 | B2 |
| 7569015 | Donaldson et al. | Aug 2009 | B2 |
| 7572223 | Donaldson | Aug 2009 | B2 |
| 7572230 | Neumann et al. | Aug 2009 | B2 |
| 7588542 | Pfeiffer et al. | Sep 2009 | B2 |
| 7590449 | Mann et al. | Sep 2009 | B2 |
| 7594892 | Cen et al. | Sep 2009 | B2 |
| 7604602 | Roteliuk et al. | Oct 2009 | B2 |
| 7608060 | Gillepsie, Jr. et al. | Oct 2009 | B2 |
| 7611467 | Zhang | Nov 2009 | B2 |
| 7650291 | Rosenfeld et al. | Jan 2010 | B2 |
| 7651466 | Hatib et al. | Jan 2010 | B2 |
| 7666151 | Sullivan et al. | Feb 2010 | B2 |
| 7678059 | Friedman et al. | Mar 2010 | B2 |
| 7695512 | Lashinski et al. | Apr 2010 | B2 |
| 7698156 | Martucci et al. | Apr 2010 | B2 |
| 7704209 | Bennett et al. | Apr 2010 | B2 |
| 7766863 | Giiiepsie, Jr. et al. | Aug 2010 | B2 |
| 7775987 | Hersh et al. | Aug 2010 | B2 |
| 7783339 | Lee et al. | Aug 2010 | B2 |
| 7785263 | Roteliuk et al. | Aug 2010 | B2 |
| 7803122 | Pfeiffer et al. | Sep 2010 | B2 |
| 7805181 | Breeuwer | Sep 2010 | B2 |
| 7815576 | Wellnhofer | Oct 2010 | B2 |
| 7815578 | Cohen et al. | Oct 2010 | B2 |
| 7837628 | Secora et al. | Nov 2010 | B2 |
| 7850617 | Goedje et al. | Dec 2010 | B2 |
| 7873416 | Guo et al. | Jan 2011 | B2 |
| D632698 | Judy et al. | Feb 2011 | S |
| D632699 | Judy et al. | Feb 2011 | S |
| 7927269 | Ten Eyck et al. | Apr 2011 | B2 |
| 7935062 | Karamanoglu et al. | May 2011 | B2 |
| 7966678 | Ten Eyck et al. | Jun 2011 | B2 |
| 7967749 | Hutchinson et al. | Jun 2011 | B2 |
| 7967757 | Roteliuk | Jun 2011 | B2 |
| 7979111 | Acquista | Jul 2011 | B2 |
| 7991625 | Rosenfeld et al. | Aug 2011 | B2 |
| 7993274 | Pruvot et al. | Aug 2011 | B2 |
| 8000937 | Zeng et al. | Aug 2011 | B2 |
| 8016766 | Goedje et al. | Sep 2011 | B2 |
| 8025674 | Barbut et al. | Sep 2011 | B2 |
| RE42803 | Lipson et al. | Oct 2011 | E |
| D649556 | Judy et al. | Nov 2011 | S |
| 8047489 | Watanabe | Nov 2011 | B2 |
| 8050748 | Ali et al. | Nov 2011 | B2 |
| 8060203 | Järverud et al. | Nov 2011 | B2 |
| 8070677 | Ali | Dec 2011 | B2 |
| D652051 | Judy et al. | Jan 2012 | S |
| D652052 | Judy et al. | Jan 2012 | S |
| 8096947 | Saigo et al. | Jan 2012 | B2 |
| 8115101 | Balji | Feb 2012 | B2 |
| 8125484 | Gering | Feb 2012 | B2 |
| 8137273 | Everett et al. | Mar 2012 | B2 |
| 8170887 | Rosenfeld et al. | May 2012 | B2 |
| 8175895 | Rosenfeld et al. | May 2012 | B2 |
| 8182429 | Mason | May 2012 | B2 |
| 8211030 | Donehoo et al. | Jul 2012 | B2 |
| 8233272 | Fidacaro et al. | Jul 2012 | B2 |
| 8234128 | Martucci et al. | Jul 2012 | B2 |
| 8235938 | Eggers et al. | Aug 2012 | B2 |
| 8246546 | Huiku | Aug 2012 | B2 |
| 8257273 | Pfeiffer | Sep 2012 | B2 |
| 8266349 | Eaton et al. | Sep 2012 | B2 |
| 8279586 | Fidacaro et al. | Oct 2012 | B2 |
| 8282567 | Kolluri | Oct 2012 | B2 |
| 8285360 | Kabasawa | Oct 2012 | B2 |
| 8315682 | Such et al. | Nov 2012 | B2 |
| RE43869 | Lewandowski et al. | Dec 2012 | E |
| 8326649 | Rosenfeld | Dec 2012 | B2 |
| 8343058 | Pfeiffer et al. | Jan 2013 | B2 |
| 8343062 | Fortin et al. | Jan 2013 | B2 |
| 8344847 | Moberg et al. | Jan 2013 | B2 |
| 8396537 | Baiji et al. | Mar 2013 | B2 |
| 8401874 | Rosenfeld | Mar 2013 | B2 |
| 8465424 | Aggarwal | Jun 2013 | B2 |
| 8465435 | Van Goudoever et al. | Jun 2013 | B2 |
| 8469887 | Haider | Jun 2013 | B2 |
| 8471697 | Judy et al. | Jun 2013 | B2 |
| 8483789 | Higgins | Jul 2013 | B2 |
| 8484393 | Eaton et al. | Jul 2013 | B2 |
| 8489427 | Simpson et al. | Jul 2013 | B2 |
| 8515531 | Costa Ribalta et al. | Aug 2013 | B2 |
| 8517939 | Parnagian | Aug 2013 | B2 |
| 8521556 | Chbat et al. | Aug 2013 | B2 |
| 8548577 | Muhlsteff et al. | Oct 2013 | B2 |
| 8562526 | Heneghan | Oct 2013 | B2 |
| 8566738 | Van Vlimmeren et al. | Oct 2013 | B2 |
| 8568327 | O'Brien | Oct 2013 | B2 |
| 8574156 | Uutela et al. | Nov 2013 | B2 |
| 8574157 | Hoctor et al. | Nov 2013 | B2 |
| 8602985 | Ali | Dec 2013 | B2 |
| 8622913 | Dentinger et al. | Jan 2014 | B2 |
| 8639521 | Eggers et al. | Jan 2014 | B2 |
| 8641757 | Pintor et al. | Feb 2014 | B2 |
| 8645154 | Eggers et al. | Feb 2014 | B2 |
| 8649586 | Wang et al. | Feb 2014 | B2 |
| 8665096 | Rantala et al. | Mar 2014 | B2 |
| 8690786 | Hersh et al. | Apr 2014 | B2 |
| 8696632 | Giiiepsie, Jr. et al. | Apr 2014 | B2 |
| 8715193 | Takala et al. | May 2014 | B2 |
| 8721543 | Saffarian | May 2014 | B2 |
| 8721556 | Roteliuk | May 2014 | B2 |
| 8730243 | Wenholz et al. | May 2014 | B2 |
| 8734339 | Rao et al. | May 2014 | B2 |
| 8737048 | Fidacaro et al. | May 2014 | B2 |
| 8737971 | van Rooyen et al. | May 2014 | B2 |
| 8740807 | Banet et al. | Jun 2014 | B2 |
| 8744875 | Eaton et al. | Jun 2014 | B2 |
| 8761851 | Benni et al. | Jun 2014 | B2 |
| 8771197 | Hatib et al. | Jul 2014 | B2 |
| 8771198 | Kumar et al. | Jul 2014 | B2 |
| 8773259 | Judy et al. | Jul 2014 | B2 |
| 8775196 | Simpson et al. | Jul 2014 | B2 |
| 8797714 | Balji et al. | Aug 2014 | B2 |
| 8805019 | Jeanne et al. | Aug 2014 | B2 |
| 8808191 | Hirsh | Aug 2014 | B2 |
| 8836514 | Rantala | Sep 2014 | B2 |
| 8840636 | Barbut | Sep 2014 | B2 |
| 8852094 | Al-Ali et al. | Oct 2014 | B2 |
| 8878677 | Nielsen | Nov 2014 | B2 |
| 8882666 | Goldberg et al. | Nov 2014 | B1 |
| 8888738 | Gillepsie, Jr. et al. | Nov 2014 | B2 |
| 8905939 | Hatib et al. | Dec 2014 | B2 |
| 8911377 | Al-Ali | Dec 2014 | B2 |
| 8922330 | Moberg et al. | Dec 2014 | B2 |
| 8923918 | Kreger et al. | Dec 2014 | B2 |
| 8992431 | Merilainen | Mar 2015 | B2 |
| 9024781 | Zhang et al. | May 2015 | B2 |
| 9047648 | Lekutai et al. | Jun 2015 | B1 |
| 9070184 | Wang et al. | Jun 2015 | B2 |
| 9101264 | Acquista | Aug 2015 | B2 |
| 9101335 | Coffeng | Aug 2015 | B2 |
| 9125630 | Menzel | Sep 2015 | B2 |
| 9149188 | Eng et al. | Oct 2015 | B2 |
| 9152268 | Li et al. | Oct 2015 | B2 |
| 9153112 | Kiani et al. | Oct 2015 | B1 |
| 9167968 | Saeed et al. | Oct 2015 | B2 |
| 9167973 | Steiner et al. | Oct 2015 | B2 |
| 9189941 | Eschelman et al. | Nov 2015 | B2 |
| 9196046 | Meyer | Nov 2015 | B2 |
| 9198620 | Balji et al. | Dec 2015 | B2 |
| 9204857 | Dentinger | Dec 2015 | B2 |
| 9220421 | Woehrle | Dec 2015 | B2 |
| 9254104 | Judy et al. | Feb 2016 | B2 |
| 9259187 | Peyton | Feb 2016 | B2 |
| 9299240 | Anson et al. | Mar 2016 | B2 |
| 9300356 | Winward et al. | Mar 2016 | B2 |
| 9307913 | O'Brien et al. | Apr 2016 | B2 |
| 9345641 | Kraus et al. | May 2016 | B2 |
| 9351640 | Tran | May 2016 | B2 |
| 9364153 | Merritt et al. | Jun 2016 | B2 |
| 9393384 | Kapur et al. | Jul 2016 | B1 |
| 9433348 | Eshelman et al. | Sep 2016 | B2 |
| 9433386 | Mestha et al. | Sep 2016 | B2 |
| 9445764 | Gross et al. | Sep 2016 | B2 |
| 9460596 | Moses | Oct 2016 | B1 |
| 9462955 | Zhou et al. | Oct 2016 | B2 |
| 9554740 | Saeed et al. | Jan 2017 | B2 |
| 9554756 | Menzel | Jan 2017 | B2 |
| 9607495 | Tivig et al. | Mar 2017 | B2 |
| 9610060 | Jaeschke et al. | Apr 2017 | B2 |
| 9659365 | Groth et al. | May 2017 | B2 |
| 9761100 | Anson et al. | Sep 2017 | B2 |
| 10405757 | Hughes et al. | Sep 2019 | B2 |
| 20020014951 | Kramer et al. | Feb 2002 | A1 |
| 20050020887 | Goldberg | Jan 2005 | A1 |
| 20050197585 | Brockway et al. | Sep 2005 | A1 |
| 20060009699 | Roteliuk et al. | Jan 2006 | A1 |
| 20060076463 | Drew | Apr 2006 | A1 |
| 20060142808 | Pearce et al. | Jun 2006 | A1 |
| 20060235309 | McIntyre | Oct 2006 | A1 |
| 20060281980 | Randlov et al. | Dec 2006 | A1 |
| 20070002791 | Kasprzyk et al. | Jan 2007 | A1 |
| 20070255114 | Ackermann | Nov 2007 | A1 |
| 20070282208 | Jacobs et al. | Dec 2007 | A1 |
| 20070287924 | Glocker et al. | Dec 2007 | A1 |
| 20080030468 | Ali et al. | Feb 2008 | A1 |
| 20080045814 | Busch | Feb 2008 | A1 |
| 20080058614 | Banet et al. | Mar 2008 | A1 |
| 20080108884 | Kiani | May 2008 | A1 |
| 20080154100 | Thalmeler et al. | Jun 2008 | A1 |
| 20080214903 | Orbach | Sep 2008 | A1 |
| 20080214904 | Saeed et al. | Sep 2008 | A1 |
| 20080221461 | Zhou et al. | Sep 2008 | A1 |
| 20080235058 | Friedman et al. | Sep 2008 | A1 |
| 20080255432 | Nielsen et al. | Oct 2008 | A1 |
| 20080288180 | Hayter | Nov 2008 | A1 |
| 20090005703 | Fasciano | Jan 2009 | A1 |
| 20090216132 | Orbach | Aug 2009 | A1 |
| 20100081944 | Baker, Jr. | Apr 2010 | A1 |
| 20100099991 | Snyder | Apr 2010 | A1 |
| 20100168596 | Jaeschke et al. | Jul 2010 | A1 |
| 20100241013 | Hatib | Sep 2010 | A1 |
| 20100259395 | Nuthi | Oct 2010 | A1 |
| 20100261979 | Kiani | Oct 2010 | A1 |
| 20100261982 | Noury et al. | Oct 2010 | A1 |
| 20100312115 | Dentinger | Dec 2010 | A1 |
| 20100331708 | Hatib | Dec 2010 | A1 |
| 20110009714 | Zong | Jan 2011 | A1 |
| 20110029248 | Saeed et al. | Feb 2011 | A1 |
| 20110060234 | Zhou et al. | Mar 2011 | A1 |
| 20110208066 | Gnadinger | Aug 2011 | A1 |
| 20110263992 | Guelen et al. | Oct 2011 | A1 |
| 20110263994 | Burns et al. | Oct 2011 | A1 |
| 20110270069 | Acquista | Nov 2011 | A1 |
| 20110295085 | Goldberg | Dec 2011 | A1 |
| 20110316704 | Nielsen et al. | Dec 2011 | A1 |
| 20120078665 | Johnson et al. | Mar 2012 | A1 |
| 20120089034 | Woehrle | Apr 2012 | A1 |
| 20120116194 | Gross et al. | May 2012 | A1 |
| 20120116218 | Martin et al. | May 2012 | A1 |
| 20120123279 | Brueser et al. | May 2012 | A1 |
| 20120179017 | Satou et al. | Jul 2012 | A1 |
| 20120191467 | LaPlante et al. | Jul 2012 | A1 |
| 20120197146 | Tan et al. | Aug 2012 | A1 |
| 20120203076 | Fatta et al. | Sep 2012 | A1 |
| 20120253156 | Muhisteff | Oct 2012 | A1 |
| 20120277673 | Levin et al. | Nov 2012 | A1 |
| 20120296177 | Von Arx et al. | Nov 2012 | A1 |
| 20130006126 | Band et al. | Jan 2013 | A1 |
| 20130013331 | Horseman | Jan 2013 | A1 |
| 20130046197 | Dlugos, Jr. et al. | Feb 2013 | A1 |
| 20130053655 | Castellanos | Feb 2013 | A1 |
| 20130085357 | Huber et al. | Apr 2013 | A1 |
| 20130090566 | Muhisteffet | Apr 2013 | A1 |
| 20130109927 | Menzel | May 2013 | A1 |
| 20130109928 | Menzel | May 2013 | A1 |
| 20130109929 | Menzel | May 2013 | A1 |
| 20130204104 | Michard et al. | Aug 2013 | A1 |
| 20130245463 | Stuebe et al. | Sep 2013 | A1 |
| 20130262730 | Al-Ali et al. | Oct 2013 | A1 |
| 20130263855 | Tivig et al. | Oct 2013 | A1 |
| 20140018650 | Lord | Jan 2014 | A1 |
| 20140066765 | Fan | Mar 2014 | A1 |
| 20140073883 | Rao et al. | Mar 2014 | A1 |
| 20140074179 | Heldman et al. | Mar 2014 | A1 |
| 20140077967 | Alvarez Osuna et al. | Mar 2014 | A1 |
| 20140081089 | O'Neill | Mar 2014 | A1 |
| 20140148702 | Chen | May 2014 | A1 |
| 20140159921 | Qualey et al. | Jun 2014 | A1 |
| 20140163362 | Pahlevan et al. | Jun 2014 | A1 |
| 20140187941 | Shusterman | Jul 2014 | A1 |
| 20140206964 | Saffarian | Jul 2014 | A1 |
| 20140235963 | Edwards et al. | Aug 2014 | A1 |
| 20140236249 | Rao et al. | Aug 2014 | A1 |
| 20140257058 | Clarysse et al. | Sep 2014 | A1 |
| 20140275849 | Acquista | Sep 2014 | A1 |
| 20140286361 | Risher-Kelly | Sep 2014 | A1 |
| 20140288947 | Simpson et al. | Sep 2014 | A1 |
| 20150097701 | Al-Ali | Apr 2015 | A1 |
| 20150155912 | Winward et al. | Jun 2015 | A1 |
| 20150220696 | Lekutai et al. | Aug 2015 | A1 |
| 20150306313 | Baykal | Oct 2015 | A1 |
| 20150313505 | Acquista | Nov 2015 | A1 |
| 20150356255 | Simpson et al. | Dec 2015 | A1 |
| 20160081562 | Lachhman | Mar 2016 | A1 |
| 20160095976 | Simpson et al. | Apr 2016 | A1 |
| 20160125142 | Awad | May 2016 | A1 |
| 20160203288 | Meng et al. | Jul 2016 | A1 |
| 20160213924 | Coleman et al. | Jul 2016 | A1 |
| 20160278869 | Grunwald | Sep 2016 | A1 |
| 20190380595 | Hughes | Dec 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 62-129032 | Jun 1987 | JP |
| 2011-10112 | Jan 2011 | JP |
| WO 1992022240 | Dec 1992 | WO |
| WO 199825532 | Jun 1998 | WO |
| WO 2006033812 | Mar 2006 | WO |
| WO 2006083933 | Aug 2006 | WO |
| WO 2006113366 | Oct 2006 | WO |
| WO 2013056160 | Apr 2013 | WO |
| WO 2013088314 | Jun 2013 | WO |
| WO 2013158314 | Oct 2013 | WO |
| WO 2013173520 | Nov 2013 | WO |
| WO 2013171620 | Nov 2013 | WO |
| WO 2014020484 | Feb 2014 | WO |
| WO 2015130705 | Feb 2015 | WO |
| WO 2017070120 | Apr 2017 | WO |
| Entry |
|---|
| US 8,613,701 B2, 12/2013, Rao et al. (withdrawn) |
| Supplemental Partial European Search Report in European Application No. 16858074.4 dated May 9, 2019. |
| International Search Report and Written Opinion for International Application No. PCT/US2016/057553, Notification dated Feb. 16, 2017. |
| Anliker et al., “AMON: A Wearable Multiparameter Medical Monitoring and Alert System,” IEEE Transaction on Information Technology in Biomedicine, Jan. 2005. |
| Philips M80001A and M80002A Data Sheet, “IntelliVue Patient Monitor MP20/MP20 Junior/MP30,” 2004. |
| U.S. Appl. No. 14/630,399, filed Feb. 24, 2015, Hughes. |
| Number | Date | Country | |
|---|---|---|---|
| 20180228386 A1 | Aug 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62243555 | Oct 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2016/057553 | Oct 2016 | US |
| Child | 15954218 | US |
