阅读说明：本技术 用于患者翻身检测和确认的系统 (System for patient turn-over detection and confirmation ) 是由 马克·泽尔哈森 布莱恩·韦德曼 于 2019-07-31 设计创作，主要内容包括：一种用于检测患者翻身的系统,包括：具有人支撑面和支撑构架的人支撑装置,用于生成测压元件数据的多个测压元件,用于感测个体的心率数据和呼吸率数据中的至少一个的传感器,以及与所述多个测压元件和所述传感器联接的计算设备。计算设备接收测压元件数据以及个体的心率数据和呼吸率数据中的至少一个,基于测压元件数据和个体的心率数据和呼吸率数据中的至少一个检测在人支撑表面上已经发生了患者翻身,并且使得发生了患者翻身的指示记入与个体相对应的电子病历中。(A system for detecting a turn in a patient, comprising: a person support apparatus having a person support surface and a support frame, a plurality of load cells for generating load cell data, a sensor for sensing at least one of heart rate data and respiration rate data of an individual, and a computing device coupled with the plurality of load cells and the sensor. The computing device receives the load cell data and at least one of the heart rate data and the respiration rate data of the individual, detects that a patient turn has occurred on the human support surface based on the load cell data and the at least one of the heart rate data and the respiration rate data of the individual, and causes an indication that a patient turn has occurred to be logged in an electronic medical record corresponding to the individual.)

1. A system, comprising:

a person support device having a person support surface and a support frame;

a plurality of load cells for generating load cell data, at least one of the plurality of load cells being positioned at or near each corner of the support frame;

a sensor for sensing at least one of heart rate data and respiration rate data of an individual, the sensor being disposed between the person support surface and the support frame; and

a computing device coupled with the plurality of load cells and the sensor for receiving the load cell data and at least one of heart rate data and respiration rate data of the individual, the computing device comprising a processor and a memory storing computer-readable and executable instructions that, when executed by the processor, cause the computing device to detect that a patient turn has occurred on the human support surface based on the load cell data and the at least one of heart rate data and respiration rate data of the individual, and cause an indication that the patient turn has occurred to be logged in an electronic medical record corresponding to the individual.

2. The system of claim 1, wherein the executable instructions, when executed by the processor, further cause the computing device to request input from a caregiver to confirm the occurrence of a patient turn.

3. The system of claim 1 or 2, wherein the computing device detects that the patient turn has occurred in response to identifying a waveform in load cell data indicative of a possible patient turn over within a predetermined period of time and at least one of an increase in heart rate and a decrease in breathing rate.

4. The system of claim 1 or 2, further comprising:

a tag corresponding to the caregiver for transmitting caregiver identification data;

a Real Time Location System (RTLS) receiver for receiving the caregiver identification data from the tag and sending the caregiver identification data; and

a real-time location system (RTLS) server for receiving the caregiver identification data from the RTLS receiver and associating the caregiver identification data with a location of the RTLS receiver to indicate the caregiver's location;

wherein the executable instructions, when executed by the processor, further cause the computing device to confirm that the patient turn occurred based on the location of the caregiver.

5. The system of claim 4, wherein the computing device confirms that the patient turn occurred in response to determining that the position of the caregiver during the patient turn is within a preset distance of the human support apparatus.

6. The system of claim 1 or 2, wherein:

the sensor senses heart rate data and respiration rate data of the individual;

the computing device receiving heart rate data and respiration rate data for the individual; and is

The computing device detects that the patient turn has occurred on the human support surface based on the load cell data, the individual's heart rate data, and respiration rate data.

7. The system of claim 1 or 2, wherein the executable instructions, when executed by the processor, further cause the computing device to display an alert or notification on a display of the computing device indicating that a predetermined period of time has elapsed since an occurrence of a patient turn.

8. The system of claim 7, wherein the computing device displays the alert or notification in response to a predetermined period of time having elapsed since a last patient turn was logged in an electronic medical record corresponding to the individual.

Technical Field

The present invention relates generally to systems for monitoring patient turn, and more particularly to systems for automatically determining that a patient has turned and for providing patient turn confirmation.

Background

To prevent pressure sores, traditional care practices dictate that individuals be repositioned approximately every two hours. The alternating position of the individual causes blood to flow throughout the skin and reduces stress on areas of the skin that otherwise begin to break over time. For some individuals, such as those who are unable to move by themselves, the caregiver may be responsible for repositioning the individual and posting the repositioning or turning to the individual's chart.

Given that treatment of pressure sores is often an irrevocable cost of patient care under various insurance guidelines, management and documentation of roll-over is important to reduce the occurrence of pressure sores in care facilities.

Therefore, a system for detecting and confirming patient turnover is needed.

Disclosure of Invention

According to some embodiments of the invention, a system for detecting a turn in a patient comprises: a person support apparatus having a person support face and a support frame, a plurality of load cells for generating load cell data, a sensor for sensing at least one of heart rate data and respiration rate data of an individual, and a computing device coupled to the plurality of load cells and the mechanical sensor. At least one of the plurality of load cells is positioned at or near each corner of the support frame. The sensor is disposed between the person support surface and the support frame. The computing device receives load cell data and at least one of heart rate data and respiration rate data of an individual. In particular, the computing device includes a processor and a memory storing computer-readable and executable instructions that, when executed by the processor, cause the computing device to detect that a patient turn has occurred on a human support surface based on a load cell and at least one of heart rate data and respiration rate data of an individual, and cause an indication that the patient turn has occurred to be logged in an electronic medical record corresponding to the individual.

According to some embodiments of the invention, a method for detecting a turn in a patient comprises: receiving load cell data from a plurality of load cells located on a person support device; receiving heart rate data and respiration rate data of an individual from a sensor coupled to a human support device; determining that a waveform of the load cell data over a period of time indicates a possible patient turn; identifying at least one of a decrease in the respiration rate of the individual over a period of time and an increase in the heart rate of the individual over a period of time; determining that a patient turn has occurred based on determining that a waveform of the load cell data over a period of time is indicative of a possible patient turn and identifying at least one of a decrease in respiration rate and an increase in heart rate of the individual over a period of time; and causing an indication that the patient has turned over to be logged into an electronic medical record corresponding to the individual.

