Patient monitoring device with improved user interface
A system for monitoring a patient in a bed can include one or more hardware processors that can receive sensor data from a sensor attached to the patient. The one or more hardware processors can determine, based on the sensor data, an orientation of an upper portion of the patient's body relative to a plane that extends along a portion of the bed that is adjacent to a lower portion of the patient's body.
Latest Masimo Corporation Patents:
Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference under 37 CFR 1.57.
FIELDThe present disclosure relates to the field of patient monitoring. More specifically, the disclosure describes, among other things, devices, systems, and methods for monitoring and/or displaying information regarding a patient's position, orientation, and/or movement in a medical environment, and an improved graphical user interface.
BACKGROUNDIn clinical settings, such as hospitals, nursing homes, convalescent homes, skilled nursing facilities, post-surgical recovery centers, and the like, patients are frequently confined to a bed for extended periods of time. Sometimes the patients are unconscious or sedated to such an extent that they have limited ability to change or control their position and/or orientation in the bed. Such patients often require assisted breathing apparatuses and, for example, may be intubated with an intubation tube. Maintaining proper airflow through an intubation tube may require correct positioning of the intubation tube and/or proper positioning of the patient to prevent inhibited airflow through the intubation tube that may develop as the result of deformation in the tube. Such patients can also be at risk of forming pressure ulcers, which pose a serious risk to the patient's health and well-being. Pressure ulcers, which may also be referred to as “bed sores,” “pressure sores,” and “decubitus ulcers,” involve injury to a patient's skin, and often the underlying tissue, which results from prolonged pressure forces applied to a site on the patient's body. Frequently, pressure ulcers develop on skin that covers bony areas of the body which have less muscle and/or fat tissue below the surface to distribute pressure applied thereto. Pressure ulcers can develop when such skin is subjected to prolonged contact with a surface of a bed or chair. Examples of such body locations include the back or side of the head, shoulders, shoulder blades, elbows, spine, hips, lower back, tailbone, heels, ankles, and skin behind the knees.
Pressure ulcers are caused by application of pressure at an anatomical site that occludes blood flow to the skin and other tissue near the location. Sustained pressure between a structural surface (such as a bed) and a particular point on the patient's body can restrict blood flow when the applied pressure is greater than the blood pressure flowing through the capillaries that deliver oxygen and other nutrients to the skin and other tissue. Deprived of oxygen and nutrients, the skin cells can become damaged, leading to tissue necrosis in as few as 2 to 6 hours. While hospital-acquired pressure ulcers commonly occur in elderly and mobility-impaired populations, such ulcers are considered to be preventable and have been termed “never events.” In some cases, medical insurance carriers have imposed restrictions on the amount they will reimburse a hospital for pressure ulcer treatment, and state and federal legislation now requires hospitals to report the occurrence of pressure ulcers in their facilities.
Risk factors for pressure ulcers can be categorized as modifiable and non-modifiable. Modifiable risk factors include actions that healthcare providers can take, while non-modifiable risk factors include aspects of patient health and behavior. It is valuable to document such non-modifiable risk factors so that caregivers can identify and attend to patients at risk of developing pressure ulcers. It is recommended that caregivers develop a documented risk assessment policy to predict the risk of a patient developing a pressure ulcer. Such an assessment can encompass all aspects of a patient's health and environment, and may employ commonly used measures in the field, such as the Braden and Norton scales. Such risk assessment tools may be used to direct preventative strategies not only when a patient is at rest in his or her bed, but also when undergoing surgery.
Additional factors that can contribute to the formation of pressure ulcers include friction and shear forces. Friction can occur when skin is dragged across a surface which can happen when patients are moved, especially when the skin is moist. Such frictional forces can damage the skin and make it more vulnerable to injury, including formation of a pressure ulcer. Shear forces occur when two forces move in opposite directions. For example, when the head portion of a bed is elevated at an incline, the patient's spine, tailbone, and hip regions tend to slide downward due to gravity. As the bony portion of the patient's body moves downward, the skin covering the area can stay in its current position, thereby pulling in the opposite direction of the skeletal structure. Such shear motion can injure the skin and blood vessels at the site, causing the skin and other local tissue to be vulnerable to formation of a pressure ulcer.
An established practice for patients at risk of forming pressure ulcers is to follow a turning protocol by which the patient is periodically repositioned, or “turned” to redistribute pressure forces placed on various points of the patient's body. Individuals at risk for a pressure ulcer are repositioned regularly. It is commonly suggested that patients be repositioned every 2 hours at specific inclination angles, and that the method of doing so minimizes the amount of friction and shear on the patient's skin. A repositioning log can be maintained and include key information, such as the time, body orientation, and outcome.
Pressure ulcer prevention programs have been effective and can reduce long-term costs associated with treatment. A 2002 study employed a comprehensive prevention program in two long-term care facilities, costing $519.73 per resident per month. Results of the program revealed pressure ulcer prevalence to be reduced by 87% and 76% in the two facilities. A later study found that prevention strategies were able to reduce pressure ulcer prevalence from 29.6% to 0% in a medical intensive care unit, and from 9.2% to 6.6% across all units of the hospital. These interventions employed strategies such as manual patient repositioning and logging, tissue visualization and palpation, pressure-reducing mattresses, and use of risk assessment tools. Turning protocols, however, do not take into consideration position changes made by the patient between established turn intervals, which, in common practice, are neither observed nor recorded. Thus, it is possible that in some circumstances, the act of following a turn protocol can have an unintended negative clinical effect.
Caregivers employ a variety of medical devices (for example, physiological sensors) that interact with patient monitoring devices which display a significant amount of patient health information. Such information is typically displayed on handheld monitoring devices or stationary monitoring devices with limited visual “real estate.” Often if not always, multiple patients are being monitored at once. Further, such health information is constantly fluctuating for multiple patients in a simultaneous manner, increasing the difficulty for a caregiver to locate, evaluate, and respond to a particular piece of health information for a particular patient. Because caregivers are under significant time pressure and only have a small amount of time to monitor, respond to, and/or treat individual patients under their care, it is incredibly difficult for caregivers to quickly obtain information regarding a patient's orientation at any given time, let alone evaluate such information and determine if the patient's orientation needs to be adjusted. Even the slightest speed advantage for caregivers in such situation can greatly reduce the likelihood that a patient will develop pressure ulcers and/or can enable caregivers to provide potentially life-saving treatment.
SUMMARYThis disclosure describes, among other things, embodiments of devices, systems, and/or methods for monitoring and/or displaying the orientation, position, and/or movement of a patient. As discussed throughout this disclosure, such monitoring can help to reduce or eliminate the formation of pressure ulcers in patients. This disclosure further describes an improved graphical user interface for displaying information related to a patient's orientation, position, and/or movement.
A patient monitor for monitoring an orientation of a patient to reduce a risk of the patient developing a pressure ulcer can comprise one or more hardware processors configured to receive output signals from a sensor attached to the patient. The sensor can be a wireless sensor and/or can include one or more accelerometers. The one or more hardware processors can be further configured to process said output signals and determine the patient's orientation. The one or more hardware processors can be further configured to maintain a plurality of timers, each of the plurality of timers associated with an available orientation of the patient and configured to account for a non-consecutive duration said patient is in said associated available orientation, wherein said non-consecutive duration is configured to vary in a first manner when said patient is oriented in said associated available orientation and vary in a second manner when said patient is not oriented in said associated available orientation. The patient monitor can further comprise a display screen configured to display an orientation trend of the patient in relation to a flat surface (for example, a bed) based on the maintained plurality of timers, wherein the one or more hardware processors are further configured to generate a structured display on the display screen. The structured display can comprise a patient representation configured to illustrate a current orientation of the patient in a bed, said current orientation being one of said available orientations. The non-consecutive duration can be configured to vary in the first manner by increasing when said patient is oriented in said associated available orientation and vary in the second manner by decreasing when said patient is not oriented in said associated available orientation. The non-consecutive duration can be configured to decrease down to a minimum of zero (0) when said patient is not oriented in said associated available orientation. The non-consecutive duration can be configured to increase up to a maximum value when said patient is oriented in said associated available orientation. The maximum value can equal, for example, 2 hours. When said non-consecutive duration increases above a maximum value, the one or more hardware processors of the patient monitor can be further configured to generate an alarm. The alarm can comprises at least one of a visual alarm and an auditory alarm. The one or more hardware processors of the patient monitor can be configured to generate a visual alarm by generating a flash or changing a color of the structured display. When said non-consecutive duration increases beyond a maximum value, the patient monitor can be configured to transmit a notification signal. The non-consecutive duration can be configured to vary in the first manner by decreasing when said patient is oriented in said associated available orientation and vary in the second manner by increasing when said patient is not oriented in said associated available orientation. The non-consecutive duration can be configured to decrease down to a minimum of zero (0) when said patient is oriented in said associated available orientation. The non-consecutive duration can be configured to increase up to a maximum value when said patient is not oriented in said associated available orientation. The maximum value can equal, for example, 2 hours. When said non-consecutive duration decreases below a minimum value, the one or more hardware processors of the patient monitor can be configured to generate an alarm. The alarm can comprise at least one of a visual alarm and an auditory alarm. The one or more hardware processors of the patient monitor can be configured to generate the visual alarm by generating a flash or changing a color of the structured display. When said non-consecutive duration decreases below a minimum value, the patient monitor can be configured to transmit a notification signal. The patient representation of the structured display can comprise at least a portion of a model patient. The patient representation of the structured display can comprise at least one of a 3D image of the model patient laying in a model hospital bed; an upper body of a 3D model patient; and a 3D image of the model patient in a walking or running position. The patient representation can further comprise one or more injury points. The structured display can comprise a heat map configured to graphically illustrate said non-consecutive durations of the patient in one or more of the available orientations. The heat map can be configured to vary in color based on the variability of said non-consecutive duration. The heat map can comprise a curved region bounded by a first curved segment and a second curved segment separated by a distance. The curved region can further comprise: a left end corresponding to a left side orientation of the patient in the hospital bed; and a right end corresponding to a right side orientation of the patient in the hospital bed, wherein a middle of the curved region corresponds to a supine position of the patient in the hospital bed and represents a line of symmetry of the curved region. The one or more hardware processors can be further configured to fill one or more of a plurality of lines in a selected portion of the curved region with a first color when the patient is in a first orientation less than a first time or a second color when the patient is in the first orientation greater than or equal to the first time. The one or more hardware processors can be configured to fill the one or more of the plurality of lines with either the first or second color in response to signal processing of data received from the sensor, and each of the plurality of lines can extend from the first curved segment to the second curved segment and represent a degree of orientation of the patient in the hospital bed. The one or more hardware processors can be configured to fill one or more of the plurality of lines with a third color representing an un-allowed patient orientation, and wherein the third color is different than both the first and second colors. The one or more hardware processors can be configured to display a hatched pattern between two of the plurality of lines in the curved region, wherein the hatched patent represents an un-allowed patient orientation. The structured display can further comprise an indicator located along the curved region and configured to indicate the current orientation of the patient in the hospital bed. The structured display can further comprise a patient inclination indicator configured to illustrate an incline position of the patient in the bed. The patient inclination indicator can be further configured to display an inclination degree of the patient in the bed. The structured display can further comprise a color legend. The structured display can further comprise an orientation graph configured to display a history of the patient's orientation over a time range.
Disclosed herein is a system for monitoring a patient such as in a bed. The system can comprise one or more hardware processors. The one or more hardware processors can be configured to receive sensor data from a sensor attached to the patient. The one or more hardware processors can be configured to determine, based on said sensor data, an orientation of an upper portion of the patient's body relative to a plane that extends along a portion of the bed that is adjacent to a lower portion of the patient's body.
In some implementations, the plane is substantially parallel with a surface upon which the bed is supported.
In some implementations, said determining said orientation comprises determining an angle between the upper portion of the patient's body and the plane, wherein said angle is relative to an axis that is substantially orthogonal to a longitudinal axis of the patient's body and parallel to the plane.
In some implementations, the one or more hardware processors are further configured to generate an alarm in response to determining that an angle between the upper portion of the patient's body and the plane is outside of a range of values.
In some implementations, the system may further comprise a display screen. The one or more hardware processors can be further configured to generate display data for rendering a graphical user interface on the display screen. The graphical user interface can comprise a graphic for illustrating an orientation history of the patient. The graphic can comprise a trend line corresponding to the orientation of the upper portion of the patient's body relative to the plane during a length of time. The graphic can comprise an upper threshold value corresponding to a first angle. The graphic can comprise a lower threshold value corresponding to a second angle.
In some implementations, the one or more hardware processors are further configured to modify a value of the upper threshold value or the lower threshold value in response to a user input via the graphical user interface.
In some implementations, the one or more hardware processors are further configured to modify an appearance of the trend line in response to determining that said orientation exceeds the upper threshold value or the lower threshold value.
In some implementations, modifying the appearance of the trend line includes modifying an appearance of a portion of the trend line that exceeds the upper threshold value or the lower threshold value and maintaining an appearance of a portion of the trend line that is within the upper threshold value and the lower threshold value.
In some implementations, the sensor includes one or more of a gyroscope or accelerometer, and the sensor data includes orientation related data.
In some implementations, said sensor comprises any of the sensors described herein.
In some implementations, the system further comprises a patient monitor, said patient monitor comprising the one or more hardware processors.
In some implementations, said patient monitor comprises any of the patient monitors described herein.
In some implementations, said graphical user interface comprises any of the graphical user interfaces described herein.
A system for monitoring a patient's orientation angle can comprise a physiological sensor device and a monitoring hub. The physiological sensor device can be coupled to an upper body portion of a patient. The physiological sensor device can comprise an inertial sensor. The inertial sensor can generate inertial data indicative of an orientation of at least the upper body portion the patient. The monitoring hub can wirelessly communicate with said physiological sensor device to access said inertial data therefrom. The monitoring hub can comprise one or more hardware processors and a display. The one or more hardware processors can determine, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity. The display can render an interactive graphical user interface that can comprise a first region that can comprise indicia of said pitch angle of the patient; and indicia of one or more orientation thresholds associated with said pitch angle. The one or more hardware processors can update said one more orientation thresholds responsive to a user input via the interactive graphical user interface. The one or more hardware processors can generate a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
In some implementations, the one or more hardware processors is further configured to adjust a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
In some implementations, the one or more hardware processors is further configured to determine a roll angle of the patient based on at least said inertial data, wherein said interactive graphical user interface further comprises a second region comprising indicia of said roll angle of the patient, the second region positioned adjacent to the first region within the interactive graphical user interface.
In some implementations, the one or more hardware processors is further configured to: determine a roll angle of the patient based on at least said inertial data; and detect a fall event of the patient based on at least said roll angle and said pitch angle, said fall event comprising a fall from a standing position or a fall from a seated or lying position.
In some implementations, the inertial sensor comprises an accelerometer, wherein the inertial data comprises acceleration data having three components, each of the three components comprising an acceleration magnitude and an acceleration direction, and the one or more hardware processors is further configured to determine the pitch angle based on at least one or more ratios of one or more of the three components of the acceleration data.
In some implementations, the one or more hardware processors is further configured to: determine a time associated with said pitch angle, said time indicating a time duration for which the patient has been oriented within a threshold of said pitch angle, said time duration comprising a single uninterrupted consecutive time duration or a plurality of non-consecutive time durations; and generate a head angle penalty alarm in response to determining that said time exceeds a head angle penalty threshold time.
In some implementations, the one or more hardware processors is further configured to: determine a time associated with said pitch angle, said time indicating a time duration for which the pitch angle has exceeded said one or more orientation thresholds, said time duration comprising a single uninterrupted consecutive time duration or a plurality of non-consecutive time durations; and generate said notification responsive to determining that said time exceeds a time threshold.
In some implementations, said user input comprises a sliding motion via the interactive graphical user interface, said sliding motion associated with adjusting a position of the indicia of the one or more orientation thresholds within said interactive graphical user interface.
In some implementations, the one or more hardware processors is further configured to update at least one of said one more orientation thresholds to include at least a first time-dependent value, said first time-dependent value comprising an angle corresponding to a duration of time.
In some implementations, the one or more hardware processors is further configured to automatically update said one more orientation thresholds based on at least an expiration of time.
In some implementations, the one or more hardware processors is further configured to determine said one or more orientation thresholds based on information associated with said patient, said information comprising one or more of patient demographics or patient medical history.
In some implementations, said one or more orientation thresholds comprises an upper orientation threshold and a lower orientation threshold.
In some implementations, said indicia of said pitch angle comprises a trend line indicating a real-time pitch angle of said patient and one or more historical pitch angles of said patient during a length of time.
In some implementations, said indicia of said pitch angle comprises a trend line, and the one or more hardware processors is further configured to cause the display to update the interactive graphical user interface to modify an appearance of said trend line responsive to determining that said pitch angle exceeds said one or more orientation thresholds, said modification comprising updating a color of said trend line or a color of a portion of said trend line.
In some implementations, the inertial sensor is detached from a bed in which the patient rests.
A method for monitoring a patient's orientation angle can comprise: accessing inertial data originating from an inertial sensor coupled to an upper body portion of a patient, said inertial data indicative of an orientation of at least said upper body portion the patient; determining, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity; displaying an interactive graphical user interface that can comprise indicia of said pitch angle of the patient and indicia of one or more orientation thresholds associated with said pitch angle; updating said one more orientation thresholds responsive to a user input via the interactive graphical user interface; and generating a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
In some implementations, the method can further comprise: adjusting a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
In some implementations, the method can further comprise: determining a roll angle of the patient based on at least said inertial data; and displaying, via the interactive graphical user interface, indicia of said roll angle of the patient adjacent to the indicia of said pitch angle of the patient within the interactive graphical user interface.
Non-transitory computer-readable media can include computer-executable instructions that, when executed by a computing system, cause the computing system to perform operations that can comprise: accessing inertial data originating from an inertial sensor coupled to an upper body portion of a patient, said inertial data indicative of an orientation of at least said upper body portion the patient; determining, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity; displaying an interactive graphical user interface that can comprise indicia of said pitch angle of the patient and indicia of one or more orientation thresholds associated with said pitch angle; updating said one more orientation thresholds responsive to a user input via the interactive graphical user interface; and generating a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
In some implementations, the non-transitory computer-readable media, when executed by the computing system, further cause the computing system to perform operations comprising: adjusting a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
Various combinations of the above and below recited features, embodiments, implementations, and aspects are also disclosed and contemplated by the present disclosure.
Additional implementations of the disclosure are described below in reference to the appended claims, which may serve as an additional summary of the disclosure.
In various implementations, systems and/or computer systems are disclosed that comprise a computer-readable storage medium having program instructions embodied therewith, and one or more processors configured to execute the program instructions to cause the systems and/or computer systems to perform operations comprising one or more aspects of the above- and/or below-described implementations (including one or more aspects of the appended claims).
In various implementations, computer-implemented methods are disclosed in which, by one or more processors executing program instructions, one or more aspects of the above- and/or below-described implementations (including one or more aspects of the appended claims) are implemented and/or performed.
In various implementations, computer program products comprising a computer-readable storage medium are disclosed, wherein the computer-readable storage medium has program instructions embodied therewith, the program instructions executable by one or more processors to cause the one or more processors to perform operations comprising one or more aspects of the above- and/or below-described implementations (including one or more aspects of the appended claims).
Throughout the drawings, reference numbers can be re-used to indicate correspondence between referenced elements. The following drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the disclosure.
While the foregoing “Brief Description of the Drawings” references generally various embodiments of the disclosure, an artisan will recognize from the disclosure herein that such embodiments are not mutually exclusive. Rather the artisan would recognize a myriad of combinations of some or all of such embodiments.
DETAILED DESCRIPTIONVarious embodiments will be described hereinafter with reference to the accompanying drawings. The drawings and the associated descriptions are provided to illustrate embodiments of the present disclosure and do not limit the scope of the claims. In the drawings, similar elements have similar reference numerals.
The present disclosure relates to devices, systems, and methods for monitoring and/or displaying information regarding a patient's position, orientation, and/or movement in a medical environment. The present disclosure also relates to an improved graphical user interface for displaying such information.
A system and/or method for monitoring and/or displaying information regarding a patient's position, orientation, and/or movement in a medical environment can include a patient-worn, wireless sensor including one or more sensors configured to obtain position, orientation and/or movement information from a patient and transmit such information to a patient monitor for display. The one or more sensors can include, for example, one or more accelerometers, gyroscopes, and/or magnetometers (i.e., compasses). Illustratively, the sensors can continuously or periodically (e.g., every second) obtain information that describes the patient's orientation in three dimensions. The wireless sensor can include a processor that is configured to process the obtained sensor information. The wireless sensor can also include a transmitter or transceiver configured to wirelessly transmit the processed sensor data, and/or information representative to and/or responsive to the sensor data, to a patient monitor (or other processing device) for further processing. The patient monitor can be configured to store and further process the received information, to display information indicative of or derived from the received data, and to transmit information to other patient care systems such as a multi-patient monitoring system which may be accessible from, for example, a nurses' station. The patient monitor can be configured to display and/or transmit alarms, alerts, and/or notifications to an external device and/or patient care system. The patient monitor can include a structured graphical user interface which displays the above-mentioned information in a static and/or dynamic fashion.
The wireless sensor 102 can also include a wireless transceiver 206 (see
The wireless sensor 102 can be affixed to the skin of the patient's body under the patient's garment as shown in
The wireless sensor 102 can be affixed to the patient's skin using any form of medically-appropriate adherent material, including a pressure-sensitive adhesive that is coated or applied to the bottom surface of the wireless sensor 102. One skilled in the art will appreciate that many other materials and techniques can be used to affix the wireless sensor 102 to the patient without departing from the scope of the present disclosure.
Frequently in clinical settings, multiple medical sensors are attached or adhered to a patient to concurrently monitor multiple physiological parameters. Some examples of medical sensors include, but are not limited to, position, orientation, and/or movement sensors, temperature sensors, respiration sensors, heart rate sensors, blood oxygen sensors (such as pulse oximetry sensors), acoustic sensors, electroencephalography (EEG) sensors, electrocardiogram (ECG) sensors, blood pressure sensors, sedation state sensors, to name a few. Typically, each sensor that is attached to a patient transmits, often by cable, the obtained physiological data to a nearby monitoring device configured to receive and process the sensor data, and transform it into clinical information to be used by care providers to monitor and manage the patient's condition. When a patient is concurrently monitored by several physiological sensors, the number of cables and the number of bedside monitoring devices used can be excessive and can limit the patient's freedom of movement and impede care providers' access to the patient. The cables connecting the patient to the bedside monitoring devices can also make it more difficult to move the patient from room to room or to switch to different bedside monitors.
Advantageously, the disclosed wireless sensor 102 can transmit data, wirelessly, to a patient data processing environment 105 in which the sensor data can be processed using one or more processing capabilities. As illustrated in
The extender/repeater 107 can receive sensor data from the wireless sensor 102 by way of the wireless communications link 104 and forward the received sensor data, via a network 108, to one or more processing nodes within the patient data processing environment 105. For example, the extender/repeater 107 can forward the received sensor data to a patient monitor 106 that might be located beyond the range of the wireless communications link 104 of a particular wireless sensor 102. Alternatively, the extender/repeater 107 can route the sensor data to other processing nodes within the patient data processing environment 105, such as, for example, a multi-patient monitoring system 110 or a nurses' station system 113 (see
In certain embodiments, the patient monitor 106 can process the sensor data provided by the wireless sensor 102. In other embodiments, processing of the sensor data can be performed by other processing nodes within the patient data processing environment 105. The patient monitor 106 can wirelessly communicate with the wireless sensor 102. The patient monitor 106 can include a display 120 (also referred to herein as a “display screen”) and/or a docking station that can mechanically and electrically mate with a portable patient monitor 122 also having a display 130. The patient monitor 106 can be contained within a movable, mountable, and portable housing formed in a generally upright, inclined shape configured to rest on a horizontal flat surface, as shown in
The display 120, alone or in combination with the display 130 of the portable patient monitor 122, can present a wide variety of measurement and/or treatment data in numerical and/or graphical (e.g., waveform) forms and/or can contain various display indicia. For example, the display 120 can display a variety of patient-specific configurations and/or parameters, such as the patient's weight, age, type of treatment, type of disease, type of medical condition, nutrition, hydration and/or length of stay, among others. In an embodiment, the display 120 occupies much of a front face of a housing of the patient monitor 106, although an artisan will appreciate the display 120 may comprise a table or tabletop horizontal configuration, a laptop-like configuration, or the like. Other embodiments may include communicating display information and data to a tablet computer, smartphone, television, or any display system recognizable to an artisan. Advantageously, the upright inclined configuration of the patient monitor 106, as illustrated in
The portable patient monitor 122 of
The removable battery isolator 320 can be a flexible strip made of an electrically insulating material that serves to block electrical communication between the battery 214 and an electrical contact (not shown) on the circuit board 340. The battery isolator 320 can be used to preserve battery power until the wireless sensor 102 is ready for use. The battery isolator 320 can block electrical connection between the battery 214 and the circuit board 340 until the battery isolator 320 is removed from the wireless sensor 102. The battery isolator 320 can be made of any material that possesses adequate flexibility to be slidably removed from its initial position and adequate dielectric properties so as to electrically isolate the battery from the circuit board 340. For example, the battery isolator 320 can be made of plastic, polymer film, paper, foam, combinations of such materials, or the like. The battery isolator 320 can include a pull tab 322 that extends through a slot 352 of the housing 350 when the wireless sensor 102 is assembled. The pull tab 322 can be textured to provide a frictional surface to aid in gripping and sliding the pull tab 322 out of its original assembled position. Once the battery isolator 320 is removed the battery 214 can electrically connect with the battery contact to energize the electronic components of the wireless sensor 102.
The mounting frame 330 is a structural support element that can help secure the battery 214 to the circuit board 340. The mounting frame 340 has wings 342 that, when assembled are slid between battery contacts 342 and the battery 214. Additionally, the mounting frame 330 serves to provide rigid structure between the circuit board 340 and the bottom base 310. According to some embodiments that include an acoustic respiratory sensor, the rigid structure transmits vibrational motion (vibrations) emanating from the patient (such as, for example, vibrational motions related to respiration, heartbeat, snoring, coughing, choking, wheezing, respiratory obstruction, and the like) to the accelerometer 210 positioned on the circuit board 340.
The circuit board 340, which may also be referred to herein as a substrate layer 340 and a circuit layer 340, mechanically supports and electrically connects electrical components to perform many of the functions of the wireless sensor 102. The circuit board 340 can include conduction tracks and connection pads. Such electrical components can include without limitation, a processor 202, a storage device 204, a wireless transceiver 206, an accelerometer 210, a gyroscope 212, a magnetometer 216, a temperature sensor 218, an acoustic respiration sensor 220, an ECG sensor 222, an oximetry sensor 224, a moisture sensor 226, and/or an impedance sensor 228 (see
As illustrated in
The housing 350 is a structural component that serves to contain and protect the components of the wireless sensor 102. The housing 350 can be made of any material that is capable of adequately protecting the electronic components of the wireless sensor 102. Examples of such materials include without limitation thermoplastics and thermosetting polymers. The housing 350 can include a slot 352 through which the battery isolator 320 is inserted during assembly. The housing 350 can also include a rim 354 that extends around the outer surface of the housing 350. The rim 354 can be used to secure the housing 350 in position relative to the bottom base 310 and the top base 360 when the wireless sensor 102 is assembled.
The wireless sensor 102 can be assembled in a variety of ways. The circuit board 340 and battery holder 342 holding the battery 214 can be placed into the housing 350. The wings 332 of the mounting frame 330 can be inserted in between the battery 214 and the battery holder 342 so as to align the mounting frame 330 with the circuit board 340. The battery isolator 320 can then be positioned between the battery contact and the battery 214. The pull tab 322 of the battery isolator 320 can then be fed through the slot 352 in the housing 350. The top base 360 can then be positioned over the housing 350, which can house the assembled circuit board 340, battery holder 342, battery 214, mounting frame 330, and battery isolator 320, using the cut-out 362 for alignment. The rim 354 of the housing 350 can adhere to the bottom surface of the top base 360, which can be coated with high tack, medical-grade adhesive. The partial assembly, which now includes the top base 360, the housing 350, the circuit board 340, the battery holder 342, the battery 214, the mounting frame 330, and the battery isolator 320, can be positioned centrally onto the top surface of the bottom base 310, aligning the edges of the base top 360 with the edges of the base bottom 310. In some embodiments, a coupon (or die cutting tool) is used to cut away excess portions of the now combined top and bottom bases 360 and 310 to form a final shape of the wireless sensor 102. The bottom surface of the bottom base 310 can then be coated with a high tack, medical-grade adhesive, and a release liner (not shown) can be placed on the bottom surface of the bottom base 310 to protect the adhesive until it is time for use.
A perspective view of the assembled wireless sensor 102 is illustrated in
As illustrated by dotted lines in
The wireless sensor 102 can be worn by a patient who has been determined to be at risk of forming one or more pressure ulcers, for example, a patient who is confined to bed for an extended period of time. The wireless sensor 102 can continuously or periodically (e.g., every second) monitor the orientation of the patient to help determine whether the patient is repositioned frequently enough to reduce the patient's risk of forming a pressure ulcer. In certain embodiments, the wireless sensor 102 minimally processes measured acceleration and/or angular velocity data and wirelessly transmits the minimally-processed data to the patient monitor 106 by way of the wireless communications link 104. In some cases, such minimal processing can conserve power of the wireless sensor 102.
The wireless sensor 102 and the patient monitor 106 can be configured to utilize different wireless technologies to form the wireless communications link 104. In certain scenarios, it may be desirable to transmit data over Bluetooth or ZigBee, for example, when the distance between the wireless sensor 102 and the patient monitor 106 is within range of Bluetooth or ZigBee communication. Transmitting data using Bluetooth or ZigBee can be advantageous because these technologies require less power than other wireless technologies. Accordingly, longevity of embodiments of the disclosed wireless sensor 102 using batteries may be increased by using Bluetooth or ZigBee protocols.
In other scenarios, it may be desirable to transmit data using Wi-Fi or cellular telephony, for example, when the distance between the wireless sensor 102 and the patient monitor 106 is out of range of communication for Bluetooth or ZigBee. A wireless sensor 102 may be able to transmit data over a greater distance using Wi-Fi or cellular telephony than other wireless technologies. In still other scenarios, it may be desirable to transmit data using a first wireless technology and then automatically switching to a second wireless technology in order to maximize data transfer and/or energy efficiency.
In some embodiments, the wireless sensor 102 automatically transmits data over Bluetooth or ZigBee when the wireless sensor 102 is within a pre-determined distance from the bedside patient monitor 106. The wireless sensor 102 automatically transmits data over Wi-Fi or cellular telephony when the wireless sensor 102 is beyond a pre-determined distance away from the bedside patient monitor 106. In certain embodiments, the wireless sensor 102 can automatically convert from Bluetooth or ZigBee to Wi-Fi or cellular telephony, and vice versa, depending on the distance between the wireless sensor 102 and the bedside patient monitor 106.
In some embodiments, the wireless sensor 102 automatically transmits data over Bluetooth or ZigBee when the Bluetooth or ZigBee signal strength is sufficiently strong or when there is interference with Wi-Fi or cellular telephony. The wireless sensor 102 automatically transmits data over Wi-Fi or cellular telephony when the Bluetooth or ZigBee signal strength is not sufficiently strong. In certain embodiments, the wireless sensor 102 can automatically convert from Bluetooth or ZigBee to Wi-Fi or cellular telephony, and vice versa, depending on signal strength.
The patient monitor 106 can be operable to receive, store, and process the measured acceleration and angular velocity data transmitted by the wireless sensor 102 to determine the patient's orientation. Once determined, the patient monitor 106 can display the patient's current orientation and/or information related to the orientation. In some embodiments, the patient monitor 106 can display the patient's current orientation along with the patient's previous orientations over time, thereby providing a user (for example, a caregiver) the ability to view a historical record of the patient's orientation. As discussed in more detail below, the patient orientation and/or information related to the patient's orientation over time can be displayed and/or illustrated by a patient representation, historical graph, “heat map” (defined below), and/or timer, enabling the clinician to readily understand the patient's present positional state and the patient's position and/or orientation history. The patient monitor 106 can also be configured to keep track of the length of time the patient remains in a particular orientation. In some embodiments, the patient monitor 106 can display the amount of time the patient has been in the current (e.g., present) orientation. Additionally, the patient monitor 106 can determine when the patient remains in a particular orientation for a duration greater than that prescribed by a clinician according to a repositioning (e.g., turning) protocol. Under such conditions, the patent monitor 106 can issue alarms, alerts, and/or notifications to the patient and/or to caregivers indicating that the patient should be repositioned to adhere to the prescribed repositioning protocol to reduce the risk of pressure ulcer formation.
As illustrated in
The accelerometer 210 can be a three-dimensional (3D) accelerometer. The term 3D accelerometer as used herein includes its broad meaning known to a skilled artisan. Measurements from the accelerometer 210 of the wireless sensor 102 can be used to determine the patient's orientation. The accelerometer 210 can measure and output signals related to a linear acceleration of the patient with respect to gravity along three axes (for example, three, mutually orthogonal axes). For example, one axis, referred to as “roll,” can correspond to the longitudinal axis of and/or extending through the patient's body (for example, along a length and/or height of the patient). Accordingly, the roll reference measurement can be used to determine whether the patient is in the prone position (for example, face down), the supine position (for example, face up), or on a side. Another reference axis of the accelerometer 210 is referred to as “pitch.” The pitch axis can correspond to the locations about the patient's hip (for example, an axis extending between and/or through the patient's hips). The pitch measurement can be used to determine whether the patient is sitting up or lying down. A third reference axis of the accelerometer 210 is referred to as “yaw.” The yaw axis can correspond to a horizontal plane in which the patient is located. When in bed, the patient can be supported by a surface structure that generally fixes the patient's orientation with respect to the yaw axis. Thus, in certain embodiments, the yaw measurement is not used to determine the patient's orientation when in a bed. The three axes that the accelerometer 210 can measure linear acceleration with respect to can be referred to as the “X,” “Y,” and “Z” axes.
The accelerometer 210 can provide acceleration information along three axes, and it can provide acceleration information which is the equivalent of inertial acceleration minus local gravitational acceleration. The accelerometer 210 may be a micro-electromechanical system (MEMS), and it may include piezo-resistors, among other forms of implementation. The accelerometer 210 may be a high-impedance charge output or a low-impedance charge output accelerometer 210. In some embodiments, the accelerometer 210 may be a tri-axial accelerometer, and the output of the accelerometer 210 may include three signals, each of which represents measured acceleration along a particular axis. The output of the accelerometer 210 can be 8-bit, 12-bit, or any other appropriate-sized output signal. The outputs of the accelerometer may be in analog or digital form. The accelerometer 210 can be used to determine the position, orientation, and/or motion of the patient to which the wireless sensor 102 is attached.
In some embodiments, the gyroscope 212 is a three-axis digital gyroscope with angle resolution of two degrees and with a sensor drift adjustment capability of one degree. The term three-axis gyroscope as used herein includes its broad meaning known to a skilled artisan. The gyroscope 212 can provide outputs responsive to sensed angular velocity of the wireless sensor 102 (as affixed to the patient) with respect to three orthogonal axes corresponding to measurements of pitch, yaw, and roll (for example, see description provided above). A skilled artisan will appreciate that numerous other gyroscopes 212 can be used in the wireless sensor 102 without departing from the scope of the disclosure herein. In certain embodiments, the accelerometer 210 and gyroscope 212 can be integrated into a single hardware component which may be referred to as an inertial measurement unit (IMU). In some embodiments, the IMU can also include an embedded processor that handles, among other things, signal sampling, buffering, sensor calibration, and sensor fusion processing of the sensed inertial data. In other embodiments, the processor 202 can perform these functions. And in still other embodiments, the sensed inertial data are minimally processed by the components of the wireless sensor 102 and transmitted to an external system, such as the patient monitor 106, for further processing, thereby minimizing the complexity, power consumption, and cost of the wireless sensor 102, which may be a single-use, disposable product.
According to an embodiment, a system and method are described herein to calculate three-dimensional position and orientation of an object derived from inputs from three sensors attached to the object: an accelerometer 210 configured to measure linear acceleration along three axes; a gyroscope 212 configured to measure angular velocity around three axes; and a magnetometer 214 configured to measure the strength of a magnetic field (such as the Earth's magnetic field) along three axes. In an embodiment, the three sensors 210, 212, and 214 are attached to or contained within to the wireless sensor 102 which is affixed to the patient. According to an embodiment, the sensors 210, 212, and 214 are sampled at a rate between approximately 10 Hz and approximately 100 Hz. One skilled in the art will appreciate that the sensors 210, 212, and 214 can be sampled at different rates without deviating from the scope of the present disclosure. The sampled data from the three sensors 210, 212, and 214, which provide nine sensor inputs, can be processed to describe the patient's position and orientation in three-dimensional space. In an embodiment, the patient's position and orientation are described in terms of Euler angles as a set of rotations around a set of X-Y-Z axes of the patient (for example, three, mutually orthogonal axes).
Also illustrated in
The acoustic respiration sensor 220 can be used to sense vibrational motion from the patient's body (for example, the patient's chest) that are indicative of various physiologic parameters and/or conditions, including without limitation, heart rate, respiration rate, snoring, coughing, choking, wheezing, and respiratory obstruction (for example, apneic events). The ECG sensor 222 can be used to measure the patient's cardiac activity. According to an embodiment, the ECG sensor 222 includes two electrodes and a single lead. The oximetry sensor(s) 224 can be used to monitor the patient's pulse oximetry, a widely accepted noninvasive procedure for measuring the oxygen saturation level of arterial blood, an indicator of a person's oxygen supply. A typical pulse oximetry system utilizes an optical sensor clipped onto a portion of the patient's body (such as, for example, a fingertip, an ear lobe, a nostril, and the like) to measure the relative volume of oxygenated hemoglobin in pulsatile arterial blood flowing within the portion of the body being sensed. Oxygen saturation (SpO2), pulse rate, a plethysmograph waveform, perfusion index (PI), pleth variability index (PVI), methemoglobin (MetHb), carboxyhemoglobin (CoHb), total hemoglobin (tHb), glucose, and/or otherwise can be measured and monitored using the oximetry sensor(s) 224. The moisture sensor 226 can be used to determine a moisture content of the patient's skin which is a relevant clinical factor in assessing the patient's risk of forming a pressure ulcer. The impedance sensor 228 can be used to track fluid levels of the patient. For example, the impedance sensor 228 can monitor and detect edema, heart failure progression, and sepsis in the patient.
An artisan will recognize from the disclosure herein that the instrument board 374 may comprise a large number of electronic components organized in a large number of ways. Using different boards such as those disclosed above advantageously provides organization and compartmentalization to the complex system.
As discussed elsewhere herein, the patient monitor 106 can keep track of the orientation of a monitored patient over time and across a plurality of orientations of the patient while in a bed (for example, a hospital bed). Methods and systems for monitoring the orientation of a patient are described in U.S. Pat. No. 10,383,527, which is incorporated by reference in its entirety. The patient monitor 106 can receive data (continuously or intermittently) from sensor 102 regarding the patient's orientation over time and can store such data in memory (such as memory 391). The patient monitor 106 can determine the time spent in each of a plurality of available orientations (for example, orientations that a patient can assume when lying on a flat surface such as a hospital bed) when the patient is in each orientation, and can store the accumulated time in such orientations in a portion of memory associated with that given orientation. For example, the patient monitor 106 can associate a timer with each of a plurality of available patient orientations and associate each of the plurality of available patient orientations with a degree of orientation (for example, left side position equals +90°) as discussed in more detail below. As such, the patient monitor 106 can keep a running log of time spent by the patient in a plurality of orientations, which can be advantageous for the purposes of following a turning protocol to avoid the development of pressure ulcers. Further, the patient monitor 106 can track time not spent in a plurality of orientations so as to provide a more holistic sense of the patient's orientation over time as discussed in more detail below. Monitoring non-consecutive durations of assumed patient orientations while also keeping track of accumulated and de-accumulated time in each of the assumed patient orientations can provide valuable information for caregivers in monitoring patients and preventing the patient from developing pressure ulcers, as also described in more detail below.
As mentioned above, the patient monitor 106 can keep a running log of time spent by the patient in a plurality of orientations to keep track of accumulated and de-accumulated time in assumed orientations. The patient monitor 106 can associate a plurality of timers with a plurality of available patient orientations. In an embodiment, the timers are implemented as counters. The patient monitor 106 can obtain data from the sensor 102 regarding the orientation of the patient, such as the degree of orientation of the patient relative to a reference point (for example, a hospital bed). Such degree of orientation can be indicative and/or representative of an angle between an axis extending normal to (for example, upward or downward from) a patient's torso or chest and an axis extending along a length and/or height of the patient (for example, the “roll” axis discussed above). Each of the plurality of timers can be associated with a degree of orientation of the patient. For example, each of the plurality of timers can be associated with a degree selected within a range between 0° and 360° or 0° and 180°, or −90° and 90°. As another example, each of the plurality of timers can be associated with a degree of orientation equal to 0°, 10°, 20°, 30°, 40°, 50°, 60°, 70°, 80°, 90°, 100°, 110°, 120°, 130°, 140°, 150°, 160°, 170°, 180°, 190°, 200°, 210°, 220°, 230°, 240°, 250°, 260°, 270°, 280°, 290°, 300°, 310°, 320°, 330°, 340°, 350°, or 360°, or any value therebetween, or any range bounded by any combination of these values, although values outside these values or ranges can be used in some cases. As another example, each of the plurality of timers can be associated with a degree of orientation equal to −90°, −80°, −70°, −60°, −50°, −40°, −30°, −20°, −10°, 0°, 10°, 20°, 30°, 40°, 50°, 60°, 70°, 80°, or 90°, or any value therebetween, or any range bounded by any combination of these values, although values outside these values or ranges can be used in some cases. As another example, the plurality of timers can include 180 timers, each of which are associated with a different one of the degrees from 0° to 180°. As another example, each of the plurality of timers can be associated with a degree “range,” such as 0°-45°, 46°-90°, 91°-135°, 136°-180°, and/or a different range selected from any combination of the values or ranges described above.
As shown in Table 1, −90° can represent a right side position of the patient with respect to a flat plane or surface used as a reference point (such as the hospital bed). When monitoring a patient and attempting to ensure that the patient does not develop pressure ulcers, it is important to make sure the patient does not remain in a particular orientation for too long. Additionally, it is important to keep track of non-consecutive durations of assumed orientations and accumulated and de-accumulated time in assumed orientations so that a patient does not return to a previously assumed orientation before enough time has elapsed. Advantageously, the patient monitor 106 can track time spent in assumed orientations over time and allow tracked (for example, “accumulated”) time in previous orientations to de-accumulate (for example, decrease) when the patient is not in those orientations.
Table 1 shows a simplified diagram/format that can be utilized by the patient monitor 106 to keep a running log of time spent in (and/or time not spent in) a plurality of orientations. While the simplified diagram contains only 5 columns and illustrates three “degree” orientations (−90°, 0°, +90°), the patient monitor 106 can generate a time log for any orientation and/or degree in between these values/orientations or beyond these values/orientations (for example, between 0°-180° or) 0°-360°. As shown in the non-limiting, illustrative example of Table 1, the accumulated time in the 0° (supine) orientation—which is, as illustrated by the highlighted cells, a current orientation of the patient—is 22 minutes and 15 seconds. Exemplary Table 1 can be, for example, stored in a memory of the patient monitor 106, such as memory 391. As also illustrated in Table 1, the accumulated time in the −90° (right side) orientation is 58 minutes and 34 seconds, and the accumulated time in the 90° (left side) orientation is 20 minutes and 25 seconds.
While the accumulated time is illustrated as having a “minute” and “second” value, the accumulated time can have additionally have an “hour” value. For example, the accumulated time can be “1:20:35” representing 1 hour, 20 minutes, and 35 seconds. As discussed above, the one or more hardware processors can track the change of accumulated time in a current orientation (in Table 1, the supine position as indicated by the underlining), and also simultaneously track the change of accumulated time in all other previously-used orientations, such as the right and left side positions. While Table 1 and the foregoing discussion mentions patient orientations with respect to and/or between −90° (right side) and 90° (left side) orientations, one skilled in the art will recognize that the same disclosure is applicable to degrees and/or orientations beyond these values and/or ranges. For example, the patient monitor 106 can keep track of time spent in orientations where the patient is prone (on stomach) and/or between the prone orientation and/or the right or left side position, where orientations and degrees associated with such orientations can be between −90° (right side) and 180° (stomach), for example.
Each of the plurality of timers associated with an orientation of the patient (such as a degree of orientation or range of degrees of the patient) can increase (for example, count up) from a value (such as zero) when the patient assumes a given orientation. For example, assuming the patient was recently placed in a hospital bed and therefore has spent no prior time in each of the plurality of orientations, each of the timers associated with one of the plurality of available orientations can have zero accumulated time. As soon as the patient assumes a particular orientation (for example, a “first orientation”) among the plurality of available orientations, the patient monitor 106 can receive and process orientation data from the sensor 102 and begin tracking and storing the time spent in that particular, “first” orientation. Thus, the timer associated with that particular, first orientation can begin to increase. If and/or when the patient switches to another, “second” orientation (which can be associated with a different degree of orientation compared to the first orientation, for example), the one or more hardware processors of the patient monitor 106 can determine that such switch or change occurred based on data received from the wireless sensor 102 and determine the new orientation, and thereafter trigger a timer associated with the new, second orientation, which can then begin increasing or counting up, for example. Simultaneous to the “counting up” of the timer associated with the second orientation, the timer associated with the previous, first orientation can begin changing, for example, by decreasing downward toward zero. Further, if and/or when the patient returns to the first orientation, the timer associated with the second orientation can begin counting down simultaneous to the timer associated with the first orientation counting up. Thus, the timers associated with the plurality of patient orientations can advantageously keep track of non-consecutive durations of orientations assumed by a patient.
Keeping track of non-consecutive durations of a plurality of patient orientations and such accumulation/de-accumulation of time in assumed/non-assumed orientations advantageously provides a holistic view of time spent in the plurality of orientations. Further, keeping track of time not spent in previously-assumed orientations incorporates the concept that time not spent in a previously-assumed orientation “relieves” portions of the patient's body from pressure and allows the portions to restore in their capacity to withstand pressure without developing pressure ulcers.
The patient monitor 106 can log accumulated and/or de-accumulated time in each of a plurality of orientations (for example, degree of orientation) in relation to time limits or maximums, for example. In following a turning and/or monitoring protocol to avoid the development of pressure ulcers in patients, caregivers may have maximum time limits that a patient can be in a given orientation. For example, the maximum time that a patient can be in a given orientation can be 15 minutes, 30 minutes, 45 minutes, 1 hour, 1 hour and 15 minutes, 1 hour and 30 minutes, 1 hour and 45 minutes, or 2 hours, among other values. This maximum time limit can be the same for each of the plurality of available orientations or it may be different. For example, if a portion of the patient's body is more susceptible or vulnerable to develop pressure ulcers, a maximum time limit associated with an orientation that corresponds to that portion of the patient's body can have a smaller maximum time limit than other patient orientations. The timers associated with each of the plurality of positions can also keep track of overage time-time spent in an orientation that is beyond the maximum time limit. For example, where the maximum time limit for a given orientation is 1 hour, when the patient is in the given orientation for more than 1 hour, the timer can continue to count up to keep track of the overage time. Alternatively, the timers can stop counting up and hold steady at the maximum time limit when such limit is reached.
While the patient monitor 106 can keep track of accumulated and de-accumulated time spent in a particular orientation by having a timer associated with such orientation count up when a patient assumes the orientation and count down when the patient is not in such orientation, the patient monitor 106 can track time spent in a particular orientation in an alternative manner. For example, the patient monitor 106 can keep track of accumulated and de-accumulated time spent in a particular orientation by having a timer associated with such orientation count down when a patient assumes the orientation and count up when the patient is not in such orientation. For example, when a patient transitions to a new orientation, a timer associated with that orientation can count down from a maximum time limit. As discussed above, the maximum time limit can be any limit prescribed or predetermined by a caregiver, such as 2 hours, 1 hour, 30 minutes, among others. Thus, as the patient remains in that orientation, the timer associated with that orientation can continue to count down towards, for example, zero. The value of time in such timer therefore can show the instantaneous time “available” or left for the patient to remain in that orientation. When the patient switches to another orientation, a timer associated with the new orientation can begin to count down from a maximum time limit (which can be the same or different from the maximum time limit associated with the previous orientation) while the timer associated with the previous orientation can simultaneously count up, thus “restoring” the time available for the patient to assume that orientation. The timers associated with each of the plurality of positions can also keep track of time spent in an orientation that is beyond the maximum time limit. For example, where the maximum time limit for a given orientation is 1 hour, when the patient is in the given orientation for more than 1 hour, the timer can continue to count down past zero (for example, can show or keep track of a negative time value) to keep track of the overage time. Alternatively, the timers can stop counting down and hold steady when the maximum time limit is reached or runs out.
Regardless of whether the timers associated with each of a plurality of patient orientations count up when a patient is in a given position and count down when the patient is not in the given position, or count down when a patient is in a given position and count up when the patient is not in the given position, the patient monitor 106 can provide valuable information that can be used by a caregiver in following a patient turn protocol to prevent patients from developing pressure ulcers. As will be discussed below, such tracking of accumulated and/or de-accumulated time in various orientations can advantageously be utilized in a structured display of the patient monitor 106 in a variety of ways to provide valuable insight to caregivers, such as in providing visual or audio alarms or generating an orientation trend of the patient.
While the systems and methods of keeping track of the orientation of a patient are described above with reference to patient monitor 106, one of skill in the art will recognize that the same can be implemented by utilizing the multi-patient monitoring system 110, nurses' station systems 113, and/or other components or system.
The structured display 410 can include a bed 422 proximate to the patient representation 424. The bed 422 can be a 3D or 2D model of a hospital bed, for example. The bed 422 can be located adjacent, proximate, and/or underneath the patient representation 424. The bed 422 can help provide context and/or can aid a caregiver in assessing a monitored patient's orientation with reference to the patient representation 424. For example, the bed 422 can act as a reference point to further illustrate the orientation of the patient representation 424. The bed 422 can be configured to blink or disappear if the patient monitor 106 detects that the patient is not in the hospital bed as discussed further below.
The structured display 410 can include a timer 426 configured to show the time that the patient has spent in the current orientation. Timer 426 can display the accumulated time in a given orientation when the patient is currently in the given orientation. As discussed above, the one or more hardware processors of the patient monitor 106 can associate each of a plurality of available orientations with a timer configured to keep track of accumulated and de-accumulated time spent in each of the plurality of available orientations. The current orientation of the patient is one of such plurality of available orientations. Timer 426 can display the current value of accumulated/de-accumulated time associated with one of the timers associated with one of the plurality of available orientations when the patient is currently in that orientation. Timer 426 can be configured to count up when the patient remains in an orientation or alternatively count down when the patient remains in an orientation in a similar or identical manner as that described above with reference to the timers associated with each of the plurality of patient orientations. For example, if a patient is in a first orientation for 30 minutes, switches to a second orientation for 2 minutes, and then switches back to the first orientation thereafter, the timer 426 can be configured to show the accumulated/de-accumulated time associated with the first orientation, which in such case will be 28 minutes. Once the first orientation is resumed by the patient in this example, the timer 426 can count up from 28 minutes. Alternatively, as discussed further above, the timers associated with each of the plurality of positions can be configured to count down when a patient is in a given orientation. In such alternative scenario, if the patient is in a first orientation for 30 minutes and the timer associated with the first orientation is configured to count down from 1 hour (which can be a maximum time limit for the first orientation), and the patient switches to a second orientation for 2 minutes and then back to the first orientation thereafter, the timer 426 will display 32 minutes. Regardless of whether the timers for each of the plurality of orientations and the timer 426 is configured to count up or down when the patient is in a given orientation, the timer 426 can advantageously display an accumulated/de-accumulated time value associated with assumed patient orientations and therefore greatly assist a caregiver in monitoring a patient's orientation and following a turn protocol.
Timer 426 can display the current value of the accumulated/de-accumulated time of the orientation with hour, minute, and/or second values. For example, as shown in
Timer 426 can alert a caregiver when a patient has exceeded a maximum time limit in a given orientation. For example, if the patient has been in a given orientation for more than the maximum time limit, the timer 426 can be configured to blink at different speeds. Additionally or alternatively, if the patient has been in a given orientation for more than the maximum time limit, the timer 426 can be configured to change in color. For example, the timer 426 can display the current time in red when the patient has been in a given orientation for a time greater than the maximum time limit. Additionally or alternatively, if the patient has been in a given orientation for more than the maximum time limit, the timer 426 can be configured to change in size. For example, as shown in
The structured display 410 can include a patient inclination indicator 421 and/or a patient inclination degree indicator 420. The patient inclination indicator 421 can be configured to display an inclination of a hospital bed and/or a patient within the hospital bed. Further, the patient inclination degree indicator 420 can display the degree of inclination of the patient in or with respect to the hospital bed. For example, if the patient is laying inclined at a degree of 30° with respect to a flat plane (such as a lower portion of the hospital bed), the patient inclination indicator 421 can visually depict such inclination by showing an upper portion of a hospital bed inclined with respect to a lower portion of the hospital bed and/or the patient inclination degree indictor can visually display “30°” as illustrated in
As discussed in more detail above, the one or more hardware processors of patient monitor 106 can be configured to log accumulated and/or de-accumulated time in each of a plurality of orientations in relation to time limits or maximums. In following a turning and/or monitoring protocol to avoid the formation of pressure ulcers in patients, caregivers may have maximum time limits that a patient can be in a given orientation. For example, the maximum permissible time a patient should be in a given orientation can be selected by a caregiver to be 30 minutes, 1 hour, or 2 hours, among other values. The patient monitor 106 can incorporate maximum limit adjuster which can allow a caregiver or user to select an appropriate time limit by which an alert can be triggered when the patient's accumulated time in a given orientation exceeds the time limit. The alerts that can be triggered in such situations can be any of the alerts discussed herein.
As discussed above, the patient monitor 106 can include one or more hardware processors that receive output signals from sensor 102 attached to the patient and process the output signals to determine information relating to the patient's orientation in, for example, a hospital bed. The one or more hardware processors can generate structured display 410 on a display screen of the patient monitor 106 which can include an orientation trend of a patient in a bed. The orientation trend can contain and/or illustrate information related to the patient's orientation. Further, this orientation trend can be associated with the plurality of timers—which are themselves associated with available orientations of the patient in a bed—that are configured to account for non-consecutive durations of the patient in one or more of the available orientations. The orientation trend can display (for example, illustrate) the accumulated/de-accumulated time of the patient in various orientations in a convenient and simple manner so that caregivers can quickly assess the orientation history of a patient and determine whether the patient is likely to develop a pressure ulcer or needs to be rotated and/or moved.
The orientation trend of the structured display 410 can include a heat map 414 configured to graphically illustrate the accumulated/de-accumulated time of the patient in a variety of orientations. The shape and/or structure of the heat map 414 can coincide and/or correspond with the plurality of available orientations discussed above. For example, the heat map 414 can be made up of a plurality of lines where each of the lines represent a degree of orientation of the patient in a hospital bed. As discussed above, the one or more hardware processors can keep track of the accumulated/de-accumulated time of a patient in a plurality of orientations. The one or more hardware processors can incorporate this information into the heat map 414 by varying a contrast of the heat map 414 as the accumulated/de-accumulated time of the patient in a given orientation increases and/or decreases. For example, the one or more hardware processors can keep a log of the patient's accumulated/de-accumulated time in a given orientation and vary a color of one of the plurality of lines of the heat map 414 that is associated with that given orientation. Each of the plurality of lines and/or plurality of orientations can be associated with a degree of orientation of the patient in and/or with respect to a flat plane (for example, a bed). For example, each of the plurality of lines can be associated with a degree of orientation available to the patient that is equal to 0°, 10°, 20°, 30°, 40°, 50°, 60°, 70°, 80°, 90°, 100°, 110°, 120°, 130°, 140°, 150°, 160°, 170°, 180°, 190°, 200°, 210°, 220°, 230°, 240°, 250°, 260°, 270°, 280°, 290°, 300°, 310°, 320°, 330°, 340°, 350°, or 360°, or any value therebetween, or any range bounded by any combination of these values, although values outside these values or ranges can be used in some cases. As another example, each of the plurality of lines can be associated with a degree of orientation available to the patient that is equal to −90°, −80°, −70°, −60°, −50°, −40°, −30°, −20°, −10°, 0°, 10°, 20°, 30°, 40°, 50°, 60°, 70°, 80°, or 90°, or any value therebetween, or any range bounded by any combination of these values, although values outside these values or ranges can be used in some cases. The above-listed degrees of orientation can be indicative and/or representative of an angle between an axis extending normal to (for example, upward or downward from) a patient's torso or chest and an axis extending along a length and/or height of the patient (for example, the “roll” axis discussed above). For example, the degrees listed above can represent an angle between a normal axis extending from a patient's chest and the roll axis.
With reference to
Based on the accumulated/de-accumulated time of the patient in the plurality of available positions as monitored by the plurality of timers, the one or more hardware processors can vary a contrast of the plurality of lines in the heat map 414. The structured display 410 of
As discussed above and shown in
The varying of contrast discussed above can be, for example, varying of color of one or more of the plurality of lines of the heat map 414. For example, based on the accumulated/de-accumulated time of the patient in the plurality of available positions as monitored by the plurality of timers, the one or more hardware processors can vary the color plurality of lines associated with the plurality of available positions and plurality of timers. The one or more hardware processors can vary the color of the plurality of lines based on a color spectrum. For example, the one or more hardware processors can vary the color of one or more of the plurality of lines between purple or blue to red, and/or vary the color based on a wavelength range, such as from 380-450 nm (representing approximate violet/purple wavelength range) to 625-750 nm (representing approximate red wavelength range). The one or more hardware processors can vary the color of the one or more of the plurality of lines from green (at or near a wavelength of 520-560 nm) to red. For example, the color of one or more of the plurality of lines can be green when the patient has some minimum accumulated time in an orientation but less than a first threshold, and the color can be varied from green to red as the patient's time in such orientation increases. For example, after the accumulated time the patient has been in a given orientation increases beyond the first threshold, the color of a line associated with that orientation can increase in wavelength from a wavelength associated with the color green to a wavelength associated with the color red). When the color is red, such color can indicate that the patient has accumulated time in the orientation at and/or greater than a second threshold (for example, a maximum time limit or threshold). The minimum accumulated time in the orientation sufficient to trigger a green color designation can be, for example, 5 seconds, 2 seconds, 1 second, or some other value. The first threshold can be, for example 30 minutes, 20 minutes, 10 minutes, 5 minutes, or some other value. The second threshold can be similar and/or identical to the maximum time limit that can be preset and/or predetermined by a caregiver and which is discussed further above. The structured display 410 can include a color legend 418 (see
Utilization of a color spectrum associated with accumulated time of a patient in orientations in the heat map 414 of structured display 410 can be significantly advantageous for caregivers. Caregivers monitor a great number of patients in clinical environments, and such monitoring involves keeping track of a large number of patient parameters and other data. Further, caregivers often employ multiple devices for monitoring such patients and patient parameters. The ability of the caregiver to simply glance at the heat map 414 and instantly obtain a holistic sense of the patient's recent orientation history and condition gives the caregiver a realistic opportunity to prevent and/or treat potentially life-threatening pressure ulcers.
Advantageously, the heat map 414 can include an indicator 442 (see
While
In addition or as an alternative to the heat map 414, 514, 614, 714, 814, the orientation trend of the structured display 410 can include an orientation graph 433. The orientation graph 433 can illustrate a history of the patient's orientation over a recent time range. The orientation graph 433 can include a first axis, which can be a position axis 432, and a second axis, which can be a time axis 434. The position axis 432 can include one or more markers indicative of patient orientations or positions. For example, the position axis 432 can include one, two, three, four, five, six, seven, or eight or more markers indicative of patient orientations or positions. As shown in
The time axis 434 can display one or more markers (such as one, two, three, four, five, six, seven, or eight or more markers) which can, similar to markers in the position axis 432, act as a reference point for data appearing in the orientation graph 433. Advantageously, the amount and/or position of the one or more markers of the time axis 434 can correspond with a time range which can appear in and/or be adjusted by time range adjuster 428. For example, where the time range is selected to be 1:00 hour using the range adjuster 428, the time axis 434 can be configured to display a 1 hour recent time range and/or can designate one or more markers spaced equally or unequally along this 1 hour recent time range on the time axis 434. The range adjuster 428 can allow a caregiver to increase the time range and/or decrease the time range using buttons or icons, which can be “+” or “−” icons as shown in
As discussed above, monitoring of the patient and/or orientation of the patient by the patient monitor 106 and the sensor 102 can be intermittent or continuous. Where the monitoring is continuous, the recent time range (defined by the time axis 434 of orientation graph 433) can be continuously updated to follow the current time. As the patient is continuously monitored, data regarding the patient's current orientation—represented in the orientation graph 433 with orientation data point 425—can be measured, processed, and plotted within the orientation graph 433, and the recent time range of the time axis 434 tracks along with such plotting. Thus, the patient's orientation over the recent time defined by the time axis 434 provides a reference by which newly measured orientation data can be measured and/or compared against.
As discussed above, the position axis 432 and/or the time axis 434 of the orientation graph 433 can act as a reference by which data regarding the patient's orientation can be compared, for example, by a caregiver. As orientation data is received by the patient monitor 106 from the sensor 102, such data can be associated with time and orientation values and is plotted in the orientation graph 433. Such data can be continuously plotted as a continuous line in the orientation graph 433, as shown in
Advantageously, the plot line 430 in the orientation graph can vary in contrast according to accumulated time in a given orientation. Based on the accumulated/de-accumulated time of the patient in one or more of the plurality of available positions as monitored by the plurality of timers, the one or more hardware processors can vary the contrast of the plot line 430. The orientation graph 433 of the structured display 410 of
As another example, the one or more hardware processors can vary the color of the data points in the orientation graph 433 from green (at or near a wavelength of 520-560 nm) to red. For example, the color of the data points can be green when the patient has some minimum accumulated time in an orientation but less than a first threshold, and the color can be varied from green to red as the patient's time in such orientation increases. For example, after the accumulated time the patient has been in a given orientation increases beyond the first threshold, the color of a data point or a set of data points associated with and/or near such orientation can increase in wavelength from a wavelength associated with the color green to a wavelength associated with the color red. When the color is red, such color can indicate that the patient has accumulated time in the orientation at and/or greater than a second threshold (for example, a maximum time limit or threshold). The minimum accumulated time in the orientation sufficient to trigger the green color designation can be, for example, 5 seconds, 2 seconds, 1 second, or some other value. The first threshold can be, for example 30 minutes, 20 minutes, 10 minutes, 5 minutes, or some other value. The second threshold can be similar and/or identical to the maximum time limit that can be preset and/or predetermined by a caregiver and which is discussed further above. The structured display 410 can include a color legend 418, which can include a range of utilized colors/wavelengths and reference time markers proximate to the legend (e.g., “2 h”, “1 h”, “0 h”) to provide the caregiver with guidance as to what the varying colors mean. Utilization of a color spectrum associated with accumulated time in orientations in the plot line 430 of structured display 410 can be significantly advantageous for caregivers. Caregivers monitor a great number of patients in clinical environments, and such monitoring involves keeping track of a high number of patient parameters and other data. Further, caregivers often employ multiple devices for monitoring such patients and patient parameters. The ability of the caregiver to simply glance at the plot line 430 and instantly obtain a holistic sense of the patient's recent orientation history and condition gives the caregiver a realistic opportunity to prevent and/or treat potentially life-threatening pressure ulcers.
Additionally, the orientation graph 433 can provide other valuable information to the caregiver regarding the patient's wellbeing and condition. For example, the variability in shape of the plot line 430 can provide information to the caregiver regarding the patient's movement and/or rotation, and can also provide insight into what orientations the patient prefers or does not prefer, especially since the orientation graph 433 can display the orientation history over a variable time range. For example, if the time axis 434 is configured to display the patient's orientation history over a 4-hour time range, the caregiver may be able to assess a wider range of the patient's orientation and/or preference/lack of preference for a given position. Such information can be helpful to a caregiver, for example, in determining if there are other afflictions and/or conditions affecting the patient. For example, if analysis of the orientation graph over a wide time range reveals that the patient never assumes a 45° degree orientation, the patient may have an injury or other issue on a portion of its body that would be pressured if the patient assumed such orientation. As another example, a high degree of fluctuations in the plot line 430 as displayed in the orientation graph 433 may be indicative of conditions such as seizures, falls, pain/discomfort, or other conditions or events, especially if such fluctuations occur in a high frequency over a small time range. In some embodiments, the one or more hardware processors can determine whether the patient's orientation has changed more than a threshold amount of a given time period, and can issue an alarm, alert, and/or notification if such scenario occurs. For example, the one or more hardware processors can determine whether the patient has not maintained a given orientation (for example, degree of orientation or degree range) for more than a threshold time (for example, 5 seconds) over a 10 minute time period, and issue an alarm, alert, and/or notification if such scenario occurs. Thus, the orientation graph can advantageously provide valuable insight to a caregiver regarding the patient's wellbeing and/or conditions affecting the patient.
The orientation graph 433 and heat map 414, 514, 614, 714, 814 can be generated alone or in combination with each other in structured display 410. Where the structured display includes both, each can be partitioned into a different area of the structured display 410. For example, the orientation graph 433 can be partitioned into a first portion 415 of structured display 410 and the heat map(s) 414, 514, 614, 714, 814 can be partitioned into a second portion 412 of structured display 410. Where both are shown and partitioned in the structured display 410, the first portion 415 can be larger than the second portion 412, which can give the orientation graph more real estate so as to allow for larger time ranges to be displayed (and thus a larger history of the patient's orientation). Advantageously, the orientation graph and the heat map 414, 514, 614, 714, 814 can work in tandem with one another, and as discussed above, can be generated based on the same data received and processed by the hardware processors of the patient monitor 106.
The structured display 410 can include a drop down bar 416 which can provide various functionality. For example, drop down bar 416 can allow a user or caregiver to place the patient monitor 106 and/or the sensor 102 coupled to the patient monitor 106 in a stand-by mode, which will temporarily stop the transmission and/or reception of data from the sensor 102 to the patient monitor 106 and/or stop analysis of data from the sensor 102. Drop down bar 416 can also allow a user or caregiver to replace or switch the sensor 102 with another sensor, by breaking the pairing or communication between the sensor 102 and pairing with another sensor. Such pairing is described further in U.S. Pat. No. 10,383,527, which is incorporated by reference in its entirety.
The orientation graph 433 and/or heat map 414, 514, 614, 714, 814 of structured display 410 can include features that illustrate orientations that are pre-determined (e.g., by a caregiver) as un-allowed. Caregivers may desire to limit or prevent the patient from utilizing a particular orientation for a variety of reasons. Such reasons may include avoiding pressure on an injury point 456 caused by surgery or a wound and/or may include trying to force the patient to utilize un-preferred orientations (see
As shown by
As discussed above, structured display 410 can include a model or image of a bed 422 underneath a patient representation 424. As illustrated in
The structured displays discussed herein can include one or both of the orientation graph 433 and heat map 414, 514, 614, 714, 814.
As discussed above, the structured display 410, 610, 710 can include a patient representation 424 to illustrate the position or orientation of a patient.
Caregivers face increasing demands and pressures in modern healthcare settings. Consequentially, such caregivers can dedicate only a small fraction of their time to each individual patient. Furthermore, as technological advances in the medical field continue to be made, caregivers are tasked with employing an increasing number of physiological monitoring devices, each of which measure enormous amounts of physiological information and transmit such information to patient monitors for display. Such physiological information often continuously fluctuates and it is often impossible, or at least extraordinarily difficult, for a caregiver to monitor, let alone react to, such information. As a result, caregivers are often unable to prevent or satisfactorily treat a number of medical conditions, such as pressure ulcers. As discussed above with respect to pressure ulcer formation, it is incredibly difficult for caregivers to quickly obtain information regarding a patient's orientation at any given time, let alone evaluate such information and determine if the patient's orientation needs to be adjusted. Given that patient orientation is just one of a significant number of patient physiological parameters that caregivers continuously monitor via patient monitors that have limited visual real estate, improvements in displaying orientation-related information via user interfaces are desperately needed so that caregivers can properly care for, and treat, their patients.
The disclosed structured displays and components thereof provide notable improvements to the current state of patient monitoring, especially with respect to monitoring a patient's orientation. The disclosed structured displays and components thereof also provide practical solutions to technical problems associated with displaying a large amount of patient physiological information on graphical user interfaces of patient monitoring devices. More specifically, the disclosed structured displays and components thereof can display a significant amount of orientation-related information while taking up only minimal visual real estate on a display and/or user interface of a patient monitor. Further, the structured displays and components thereof disclosed herein can present such orientation-related information in an efficient and easily “digestible” manner so as to enable caregivers to quickly assess and treat patients at risk of developing, or suffering from, pressure ulcers. For example, the disclosed heat maps 414, 514, 614, 714, 814 and/or orientation graph 433, alone or in combination with the disclosed patient representation 424, can provide a caregiver with a holistic sense of a patient's recent orientation history and/or current orientation in a matter of seconds. At the same time, as discussed and shown herein, such components (and others discussed herein) can be organized and/or configured as part of a structured display which takes up minimal space on a user interface of a display screen. As discussed, such minimal utilization of visual real estate can be critical where the user interface and/or display screen is small (for example, handheld devices or mobile phones) or where the user interface is cluttered with a significant number of displays related to other physiological parameters (for example, see
As used herein, the term “patient” is not intended to be limiting of the present disclosure. In some implementations, the term “patient” may refer to a person in a hospital receiving medical care. In some implementations, the term “patient” may refer to a person who is not in a hospital or other medical care facility. For example, the term “patient” may refer to a person at home.
As shown in
The orientation map 2314A can include one or more zones. For example, the orientation map 2314A can be partitioned into various zones. In the example shown, the orientation map 2314A is partitioned into six zones. The zones may correspond to an orientation of a patient. For example, the zones may be labeled with a name that corresponds to a certain patient orientation. As another example, the position of the zones within the orientation map 2314A and/or with respect to the other zones may correspond to the physical orientation of the patient. As another example, the angle of the zones, as oriented within the semi-annular orientation map 2314A, may correspond to the physical angle of orientation of the patient. In the example shown, the zones of orientation map 2314A can include R2 (Right 2), R1 (Right 1), SR (Supine Right), SL (Supine Left), L1 (Left 1), L2 (Left 2). As an example, the R2 zone may correspond to an orientation in which the patient is laying on their right side. The L2 zone may correspond to an orientation in which the patient is laying on their left side. The other zones may similarly correspond to various orientations of the patient.
The number of zones is not intended to be limiting. Orientation map 2314A, or any of the other orientation maps shown and/or discussed herein, can include any number of zones, such as two zones, three zones, four zones, five zones, six zones, seven zones, eight zones, nine zones, ten zones, or more than ten zones. The orientation map 2314A can be semi-annular. In some implementations, the orientation map 2314A can comprise one or more other shapes, such as shown and/or discussed with reference to
In some implementations, one or more zones of the orientation map 2314A may not be labelled with various names. In some implementations, orientation map 2314A may be displayed within user interface 2300A as bigger or smaller than what is shown in this example. In some implementations, orientation map 2314A may be displayed in a different location within user interface 2300A than what is shown in this example.
The zones of the orientation map 2314A may be colored, shaded, textured (such as cross hatching) or otherwise varied to visually indicate via the user interface 2300A information relating to each of the zones. For example, the zones may be shaded a certain color depending on the amount of time the patient has spent in an orientation corresponding to a given zone within a certain time frame. This may help a care giver quickly determine in which orientations a patient may be safely oriented (such as indicated by a green zone) or which orientations may present potential risk to the patient (such as indicated by a red zone or yellow zone).
In this example, zones R2, R1, SR and L2 may include a first shading or coloring, indicating the patient has spent a relatively small amount of time, such as less than 10 minutes, for example, in any one of those zones within a recent time frame, such as less than 30 minutes, less than 1 hour, less than 1.5 hours, less than 2 hours etc. In this example, zone L1 may include a second shading or coloring, which may indicate that the patient has spent more than a first threshold amount of time and less than a second threshold amount of time in an orientation corresponding to zone L1 within a recent time frame. In this example, the SL zone may include a third shading or coloring which may indicate that the patient has spent more than the second threshold amount of time in an orientation corresponding to zone SL within a recent time frame and that it may be unsafe or pose risks to the patient to orient the patient in that position in the near future, such as before a certain length of time has passed.
The examples shown and/or described are not intended to be limiting of the present disclosure. In some implementations, the user interface 2300A may display the zones as any one of a number of various shades, colors, textures, or the like based on whether a patient has been oriented in an orientation associated with a particular zone for more than a certain threshold amount of time. For example, a first threshold of time may be associated with a first shade or color etc., a second threshold of time may be associated with a second shade or color etc., a third threshold of time may be associated with a third shade or color etc., a fourth threshold of time may be associated with a fourth shade or color etc., and so forth.
The zones of orientation map 2314A may transition between displaying various colors, shading, textures, etc. based on an amount of time that the patient had spent in an orientation corresponding to a zone (within a recent time frame). For example, if the patient spends more time in zone L1 such that the time exceeds a threshold, zone L1 may transition to different color or shading, such as to match the color or shading of zone SL. The zones of orientation map 2314A may transition between displaying various colors, shading, textures, etc. based on an amount of time the patient has not spent in an orientation corresponding to that zone (within a recent time frame). For example, if the patient spends a certain amount of time not oriented in a position corresponding to zone SL, then zone SL may transition to different color or shading, such as to match the color or shading of zone L1, or any of the zones R2, R1, SR, L2. As an example, the systems and devices, such as patient monitor 106 may increment a timer associated with a patient orientation associated with a zone if a patient is oriented in that orientation and may decrement the timer if the patient is not oriented in that orientation. The systems and devices, such as patient monitor 106 may change the display of the zone, such as coloring, shading, etc. associated with the timer based on the time of the timer.
The user interface 2300A may include timer 2326A. Timer 2326A may include similar structural and/or operational features as any of the other example timers discussed herein such as timer 426. Timer 2326A may indicate the amount of time a patient has spent in a current orientation. Timer 2326A may count up or may count down. In this example, the timer 2326A is 1 hour and 13 minutes. In some implementations, this may indicate that the patient is has been oriented in the Left 1 position for 1 hour and 13 minutes. In some implementations, this may indicate that the patient may be safely oriented in the Left 1 position for another 1 hour and 13 minutes before a risk is posed to the patient and the L1 zone transitions to a different shading or coloring to indicate the increased risk associated with that orientation.
The user interface 2300A may include indicator 2342A. Indicator 2342A may include similar structural and/or operational features as any of the other example indicators shown and/or discussed herein. The indicator 2342A may be adjacent to the orientation map 2314A. The indicator 2342A may be adjacent to a zone corresponding to a physical orientation in which the patient is currently oriented. In this example, the indicator 2342A is displayed adjacent to zone L1 which may indicate that the patient is currently oriented in the Left 1 position. In some implementations, the indicator 2342A may change color, shading, contrast, texture, or the like based on the amount of time the patient has spent in an orientation corresponding to the zone adjacent to the indicator 2342A. For example, the color of the indicator 2342A may match the color of the zone to which the indicator 2342A is adjacent.
The user interface 2300A may include a plot line 2330A. The plot line 2330A may include similar structural and/or operational features as any of the other plot lines discussed herein, such as plot line 430. An axis of the plot line 2330A, such as the Y axis or vertical axis, may correspond to zones of the orientation map 2314A and/or may correspond to physical orientations of a patient. The Y axis of plot line 2330A may be labelled with labels corresponding to the zones of orientation map 2314A. For example, the Y axis may include one or more of the following labels: “R2” “R1” “SR” “SL” “L1” “L2”. The positions of the labels along the Y axis of the plot line 2330A may correspond to the positions of the zones within the orientation map 2314A and/or may correspond to the physical orientations of the patient. In some implementations, the user interface 2300A may display horizontal lines along the vertical axis corresponding to the zone labels to demarcate the various zones along plot line 2330A.
As shown in
As shown in
As shown in
As shown in
A user may select component 2511 to select a monitoring mode. The monitoring mode may determine one or more features of any of the example user interfaces or display shown and/or discussed herein. For example, depending on the monitoring mode, a system or computing device may display a heat map or orientation map differently. Monitoring modes can include a standard monitoring mode in which a display may display a heat map such as any of the heat maps 414, 514, 614, 714, and/or 814 shown and/or discussed herein. Monitoring modes can include a 6 zone mode, 5 zone mode, 4 zone mode, 3 zone mode, or the like, during which a display may display user interfaces 2300A-2300D and/or orientation maps 2314A-2314D, respectively. Accordingly, a user may select, via user interface 2500, to change the display of a heat map and/or orientation map. For example, a user may select, via user interface 2500, to change the number of zones displayed in an orientation map. As another example, a user may select, via user interface 2500, whether a heat map and/or orientation map includes any zones at all. As another example, a user may select, via user interface 2500, to change the shape of a heat map and/or orientation map to any of the shapes shown and/or discussed herein, such as semi-circular, annular, ellipsoidal, parallelogram, etc., for example.
A user may select component 2513 to select a zone width of an orientation map. The zone width may be expressed as angular (e.g., degrees, radians), for example, in implementations where an orientation map, is ellipsoidal, circular, annular, or the like. The zone width may be expressed as a length (e.g., centimeters, inches, etc.), for example, in implementations where an orientation map is a parallelogram. The zone width may be expressed as a unitless number or size, such as small, medium, or large, or 1, 2, or 3. In the example shown, a user may select or input 15 degrees (as shown) such that each of the zones within an orientation map spans 15 degrees.
A user may select component 2515 to select a mode of operation. Modes of operation can include a standby monitoring mode and a normal monitoring mode. During a standby monitoring mode, one or more devices or systems such as the patient monitor 106 and/or the sensor 102 may pause or cease one or more operations or functions. During a standby mode, a sensor may continue to operate or collect data and a monitor or other device may discontinue displaying one or more features such as a heat map or orientation map. During a standby mode, a monitor or other device may display a heat map and/or orientation map that does not include data related to the orientation of a patient. For example, a heat map or orientation map may not be shaded or colored etc.
A user may select component 2517 to select to clear a sensor history. Clearing the sensor history may reset one or more alarms associated with a patient orientation. Clearing the sensor history may reset one or more timers associated with a patient orientation. Clearing the sensor history may reset information displayed on a user interface or display.
A user may select component 2601 to select or input a position duration (e.g., 2 hours). The position duration may be a threshold length of time a patient can be in an orientation position before the system or devices generates an alarm or before a corresponding portion of a heat map or orientation map, such as a zone, changes state, such as changing shading, coloring, or the like.
A user may select component 2603 to select or input a position decay rate (e.g., 1 hour 45 minutes). The position decay rate can be a threshold length of time that a patient is not in an orientation position before a corresponding portion of a heat map or orientation map, such as a zone, changes state, such as changing shading, coloring, or the like.
A user may select component 2605 to select or input an upright angle (e.g., 50 degrees). The upright angle may be a preferred angle at which to orient the patient or may be a threshold angle which may trigger the patient monitor 106 to output an alarm if exceeded.
A user may select component 2607 to turn a fall detection alarm on or off. The patient monitor may output an alarm if it detects the patient has fallen when the fall detection alarm is turned on and may not output an alarm if it detects the patient has fallen when the fall detection alarm is turned off.
The user interface 2600 can include a zone map 2613. The zone map 2613 may be associated with a corresponding orientation map and/or heat map. For example, the zone map 2613 may display the same number and types of zones as an associated orientation map. The zone map 2613 may be a same shape as an associated orientation map. The zone map 2613 may include a similar zone configuration or arrangement as an associated orientation map. In some implementations, the zone map 2613 may include similar structural and/or operational features as any of the example orientation maps shown and/or discussed herein. For example, the zone map 2613 can provide information to a caregiver relating to the patient's orientation, position, and/or movement with respect to a surface such as a bed and/or the ground. The zone map 2613 can provide information relating to the patient's past, present, and/or suggested future orientation. For example, the zone map 2613, or portions thereof, may change color, shading, contrast, or the like based on the amount of time a patient has spent in an orientation corresponding to that portion of the zone map 2613.
A user may select, via the zone map 2613, whether to allow or to restrict each of the various zones of the zone map 2613. A user may allow or restrict the various zones by touching any portion of the zone. A user may toggle a zone between allowed or restricted as many times as required or desired. A zone that is restricted may be displayed differently than a zone that is allowed. For example, a zone that is restricted may have a different shading, coloring, texture, etc. than a zone that is allowed. In some implementations, all zones may be displayed as allowed as a default. In some implementations, confirmation may be required to change the status of a zone between allowed and restricted. Restricted zones may also be referred to as un-allowed zones herein.
An allowed zone may be a zone associated with a patient orientation which may be safe for a patient to assume. In some implementations, the systems and devices, such as patient monitor 106, would not immediately trigger an alarm if a patient were oriented in an orientation associated with an allowed zone. In some implementations, the systems and devices, such as patient monitor 106, may trigger an alarm if a patient has been oriented in an orientation associated with an allowed zone in excess of a threshold amount of time. A restricted zone may be a zone associated with a patient orientation that may be unsafe for a patient to assume. In some implementations, the systems and devices, such as patient monitor 106, would automatically and/or immediately trigger an alarm if a patient were oriented in an orientation associated with a restricted zone. In some implementations, the systems and devices, such as patient monitor 106, would trigger an alarm if a patient were oriented in an orientation associated with a restricted zone regardless of a timer associated with said patient orientation or an amount of time a patient has spent orientated in said orientation. A restricted zone may be a zone that is not allowed. In some implementations, a zone may be allowed or restricted regardless of a timer associated with a patient orientation associated with the zone. For example, a zone may be allowed or restricted regardless of an amount of time a patient has spent orientated in an orientation associated with the zone.
In some implementations, the zones of orientation map 2613 may be grouped into sections. For example, the L1 and L2 zone may be grouped as a “Left” section, the S zone may be grouped as a “Supine” section, and the R1 and R2 zones may be grouped as a “Right” section. In some implementations, a section may include one or more zones. In some implementations, a zone may be a part of only one section. A user may allow or restrict various zones of the zone map 2613 by touching any portion of a section of zones. In some implementations, touching a section of zones will allow all zones of the section. In some implementations, touching a section of zones will restrict all zones of the section. In some implementations, touching a section of zones will change the status of all zones of the section. For example, all allowed zones would become restricted, and all restricted zones would become allowed. In some implementations, a section with one or more allowed zones may be displayed differently (e.g., different shading, coloring, texture, etc.) than a section with one or more restricted zones.
The user interface 2600 can include a zone map 2617. The zone map 2617 may be associated with a corresponding orientation map and/or heat map. For example, the zone map 2617 may display the same number and types of zones as an associated orientation map. In some implementations, the zone map 2617 may be a different shape and/or include a different zone configuration than an associated orientation map. For example, the zone map 2617 may correspond to orientation map 2314D shown and/or described herein.
The zone map 2617 can include three zones such as a right zone, a supine zone, and a left zone. In some implementations, the zone map 2617 may include more or less than three zones. The zone map 2617 can include patient representations such as patient representations 2619A, 2619B, 2619C. The patient representations 2619 may correspond to respective zones. For example, patient representation 2619A may correspond to the right zone, patient representation 2619B may correspond to the supine zone, and patient representation 2619C may correspond to the left zone. The patient representations 2619 may be displayed in an orientation corresponding to the zone with which they are associated. For example, patient representation 2619A may be displayed as laying on a right side of the body corresponding to the right zone, patient representation 2619B may be displayed as laying on the back corresponding to a supine zone, and patient representation 2619C may be displayed as laying on a left side of the body corresponding to the left zone.
A user may select, via the zone map 2617, whether to allow or to restrict each of the various zones of the zone map 2617. A user may allow or restrict the various zones by touching any portion of the zone such as a patient representation or an area surrounding a patient representation. A user may toggle a zone as allowed or restricted as many times as required or desired. A zone that is restricted may be displayed differently than a zone that is allowed. For example, a zone that is restricted may have a different shading, coloring, texture, etc. than a zone that is allowed. For example, a patient representation or area surrounding a patient representation of an allowed zone may have a different shading, coloring, texture, etc. than a patient representation or area surrounding a patient representation of a restricted zone.
User interface 2700 can include an orientation map 2714. Orientation map 2714 may correspond to a zone map. For example, orientation map 2714 may correspond to zone map 2613 shown and/or discussed with reference to
Orientation map 2714 may display restricted zones differently than allowed zones. For example, zones L1 and L2 may be restricted and may be displayed differently than the other zones, such as zones R2, R1, and S, which may be allowed. For example, the restricted zones, such as L1 and L2 may have a different coloring, shading, texture, etc. than allowed zones.
The user interface 2700 may include a plot line 2713. The user interface 2700 may display the background of plot line 2713 differently based on whether the portions of the background of plot line 2713 are associated with allowed or restricted zones. For example, the user interface 2700 may display the portion 2703, which may correspond to restricted zones L1 and L2 differently than portion 2701 which may correspond to allowed zones R2, R1, and S.
User interface 2750 can include an orientation map 2754. Orientation map 2754 can include similar structural and/or operation features as orientation map 2714 shown and/or discussed herein. In this example implementation, a patient may have been oriented to an orientation associated with the L1 zone. The L1 zone may be restricted. In response, the user interface 2750 may display one or more alarms 2758. The user interface 2750 may display the alarm(s) 2758 immediately after a patient enters an orientation associated with a restricted zone, such as L1 zone. The alarm may include auditory and/or visual signals.
The indicator 2742 may change color, shading, etc. based on whether the patient is oriented in an orientation associated with a restricted zone or an allowed zone. For example, the indicator 2742 may change a shading, coloring, etc. when the patient moves from an allowed zone, such as the S zone, to a restricted zone, such as the L1 zone.
The restricted zones may change color, shading, etc. based on whether the patient is oriented in an orientation associated with the restricted zones. For example, the L1 zone which may be restricted may change color, shading, etc. when the patient moves to the L1 zone. As shown in this example, the L2 zone and L1 zones, which may both be restricted, may be displayed differently because the patient is oriented in an orientation associated with the L1 zone and not oriented in an orientation associated with the L2 zone.
The user interface 2800 can include a zone map 2813. The zone map 2813 may be associated with a corresponding orientation map and/or heat map. For example, the zone map 2813 may display the same number and types of zones as an associated orientation map. The zone map 2813 may be a same shape as an associated orientation map. The zone map 2813 may include a similar zone configuration or arrangement as an associated orientation map.
A user may select, via the zone map 2813, whether to allow or to restrict each of the various zones of the zone map 2813. A user may allow or restrict the various zones by touching any portion of the zone. A user may toggle a zone between allowed or restricted as many times as required or desired. A zone that is restricted may be displayed differently than a zone that is allowed. For example, a zone that is restricted may have a different shading, coloring, texture, etc. than a zone that is allowed. In this example, the zones R2, R1, and L2 may be restricted. The zones S and L1 may be allowed.
In some implementations, the zones of orientation map 2813 may be grouped into sections. For example, the L1 and L2 zone may be grouped as section 2815C representing the “Left” zones, the S zone may be grouped as section 2815B representing the “Supine” zone, and the R1 and R2 zones may be grouped as section 2815A representing the “Right” zones. In some implementations, a section may include one or more zones. In some implementations, a zone may be a part of only one section.
A user may allow or restrict various zones of the zone map 2813 by touching any portion of a section of zones. For example, a user may toggle whether a zone is allowed or restricted by touching the title of a section of zones, such as “right”, “supine”, or “left”. As another example, a user may toggle whether a zone is allowed or restricted by touching any area within any of sections 2815A-2815C. In some implementations, touching a section of zones will allow all zones of the section. In some implementations, touching a section of zones will restrict all zones of the section. In some implementations, touching a section of zones will change the status of all zones of the section. For example, all allowed zones would become restricted, and all restricted zones would become allowed. In some implementations, a section with one or more allowed zones may be displayed differently (e.g., different shading, coloring, texture, etc.) than a section with one or more restricted zones.
A section background may be displayed differently based on whether the zones of the section are allowed or restricted. For example, a section background may be displayed with a first shading, coloring, and/or texture if most or all zones within that section are restricted and may be displayed with a second shading, coloring, and/or texture if most or all zones within that section are allowed. As another example, a section outline may be displayed with a first shading, coloring, and/or texture if any zone within that section is restricted and may be displayed with a second shading, coloring, and/or texture if all zones within that section are allowed.
As shown in this example, the section background 2815A may be displayed with a first shading, coloring, and/or texture which may be because most or all of the zones within that section are restricted. Section backgrounds 2815B and 2815C may be displayed with a second shading, coloring, and/or texture which may be because at least of the zones within the respective sections is allowed. As further shown in this example, the section outlines 2817A and 2817C may be displayed with a first shading, coloring, and/or texture which may be because at least one zone within respective sections is restricted. Section outline 2817B may be displayed with a second shading, coloring, and/or texture which may be because all zones within that section are allowed.
The user interface 2850 can include a zone map 2853. The zone map 2853 can include one or more zones. One or more of the zones may be allowed. One or more of the zones may be restricted. As shown, the R2 and L2 zones may be restricted. The R1, S, and L1 zones may be allowed. A user may toggle the zones between allowed and restricted, via the user interface 2850, as shown and/or discussed herein.
The zones of zone map 2853 may be locked or unlocked. In some implementations, a locked zone may not be changed between being allowed or restricted. For example, a locked allowed zone may not be changed to be restricted and a locked restricted zone may not be changed to be allowed. An allowed zone may be locked or not locked. A restricted zone may be locked or not locked.
A zone may be locked or not locked based at least in part on an amount of time a patient has spent in an orientation associated with the zone. For example, the system or devices such as patient monitor 106 may lock a zone as restricted if a patient has exceeded a threshold amount of time in an orientation associated with that zone. A zone may be locked or not locked based at least in part on the lock status of other zones within the orientation map. For example, the system or devices such as patient monitor 106 may lock a zone as allowed if all other zones are restricted because at least one zone may be required to be allowed. As another example, the system or devices such as patient monitor 106 may lock a zone as allowed if adjacent zones are allowed. A zone may be locked or not locked based at least in part on a user selection such as via user interface 2850. For example, a user may select various zones or sections of zones to lock or unlock them.
User interface 2853 may display an icon 2855B to indicate that a zone is locked. Icon 2855B may be a symbol of a lock. Icon 2855B may be displayed within a zone that is locked. As shown, icon 2855B is displayed within the S zone indicating that the S zone may be locked. The other zones of zone map 2853 may not be locked and may not display an icon similar to 2853. In some implementations, the user interface 2853 may display a locked zone with a coloring, shading, texture, etc. that is different than an allowed zone, a restricted zone, and/or an unlocked zone.
In some implementations, the zones of orientation map 2653 may be grouped into sections. A section may include one or more zones. In some implementations, a section may include icon 2855A if one its zones is locked. In some implementations, a section may include icon 2855A if most or all of its zones are locked. As shown, the supine section may display icon 2855A because most or all of its zones are locked.
The user interface 2870 can include a zone map 2873. The zone map 2873 can include one or more zones. One or more of the zones may be allowed. For example, the R1 zone may be allowed. One or more of the zones may be restricted. For example, the R2, S, L1, and L2 zones may be restricted. One or more zones may be locked. For example, the R1 and L1 zones may be locked. The R1 zone may be locked as allowed. The L1 zone may be locked as restricted. One or more zones may be not locked. For example, the R2, S, and L2 zones may not be locked.
As an example, the R1 zone may be locked as allowed because it is the only allowed zone and at least one zone must be allowed. As an example, the L1 zone may be locked as restricted because a patient has spent more than a threshold amount of time in an orientation associated with zone L1. As another example, the L1 zone may be locked as restricted because a user has set it as such, such as via the user interface 2870.
The user interface 2870 may display icon 2875A within zone R1 to indicate zone R1 is locked. The user interface May 2870 display icon 2875B within zone L1 to indicate zone L1 is locked. In some implementations, the user interface 2870 may display a locked allowed zone differently than a locked restricted zone. For example, the user interface 2870 may display zone R1, which may be locked allowed, with a different coloring, shading, texture, etc. than zone L1 which may be locked restricted.
As shown in
The orientation indicator 3101A and/or plot line 3105A can indicate an orientation of a patient, such as a position of a patient and/or an angle of a patient. The orientation indicator 3101A and/or plot line 3105A can indicate an angle of the patient, or an angle of a portion of the patient such as an upper portion such as a torso portion, with respect to a plane or surface. The plane or surface can extend along, or can be substantially parallel with, a portion of the bed, such as a portion of the bed that is adjacent to a lower portion of the patient's body such as the legs. The plane or surface can extend along, or can be substantially parallel with, a floor surface, a ground surface, and/or a surface on which the bed rests or is supported. The plane or surface may be a horizontal surface. The plane or surface may be orthogonal to a gravitational force exerted by the Earth such as may be determined by a gyroscope and/or accelerometer. The orientation indicator 3101A and/or plot line 3105A can indicate the angle of the patient, or portion of the patient, about an axis that is parallel to the plane or surface, and that is perpendicular to a longitudinal axis of the patient's body or portion of the patient's body. The axis may be associated with, adjacent to, and/or may intersect a hip region of the patient. The axis may be associated with, adjacent to, and/or may intersect a feet region of the patient. The angle of the patient, such as indicated by the orientation indicator 3101A and/or plot line 3105A, may be referred to as the “head of patient” angle and/or as the “pitch angle”. The angle of the patient, such as indicated by the orientation indicator 3101A and/or plot line 3105A, may correspond to a “pitch” of the patient.
As an example, the orientation indicator 3101A and/or plot line 3105A may indicate 90° for a patient sitting upright, or may indicate 45° for a patient who is reclined or slouching, or may indicate 0° for patient laying down such as in a supine position.
The device on which user interface 3100A is displayed, such as patient monitor 106, may receive patient orientation data from one or more sensors which may be remote to the device. The sensor(s) may be any of the example sensors shown and/or discussed herein such as sensor 102 shown and/or described herein. For example, the patient monitor may receive sensor data from a sensor that is secured to the patient, such as on a chest or torso portion of the patient. As another example, the patient monitor may receive sensor data from a sensor that is secured to a bed or otherwise incorporated into the bed, such as a hospital bed, which may adjust positions such as by inclining or reclining. In some implementations, the patient monitor may receive sensor data from a sensor that is secured to the patient, such as sensor 102, as well as from a sensor that is secured, or incorporated, into a bed. In some implementations, the patient monitor may receive sensor data from only a sensor that is secured to the patient. Orientation indicator 3101A and/or plot line 3105A may display patient orientation, such as “head of patient” angle, based on sensor data received from a sensor that is secured to the patient.
In some implementations, a sensor that is secured to the patient may provide orientation data that more accurately reflects the orientation of the patient than a sensor that is secured or incorporated into a bed. For example, a bed may include a sensor that collects data relating to the orientation of the bed such as whether the bed is inclined or reclined, and at what degrees. In some implementations, the angle of a bed, or portion of the bed, such as determined by one or more sensors secured or incorporated into the bed may be referred to as a “head of bed” angle. However, the orientation of a patient positioned on the bed may not match the orientation of the bed. In other words, the “head of patient angle” may not match the “head of bed” angle. For example, a bed, or portion thereof, may be inclined at 30° with respect to the ground, but the patient may be slouching in the bed such that the patient, or chest or torso portion of the patient, is inclined at less than 30°, such as at 25°, 20°, 15°, etc., with respect to the ground.
A precise knowledge of a patient's orientation may be desirable in certain circumstances. For example, a patient may have difficulty breathing in certain orientations and may need to avoid those orientations, a patient may be intubated and may need to avoid certain orientations to prevent obstruction to an intubation tube, a patient may have a feeding tube and may need to avoid certain orientations to prevent obstruction to the feeding tube, a patient may frequently experience acid reflux and may need to avoid certain orientations that would trigger an acid reflux response, a patient may have joint or skeletal muscular irregularities that may dictate the need to avoid certain orientations, a patient may be under the effects of medication and may need to avoid certain orientations (e.g., sitting up). Accordingly, provided herein are improved systems and methods for determining, displaying, and/or monitoring a patient's orientation with improved accuracy with may facilitate the patient's health.
The user interface 3100A can include a second region 3112A. The second region 3112A can display information relating to an angle of a patient about a longitudinal axis along the length of the patient's body which may be referred to herein as a “roll angle”. The second region 3112A may be positioned adjacent to the first region 3110A. The second region 3112A may be positioned above the first region 3110A. A trend line indicating roll angle of the patient may be positioned adjacent to plot line 3105A, for example, such that the time axes of the trend lines correspond to each other.
The user interface 3100A can include a third region 3113A. The third region 3112A can display information to a physiology of a patient such as physiological parameters, values, trend lines, etc. The third region 3113A may be positioned adjacent to the second region 3112A. The third region 3113A may be positioned above the second region 3112A. physiological trend lines within the third region 3113A may be positioned adjacent to trend lines within the second region 3112A and/or the first region 3110a such that the time axes of the trend lines correspond to each other.
The user interface 3100A can include an upper orientation threshold 3103A and a lower orientation threshold 3107A. The orientation thresholds 3103A, 3107A may be displayed within the first region 3110A. The orientation thresholds 3103A, 3107A may correspond to upper and lower angles within which a patient should be oriented. For example, a patient may need to be oriented at an angle within 15° and 30°. Accordingly, the upper orientation threshold 3103A may correspond to 30° and the lower orientation threshold 3107A may correspond to 15°. The orientation thresholds 3103A, 3107A may visually bound the plot line 3105A or at least bound an area corresponding desire patient pitch angles. The orientation thresholds 3103A, 3107A may be represented numerically. The orientation thresholds 3103A, 3107A may represents past, present, and/or future thresholds. The patient monitor may generate an alarm in response to determining that the patient is oriented at an angle that exceeds either the upper orientation threshold 3103A or the lower orientation threshold 3107A. In some implementations, the patient monitor may generate an alarm in response to determining that the patient has been oriented at one or more angles in excess of either orientation threshold 3103A, 3107A for more than a threshold length of time, which may be a consecutive or non-consecutive length of time.
A user, such as a healthcare provider, may set or adjust the orientation thresholds 3103A, 3107A, such as via the interactive user interface 3100A, such as depending on the health status of the patient. For example, a healthcare provider may set an upper threshold to be 30° to prevent the patient from being oriented at an angle greater than 30° because the patient may have intubation tube which may risk becoming obstructed if the patient were oriented at greater than 30°. As another example, a healthcare provider may set a lower threshold to be 10° to prevent the patient from being oriented at an angle of less than 10° because the patient may have skeletal muscular irregularities, such as hip or lower back immobility, which may cause severe pain if the patient were oriented at less than 10°, such as in a supine position. Adjusting the orientation thresholds 3103A, 3107A can include interaction via the interactive user interface 3100A. For example, a user may adjust the orientation thresholds 3103A, 3107A by touching the orientation thresholds 3103A, 3107A, such as in implementations where the interactive user interface 3100A comprises a touchscreen. Additional examples include the user sliding or dragging the orientation thresholds 3103A, 3107A to various locations via interactive user interface 3100A. In some implementations, a user may adjust the orientation thresholds 3103A, 3107A by numerical entry (e.g., typing in a value) such as via the interactive user interface 3100A. In some implementations, a user may adjust the orientation thresholds 3103A, 3107A by providing a verbal command.
In some implementations, a user may set an orientation threshold to have multiple values which may depend on time. For example, a user may set orientation threshold 3103A to be 45° for a first hour, 0° for a second hour, and 15° for a third hour. Accordingly, the orientation thresholds 3103A, 3107A, may be time-dependent based on at least a user input. Allowing for time-dependent threshold values may allow for more precise patient monitoring.
Various example upper and lower thresholds are provided herein but are not intended to be limiting of the present disclosure. In some implementations, the upper orientation threshold 3103A may be set to be less than about 90°, such as less than about 80°, less than about 60°, less than about 45°, less than about 35°, less than about 25°, less than about 15°, or less than about 10°. In some implementations, the upper orientation threshold 3103A may be set to be greater than 90°. In some implementations, the lower orientation threshold 3107A may be set to be less than about 90°, such as less than about 80°, less than about 60°, less than about 45°, less than about 35°, less than about 25°, less than about 15°, less than about 10°, or less than about 5°. In some implementations, the lower orientation threshold 3107A may be set to be about 0°. In some implementations, the lower orientation threshold 3107A may be set to be less than about 0° such as if the patient's head needs to be inclined to below the patient's hips or feet, for example, to increase blood flow to the patient's head. In some implementations, the lower orientation threshold 3107A must be less than the upper orientation threshold 3103A. In some implementations, the lower orientation threshold 3107A and the upper orientation threshold 3103A must be separated by at least a minimum separation threshold, such as about 1°, about 5°, about 10°, or about 15°, etc. In some implementations, adjusting an upper and/or lower orientation threshold 3103A, 3107A may simultaneously adjust the other threshold. For example, increasing the upper orientation threshold 3103A by 5° may simultaneously increase the lower orientation threshold 3107A by 5° such that the separation between the upper and lower orientation thresholds 3103A, 3107A remains constant. In some implementations, the upper and/or lower orientation threshold 3103A, 3107A may be adjusted independently of each other.
The portion of user interface 3100A between the upper orientation threshold 3103A and lower orientation threshold 3107A may include different shading, coloring, etc. than other portions of the user interface 3100A. In some implementations, the user interface 3100A may include only an upper orientation threshold 3103A or may include only a lower orientation threshold 3107A.
In the example shown in
In the example shown in
As another example, portion 3111 of plot line 3105B indicates that the patient orientation is greater than the upper orientation threshold 3103B for a duration of time. The patient monitor may generate an alarm, such as an auditory and/or visual indicator, to alert a user that that the patient is oriented at an angle greater than the upper orientation threshold 3103B. In some implementations, the patient monitor may generate the alarm immediately in response to determining that patient orientation is greater than upper orientation threshold 3103B, such as the beginning of portion 3111. In some implementations, the patient monitor may not generate the alarm until after a threshold length of time has transpired that the patient is oriented at an angle greater than the upper orientation threshold 3103B, such as toward the latter part of portion 3111. In some implementations, a user may fix the alarm delay length of time such as based on the circumstances or seriousness of the patient's health condition. The alarm may terminate in response to determining that the patient is oriented at an angle within the upper and lower orientation thresholds 3103B, 3107B.
Portions 3109 and/or 3111 may include different shading, coloring, etc. than other portions of the plot line 3105B corresponding to times wherein the patient is oriented at angles within orientation thresholds 3103B, 3107B. In some implementations, the entire plot line 3105B may change appearance (e.g., color and/or shading) whenever the pitch angle exceeds an orientation threshold.
At block 3201, one or more hardware processors associated with a computing device, such as a patient monitor or monitoring hub device, can access inertial data. The inertial data may be generated by an inertial sensor. The inertial sensor may be coupled to a patient. The inertial sensor may be coupled to the body of a patient such as to the skin of a patient. The inertial sensor may be attached to the torso of a patient. The inertial sensor may be worn by a patient such as on a wrist of the patient. The inertial sensor may be coupled to the clothing of a patient. The inertial sensor may be detached from a bed in which the patient is sitting or lying. The inertial sensor may move independently of the bed, such as if the patient moves but the bed does not. Advantageously, the inertial sensor coupled directly to the patient may generate inertial data that more accurately represents the patient's orientation, position, movement, etc. than an inertial sensor indirectly coupled to the patient, such as an inertial sensor on a bed of the patient. The inertial sensor may be any of the example sensors shown and/or described herein. The inertial sensor may comprise an accelerometer and/or gyroscope.
The inertial data may comprise acceleration data. The inertial data may comprise components, such as three components. A component of the inertial data may comprise a vector having a magnitude and a direction. The inertial data components may be represented as X, Y, and Z components. The components of the inertial data may be orthogonal to each other. As an example, inertial data representing an object at rest may have two components with zero magnitude and a third component with 9.8 m/s2 magnitude. These example components indicate that the object is not moving but has the earth's gravitational force acting on it. In some implementations, the inertial sensor may undergo an initial, patient-specific calibration to calibrate the various components of the inertial data to account for various anatomical characteristics of the patient. For example, different anatomical characteristics of different patients such as muscle mass, bone structure, breasts, etc. may affect a sensor's orientation when worn by the various patients, which may affect the data of the inertial components. Accordingly, calibrating a sensor may properly calibrate component data (e.g., with respect to a direction of gravity) which may yield more accurate inertial data.
The hardware processors can receive the inertial data from the inertial sensor as the inertial sensor generates the inertial data (e.g., in real time). The hardware processors may receive the inertial data from the inertial sensor at a time after the inertial sensor generated the data. The hardware processors may retrieve the inertial data from memory. The inertial data can comprise real-time inertial data and/or historical inertial data. The hardware processors can receive the inertial data via wireless communication.
At block 3203, the hardware processors can determine a pitch angle of the patient based on the inertial data. In some implementations, hardware processor(s) associated with and/or implemented on a sensor, such as sensor 102, may perform one or more calculations to determine pitch angle. In some implementations, hardware processor(s) associate with and/or implemented on a patient monitor, such as patient monitor 106, may perform one or more calculations to determine pitch angle.
As used herein, “pitch angle” may refer to an orientation or position of a patient. Pitch angle may refer to an angle between an upper portion of a patient's body, such as the torso, and a lower portion of the patient's body, such as the legs. Pitch angle may refer to an angle between an upper portion of the patient's body and a horizontal plane. Pitch angle may refer to an angle between an upper portion of the patient's body and a plane that is normal to a direction of a gravitational force. Pitch angle may refer to an angle between an upper portion of the patient's body and a plane that is parallel to a direction of a gravitational force. Pitch angle may refer to an angle between an upper portion of the patient's body and a bed surface on which the patient is sitting or lying. Pitch angle may be described in radians or degrees. Pitch angle may also be referred to herein as “head of patient angle.”
The hardware processors can determine pitch angle of the patient based on data generated by inertial sensor(s) such as an accelerometer. The hardware processors can determine pitch angle based on calculating a ratio of magnitudes of one or more acceleration components. In some implementations, the hardware processors may determine pitch angle based on inertial data from a plurality of sensors which may be coupled to a plurality of body portions of a patient. The pitch angle may accurately represent an orientation of the patient, even when the orientation of the patient does not match an orientation of bed in which the patient is resting, at least because the inertial data used to determine pitch angle is generated by a sensor directly coupled to the patient's body portion of interest, such as the chest.
At block 3205, the hardware processors can determine one or more orientation thresholds associated with the pitch angle. The orientation threshold(s) can include an upper threshold and a lower threshold. The orientation thresholds may bound a range of angles within which it is desirable for the pitch angle to remain. The hardware processors can determine the orientation thresholds based on a user input. The hardware processors can receive the user input via a user interface, such as any of the example user interfaces shown and/or described herein. The user input can include any user interaction via a user interface, such as a sliding motion, swiping motion, or drawing motion to indicate desired thresholds, which may be via a touchscreen. The user input can include numerical entry via a user interface to indicate desired thresholds. The user input can include a voice command receive by the hardware processors implementing speech recognition. In some implementations, the hardware processors may protect against user input via password protection or the like. For example, a user may not be able to set or adjust orientation thresholds unless they input a correct password. In some implementations, the hardware processors may perform user verification or authorization to receive user input to set or adjust orientation thresholds. For example, the hardware processors may verify an identify of a user along with the user's authorizations or permissions to set or adjust orientation thresholds. As an example, only an authorized healthcare provider, such as a nurse or doctor charged with caring for a patient, may set or adjust orientation thresholds associated with the patient.
In some implementations, the hardware processors may determine the orientation thresholds automatically. For example, when monitoring a patient for a first time, a user may not yet have inputted any orientation thresholds and the hardware processors may determine orientation thresholds which can be used indefinitely or until a user modifies the orientation thresholds. The orientation thresholds may be preconfigured. The hardware processors may determine the orientation thresholds based on patient demographic, such as age, gender, height, weight, etc. The hardware processors may determine orientation thresholds based on a patient's medical history, such as a history of injuries, a history of medical procedures, a history of medication intake, a sleep history, a dietary history, or the like. As an example, the hardware processors may determine that the orientation thresholds should be set to constrain a patient to a substantially prone position (e.g., to facilitate sleeping) based on determining that the patient has recently undergone surgery and may be experiencing the effects of anesthesia and should not be seated upright to prevent the patient from falling down or out of the bed. The hardware processors may determine orientation thresholds based on time. For example, the hardware processors may adjust the orientation thresholds incrementally (e.g., every 10 minutes, every 30 minutes, every hour, or the like), to ensure that the patient is continually adjusting their position which may prevent stiffness, soreness, pressure sores, muscles aches, joint aches, etc., and which may improve circulation.
At block 3207, the hardware processors can cause a display to render a user interface comprising indicia of the pitch angle. In some implementations, the user interface may also comprise indicia of one or more orientation thresholds. In some implementations, the user interface may not comprise indicia of orientation thresholds. Example user interfaces comprising indicia of pitch angle and/or orientation threshold(s) are shown and/or described with reference to
At block 3209, the hardware processors may optionally update the one or more orientation thresholds. The hardware processors may update the orientation thresholds based on a user input. The hardware processors may update the orientation thresholds automatically such as according to any of the example procedures described at block 3205. Updating the orientation thresholds may comprise updating indicia of the orientation thresholds displayed on a user interface.
At block 3211, the hardware processors can generate an alarm. The alarm can indicate that the patient's pitch angle exceeds an orientation threshold. The alarm can comprise a visual, audio, and/or tactile indicator. In some implementations, the hardware processors may generate the alarm in response to determining, at any time, that the patient's pitch angle exceeds an orientation threshold. In some implementations, the hardware processors may generate the alarm in response to determining that the pitch angle has exceeded an orientation threshold for longer than a threshold amount of time. The threshold amount of time may be compared against a single, uninterrupted consecutive duration of time in which the pitch angle exceeds an orientation threshold. The threshold amount of time may be compared against a plurality of non-consecutive durations of time in which the pitch angle exceeds an orientation threshold. The threshold amounts of time may be reset periodically and/or reset based on the pitch angle changing, such as for greater than a certain amount of time.
In some implementations, the hardware processors may generate more than one type of alarm. For example, the hardware processors may generate a first type of alarm (which may be referred to as an “orientation” alarm) whenever the pitch angle has exceeded an orientation threshold and/or whenever the pitch angle has exceeded an orientation threshold for longer than a threshold amount of time. As another example, the hardware processors may generate a second type of alarm (which may be referred to as a “head angle penalty” alarm) as described in greater detail at block 3213.
At block 3213, the hardware processors may generate an alarm based on determining that the pitch angle has not changed substantially within a certain length of time. The alarm be referred to as a “head angle penalty” alarm. The hardware processors may determine that the pitch angle has remained substantially unchanged if the pitch angle has not deviated by more than a certain amount (e.g., as measured in degrees or radians) or by more than a certain percentage. For example, the amount of deviation may be less than 5 degrees, less than 10 degrees, less than 15 degrees, less than 45 degrees, etc. In one example scenario, the hardware processors may generate an alarm if a patient has been lying on their back for longer than a threshold amount of time such that their pitch angle has remained within certain threshold angles, such as within 5 degrees of itself. Advantageously, generating a “head angle penalty” alarm may indicate that a patient may need to change their orientation (e.g., pitch angle) to prevent pressure sores from forming, such as on the back of a patient's head. Moreover, monitoring “head angle penalty” may additionally be useful for infant care where infants spend prolonged periods lying on their back, which can lead to deformed skulls (e.g., flat heads). The threshold amount of time for determining whether to generate an alarm may be compared against a single, uninterrupted consecutive duration of time in which the pitch angle remains unchanged. The threshold amount of time may be compared against a plurality of non-consecutive durations of time in which the pitch angle remains unchanged. The threshold amounts of time may be reset periodically and/or reset based on the pitch angle changing, such as for greater than a certain amount of time.
At block 3215, the hardware processors may adjust a bed on which the patient is resting. The hardware processors can adjust a position of the bed, an angle of the bed, an inclination of the bed, a firmness of the bed, and so forth. As an example, the hardware processors may cause a portion of a bed supporting the upper portion of the patient's body to incline to raise the patient from a reclined position to a seated position. The hardware processors can adjust the bed based on one or more of the pitch angle, the orientations threshold(s), a duration of time associated with the pitch angle, generating an alarm at block 3211, and/or generating an alarm at block 3213. Adjusting the bed may cause the patient's pitch angle to change. Accordingly, the hardware processors may automatically adjust the patient's pitch angle without requiring human intervention, such as without requiring a healthcare provider to manually adjust the bed. The hardware processors can automatically adjust the bed based on determining an optimal pitch angle for the patient. In some implementations, adjusting the bed position may silence an alarm for example if adjusting the bed position causes the patient's pitch angle to change. In some implementations, automatically adjusting the bed may obviate the need to generate an alarm in the first place. For example, the hardware processors may adjust a bed position prior to, and in anticipation of, an impending alarm which may nullify the generation of the alarm. Accordingly, the process described herein may reduce computer processing requirements such as by reducing and/or eliminating alarms.
In some implementations, the hardware processors may adjust a bed of the patient based on at least other sensor data, which may be in combination with pitch angle and/or motion sensor data. For example, the hardware processors may adjust a bed based on sensor data from one or more of a pulse oximeter, ECG sensor, and/or the like. The hardware processor may adjust the bed based on one or more physiological parameters such as SpO2, respiration related parameters, ECG data, heart rate, pulse rate, perfusion index, pleth variability index, or the like.
In some implementations, the hardware processors may adjust a bed of the patient based on at least camera data, which may be in combination with other data. The hardware processor may analyze image data from a camera capturing images of the environment of the patient. The hardware processors may implement one or more image processing techniques such as pattern recognition. The hardware processor may determine posture or orientation of the patient based on analyzing camera image data. The hardware processor can adjust a position of the bed based on the patient's orientation as determined from the camera image data.
In some implementations, a user may select to disallow certain bed positions to prevent the hardware processors (or a user) from adjusting the bed to the disallowed positions. A user may select to disallow certain bed positions via a user interface. The hardware processor may not position the bed in disallowed positions. In some implementations, the hardware processors may prevent a user from adjusting the bed or from adjusting the bed to certain positions such as by locking the bed.
At block 3217, the hardware processor may detect a fall event of the patient. The hardware processors can determine a fall event of the patient based on the pitch angle, the roll angle, or a combination of the pitch and roll angles. Combining pitch angle data with roll angle data may provide a more complete representation of patient orientation such that the accuracy of fall event detection is improved. A fall event can include a fall from a standing position or a fall from a seated position, or a fall from a lying position, such as a fall from a bed to the ground.
A sensor 3301 may generate sensor data. The sensor 3301 may comprise an inertial sensor, such as an inertial measurement unit. The sensor 3301 may comprise any of the example sensors shown and/or described herein, such as sensor 102. The sensor 3301 may be an accelerometer. The sensor 3301 may output sensor data, which can include acceleration data. The sensor 3301 can output sensor data within a range. The sensor data range may have an upper bound of less than 15 g, less than 12 g, less than 10 g, less than 8 g, less than 6 g, less than 4, or less than 2 g, where 1 g=9.81 m/s2. In some implementations, the sensor data range may have an upper bound of 8 g. The sensor data range may have a lower bound of greater than −15 g, greater than −12 g, greater than −10 g, greater than −8 g, greater than −6 g, greater than −4, or greater than −2 g. Outputting sensor data within a range may reduce processing requirements, reduce manufacturing expenses, and preserve power consumption. For example, it may not be necessary to expend resources seeking to obtain sensor data in excess of a threshold such as greater than 15 g, for example, at least because 15 g may rarely or never occur in certain implementations. Accordingly implementing a sensor capable of outputting sensor data within a range, such as within −8 g and +8 g may reduce manufacturing expenses, processing requirements, and energy consumption without sacrificing accuracy.
The sensor 3301 can generate and/or output data at a rate of less than 200 Hz, less than 100 Hz, less than 50 Hz, less than 40 Hz, less than 30 Hz, less than 25 Hz, less than 20 Hz, less than 10 Hz, etc. In some implementations, the sensor 3301 may output data at a rate of 26 Hz. In some implementations, outputting data at rate disclosed herein, such as at 26 Hz for example, may provide data sufficiently quickly to accurately determine and/or process a patient's pitch angle, given the fidelity requirements of certain implementations. The relationship between pitch angle accuracy and sensor data generation rate may be directly correlated. For example, outputting data at a greater frequency may result in more accurate pitch angle determinations whereas outputting data at a lower frequency may result in less accurate pitch angle determinations. Outputting sensor data at higher frequencies may result in greater energy consumption, reduced battery lifetimes, greater processing requirements, etc. Accordingly, selecting a sensor data frequency rate that is optimal for the accuracy requirements of the system may optimize system performance. In some implementations, preserving battery power, reducing processing requirements, etc. may be more important than accuracy, at least to a threshold. In some implementations, the sensor 3301 may output data at a rate that is as low as possible without sacrificing accuracy of the system processing requirements. In some implementations, outputting data at a rate of 26 Hz, for example, may preserve power and reduce processing requirements while also providing sufficiently accurate results.
The sensor 3301 may output an array of data. The array size may correspond to data frequency generation rate. The sensor data may comprise one or more vectors having a magnitude and one or more direction components. The sensor data can have an X component, a Y component, and a Z component. The components of the sensor data may be orthogonal to each other.
The unit vector engine 3303 can receive data output from the sensor 3301. The unit vector engine 3303 can determine a magnitude of the sensor data. The unit vector engine 3303 can calculate sensor data magnitude according to Equation 1 as follows:
Magnitude=√{square root over (Ax2+Ay2+Az2)} (1).
The unit vector engine 3303 can determine one or more unit vectors for the sensor data. The unit vector engine 3303 can determine a unit vector for each component of the sensor data. The unit vector engine 3303 can determine one or more unit vectors according to equations 2-4 as follows:
The unit vector engine 3303 can output unit vectors.
The axes magnitude engine 3305 can determine a magnitude of one or more components of the sensor data. The axes magnitude engine 3305 can determine the axes magnitude(s) based on at least one or more of the unit vectors from the unit vector engine 3303. The axes magnitude engine 3305 can determine a magnitude of a Y and Z component. The axes magnitude engine can determine axis magnitude(s) according to equation 5 as follows:
YZ_Magnitude=√{square root over (Ay_uv2+Az_uv2)} (5).
The raw pitch angle engine 3307 can receive data output from the unit vector engine 3303. The raw pitch angle engine 3307 can receive a unit vector corresponding to one or more components of the sensor data, such as the unit vector of the X component of the sensor data (e.g., Ax_uv). The raw pitch angle engine 3307 can receive data output from the axes magnitude engine 3305. The raw pitch angle engine 3307 can receive a magnitude corresponding to one or more components of the sensor data. The raw pitch angle engine 3307 can receive a magnitude of the Y and Z component. The raw pitch angle engine 3307 can determine a raw pitch angle from data receive from the unit vector engine 3303 and/or the axes magnitude engine 3305. The raw pitch angle engine can determine a raw pitch angle according to equation 6, as follows:
The raw pitch angle engine 3307 can output a raw pitch angle in radians. The raw pitch angle engine 3307 can output a raw pitch angle in degrees, such as by multiplying the result of equation 4 by 180/π.
The calibration engine 3309 can receive an output from the raw pitch angle engine 3307. The calibration engine 3309 can calculate an average raw pitch angle from one or more raw pitch angle outputs received from the raw pitch angle engine 3307. The calibration engine 3309 can calculate an average raw pitch angle from data received during a length of time, such as less than 5 second, less than 3 seconds, less than 2 seconds, less than 1.5 seconds, less than 1 second, less than 0.5 seconds, or the like. In some implementations, the calibration engine can calculate an average pitch angle from data received from the raw pitch angle engine 3307 over the length of 1 second.
The calibration engine 3309 can determine a calibrated pitch angle from the raw pitch angle received from the raw pitch angle engine 3307 and/or from an average raw pitch angle. The calibration engine 3309 can determine a calibrated pitch angle from a calibration curve. An example calibration curve is shown in
calibrated pitch angle=temporary*50−20 (8).
Calibrating pitch angles may compensate for variations between patient anatomies. For example, different patients may have different sternal angles which may cause a sensor positioned on the patient's chest to be oriented at various degrees. A sternal angle may be referred to as an angle of Louis. Most patients may have a sternal angle that is greater than 0°. For example, when a patient is in a prone position, their sternal angle may be greater than 0° with respect to horizontal such that a sensor positioned on their chest would indicate a pitch angle of greater than 0°. Accordingly, calibrating pitch angles such as to compensate for sternal angles may improve an accuracy of determining patient pitch angles.
In some implementations, a processor may calculate a pitch angle using a pre-defined calibration curve such as a calibration curve similar or identical to the calibration curve 3400 shown in
With continued reference to
A posture detection engine 3313 can receive the calibrated pitch angle from the calibration engine 3309. The posture detection engine 3313 can detect a posture of the patient from the calibrated pitch angle. The posture detection engine 3313 can analyze the calibrated pitch angle alone or in combination with other information, such as orientation thresholds, and/or historical calibrated pitch angles. In some implementations, the posture detection engine 3313 can optionally determine a patient posture based on pitch angle and roll angle received from a roll angle engine 3317. The posture detection engine 3313 can implement one or more operations based on at least the calibrated pitch angle, a determined patient posture, and/or an orientation threshold. Operations can include generating a notification and/or adjusting a bed angle of the patient.
A fall detection engine 3315 can receive the calibrated pitch angle from the calibration engine 3309. The fall detection engine 3315 can detect a fall event or a fall condition status of the patient from at least the calibrated pitch angle. In some implementations, the fall detection engine 3315 can optionally detect a fall event from calibrated pitch angle in combination with other information such as a roll angle of the patient from a roll angle detection engine 3317. Detecting fall events from pitch angle and roll angle may improve an accuracy of fall detection. Detecting fall events from pitch angle and roll angle may increase the types of falls detected such as by providing more data that represents more types of motion of the patient. Fall events can include a patient fall from a standing position, a patient fall from a sitting position such as when sitting in on a chair or bed, and/or a patient fall from a lying position, such as when rolling off of a bed to the ground.
Additional Considerations
Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.
The various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by one or more hardware processors, such as microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Hardware processors can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a hardware processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A hardware processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
The steps of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the hardware processor such that the hardware processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the hardware processor. The storage medium can be volatile or nonvolatile.
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way 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 states 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. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.
Language of degree used herein, such as the terms “approximately,” “about,” “generally,” and “substantially” as used herein represent a value, amount, or characteristic close to the stated value, amount, or characteristic that still performs a desired function or achieves a desired result. For example, the terms “approximately”, “about”, “generally,” and “substantially” may refer to an amount that is within less than 10% of, within less than 5% of, within less than 1% of, within less than 0.1% of, and within less than 0.01% of the stated amount. As another example, in certain embodiments, the terms “generally parallel” and “substantially parallel” refer to a value, amount, or characteristic that departs from exactly parallel by less than or equal to 10 degrees, 5 degrees, 3 degrees, or 1 degree. As another example, in certain embodiments, the terms “generally perpendicular” and “substantially perpendicular” refer to a value, amount, or characteristic that departs from exactly perpendicular by less than or equal to 10 degrees, 5 degrees, 3 degrees, or 1 degree.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the systems, devices or methods illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.
The term “and/or” herein has its broadest, least limiting meaning which is the disclosure includes A alone, B alone, both A and B together, or A or B alternatively, but does not require both A and B or require one of A or one of B. As used herein, the phrase “at least one of” A, B, “and” C should be construed to mean a logical A or B or C, using a non-exclusive logical or.
The apparatuses, systems, and/or methods described herein may be implemented by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions that are stored on a non-transitory tangible computer readable medium. The computer programs may also include stored data. Non-limiting examples of the non-transitory tangible computer readable medium are nonvolatile memory, magnetic storage, and optical storage.
Although the foregoing disclosure has been described in terms of certain preferred embodiments, other embodiments will be apparent to those of ordinary skill in the art from the disclosure herein. Additionally, other combinations, omissions, substitutions and modifications will be apparent to the skilled artisan in view of the disclosure herein. Accordingly, the present invention is not intended to be limited by the description of the preferred embodiments, but is to be defined by reference to claims.
Claims
1. A system for monitoring a patient's orientation angle to improve a health of the patient, the system comprising:
- a physiological sensor device coupled to an upper body portion of a patient, the physiological sensor device comprising: an inertial sensor configured to generate inertial data indicative of an orientation of at least said upper body portion the patient; and
- a monitoring hub configured to wirelessly communicate with said physiological sensor device to access said inertial data therefrom, said monitoring hub comprising: one or more hardware processors configured to: determine, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity; and a display configured to render an interactive graphical user interface, said interactive graphical user interface comprising: a first region comprising: indicia of said pitch angle of the patient; and indicia of one or more orientation thresholds associated with said pitch angle; and said one or more hardware processors further configured to: update said one more orientation thresholds responsive to a user input via the interactive graphical user interface; and generate a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
2. The system of claim 1, wherein the one or more hardware processors is further configured to:
- adjust a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
3. The system of claim 1, wherein the one or more hardware processors is further configured to determine a roll angle of the patient based on at least said inertial data, wherein said interactive graphical user interface further comprises a second region comprising indicia of said roll angle of the patient, the second region positioned adjacent to the first region within the interactive graphical user interface.
4. The system of claim 1, wherein the one or more hardware processors is further configured to:
- determine a roll angle of the patient based on at least said inertial data; and
- detect a fall event of the patient based on at least said roll angle and said pitch angle, said fall event comprising a fall from a standing position or a fall from a seated or lying position.
5. The system of claim 1, wherein the inertial sensor comprises an accelerometer, wherein the inertial data comprises acceleration data having three components, each of the three components comprising an acceleration magnitude and an acceleration direction, wherein the one or more hardware processors is further configured to determine the pitch angle based on at least one or more ratios of one or more of the three components of the acceleration data.
6. The system of claim 1, wherein the one or more hardware processors is further configured to:
- determine a time associated with said pitch angle, said time indicating a time duration for which the patient has been oriented within a threshold of said pitch angle, said time duration comprising a single uninterrupted consecutive time duration or a plurality of non-consecutive time durations; and
- generate a head angle penalty alarm in response to determining that said time exceeds a head angle penalty threshold time.
7. The system of claim 1, wherein the one or more hardware processors is further configured to:
- determine a time associated with said pitch angle, said time indicating a time duration for which the pitch angle has exceeded said one or more orientation thresholds, said time duration comprising a single uninterrupted consecutive time duration or a plurality of non-consecutive time durations; and
- generate said notification responsive to determining that said time exceeds a time threshold.
8. The system of claim 1, wherein said user input comprises a sliding motion via the interactive graphical user interface, said sliding motion associated with adjusting a position of the indicia of the one or more orientation thresholds within said interactive graphical user interface.
9. The system of claim 1, wherein the one or more hardware processors is further configured to:
- update at least one of said one more orientation thresholds to include at least a first time-dependent value, said first time-dependent value comprising an angle corresponding to a duration of time.
10. The system of claim 1, wherein the one or more hardware processors is further configured to:
- automatically update said one more orientation thresholds based on at least an expiration of time.
11. The system of claim 1, wherein the one or more hardware processors is further configured to:
- determine said one or more orientation thresholds based on information associated with said patient, said information comprising one or more of patient demographics or patient medical history.
12. The system of claim 1, wherein said one or more orientation thresholds comprises an upper orientation threshold and a lower orientation threshold.
13. The system of claim 1, wherein said indicia of said pitch angle comprises a trend line indicating a real-time pitch angle of said patient and one or more historical pitch angles of said patient during a length of time.
14. The system of claim 1, wherein said indicia of said pitch angle comprises a trend line, wherein the one or more hardware processors is further configured to:
- cause the display to update the interactive graphical user interface to modify an appearance of said trend line responsive to determining that said pitch angle exceeds said one or more orientation thresholds, said modification comprising updating a color of said trend line or a color of a portion of said trend line.
15. The system of claim 1, wherein the inertial sensor is detached from a bed in which the patient rests.
16. A method for monitoring a patient's orientation angle to improve a health of the patient, the method comprising:
- accessing inertial data originating from an inertial sensor coupled to an upper body portion of a patient, said inertial data indicative of an orientation of at least said upper body portion the patient;
- determining, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity;
- displaying an interactive graphical user interface comprising: indicia of said pitch angle of the patient; and indicia of one or more orientation thresholds associated with said pitch angle;
- updating said one more orientation thresholds responsive to a user input via the interactive graphical user interface; and
- generating a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
17. The method of claim 16, further comprising:
- adjusting a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
18. The method of claim 16, further comprising:
- determining a roll angle of the patient based on at least said inertial data; and
- displaying, via the interactive graphical user interface, indicia of said roll angle of the patient adjacent to the indicia of said pitch angle of the patient within the interactive graphical user interface.
19. Non-transitory computer-readable media including computer-executable instructions that, when executed by a computing system, cause the computing system to perform operations comprising:
- accessing inertial data originating from an inertial sensor coupled to an upper body portion of a patient, said inertial data indicative of an orientation of at least said upper body portion the patient;
- determining, based on said inertial data, a pitch angle of the patient, said pitch angle comprising an angle of the upper body portion of the patient relative to a plane that is substantially normal to a direction of an acceleration component due to gravity;
- displaying an interactive graphical user interface comprising: indicia of said pitch angle of the patient; and indicia of one or more orientation thresholds associated with said pitch angle;
- updating said one more orientation thresholds responsive to a user input via the interactive graphical user interface; and
- generating a notification based on determining that said pitch angle exceeds said one or more orientation thresholds.
20. The non-transitory computer-readable media of claim 19, when executed by the computing system, cause the computing system to perform operations comprising:
- adjusting a position of a bed of the patient based on one or more of said pitch angle, one or more orientation thresholds, or determining that said pitch angle exceeds said one or more orientation thresholds.
| 4960128 | October 2, 1990 | Gordon et al. |
| 4964408 | October 23, 1990 | Hink et al. |
| 5319355 | June 7, 1994 | Russek |
| 5337744 | August 16, 1994 | Branigan |
| 5341805 | August 30, 1994 | Stavridi et al. |
| 5377676 | January 3, 1995 | Vari et al. |
| 5431170 | July 11, 1995 | Mathews |
| 5436499 | July 25, 1995 | Namavar et al. |
| 5456252 | October 10, 1995 | Vari et al. |
| 5479934 | January 2, 1996 | Imran |
| 5482036 | January 9, 1996 | Diab et al. |
| 5494043 | February 27, 1996 | O'Sullivan et al. |
| 5533511 | July 9, 1996 | Kaspari et al. |
| 5590649 | January 7, 1997 | Caro et al. |
| 5602924 | February 11, 1997 | Durand et al. |
| 5638816 | June 17, 1997 | Kiani-Azarbayjany et al. |
| 5638818 | June 17, 1997 | Diab et al. |
| 5645440 | July 8, 1997 | Tobler et al. |
| 5671914 | September 30, 1997 | Kalkhoran et al. |
| 5726440 | March 10, 1998 | Kalkhoran et al. |
| D393830 | April 28, 1998 | Tobler et al. |
| 5743262 | April 28, 1998 | Lepper, Jr. et al. |
| 5747806 | May 5, 1998 | Khalil et al. |
| 5750994 | May 12, 1998 | Schlager |
| 5758644 | June 2, 1998 | Diab et al. |
| 5760910 | June 2, 1998 | Lepper, Jr. et al. |
| 5890929 | April 6, 1999 | Mills et al. |
| 5919134 | July 6, 1999 | Diab |
| 5987343 | November 16, 1999 | Kinast |
| 5997343 | December 7, 1999 | Mills et al. |
| 6002952 | December 14, 1999 | Diab et al. |
| 6010937 | January 4, 2000 | Karam et al. |
| 6027452 | February 22, 2000 | Flaherty et al. |
| 6040578 | March 21, 2000 | Malin et al. |
| 6066204 | May 23, 2000 | Haven |
| 6115673 | September 5, 2000 | Malin et al. |
| 6124597 | September 26, 2000 | Shehada et al. |
| 6128521 | October 3, 2000 | Marro et al. |
| 6129675 | October 10, 2000 | Jay |
| 6144868 | November 7, 2000 | Parker |
| 6152754 | November 28, 2000 | Gerhardt et al. |
| 6184521 | February 6, 2001 | Coffin, IV et al. |
| 6232609 | May 15, 2001 | Snyder et al. |
| 6241683 | June 5, 2001 | Macklem et al. |
| 6253097 | June 26, 2001 | Aronow et al. |
| 6255708 | July 3, 2001 | Sudharsanan et al. |
| 6280381 | August 28, 2001 | Malin et al. |
| 6285896 | September 4, 2001 | Tobler et al. |
| 6308089 | October 23, 2001 | von der Ruhr et al. |
| 6317627 | November 13, 2001 | Ennen et al. |
| 6321100 | November 20, 2001 | Parker |
| 6334065 | December 25, 2001 | Al-Ali et al. |
| 6360114 | March 19, 2002 | Diab et al. |
| 6368283 | April 9, 2002 | Xu et al. |
| 6411373 | June 25, 2002 | Garside et al. |
| 6415167 | July 2, 2002 | Blank et al. |
| 6430437 | August 6, 2002 | Marro |
| 6430525 | August 6, 2002 | Weber et al. |
| 6463311 | October 8, 2002 | Diab |
| 6470199 | October 22, 2002 | Kopotic et al. |
| 6487429 | November 26, 2002 | Hockersmith et al. |
| 6505059 | January 7, 2003 | Kollias et al. |
| 6525386 | February 25, 2003 | Mills et al. |
| 6526300 | February 25, 2003 | Kiani et al. |
| 6534012 | March 18, 2003 | Hazen et al. |
| 6542764 | April 1, 2003 | Al-Ali et al. |
| 6580086 | June 17, 2003 | Schulz et al. |
| 6584336 | June 24, 2003 | Ali et al. |
| 6587196 | July 1, 2003 | Stippick et al. |
| 6587199 | July 1, 2003 | Luu |
| 6597932 | July 22, 2003 | Tian et al. |
| 6606511 | August 12, 2003 | Ali et al. |
| 6635559 | October 21, 2003 | Greenwald et al. |
| 6639668 | October 28, 2003 | Trepagnier |
| 6640116 | October 28, 2003 | Diab |
| 6640117 | October 28, 2003 | Makarewicz et al. |
| 6658276 | December 2, 2003 | Kiani et al. |
| 6661161 | December 9, 2003 | Lanzo et al. |
| 6697656 | February 24, 2004 | Ai-Ali |
| 6697658 | February 24, 2004 | Al-Ali |
| RE38476 | March 30, 2004 | Diab et al. |
| RE38492 | April 6, 2004 | Diab et al. |
| 6738652 | May 18, 2004 | Mattu et al. |
| 6760607 | July 6, 2004 | Al-Ali |
| 6788965 | September 7, 2004 | Ruchti et al. |
| 6816241 | November 9, 2004 | Grubisic |
| 6822564 | November 23, 2004 | Al-Ali |
| 6850787 | February 1, 2005 | Weber et al. |
| 6850788 | February 1, 2005 | Al-Ali |
| 6876931 | April 5, 2005 | Lorenz et al. |
| 6920345 | July 19, 2005 | Al-Ali et al. |
| 6934570 | August 23, 2005 | Kiani et al. |
| 6943348 | September 13, 2005 | Coffin, IV |
| 6956649 | October 18, 2005 | Acosta et al. |
| 6961598 | November 1, 2005 | Diab |
| 6970792 | November 29, 2005 | Diab |
| 6985764 | January 10, 2006 | Mason et al. |
| 6990364 | January 24, 2006 | Ruchti et al. |
| 6998247 | February 14, 2006 | Monfre et al. |
| 7003338 | February 21, 2006 | Weber et al. |
| 7015451 | March 21, 2006 | Dalke et al. |
| 7027849 | April 11, 2006 | Al-Ali |
| D526719 | August 15, 2006 | Richie, Jr. et al. |
| 7096052 | August 22, 2006 | Mason et al. |
| 7096054 | August 22, 2006 | Abdul-Hafiz et al. |
| D529616 | October 3, 2006 | Deros et al. |
| 7133710 | November 7, 2006 | Acosta et al. |
| 7142901 | November 28, 2006 | Kiani et al. |
| 7184963 | February 27, 2007 | Shannon |
| 7225006 | May 29, 2007 | Al-Ali et al. |
| RE39672 | June 5, 2007 | Shehada et al. |
| 7254429 | August 7, 2007 | Schurman et al. |
| 7254431 | August 7, 2007 | Al-Ali et al. |
| 7254434 | August 7, 2007 | Schulz et al. |
| 7274955 | September 25, 2007 | Kiani et al. |
| D554263 | October 30, 2007 | Al-Ali et al. |
| 7280858 | October 9, 2007 | Al-Ali et al. |
| 7289835 | October 30, 2007 | Mansfield et al. |
| 7292883 | November 6, 2007 | De Felice et al. |
| 7341559 | March 11, 2008 | Schulz et al. |
| 7343186 | March 11, 2008 | Lamego et al. |
| D566282 | April 8, 2008 | Al-Ali et al. |
| 7356365 | April 8, 2008 | Schurman |
| 7371981 | May 13, 2008 | Abdul-Hafiz |
| 7373193 | May 13, 2008 | Al-Ali et al. |
| 7377794 | May 27, 2008 | Al-Ali et al. |
| 7395158 | July 1, 2008 | Monfre et al. |
| 7415297 | August 19, 2008 | Al-Ali et al. |
| 7438683 | October 21, 2008 | Al-Ali et al. |
| 7483729 | January 27, 2009 | Al-Ali et al. |
| D587657 | March 3, 2009 | Al-Ali et al. |
| 7500950 | March 10, 2009 | Al-Ali et al. |
| 7509494 | March 24, 2009 | Al-Ali |
| 7510849 | March 31, 2009 | Schurman et al. |
| 7514725 | April 7, 2009 | Wojtczuk et al. |
| 7519406 | April 14, 2009 | Blank et al. |
| D592507 | May 19, 2009 | Wachman et al. |
| 7530942 | May 12, 2009 | Diab |
| 7593230 | September 22, 2009 | Abul-Haj et al. |
| 7596398 | September 29, 2009 | Al-Ali et al. |
| 7606608 | October 20, 2009 | Blank et al. |
| 7620674 | November 17, 2009 | Ruchti et al. |
| D606659 | December 22, 2009 | Kiani et al. |
| 7629039 | December 8, 2009 | Eckerbom et al. |
| 7640140 | December 29, 2009 | Ruchti et al. |
| 7647083 | January 12, 2010 | Al-Ali et al. |
| D609193 | February 2, 2010 | Al-Ali et al. |
| D614305 | April 20, 2010 | Al-Ali et al. |
| 7697966 | April 13, 2010 | Monfre et al. |
| 7698105 | April 13, 2010 | Ruchti et al. |
| RE41317 | May 4, 2010 | Parker |
| RE41333 | May 11, 2010 | Blank et al. |
| 7729733 | June 1, 2010 | Al-Ali et al. |
| 7761127 | July 20, 2010 | Al-Ali et al. |
| 7764982 | July 27, 2010 | Dalke et al. |
| D621516 | August 10, 2010 | Kiani et al. |
| 7791155 | September 7, 2010 | Diab |
| RE41912 | November 2, 2010 | Parker |
| 7880626 | February 1, 2011 | Al-Ali et al. |
| 7909772 | March 22, 2011 | Popov et al. |
| 7919713 | April 5, 2011 | Al-Ali et al. |
| 7937128 | May 3, 2011 | Ai-Ali |
| 7937129 | May 3, 2011 | Mason et al. |
| 7941199 | May 10, 2011 | Kiani |
| 7957780 | June 7, 2011 | Lamego et al. |
| 7962188 | June 14, 2011 | Kiani et al. |
| 7976472 | July 12, 2011 | Kiani |
| 7990382 | August 2, 2011 | Kiani |
| 8008088 | August 30, 2011 | Bellott et al. |
| RE42753 | September 27, 2011 | Kiani-Azarbayjany et al. |
| 8028701 | October 4, 2011 | Al-Ali et al. |
| 8048040 | November 1, 2011 | Kiani |
| 8050728 | November 1, 2011 | Al-Ali et al. |
| RE43169 | February 7, 2012 | Parker |
| 8118620 | February 21, 2012 | Al-Ali et al. |
| 8130105 | March 6, 2012 | Al-Ali et al. |
| 8182443 | May 22, 2012 | Kiani |
| 8190223 | May 29, 2012 | Al-Ali et al. |
| 8203438 | June 19, 2012 | Kiani et al. |
| 8203704 | June 19, 2012 | Merritt et al. |
| 8219172 | July 10, 2012 | Schurman et al. |
| 8224411 | July 17, 2012 | Al-Ali et al. |
| 8229532 | July 24, 2012 | Davis |
| 8233955 | July 31, 2012 | Al-Ali et al. |
| 8255026 | August 28, 2012 | Al-Ali |
| 8265723 | September 11, 2012 | McHale et al. |
| 8274360 | September 25, 2012 | Sampath et al. |
| 8280473 | October 2, 2012 | Al-Ali |
| 8315683 | November 20, 2012 | Al-Ali et al. |
| RE43860 | December 11, 2012 | Parker |
| 8346330 | January 1, 2013 | Lamego |
| 8353842 | January 15, 2013 | Al-Ali et al. |
| 8355766 | January 15, 2013 | MacNeish, III et al. |
| 8374665 | February 12, 2013 | Lamego |
| 8388353 | March 5, 2013 | Kiani et al. |
| 8401602 | March 19, 2013 | Kiani |
| 8414499 | April 9, 2013 | Al-Ali et al. |
| 8418524 | April 16, 2013 | Al-Ali |
| 8428967 | April 23, 2013 | Olsen et al. |
| 8430817 | April 30, 2013 | Al-Ali et al. |
| 8437825 | May 7, 2013 | Dalvi et al. |
| 8455290 | June 4, 2013 | Siskavich |
| 8457707 | June 4, 2013 | Kiani |
| 8471713 | June 25, 2013 | Poeze et al. |
| 8473020 | June 25, 2013 | Kiani et al. |
| 8509867 | August 13, 2013 | Workman et al. |
| 8515509 | August 20, 2013 | Bruinsma et al. |
| 8523781 | September 3, 2013 | Al-Ali |
| D692145 | October 22, 2013 | Al-Ali et al. |
| 8571617 | October 29, 2013 | Reichgott et al. |
| 8571618 | October 29, 2013 | Lamego et al. |
| 8571619 | October 29, 2013 | Al-Ali et al. |
| 8577431 | November 5, 2013 | Lamego et al. |
| 8584345 | November 19, 2013 | Al-Ali et al. |
| 8588880 | November 19, 2013 | Abdul-Hafiz et al. |
| 8630691 | January 14, 2014 | Lamego et al. |
| 8641631 | February 4, 2014 | Sierra et al. |
| 8652060 | February 18, 2014 | Al-Ali |
| 8666468 | March 4, 2014 | Al-Ali |
| 8670811 | March 11, 2014 | O'Reilly |
| RE44823 | April 1, 2014 | Parker |
| RE44875 | April 29, 2014 | Kiani et al. |
| 8688183 | April 1, 2014 | Bruinsma et al. |
| 8690799 | April 8, 2014 | Telfort et al. |
| 8702627 | April 22, 2014 | Telfort et al. |
| 8712494 | April 29, 2014 | MacNeish, III et al. |
| 8715206 | May 6, 2014 | Telfort et al. |
| 8723677 | May 13, 2014 | Kiani |
| 8740792 | June 3, 2014 | Kiani et al. |
| 8755535 | June 17, 2014 | Telfort et al. |
| 8755872 | June 17, 2014 | Marinow |
| 8764671 | July 1, 2014 | Kiani |
| 8768423 | July 1, 2014 | Shakespeare et al. |
| 8771204 | July 8, 2014 | Telfort et al. |
| 8781544 | July 15, 2014 | Al-Ali et al. |
| 8790268 | July 29, 2014 | Al-Ali |
| 8801613 | August 12, 2014 | Al-Ali et al. |
| 8821397 | September 2, 2014 | Al-Ali et al. |
| 8821415 | September 2, 2014 | Al-Ali et al. |
| 8830449 | September 9, 2014 | Lamego et al. |
| 8840549 | September 23, 2014 | Al-Ali et al. |
| 8852094 | October 7, 2014 | Al-Ali et al. |
| 8852994 | October 7, 2014 | Wojtczuk et al. |
| 8897847 | November 25, 2014 | Al-Ali |
| 8911377 | December 16, 2014 | Al-Ali |
| 8989831 | March 24, 2015 | Al-Ali et al. |
| 8998809 | April 7, 2015 | Kiani |
| 9066666 | June 30, 2015 | Kiani |
| 9066680 | June 30, 2015 | Al-Ali et al. |
| 9095316 | August 4, 2015 | Welch et al. |
| 9106038 | August 11, 2015 | Telfort et al. |
| 9107625 | August 18, 2015 | Telfort et al. |
| 9131881 | September 15, 2015 | Diab et al. |
| 9138180 | September 22, 2015 | Coverston et al. |
| 9153112 | October 6, 2015 | Kiani et al. |
| 9192329 | November 24, 2015 | Al-Ali |
| 9192351 | November 24, 2015 | Telfort et al. |
| 9195385 | November 24, 2015 | Al-Ali et al. |
| 9211095 | December 15, 2015 | Al-Ali |
| 9218454 | December 22, 2015 | Kiani et al. |
| 9245668 | January 26, 2016 | Vo et al. |
| 9267572 | February 23, 2016 | Barker et al. |
| 9277880 | March 8, 2016 | Poeze et al. |
| 9307928 | April 12, 2016 | Al-Ali et al. |
| 9323894 | April 26, 2016 | Kiani |
| D755392 | May 3, 2016 | Hwang et al. |
| 9326712 | May 3, 2016 | Kiani |
| 9392945 | July 19, 2016 | Al-Ali et al. |
| 9408542 | August 9, 2016 | Kinast et al. |
| 9436645 | September 6, 2016 | Al-Ali et al. |
| 9445759 | September 20, 2016 | Lamego et al. |
| 9474474 | October 25, 2016 | Lamego et al. |
| 9480435 | November 1, 2016 | Olsen |
| 9510779 | December 6, 2016 | Poeze et al. |
| 9517024 | December 13, 2016 | Kiani et al. |
| 9532722 | January 3, 2017 | Lamego et al. |
| 9560996 | February 7, 2017 | Kiani |
| 9579039 | February 28, 2017 | Jansen et al. |
| 9622692 | April 18, 2017 | Lamego et al. |
| D788312 | May 30, 2017 | Al-Ali et al. |
| 9649054 | May 16, 2017 | Lamego et al. |
| 9697928 | July 4, 2017 | Al-Ali et al. |
| 9717458 | August 1, 2017 | Lamego et al. |
| 9724016 | August 8, 2017 | Al-Ali et al. |
| 9724024 | August 8, 2017 | Al-Ali |
| 9724025 | August 8, 2017 | Kiani et al. |
| 9749232 | August 29, 2017 | Sampath et al. |
| 9750442 | September 5, 2017 | Olsen |
| 9750461 | September 5, 2017 | Telfort |
| 9775545 | October 3, 2017 | Al-Ali et al. |
| 9778079 | October 3, 2017 | Al-Ali et al. |
| 9782077 | October 10, 2017 | Lamego et al. |
| 9787568 | October 10, 2017 | Lamego et al. |
| 9808188 | November 7, 2017 | Perea et al. |
| 9839379 | December 12, 2017 | Al-Ali et al. |
| 9839381 | December 12, 2017 | Weber et al. |
| 9847749 | December 19, 2017 | Kiani et al. |
| 9848800 | December 26, 2017 | Lee et al. |
| 9861298 | January 9, 2018 | Eckerbom et al. |
| 9861305 | January 9, 2018 | Weber et al. |
| 9877650 | January 30, 2018 | Muhsin et al. |
| 9891079 | February 13, 2018 | Dalvi |
| 9924897 | March 27, 2018 | Abdul-Hafiz |
| 9936917 | April 10, 2018 | Poeze et al. |
| 9955937 | May 1, 2018 | Telfort |
| 9965946 | May 8, 2018 | Al-Ali et al. |
| D820865 | June 19, 2018 | Muhsin et al. |
| 9986952 | June 5, 2018 | Dalvi et al. |
| D822215 | July 3, 2018 | Al-Ali et al. |
| D822216 | July 3, 2018 | Barker et al. |
| 10010276 | July 3, 2018 | Al-Ali et al. |
| 10086138 | October 2, 2018 | Novak, Jr. |
| 10111591 | October 30, 2018 | Dyell et al. |
| D833624 | November 13, 2018 | DeJong et al. |
| 10123729 | November 13, 2018 | Dyell et al. |
| D835282 | December 4, 2018 | Barker et al. |
| D835283 | December 4, 2018 | Barker et al. |
| D835284 | December 4, 2018 | Barker et al. |
| D835285 | December 4, 2018 | Barker et al. |
| 10149616 | December 11, 2018 | Al-Ali et al. |
| 10154815 | December 18, 2018 | Al-Ali et al. |
| 10159412 | December 25, 2018 | Lamego et al. |
| 10188348 | January 29, 2019 | Al-Ali et al. |
| RE47218 | February 5, 2019 | Al-Ali |
| RE47244 | February 19, 2019 | Kiani et al. |
| RE47249 | February 19, 2019 | Kiani et al. |
| 10205291 | February 12, 2019 | Scruggs et al. |
| 10226187 | March 12, 2019 | Al-Ali et al. |
| 10231657 | March 19, 2019 | Al-Ali et al. |
| 10231670 | March 19, 2019 | Blank et al. |
| RE47353 | April 16, 2019 | Kiani et al. |
| 10279247 | May 7, 2019 | Kiani |
| 10292664 | May 21, 2019 | Al-Ali |
| 10299720 | May 28, 2019 | Brown et al. |
| 10327337 | June 18, 2019 | Schmidt et al. |
| 10327713 | June 25, 2019 | Barker et al. |
| 10332630 | June 25, 2019 | Al-Ali |
| 10383520 | August 20, 2019 | Wojtczuk et al. |
| 10383527 | August 20, 2019 | Al-Ali |
| 10388120 | August 20, 2019 | Muhsin et al. |
| D864120 | October 22, 2019 | Forrest et al. |
| 10441181 | October 15, 2019 | Telfort et al. |
| 10441196 | October 15, 2019 | Eckerbom et al. |
| 10448844 | October 22, 2019 | Al-Ali et al. |
| 10448871 | October 22, 2019 | Al-Ali et al. |
| 10456038 | October 29, 2019 | Lamego et al. |
| 10463340 | November 5, 2019 | Telfort et al. |
| 10471159 | November 12, 2019 | Lapotko et al. |
| 10505311 | December 10, 2019 | Al-Ali et al. |
| 10524738 | January 7, 2020 | Olsen |
| 10532174 | January 14, 2020 | Al-Ali |
| 10537285 | January 21, 2020 | Shreim et al. |
| 10542903 | January 28, 2020 | Al-Ali et al. |
| 10555678 | February 11, 2020 | Dalvi et al. |
| 10568553 | February 25, 2020 | O'Neil et al. |
| 10608817 | March 31, 2020 | Haider et al. |
| D880477 | April 7, 2020 | Forrest et al. |
| 10617302 | April 14, 2020 | Al-Ali et al. |
| 10617335 | April 14, 2020 | Al-Ali et al. |
| 10637181 | April 28, 2020 | Al-Ali et al. |
| D886849 | June 9, 2020 | Muhsin et al. |
| D887548 | June 16, 2020 | Abdul-Hafiz et al. |
| D887549 | June 16, 2020 | Abdul-Hafiz et al. |
| 10667764 | June 2, 2020 | Ahmed et al. |
| 10682076 | June 16, 2020 | Larson |
| D890708 | July 21, 2020 | Forrest et al. |
| 10721785 | July 21, 2020 | Al-Ali |
| 10729357 | August 4, 2020 | Larson |
| 10736518 | August 11, 2020 | Al-Ali et al. |
| 10750984 | August 25, 2020 | Pauley et al. |
| D897098 | September 29, 2020 | Ai-Ali |
| 10779098 | September 15, 2020 | Iswanto et al. |
| 10827961 | November 10, 2020 | Iyengar et al. |
| 10828007 | November 10, 2020 | Telfort et al. |
| 10832818 | November 10, 2020 | Muhsin et al. |
| 10849554 | December 1, 2020 | Shreim et al. |
| 10856750 | December 8, 2020 | Indorf et al. |
| 10874330 | December 29, 2020 | Larson |
| D906970 | January 5, 2021 | Forrest et al. |
| D908213 | January 19, 2021 | Abdul-Hafiz et al. |
| 10918281 | February 16, 2021 | Al-Ali et al. |
| 10932705 | March 2, 2021 | Muhsin et al. |
| 10932729 | March 2, 2021 | Kiani et al. |
| 10939878 | March 9, 2021 | Kiani et al. |
| 10956950 | March 23, 2021 | Al-Ali et al. |
| D916135 | April 13, 2021 | Indorf et al. |
| D917046 | April 20, 2021 | Abdul-Hafiz et al. |
| D917550 | April 27, 2021 | Indorf et al. |
| D917564 | April 27, 2021 | Indorf et al. |
| D917704 | April 27, 2021 | Al-Ali et al. |
| 10987066 | April 27, 2021 | Chandran et al. |
| 10991135 | April 27, 2021 | Al-Ali et al. |
| D919094 | May 11, 2021 | Al-Ali et al. |
| D919100 | May 11, 2021 | Al-Ali et al. |
| 11006867 | May 18, 2021 | Al-Ali |
| D921202 | June 1, 2021 | Al-Ali et al. |
| 11024064 | June 1, 2021 | Muhsin et al. |
| 11026604 | June 8, 2021 | Chen et al. |
| D925597 | July 20, 2021 | Chandran et al. |
| D927699 | August 10, 2021 | Al-Ali et al. |
| 11076777 | August 3, 2021 | Lee et al. |
| 11114188 | September 7, 2021 | Poeze et al. |
| D933232 | October 12, 2021 | Al-Ali et al. |
| D933233 | October 12, 2021 | Al-Ali et al. |
| D933234 | October 12, 2021 | Al-Ali et al. |
| 11145408 | October 12, 2021 | Sampath et al. |
| 11147518 | October 19, 2021 | Al-Ali et al. |
| 11185262 | November 30, 2021 | Al-Ali et al. |
| 11191484 | December 7, 2021 | Kiani et al. |
| D946596 | March 22, 2022 | Ahmed |
| D946597 | March 22, 2022 | Ahmed |
| D946598 | March 22, 2022 | Ahmed |
| D946617 | March 22, 2022 | Ahmed |
| 11272839 | March 15, 2022 | Al-Ali et al. |
| 11289199 | March 29, 2022 | Al-Ali |
| RE49034 | April 19, 2022 | Al-Ali |
| 11298021 | April 12, 2022 | Muhsin et al. |
| D950580 | May 3, 2022 | Ahmed |
| D950599 | May 3, 2022 | Ahmed |
| D950738 | May 3, 2022 | Al-Ali et al. |
| D957648 | July 12, 2022 | Al-Ali |
| 11382567 | July 12, 2022 | O'Brien et al. |
| 11389093 | July 19, 2022 | Triman et al. |
| 11406286 | August 9, 2022 | Al-Ali |
| 11417426 | August 16, 2022 | Muhsin et al. |
| 11439329 | September 13, 2022 | Lamego |
| 11445948 | September 20, 2022 | Scruggs et al. |
| D965789 | October 4, 2022 | Al-Ali et al. |
| D967433 | October 18, 2022 | Al-Ali et al. |
| 11464410 | October 11, 2022 | Muhsin |
| 11504058 | November 22, 2022 | Sharma et al. |
| 11504066 | November 22, 2022 | Dalvi et al. |
| D971933 | December 6, 2022 | Ahmed |
| D973072 | December 20, 2022 | Ahmed |
| D973685 | December 27, 2022 | Ahmed |
| D973686 | December 27, 2022 | Ahmed |
| D974193 | January 3, 2023 | Forrest et al. |
| D979516 | February 28, 2023 | Al-Ali et al. |
| D980091 | March 7, 2023 | Forrest et al. |
| 11596363 | March 7, 2023 | Lamego |
| 11627919 | April 18, 2023 | Kiani et al. |
| 11637437 | April 25, 2023 | Al-Ali et al. |
| D985498 | May 9, 2023 | Al-Ali et al. |
| 11653862 | May 23, 2023 | Dalvi et al. |
| D989112 | June 13, 2023 | Muhsin et al. |
| D989327 | June 13, 2023 | Al-Ali et al. |
| 11678829 | June 20, 2023 | Al-Ali et al. |
| 11679579 | June 20, 2023 | Al-Ali |
| 11684296 | June 27, 2023 | Vo et al. |
| 11692934 | July 4, 2023 | Normand et al. |
| 11701043 | July 18, 2023 | Al-Ali et al. |
| D997365 | August 29, 2023 | Hwang |
| 11721105 | August 8, 2023 | Ranasinghe et al. |
| 11730379 | August 22, 2023 | Ahmed et al. |
| D998625 | September 12, 2023 | Indorf et al. |
| D998630 | September 12, 2023 | Indorf et al. |
| D998631 | September 12, 2023 | Indorf et al. |
| D999244 | September 19, 2023 | Indorf et al. |
| D999245 | September 19, 2023 | Indorf et al. |
| D999246 | September 19, 2023 | Indorf et al. |
| 11766198 | September 26, 2023 | Pauley et al. |
| D1000975 | October 10, 2023 | Al-Ali et al. |
| 11803623 | October 31, 2023 | Kiani et al. |
| 11832940 | December 5, 2023 | Diab et al. |
| D1013179 | January 30, 2024 | Al-Ali et al. |
| 11872156 | January 16, 2024 | Telfort et al. |
| 11879960 | January 23, 2024 | Ranasinghe et al. |
| 11883129 | January 30, 2024 | Olsen |
| D1022729 | April 16, 2024 | Forrest et al. |
| 11951186 | April 9, 2024 | Krishnamani et al. |
| 11974833 | May 7, 2024 | Forrest et al. |
| 11986067 | May 21, 2024 | Al-Ali et al. |
| 11986289 | May 21, 2024 | Dalvi et al. |
| 11986305 | May 21, 2024 | Al-Ali et al. |
| 11992308 | May 28, 2024 | Al-Ali |
| 20010034477 | October 25, 2001 | Mansfield et al. |
| 20010039483 | November 8, 2001 | Brand et al. |
| 20020010401 | January 24, 2002 | Bushmakin et al. |
| 20020058864 | May 16, 2002 | Mansfield et al. |
| 20020133080 | September 19, 2002 | Apruzzese et al. |
| 20030013975 | January 16, 2003 | Kiani |
| 20030018243 | January 23, 2003 | Gerhardt et al. |
| 20030144582 | July 31, 2003 | Cohen et al. |
| 20030156288 | August 21, 2003 | Barnum et al. |
| 20030212312 | November 13, 2003 | Coffin, IV et al. |
| 20040106163 | June 3, 2004 | Workman, Jr. et al. |
| 20050055276 | March 10, 2005 | Kiani et al. |
| 20050234317 | October 20, 2005 | Kiani |
| 20060073719 | April 6, 2006 | Kiani |
| 20060189871 | August 24, 2006 | Al-Ali et al. |
| 20070073116 | March 29, 2007 | Kiani et al. |
| 20070180140 | August 2, 2007 | Welch et al. |
| 20070244377 | October 18, 2007 | Cozad et al. |
| 20080064965 | March 13, 2008 | Jay et al. |
| 20080094228 | April 24, 2008 | Welch et al. |
| 20080103375 | May 1, 2008 | Kiani |
| 20080221418 | September 11, 2008 | Al-Ali et al. |
| 20090036759 | February 5, 2009 | Ault et al. |
| 20090093687 | April 9, 2009 | Telfort et al. |
| 20090095926 | April 16, 2009 | MacNeish, III |
| 20090247984 | October 1, 2009 | Lamego et al. |
| 20090275844 | November 5, 2009 | Al-Ali |
| 20100004518 | January 7, 2010 | Vo et al. |
| 20100030040 | February 4, 2010 | Poeze et al. |
| 20100099964 | April 22, 2010 | O'Reilly et al. |
| 20100234718 | September 16, 2010 | Sampath et al. |
| 20100270257 | October 28, 2010 | Wachman et al. |
| 20100298742 | November 25, 2010 | Perlman |
| 20110028806 | February 3, 2011 | Merritt et al. |
| 20110028809 | February 3, 2011 | Goodman |
| 20110040197 | February 17, 2011 | Welch et al. |
| 20110082711 | April 7, 2011 | Poeze et al. |
| 20110087081 | April 14, 2011 | Kiani et al. |
| 20110118561 | May 19, 2011 | Tari et al. |
| 20110137297 | June 9, 2011 | Kiani et al. |
| 20110172498 | July 14, 2011 | Olsen et al. |
| 20110234395 | September 29, 2011 | Johnson |
| 20120123231 | May 17, 2012 | O'Reilly |
| 20120165629 | June 28, 2012 | Merritt et al. |
| 20120209084 | August 16, 2012 | Olsen et al. |
| 20120226117 | September 6, 2012 | Lamego et al. |
| 20120283524 | November 8, 2012 | Kiani et al. |
| 20130023775 | January 24, 2013 | Lamego et al. |
| 20130060147 | March 7, 2013 | Welch et al. |
| 20130096405 | April 18, 2013 | Garfio |
| 20130296672 | November 7, 2013 | O'Neil et al. |
| 20130345921 | December 26, 2013 | Al-Ali et al. |
| 20140166076 | June 19, 2014 | Kiani et al. |
| 20140180160 | June 26, 2014 | Brown et al. |
| 20140187973 | July 3, 2014 | Brown et al. |
| 20140275871 | September 18, 2014 | Lamego et al. |
| 20140275872 | September 18, 2014 | Merritt et al. |
| 20140316217 | October 23, 2014 | Purdon et al. |
| 20140316218 | October 23, 2014 | Purdon et al. |
| 20140323897 | October 30, 2014 | Brown et al. |
| 20140323898 | October 30, 2014 | Purdon et al. |
| 20150005600 | January 1, 2015 | Blank et al. |
| 20150011907 | January 8, 2015 | Purdon et al. |
| 20150073241 | March 12, 2015 | Lamego |
| 20150080754 | March 19, 2015 | Purdon et al. |
| 20150099950 | April 9, 2015 | Al-Ali et al. |
| 20170024748 | January 26, 2017 | Haider |
| 20170055896 | March 2, 2017 | Al-Ali |
| 20170251974 | September 7, 2017 | Shreim et al. |
| 20180125412 | May 10, 2018 | Ferber |
| 20180242926 | August 30, 2018 | Muhsin et al. |
| 20180247712 | August 30, 2018 | Muhsin et al. |
| 20190320906 | October 24, 2019 | Olsen |
| 20200060869 | February 27, 2020 | Telfort et al. |
| 20200111552 | April 9, 2020 | Ahmed |
| 20200113520 | April 16, 2020 | Abdul-Hafiz et al. |
| 20200138368 | May 7, 2020 | Kiani et al. |
| 20200163597 | May 28, 2020 | Dalvi et al. |
| 20200253474 | August 13, 2020 | Muhsin et al. |
| 20200253544 | August 13, 2020 | Belur Nagaraj et al. |
| 20200275841 | September 3, 2020 | Telfort et al. |
| 20200288983 | September 17, 2020 | Telfort et al. |
| 20200329983 | October 22, 2020 | Al-Ali et al. |
| 20200329993 | October 22, 2020 | Al-Ali et al. |
| 20210022628 | January 28, 2021 | Telfort et al. |
| 20210104173 | April 8, 2021 | Pauley et al. |
| 20210117525 | April 22, 2021 | Kiani et al. |
| 20210121582 | April 29, 2021 | Krishnamani et al. |
| 20210161465 | June 3, 2021 | Barker et al. |
| 20210236729 | August 5, 2021 | Kiani et al. |
| 20210256835 | August 19, 2021 | Ranasinghe et al. |
| 20210275101 | September 9, 2021 | Vo et al. |
| 20210290072 | September 23, 2021 | Forrest |
| 20210290080 | September 23, 2021 | Ahmed |
| 20210290120 | September 23, 2021 | Al-Ali |
| 20210290177 | September 23, 2021 | Novak, Jr. |
| 20210290184 | September 23, 2021 | Ahmed |
| 20210296008 | September 23, 2021 | Novak, Jr. |
| 20210330228 | October 28, 2021 | Olsen et al. |
| 20210386382 | December 16, 2021 | Olsen et al. |
| 20210402110 | December 30, 2021 | Pauley et al. |
| 20220039707 | February 10, 2022 | Sharma et al. |
| 20220053892 | February 24, 2022 | Al-Ali et al. |
| 20220071562 | March 10, 2022 | Kiani |
| 20220096603 | March 31, 2022 | Kiani et al. |
| 20220151521 | May 19, 2022 | Krishnamani et al. |
| 20220218244 | July 14, 2022 | Kiani et al. |
| 20220287574 | September 15, 2022 | Telfort et al. |
| 20220296161 | September 22, 2022 | Al-Ali et al. |
| 20220361819 | November 17, 2022 | Al-Ali et al. |
| 20220379059 | December 1, 2022 | Yu et al. |
| 20220392610 | December 8, 2022 | Kiani et al. |
| 20230028745 | January 26, 2023 | Al-Ali |
| 20230038389 | February 9, 2023 | Vo |
| 20230045000 | February 9, 2023 | Al-Ali |
| 20230045647 | February 9, 2023 | Vo |
| 20230058052 | February 23, 2023 | Al-Ali |
| 20230058342 | February 23, 2023 | Kiani |
| 20230069789 | March 2, 2023 | Koo et al. |
| 20230087671 | March 23, 2023 | Telfort et al. |
| 20230110152 | April 13, 2023 | Forrest et al. |
| 20230111198 | April 13, 2023 | Yu et al. |
| 20230115397 | April 13, 2023 | Vo et al. |
| 20230116371 | April 13, 2023 | Mills et al. |
| 20230135297 | May 4, 2023 | Kiani et al. |
| 20230138098 | May 4, 2023 | Telfort et al. |
| 20230145155 | May 11, 2023 | Krishnamani et al. |
| 20230147750 | May 11, 2023 | Barker et al. |
| 20230210417 | July 6, 2023 | Al-Ali et al. |
| 20230222805 | July 13, 2023 | Muhsin et al. |
| 20230222887 | July 13, 2023 | Muhsin et al. |
| 20230226331 | July 20, 2023 | Kiani et al. |
| 20230284916 | September 14, 2023 | Telfort |
| 20230284943 | September 14, 2023 | Scruggs et al. |
| 20230301562 | September 28, 2023 | Scruggs et al. |
| 20230346993 | November 2, 2023 | Kiani et al. |
| 20230368221 | November 16, 2023 | Haider |
| 20230371893 | November 23, 2023 | Al-Ali et al. |
| 20230389837 | December 7, 2023 | Krishnamani et al. |
| 20240016418 | January 18, 2024 | Devadoss et al. |
| 20240016419 | January 18, 2024 | Devadoss et al. |
| 20240047061 | February 8, 2024 | Al-Ali et al. |
| 20240049310 | February 8, 2024 | Al-Ali et al. |
| 20240049986 | February 15, 2024 | Al-Ali et al. |
| 20240081656 | March 14, 2024 | DeJong et al. |
| 20240122486 | April 18, 2024 | Kiani |
| 20240180456 | June 6, 2024 | Al-Ali |
- US 2024/0016391 A1, 01/2024, Lapotko et al. (withdrawn)
Type: Grant
Filed: Oct 13, 2023
Date of Patent: May 5, 2026
Assignee: Masimo Corporation (Irvine, CA)
Inventors: Ammar Al-Ali (San Juan Capistrano, CA), Dishant Parshottambhai Donga (Anaheim, CA), Sung Uk Lee (Irvine, CA), Mohammad Usman (Mission Viejo, CA), Faisal Kashif (Irvine, CA)
Primary Examiner: Walter L Lindsay, Jr.
Assistant Examiner: Warren K Fenwick
Application Number: 18/486,701
International Classification: A61B 5/11 (20060101); A61B 5/00 (20060101); A61G 7/018 (20060101); G01P 15/02 (20130101); G01P 15/18 (20130101); G06F 3/01 (20060101); G06F 3/04847 (20220101); G06T 11/00 (20060101);