Additional features and advantages will be set forth in the detailed description which follows, and in part will be readily apparent to those skilled in the art from that description or recognized by practicing the embodiments described herein, including the detailed description which follows, the claims, as well as the appended drawings.

It is to be understood that both the foregoing general description and the following detailed description describe various embodiments, and are intended to provide an overview or framework for understanding the nature and character of the claimed subject matter. The accompanying drawings are included to provide a further understanding of the various embodiments, and are incorporated in and constitute a part of this specification. The drawings illustrate various embodiments described herein, and together with the description serve to explain the principles and operation of the claimed subject matter.

Drawings

Referring now to the illustrative examples in the drawings, wherein like reference numbers represent the same or similar elements throughout:

fig. 1 is a perspective view of a person support apparatus according to one or more embodiments shown and described herein;

FIG. 2 is a block diagram illustrating the location of a plurality of load cells relative to the person support apparatus of FIG. 1;

FIG. 3 is a block diagram illustrating an exemplary control unit of a mechanical sensor for sensing respiratory and heartbeat-related motion in an individual in accordance with one or more embodiments shown and described herein;

FIG. 4 is a graph plotting breathing rate, heart rate, caregiver position, and load cell data over time to indicate the occurrence of a patient turn in accordance with one or more embodiments shown and described herein;

FIG. 5 is a block diagram showing an individual and caregiver located in a room and having tags in communication with a Real Time Location System (RTLS) in accordance with one or more embodiments shown and described herein;

FIG. 6 is an example screen shot of an Electronic Medical Record (EMR) of an individual displayed on a computing device according to one or more embodiments shown and described herein; and

fig. 7 is a block diagram of an exemplary method for detecting and logging a patient turn in accordance with one or more embodiments shown and described herein.

Detailed Description

FIG. 1 generally depicts one embodiment of a human support device for detecting a turn in a patient. The person support apparatus includes a plurality of load cells and at least one mechanical sensor. The load cells provide load cell data that can be analyzed by a computing device to determine that a possible patient turn has occurred based on movement of the individual on the human support device. The mechanical sensor senses heart rate data and/or respiration rate data of the individual. In an embodiment, the computing device analyzes morphology in the heart rate data and/or the respiratory rate data to determine whether a possible patient turn has occurred. Accordingly, the computing device may detect the occurrence of a patient turn based on the load cell data, heart rate data, and/or respiration rate data. Various embodiments of systems and methods for detecting a turn in a patient will be described in more detail herein with particular reference to the accompanying drawings.

In fig. 1, a person support apparatus 100 is shown that includes a frame 102 and a person support surface 104. The frame 102 includes a base 106, an upper frame assembly 108, and a lift system 110 that couples the upper frame assembly 108 to the base 106. The lift system 110 is operable to raise, lower, and tilt the upper frame assembly 108 relative to the base 106. The person support device 100 has a head end 112 and a foot end 114, and further includes a footboard 116 located at the foot end 114 of the person support device 100 and a headboard 118 located at the head end 112 of the person support device 100. The headboard 118 is coupled with an upright portion 120 of the base 106 at the head end 112 of the person support apparatus 100. The foot pedal 116 is coupled with the upper frame assembly 108. Base 106 includes wheels or casters 122 that roll along a floor (not shown) as person support 100 is moved from one location to another. A pair of foot switches 124 are coupled to base 106 and are used to brake and release casters 122.

As shown in FIG. 1, the people support device 100 has four guardrail assemblies coupled to an upper frame assembly 108. The four guardrail assemblies include a pair of head guardrail assemblies 126 (sometimes referred to as head railings) and a pair of foot guardrail assemblies 128 (sometimes referred to as foot railings). Each guardrail assembly 126,128 is movable between a raised position as shown in fig. 1 and a lowered position (not shown). The guardrail assemblies 126,128 are sometimes referred to herein as guardrails 126, 128. Each guardrail 126,128 includes a coupler 130, and coupler 130 is coupled to upper frame assembly 108 and is configured to guide guardrail 126,128 between the raised and lowered positions.

The upper frame assembly 108 includes a lifting frame 132, a counterweight frame 134 supported relative to the lifting frame 132, and a person support platform 136. A person support platform 136 is carried by the weighted frame 134 and engages the underside of the person support surface 104. As shown in FIG. 1, the person support platform 136 includes a head 138, a seat portion 140, a thigh portion 142, and a foot 144. In various embodiments, the sections 138,142, and 144 are movable relative to the weight frame 134. For example, the head 138 may be pivotally raised and lowered relative to the seat portion 140, the foot 144 may be pivotally raised and lowered relative to the thigh portion 142, and the thigh portion 142 may articulate relative to the seat portion 140. Further, in some embodiments, the feet 144 may be extended and retracted to change the overall length of the feet 144, and thus the overall length of the person support platform 136.

In the embodiment depicted in FIG. 1, the seat portion 140 is fixed in position relative to the counterweight frame 134 as the person support platform 136 moves between its various positions, including a horizontal position (shown in FIG. 1) and a seat position (not shown). In other embodiments, the seat portion 140 also moves relative to the weighted frame 134, such as by pivoting and/or translating. In such embodiments, thigh portion 142 and foot portion 144 may also translate with seat portion 140. In the seating position, the head portion 138 extends upwardly from the counterweight frame 134 and the foot portion 144 extends downwardly from the thigh portion 142.

Further, the person support device 100 includes four foot switches 146a,146b,146c,146d coupled to the base 106. In an embodiment, a foot pedal may be used to raise and lower portions of the person support apparatus 100. For example, foot switch 146a may be used to raise the upper frame assembly 108 relative to the base 106, foot switch 146b may be used to lower the upper frame assembly 108 relative to the base 106, foot switch 146c may be used to raise the head 138 relative to the counterweight frame 134, and foot switch 146d may be used to lower the head 138 relative to the counterweight frame 134. In other embodiments, one or more foot switches may be omitted, or additional foot switches may be included.

In an embodiment, each guardrail 126 includes a first user control panel 148 coupled to an outboard side of guardrail 126, and each guardrail 128 includes a second user control panel 150 coupled to an outboard side of guardrail 128. The control panels 148,150 include various buttons that may be used by a caregiver to control the associated functions of the personal support device 100. For example, the first user control panel 148 may include buttons for operating the motor to raise and lower the head 138, buttons for operating the motor to raise and lower the thigh section 142, and buttons for operating the motor to raise, lower, and tilt the upper frame assembly 108 relative to the base 106. The second user control panel 150 may include a button for operating the motor to raise and lower the foot 144, and a button for operating the motor to extend and retract the foot 144.

In various embodiments, one or more components of human support apparatus 100 are coupled with computing device 200, computing device 200 being configured to sense and/or collect information from the components coupled therewith, process the information, and perform one or more actions based on the information. The computing device 200 may further provide various resources to the human support apparatus 100. Resources include, for example, providing processing, storage, software, and information to the person support apparatus 100 from other systems in the establishment. In various embodiments, as will be described in greater detail below, the computing device 200 may detect and/or confirm the occurrence of a patient turn based on information sensed or collected from various components of the human support apparatus 100. The components may be wirelessly coupled with computing device 200, for example, over network 202, or the components may be coupled with computing device 200 via wires. Thus, in some embodiments, one or more components of human support apparatus 100 may include wireless communication circuitry, or may be communicatively coupled with wireless communication circuitry (not shown) incorporated in human support device 100.

Computing device 200 may be any device having hardware (e.g., a chipset, processor, memory, etc.) for communicatively coupling with network 202. In particular, depending on the particular embodiment, the computing device may be a mobile device, a desktop computing device, or a computing device incorporated into or attached to the person support apparatus 100. For example, the computing device 200 may be a smartphone, a tablet, an e-reader, a laptop, a desktop, or a computer associated with the personal support apparatus 100. In various embodiments, computing device 200 may be a device accessible by one or more caregivers, such as a computing device located at a nurse station, a doctor's office, or carried by a caregiver.

In various embodiments, computing device 200 includes one or more persistent storage components, one or more processing devices, a display 204, speakers, at least one input device, and network interface hardware. The one or more persistent storage components store computer-readable and executable instructions that, when executed by the processor, cause the computing device 200 to perform one or more of the functions described herein. In particular, one or more non-transitory memory components may store computer-readable and executable instructions that, when executed by a processor, cause the computing device 200 to perform the functions of the various modules described below, including but not limited to analyzing data from one or more components of the human support apparatus 100, identifying a possible patient turn, confirming an occurring patient turn, and/or causing an indication that a patient turn occurred to be logged in an electronic medical record corresponding to the individual. By way of example, and not limitation, the at least one input device may include a microphone, keyboard, touch screen, mouse, and the like. The network interface hardware may depend on the particular embodiment, and may include hardware that enables the computing device 200 to communicate via a network. The display may comprise any medium capable of transmitting light output, such as a cathode ray tube, a light emitting diode, a liquid crystal display, a plasma display, and the like. Further, in some embodiments, the display is a touch screen that, in addition to providing visual information, detects the presence and location of tactile input on or near the surface of the display. Computing device 200 may include additional or fewer components, depending on the particular embodiment. For example, in embodiments where computing device 200 is a smartphone, it may also include cellular network hardware and a microphone, but not a mouse, while in embodiments where computing device 200 is a desktop computing device, it may include a keyboard and a mouse, but not a touch screen.

In various embodiments, the computing device 200 is communicatively coupled with one or more input devices of the person support apparatus 100 that collect information indicative of the occurrence of a patient turn. For example, in various embodiments, the person support apparatus 100 may include load cells 152a-152d, mechanical sensors 154, and/or the like, where the load cells 152a-152d, mechanical sensors 154, and/or the like provide data to the computing device 200, and the computing device 200 detects and/or confirms the occurrence of a patient turn based on the received data. Various input devices and methods for detecting and/or confirming that a patient turn has occurred will now be described.

In various embodiments, the person support device 100 also includes a plurality of load cells located between the weighted frame 134 and the base 106. Each load cell is configured to generate a voltage or current signal indicative of a weight applied to the load cell from the weight member 134 relative to the base 106. In the embodiment shown in FIG. 1, four load cells 152a, 152b, 152c, and 152d are located between the weight frame 134 and the base 106; although only two load cells 152a and 152c are visible in fig. 1, there is one load cell at or near each corner of the person support apparatus 100. However, all four load cells 152a, 152b, 152c, and 152d are shown in FIG. 2.

Hereinafter, some structural components of the human support device 100 will be designated as "right," "left," "head," and "foot" from a reference point of an individual lying supine on the human support surface 104, with the individual's head facing the head end 112 of the human support device 100 and the individual's foot facing the foot end 114 of the human support device 100. For example, the weight frame 134 shown in fig. 2 may include a head end weight frame member 134c mounted at one end of the right side weight frame member 134a and at an opposite end at one end of the left side weight frame member 134 b. The opposite ends of the right and left weighted frame members 134a and 134b are mounted to foot end weighted frame member 134 d. The opposite ends of the intermediate weighted frame member 134e are mounted on the right and left weighted frame members 134a and 134b, respectively, between the head end weighted frame member 134c and the foot end weighted frame member 134 d.

As shown in the block diagram of fig. 2, a Right Head Load Cell (RHLC)152a is illustratively positioned near the right head end of the person support device 100 between the base support frame 106a secured to the base 106 near the head end 112 and the connection of the head end weighted frame member 134c and the right side weighted frame member 134 a. A Left Head Load Cell (LHLC)152b is illustratively positioned near the left head end of the people support 100 between the connection of the base support frame 106a and the head end weighted frame member 134c and the left side weighted frame member 134 b. A Right Foot Load Cell (RFLC)152c is illustratively positioned near the right foot end of the person support 100 between the connection of the base support frame 106b, which is fixed to the base 106 near the foot end 114 of the person support 100, and the foot end weighted frame member 134d and the right side weighted frame member 134 a. Left Foot Load Cell (LFLC)152d is illustratively positioned near the left foot end of person support device 100 between the connection of base support frame 106b and foot end weighted frame member 134d and left side weighted frame member 134 b. In the embodiment shown in FIG. 2, the four corners of the person support platform 136 are shown extending beyond the four corners of the weighted frame 134, and thus beyond the location of the four load cells 152a-152 d.

In the illustrated embodiment, each load cell 152a-152d is a weight sensor having a resistive strain gauge coupled to a deflectable block (not shown) and structurally couples the weighted frame 134 to the base 106. However, it should be understood that other weight detection devices may alternatively be used. Such devices may include, but are not limited to, Linear Variable Displacement Transducers (LVDTS) and/or other weight-sensing devices that may operate according to known capacitive, inductive, or other physical principles.

In various embodiments, the load cells 152a-152d generate signals that are sent to the computing device 200. In other words, the load cells 152a-152d generate load cell data that is transmitted to the computing device 200. As will be described in more detail below, the computing device 200 receives load cell data and, using the load pattern analysis module 301, may analyze the load cell data (e.g., waveforms) received from the load cells 152a-152d in order to detect or confirm a patient turn. For example, the load pattern analysis module 301 may determine that a particular waveform is indicative of a possible patient turn because the signals generated by the load cells 152a-152d will vary as the patient moves from an initial position (i.e., the supine position) to a position where they increase the weight supported on one side of the human support surface 104 to a final position (i.e., the prone position).

Returning to fig. 1, in various embodiments, the person support apparatus 100 further includes a mechanical sensor 154 coupled with the computing device 200. For example, the mechanical sensor 154 may be in the form of a motion sensor such as a pressure gauge (e.g., a piezoelectric sensor) or a strain gauge. The mechanical sensor 154 detects one or more physiological characteristics of the individual without contacting or viewing the individual or clothing worn by the individual. The mechanical sensor 154 is positioned below the person support surface 104 and is configured to sense respiration and heartbeat-related motion (e.g., respiration rate data and heart rate data) of the individual. In some embodiments, the mechanical sensor 154 may be incorporated into the person support surface 104. Although shown in fig. 1 as being located in a region corresponding to the abdomen or chest of the individual being supported by the human support device 100, it is contemplated that in some embodiments, the mechanical sensor 154 may be positioned in a region corresponding to the leg of the individual. For some applications, such positioning may provide a clearer pulse signal than positioning under the chest or abdomen of an individual. In some embodiments, the mechanical sensor 154 includes a plurality of pressure or strain sensors arranged in a grid. The use of a grid rather than a single meter may allow for improved signal reception. It is further contemplated that in some embodiments, a fiber optic sensor may be used as an alternative to the mechanical sensor 154.

Regardless of the specific type of mechanical sensor 154, in various embodiments, the mechanical sensor 154 senses movement of an individual positioned on the human support device (e.g., movement caused by a caregiver rolling or otherwise repositioning the individual) and generates a corresponding output. In an embodiment, the output generated by the mechanical sensor 154 is transmitted to the computing device 200, and the computing device 200 processes the output, including, for example, amplifying the output.

FIG. 3 is a schematic block diagram illustrating components of computing device 200. In various embodiments, computing device 200 includes a motion data acquisition module 300 and a pattern analysis module 302. The pattern analysis module 302 includes at least a load pattern analysis module 301, a breathing pattern analysis module 304, and a heartbeat pattern analysis module 306. However, in some embodiments, the pattern analysis module 302 may also include one or more of a cough analysis module, a restlessness analysis module, and a blood pressure analysis module (not shown). It is contemplated that other analysis modules may be included, depending on the particular embodiment.

In various embodiments, the motion data acquisition module 300 is adapted to non-invasively monitor the repositioning, breathing, and heartbeat patterns of an individual supported on the human support device 100. The load pattern analysis module 301, the breathing pattern analysis module 304 and the heartbeat pattern analysis module 306 are adapted to analyze the respective patterns to (a) predict an impending clinical event, such as asthma attack or heart disease related lung fluid accumulation, and/or (b) monitor severity and progression of the clinical event as it occurs. In some embodiments, the load pattern analysis module 301, the breathing pattern analysis module 304 and the heartbeat pattern analysis module 306 are adapted to analyze the respective patterns to determine a likelihood of an impending adverse clinical event without having to determine the nature of the event. In various embodiments described herein, the computing device 200 may provide notifications to caregivers about predicted or occurring clinical events via one of the user interfaces described herein.

The motion data acquisition module 300 generally includes circuitry for processing the raw signals generated by the load cells 152a-152D and the mechanical sensor 154, such as at least one preamplifier 308, at least one filter 310, and an analog-to-digital (A/D) converter 312. The filter 310 may be a band pass filter or a low pass filter. The low pass data may be digitized and stored in memory at a suitable sampling rate (e.g., 10 Hz). After the a/D converter 312 converts the amplified and filtered signal, the signal is passed to the pattern analysis module 302 for analysis.

In some embodiments, as will be described in more detail below, pattern analysis module 302 combines parameter data generated from load pattern analysis module 301, breathing pattern analysis module 304, and heartbeat pattern analysis module 306, and analyzes the combined data to predict and/or monitor a clinical event or patient turn. For some embodiments, pattern analysis module 302 derives a score for each parameter based on the deviation of the parameter from a baseline value (either for an individual or based on an overall average). The pattern analysis module 302 may combine the scores, such as by taking an average, maximum, standard deviation, or other function of the scores. The combined score may then be compared to one or more thresholds to determine whether the event is predicted, currently occurring, or neither predicted nor occurring, and/or to monitor the severity and progression of the event that is occurring. In some embodiments, pattern analysis module 302 may learn criteria and/or functions for combining individual parameter scores for an individual or group of patients based on personal history. For example, the pattern analysis module 302 can perform such learning by analyzing parameters measured prior to a previous clinical event and stored in an individual Electronic Medical Record (EMR).

The breathing pattern analysis module 304 is adapted to extract breathing patterns from the motion data and the heartbeat pattern analysis module 306 is adapted to extract heartbeat patterns from the motion data, while the load pattern analysis module 301 is adapted to extract repositioning patterns from the load cell data. In some embodiments, the load pattern analysis module 301 may additionally or alternatively extract the repositioning pattern from the motion data received from the mechanical sensor 154.

In an embodiment, the load pattern analysis module 301 may determine that a particular waveform (i.e., signal) is indicative of a possible patient turn because the signals generated by the load cells 152a-152d will change as the patient moves from an initial position (i.e., supine position) to a position where they will support an increased weight on one side of the human support surface 104 to a final position (i.e., prone position).

In some embodiments, the breathing rate of the individual is measured over a period of time, and the breathing pattern analysis module 304 determines a parameter of the breathing rate of the individual over the duration of time, such as a median breathing rate, an average breathing rate, a maximum breathing rate, and/or a breathing rate pattern. The breathing pattern analysis module 304 may compare the predetermined parameter to the same parameter determined the previous day over a time period corresponding to the time period used to determine the breathing parameter for the current day. For example, the parameter may be compared to the same parameter determined the same day at the same time of day and same duration.

In various embodiments, the heartbeat pattern analysis module 306 performs a substantially similar analysis on the heart rate of the individual as described with respect to the breathing pattern analysis module 304. For example, the heartbeat pattern analysis module 306 may compare a predetermined parameter of the individual's cardiac cycle to the same parameter determined the day before over a period of time corresponding to the period of time used to determine the cardiac cycle parameter for the day to determine whether the event was predicted, currently occurred, or neither predicted nor occurred, and/or to monitor the severity and progression of the event.

Although in embodiments, the computing device 200 is described as receiving or collecting information from the mechanical sensor 154 and the load cells 152a-152d, it is contemplated that any number of separate computing devices may be employed. For example, the mechanical sensor 154 may be communicatively coupled with one computing device, while the load cells 152a-152d are communicatively coupled with a second computing device, where each computing device performs pattern analysis on the data it receives. Further, it should be understood that additional and/or alternative inputs may be employed depending on the particular embodiment. For example, in some embodiments, the human support surface 104 may include one or more pressure sensors that may detect motion of the patient based on the redistribution of pressure on the human support surface 104. Such a system may be used to predict the departure of an individual from the human support device 100 and may additionally analyze data to detect or confirm a patient turn. Additional details regarding the system for predicting departure may be found in U.S. patent No.9,761,109, entitled "user departure prediction system, method, and apparatus," which is hereby incorporated by reference in its entirety.

In various embodiments, the pattern analysis module 302, the load pattern analysis module 301, the breathing pattern analysis module 304, and/or the heartbeat pattern analysis module 306 may detect and/or confirm the presence of a possible patient turn based on signals from the load cells 152a-152d and/or the mechanical sensors 154. Additional details regarding the mechanical sensor 154 and the pattern analysis module 302 may be found, for example, in U.S. patent No.8,491,492 entitled "monitoring the condition of a subject," which is hereby incorporated by reference in its entirety. Without being limited by theory, it is believed that a turn over of a patient will decrease the individual's breathing rate and increase the individual's heart rate over a predetermined period of time as compared to a previous period of time. Thus, the pattern analysis module 302 may analyze the individual's motion, heart rate, and breathing rate and determine that a patient turn may have occurred when an increase in heart rate and a decrease in breathing rate occur with a particular load cell waveform over a predetermined period of time.

For example, as shown in fig. 4, plots of respiration rate 402, heart rate 404, and load cell data 406 over time (x-axis) each indicate a change in a particular time indicative of a patient turning over. By combining pattern analysis of load cell data with pattern analysis of heart rate and respiratory rate, the occurrence of a patient turn 408 may be reliably identified based on the data as compared to analyzing the pattern of any single data set alone. Fig. 4 also includes information about the presence of a caregiver 410 in the room, which can be used to further confirm the occurrence of a patient turn, as will now be described.

Caregiver tracking system

In various embodiments, a real-time location system 500 is provided for tracking various people throughout an environment (e.g., a medical facility such as a hospital, nursing home, rehabilitation facility, doctor's office, etc.). In particular, the system 500 may detect the presence of one or more people in the room 502. Accordingly, the real-time positioning system 500 may be used to determine whether a caregiver is within a preset distance of the human support device 100 during a detected turn of the patient.

The system 500 includes a Real Time Location System (RTLS) receiver 504 located within a room 502 to receive wireless signals from a caregiver's token or tag 506 and from an individual's token or tag 508, such as a person located on a person support. The tags 506,508 are carried by the caregiver and individual, respectively, and may be clipped or otherwise attached to the caregiver or individual's clothing, etc. In some embodiments, the tags 506,508 may be in the form of a wristband, key fob, wireless phone, pendant, or the like.

The caregiver's tag 506 sends caregiver Identification Data (ID) to the RTLS receiver 504, and the individual's tag 508 sends the individual's identification data to the RTLS receiver 504. In various embodiments, the identification data may be transmitted by the tags 506,508 at predetermined time intervals, such as, by way of example and not limitation, every three seconds or every thirty seconds. In other embodiments, the tags 506,508 may transmit identification data in response to a signal received from the receiver 504 or other device. In such embodiments, battery life of the tags 506,508 may be conserved because transmissions only occur in response to requests from the receiver 504 that are at a communication distance from the tags 506, 508.

In some embodiments, the RTLS receiver 504 may be included as part of a transceiver. Thus, the double-headed dashed arrow between the tags 506,508 and the RTLS receiver 504 in FIG. 5 indicates that there may be two-way (e.g., two-way) communication between the tags 506,508 and the RTLS receiver 504. However, it should be understood that the wireless communication technology used for communication from the RTLS receiver 504 to the tags 506,508 need not be the same as the wireless communication technology used for communication from the tags 506,508 to the RTLS receiver 504. In various embodiments, the wireless communication technology may be, for example, Infrared (IR), Radio Frequency (RF), Ultrasonic (US), Ultra Wideband (UWB), or Ultra Low Frequency (ULF), or other wireless communication technology. In an embodiment, RTLS receiver 504 may be included as part of a Wireless Access Point (WAP) that communicates using WiFi technology.

The RTLS receiver 504 sends the received caregiver ID data and the identification data of the individual to the RTLS server 510. In some embodiments, the RTLS receiver 504 may also send RTLS receiver ID and/or locator element ID data to the RTLS server 510. The RTLS receiver ID data or locating unit ID data is associated with the room 502 in which the RTLS receiver 504 or locating unit is located. Thus, the RTLS server 510 can correlate the caregiver ID data from the tag 506, the identification data of the individual from the tag 508, and the room ID data from the RTLS receiver 504 to indicate which caregiver and individual is in which room. It is understood that various institutions have multiple rooms 502 with RTLS receivers 504, with the RTLS receivers 504 communicating with RTLS servers 510 to track the whereabouts of multiple caregivers and individuals throughout the institution. Thus, the tags 506,508, the RTLS receiver 504, and the RTLS server 510 together are considered a Real Time Location System (RTLS).

In FIG. 5, RTLS server 510 communicates with login server 514 via network 202. Although shown as two servers performing separate functions as in fig. 5, it is contemplated that in some embodiments, the functions performed by the RTLS server 510 and the functions performed by the login server 514 may be performed on a single server. That is, in some embodiments, the software that controls the location and tracking functions of the RTLS server and the software that controls the login functions of the login server 514 may be located on a single server. It is further contemplated that the functions of the RTLS server 510 and/or the login server 514 may be performed by the computing device 200 described above. The server and/or computing device may also have the functionality of any other server in the organization's network 202. Thus, by way of example and not limitation, the login server 514 and/or the RTLS server 510 may function as a nurse call server, an Admission Discharge Transfer (ADT) server, an Electronic Medical Record (EMR) server 518, or a workflow server. Further, although the double-headed arrow interconnecting RTLS receiver 504 and RTLS server 510 means that no connection to network 202 is involved (e.g., direct wiring between RTLS receiver 504 and RTLS server 510), it is contemplated that communication between RTLS receiver 504 and RTLS server 510 may include the infrastructure of network 202.

As shown in fig. 5, the login server 514 is coupled with the computing device 200 in the room 502 via the network 202. The computing device 200 includes a display 204. In some embodiments, an Internet Protocol (IP) address or Media Access Control (MAC) address of computing device 200 is associated with room 502 in which computing device 200 is located. Thus, the databases in the RTLS server 510 and/or the login server 514 store information about the location of the computing device 200 based on the IP or MAC address of the computing device 200 transmitted to the login server 512 via the network 202. Alternatively or additionally, the tag 516 may be attached to the computing device 200. As shown in fig. 5, the tag 516 communicates with the RTLS server 510 via the RTLS receiver 504. The use of the tags 516 to track the whereabouts of a particular computing device 200 may be particularly suitable for embodiments in which the computing device 200 is used for transportation throughout an organization, such as a tablet or a wheeled computer.

In various embodiments, depending on the identity of the caregiver as indicated by the caregiver Identification Data (ID) from tag 506 and the identity of the individual as indicated by the individual's identification data from tag 508 sensed by RTLS receiver 504 in room 502, login server 514 sends one or more messages to computing device 200 to automatically log the caregiver into computing device 200 and display an initial screen on display 204. Thus, in embodiments, the caregiver does not need to enter any information at the computing device 200 to log into the computing device 200. Logging into computing device 200 is also considered logging into network 202 in the various embodiments described herein. Thus, once the caregiver logs into computing device 200, the caregiver can navigate to various software applications available on various computing devices and servers connected to network 202, including RTLS server 510, login server 514, and Electronic Medical Record (EMR) server 518. Additional details regarding RTLS systems, including various functions that may be performed using the caregiver location tracking system described herein, may be found in U.S. patent application publication No.2017/0004259 entitled "automatic contextual login using real-time location system information," the entire contents of which are hereby incorporated by reference.

The EMR server 518 stores electronic medical records for each individual in the institution. As described above, in various embodiments, data from the load cells 152a-152d, data from the mechanical sensors 154, information regarding clinical events, various parameter events related to respiration rate and/or heart rate, and possible or confirmed patient turn may be stored in the individual's EMR. In various embodiments, the presence of a caregiver in the room 502 during a possible patient turn may also be stored in the individual's EMR.

For example, as shown in FIG. 4, the presence of a caregiver 410 in a room 502 may be logged over time. When the pattern analysis module 302 determines that the respiration rate, heart rate, and/or load cell data indicate that a patient turn may occur, the presence of a caregiver in the room may be used for confirmation. In particular, if the pattern analysis module 302 determines that the respiration rate, heart rate, and/or load cell data indicate that a patient turn may occur, but the caregiver is not in the room, the patient turn will not be logged and stored in the individual's EMR. However, as shown in fig. 4, if the pattern analysis module 302 determines that a respiration rate, heart rate, and/or load cell data indicates that a patient turn may occur, and that the caregiver is in the room, the patient turn is logged and stored in the individual's EMR. In an embodiment, as shown in fig. 6, it is contemplated that after the occurrence of a patient turn is identified by the pattern analysis module 302, the occurrence of the patient turn may be automatically logged in the individual's EMR, which may increase the accuracy of the EMR with respect to the patient turn.

In some embodiments, to ensure that a patient turn is not incorrectly posted to the individual EMR, the computing device 200 may request a turn confirmation from the caregiver. For example, after identifying a possible occurrence of a patient turn, the computing device 200 may display a confirmation prompt on the display 204 requesting input from the caregiver to confirm that the patient turned over. In an embodiment, the caregiver may select a button, press a key, or otherwise provide input to confirm that a patient turn has occurred before the patient turn is registered with the EMR. In some such embodiments, an unproven turn may additionally be stored in the EMR, e.g., indicating that a possible patient turn was detected but not confirmed.

FIG. 6 is a screenshot of an example Electronic Medical Record (EMR)600 of an individual, such as might be displayed on the display 204 of the computing device 200 when a caregiver logs in. The EMR includes identification and demographic information 602 including, by way of example and not limitation, the name, age, gender, location, etc. of the individual. The EMR600 shown in fig. 6 also includes several additional information blocks, including a question list 604, an allergy/contraindications list 606, a medication list 608, a health maintenance log 610, and a turn log 612. It is contemplated that the EMR600 may include any or all of these blocks of information, and may include additional blocks of information, depending on the particular embodiment. The question list 604 may, for example, include diagnoses and conditions of the individual being treated. Allergy/contraindications list 606 may include any allergies of the individual, as well as a list of any drugs or procedures that are contraindicated based on other information available in the EMR.

The medication list 608 may include any medications that the individual is taking or has taken, as well as information about the dose, the time of the last dose, and the time of the next dose. Health maintenance log 610 may include information about any procedures or treatments that have been performed on the individual. Finally, turn log 612 may include a log of patient turns, such as those automatically identified and logged by pattern analysis module 302 and/or manually entered turns by a caregiver. In an embodiment, turn log 612 includes the date and time that the turn was completed. In other embodiments, turn log 612 may include information such as whether a turn was confirmed, whether a caregiver performed a turn, or from additional instructions to the caregiver regarding a turn. Thus, a user viewing the individual's EMR can easily see the individual's patient turn history, and can determine when the next turn should occur.

To illustrate one or more embodiments in another manner, fig. 7 depicts an exemplary flow chart illustrating a method of determining that a patient turn has occurred. First, the individual's respiration rate 702, heart rate 704, and load cell data 706 are analyzed to identify a possible turn at 708. For example, as described above, the pattern analysis module 302 on the computing device 200 may analyze the data received from the mechanical sensors 154 and the load cells 152a-152d, identify that the individual's breathing rate has changed, the individual's heart rate has changed, and identify that there has been motion on the patient support surface 104 indicative of a possible patient turn.

Next, in some embodiments, based on the caregiver location data 710, the computing device determines whether the caregiver is in the room at 712. If the caregiver is not in the room when a turn is possible (e.g., "no" at block 712), the computing device determines that no turn has occurred at 714. However, if the caregiver is in the room when a turn is possible (e.g., "yes" at block 712), the computing device determines that a turn has occurred at 716. It should be appreciated that in an embodiment, using caregiver location data to confirm a turn is optional. In embodiments that do not include such a step, but include a step of confirming the turn by requesting caregiver input, the method may proceed from block 708 to block 716.

In various embodiments, after determining that a turn has occurred, the computing device may request confirmation at 718 that a turn has occurred. If the computing device confirms the turn based on the received caregiver input 720 confirming the turn (e.g., "yes" at block 718), the turn is logged into the individual's EMR at 722. However, if the computing device is unable to confirm the turn, such as an indication from the caregiver that a turn has not occurred or a lack of caregiver input (e.g., "no" at block 718), the computing device determines at 724 that a turn has not occurred. Alternatively, in some embodiments, if confirmation from the caregiver is not received, the computing device logs the turn in the individual's EMR, noting that the turn was not confirmed.

Although the method illustrated in fig. 7 is described as being performed by a computing device, it is contemplated that in some embodiments, more than one computing device or server communicatively coupled to the network 202 may perform one or more steps of the method. Thus, it should be understood that in the various embodiments described herein, various facility information systems (e.g., from H)Of ill-Rom

System, EMR system, Smart Connect System from Hill-Rom and Smart from Hill-Rom

Systems) may communicate with each other to perform the described functions.

In some embodiments herein, in addition to determining that a patient turn has occurred and posting the patient turn in the individual's EMR, the system described herein may provide a notification or reminder to the caregiver that the individual should be turned. For example, if a predetermined period of time (e.g., a period of time greater than about one hour 45 minutes, about two hours, and 15 minutes or more) has elapsed since the last patient turn occurred, the computing device 200 may display an alert or notification on the display 204. The particular time period may vary depending on the particular embodiment. Additionally, instead of the computing device displaying an alert or notification, it is contemplated that any computing device connected to the network 202 may receive the alert or notification, including, for example, a mobile computing device carried by a caregiver, a computing device at a nurse's station, etc. Further, it is contemplated that any of the several computing devices and servers described in the various embodiments herein may determine that an alert or notification should be sent or displayed. For example, the pattern analysis module 302 may determine that the individual should be rolled over and that no rolling over occurred within a threshold period of time, or an application or module on the EMR server 518, login server 514, RTLS server 510, or any other server or computing device connected to the network 202 may perform this function, so long as such server or computing device is communicatively coupled with the individual's EMR and can determine the time of the last logged patient roll over.

In various embodiments, patient turn data, particularly the occurrence of patient turns and their frequency, may be used to adjust one or more treatment protocols for an individual and/or institution. For example, the data may be used to determine that certain cohorts of patients should be turned more frequently, e.g., based on age, gender, or diagnosis. Thus, when certain groups of patients are indicated as more prone to pressure sores based on trends in patient turn-over data, the threshold time period for an alarm or notification may be adjusted to remind caregivers to turn over particular individuals more frequently. Patient turn data may further be used to confirm and document that certain treatment regimens have been used, such as may be required by insurance or applicable regulations for an institution.

Thus, the various embodiment systems described herein analyze patterns in the load cell data, heart rate data, and/or respiration rate data to determine whether a patient turn has occurred, and automatically log the occurrence of the patient turn in an electronic medical record corresponding to the individual. Additional information, such as information about the caregiver's position and/or input from the caregiver, may be used to confirm the occurrence of a patient turn. In various embodiments described herein, the system may further provide a notification or alert or adjust a treatment regimen based on the logged patient turn.

In addition to the embodiments described above, many other embodiments are possible and still be included within the spirit and scope of the claims that define the embodiments described herein. For example, while various combinations of features of the wound dressing have been shown and described, it is contemplated that these features may be combined in other ways, as described in detail or shown in the drawings.

Embodiments may be described with reference to the following clauses, wherein preferred features are listed in the dependent clauses.

1. A system, comprising: a person support device having a person support surface and a support frame; a plurality of load cells for generating load cell data, at least one of the plurality of load cells being positioned at or near each corner of the support frame; a sensor for sensing at least one of heart rate data and respiration rate data of an individual, the sensor being disposed between the person support surface and the support frame; and a computing device coupled with the plurality of load cells and the sensor for receiving the load cell data and at least one of heart rate data and respiration rate data of the individual, the computing device comprising a processor and a memory storing computer-readable and executable instructions that, when executed by the processor, cause the computing device to detect that a patient turn has occurred on a human support surface based on the load cell data and the at least one of heart rate data and respiration rate data of the individual, and cause an indication that a patient turn has occurred to be logged in an electronic medical record corresponding to the individual.

2. The system of clause 1, wherein the executable instructions, when executed by the processor, further cause the computing device to request input from a caregiver to confirm that a patient turn has occurred.

3. The system of clause 1 or 2, wherein the computing device detects that a patient turn has occurred in response to identifying a waveform in the load cell data indicative of a possible patient turn within a predetermined period of time and at least one of an increase in heart rate and a decrease in breathing rate.

4. The system of any of clauses 1-3, further comprising: a tag corresponding to the caregiver for transmitting caregiver identification data; a real-time location system (RTLS) receiver for receiving the caregiver identification data from the tag and sending the caregiver identification data; and a real-time location system (RTLS) server for receiving the caregiver identification data from the RTLS receiver and associating the caregiver identification data with a location of the RTLS receiver to indicate a location of a caregiver; wherein the executable instructions, when executed by a processor, further cause a computing device to confirm that a patient turn has occurred based on the location of the caregiver.

5. The system of clause 4, wherein the computing device confirms that a patient turn has occurred in response to determining that the position of the caregiver during the patient turn is within a preset distance of the human support apparatus.

6. The system of any of clauses 1-5, wherein the sensor senses heart rate data and respiration rate data of the individual; the computing device receiving heart rate data and respiration rate data for the individual; and the computing device detects that a patient turn has occurred on the human support surface based on the load cell data, the individual's heart rate data, and respiration rate data.

7. The system of any of clauses 1-6, wherein the executable instructions, when executed by the processor, further cause the computing device to display an alert or notification on a display of the computing device indicating that a predetermined period of time has elapsed since a patient turn occurred.

8. The system of clause 7, wherein the computing device displays the alert or notification in response to the passage of a predetermined period of time since the last patient turn was logged in the electronic medical record corresponding to the individual.

9. A method, comprising: receiving load cell data from a plurality of load cells located on a person support device; receiving heart rate data and respiration rate data of an individual from a sensor coupled with the human support device; determining that a waveform of the load cell data over a period of time indicates a possible patient turn; identifying at least one of a decrease in the individual's breathing rate over the period of time and an increase in the individual's heart rate over the period of time; determining that a patient turn has occurred based on said determining that said waveform of said load cell data over said period of time is indicative of a possible patient turn and said identifying at least one of a decrease in respiration rate and an increase in heart rate of said individual over said period of time; and causing an indication that the patient has turned over to be logged into an electronic medical record corresponding to the individual.

10. The method of clause 9, further comprising: receiving caregiver identification data indicative of caregiver location; and confirming that a patient turn has occurred based on the location of the caregiver.

11. The method of clause 10, wherein the confirming that a patient turn has occurred is in response to determining that the position of the caregiver is within a preset distance of the human support device during a patient turn.

12. The method of clause 11, wherein the preset distance is within a room in which the person support apparatus is located.

13. The method of any of clauses 9-12, further comprising: causing display of an alert or notification on a display of the computing device indicating that a predetermined period of time has elapsed since a patient turn occurred.

14. The method of clause 13, wherein causing the alarm or notification to be displayed is in response to the elapse of a predetermined period of time since the last patient turn was logged in the electronic medical record corresponding to the individual.

15. The method of clause 13 or 14, wherein the computing device is selected from the group consisting of a mobile computing device carried by a caregiver and a computing device of a nurse station.

16. The method of any of clauses 9-15, further comprising: a request is made to a caregiver to confirm that a patient turn has occurred before causing an indication that a patient turn has occurred to be posted in an electronic medical record corresponding to the individual.

17. The method of clause 16, wherein if confirmation is not received from the caregiver, the indication that a patient turn has occurred is not posted in the electronic medical record corresponding to the individual.

18. The method of clause 16, wherein if confirmation is not received from the caregiver, the indication that a patient turn has occurred is entered into the electronic medical record corresponding to the individual and noting that the patient turn has not been confirmed.

19. The method of any of clauses 9-18, further comprising: adjusting a treatment plan based on the frequency of occurrence of patient turns recorded in the electronic medical record corresponding to the individual.

20. The method of clause 19, wherein adjusting the treatment regimen comprises adjusting a threshold time period for an alert or notification regarding a next patient turn of the individual.

Any theory, mechanism of operation, proof, or finding stated herein is meant to further enhance understanding of the principles of the present invention and is not intended to make the present invention in any way dependent upon such theory, mechanism of operation, illustrative embodiment, proof, or finding. It should be understood that while the use of preferred, preferably or preferential terms in the foregoing description indicates that the feature so described may be more desirable, it nonetheless may not be necessary and embodiments lacking the same may be contemplated as within the scope of the invention, that scope being defined by the claims that follow.

In reading the claims, it is intended that when words such as "a," "an," "at least one," and "at least a portion" are used, there is no intention to limit the claims to only one item unless specifically stated otherwise in the claims. When the expression "at least a portion" and/or "a portion" is used, the object may include a portion and/or the entire object, unless explicitly stated otherwise.

It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments described herein without departing from the spirit and scope of the claimed subject matter. Thus, it is intended that the present specification cover the modifications and variations of the various embodiments described herein provided they come within the scope of the appended claims and their equivalents.