SURGICAL TABLE AND METHOD FOR DETECTING CARDIOPULMONARY RESUSCITATION BY THE SURGICAL TABLE

Abstract

A surgical table comprises a base, a tabletop attached to the base, a force sensor, and a controller. The force sensor is configured to detect a force exerted to the tabletop (3) and to transmit the force to the controller. The controller is configured to evaluate the force exerted to the tabletop and to execute a predefined routine for determining cardiopulmonary resuscitation for a patient lying on the tabletop by distinguishing forces caused by the cardiopulmonary resuscitation from other forces exerted to the tabletop.

Claims

1. A surgical table comprising a base, a tabletop attached to the base, a force sensor, and a controller, wherein the force sensor is configured to detect a force exerted to the tabletop and to transmit the force to the controller, and the controller is configured to evaluate the force exerted to the tabletop and to execute a predefined routine for determining cardiopulmonary resuscitation for a patient lying on the tabletop by distinguishing forces caused by the cardiopulmonary resuscitation from other forces exerted to the tabletop.

2. The surgical table of claim 1, wherein the predefined routine is configured to stop evaluation during motion of the surgical table.

3. The surgical table of claim 2, wherein the predefined routine is configured to determine exerted forces as forces of the cardiopulmonary resuscitation when force peaks values are within a predefined force peak value range (RFP) and a force peak interval is within a predefined force peak interval range.

4. The surgical table of claim 3, wherein the predetermined force peak value range (RFP) is defined by an upper limit value (Lu) being 5% more than a first detected force peak value and a lower limit value (Ll) being 5% less than the first detected force peak value (F1).

5. The surgical table of claim 3, wherein the predetermined force peak interval range is formed by a range of 80 to 120 force peaks/minute.

6. The surgical table of claim 1, wherein the force sensor is arranged in the tabletop.

7. The surgical table of claim 1, wherein the force sensor is arranged in the base.

8. The surgical table of claim 1, wherein the force sensor is configured as a sensor additionally providing load data of the tabletop to the controller.

9. The surgical table of claim 1, wherein the controller is configured to store occurrence of the cardiopulmonary resuscitation.

10. The surgical table of claim 1, wherein the force sensor is configured to output a signal indicative of the detected force, the force signal being transmitted to the controller.

11. A method for detecting cardiopulmonary resuscitation by a surgical having a tabletop, a controller, and a force sensor configured to detect a force exerted to the tabletop and to transmit the force to the controller, the controller being configured to evaluate the force exerted to the tabletop and to execute a predefined routine for determining cardiopulmonary resuscitation for a patient lying on the tabletop by distinguishing forces caused by the cardiopulmonary resuscitation from other forces exerted to the tabletop, the method including the steps: detecting several consecutive force peaks (P1, P2, P3, P1′, P2′, P3′) by the force sensor; and determining the consecutive force peaks (P1, P2, P3) as cardiopulmonary resuscitation if the force peak values are within a predefined force peak value range (RFP) and the force peaks are within a predefined force peak interval range.

12. The method of claim 11, wherein the predefined force peak value range (RFP) is defined by an upper limit value (Lu) being 5% more than a first detected force peak value (F1) and a lower limit value (Ll) being 5% less than the first detected force peak value (F1).

13. The method of claim 11, wherein an end of the cardiopulmonary resuscitation is determined if, within a predefined interval after a last force peak (P3) determined as being a force peak of the cardiopulmonary resuscitation, there are no force peaks, or the consecutive force peaks are outside the predefined force peak value range (RFP) and/or outside the predefined force peak interval range.

14. The method of claim 11, wherein occurrence of the cardiopulmonary resuscitation is stored by the controller.

15. The method of claim 14, wherein a duration of the cardiopulmonary resuscitation is detected and stored by the controller.

16. The method of claim 11, wherein occurrence of the cardiopulmonary resuscitation and/or a duration of the cardiopulmonary resuscitation are/is transferred to a hospital's Electronic Medical Record system.

17. The method of claim 11, wherein the step of determining the consecutive force peaks (P1, P2, P3) is stopped during motion of the surgical table.

18. A method for detecting cardiopulmonary resuscitation, carried out by a patient support apparatus comprising a force sensor, including the steps: detecting several consecutive force peaks (P1, P2, P3, P1′, P2′, P3′) by the force sensor; and determining the consecutive force peaks (P1, P2, P3) as cardiopulmonary resuscitation if the force peak values are within a predefined force peak value range (RFP) and the force peaks are within a predefined force peak interval range.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The detailed description particularly refers to the accompanying figures in which:

[0027] FIG. 1 shows a principal view of a first embodiment of a surgical table according to the present disclosure;

[0028] FIG. 2 shows a principal view of a second embodiment of the surgical table according to the present disclosure;

[0029] FIG. 3 shows a diagram including an example of a force curve of a force caused by cardiopulmonary resuscitation; and

[0030] FIG. 4 shows a diagram including an example of a force curve of a force not caused by the cardiopulmonary resuscitation.

DETAILED DESCRIPTION

[0031] FIG. 1 shows a principal view of a first embodiment of a surgical table 1 according to the present disclosure. The surgical table 1 comprises a base 2 and a tabletop 3 attached to the base 2. The surgical table 1 is configured as a movable surgical table having castors 7 for being movable.

[0032] The surgical table 1 further comprises a force sensor 4 and a controller 5. The force sensor 4 is arranged in the base of the surgical table 1. The controller 5 comprises at least one processor, and memory encoding instructions which, when executed by the at least one processor, cause the at least one processor to be configured to carry out the steps described herein.

[0033] The force sensor 4 is further configured to detect a force exerted to the tabletop 3. This detected force can be a force caused by a patient lying on the tabletop 3, by external forces impacting onto the tabletop 3, or by inertia force when the surgical table 1 is, e.g., moved across a door sill. Moreover, the force sensor 4 is configured as a sensor additionally providing quasi-static load data of the tabletop 3 to the controller 5. This means that the force sensor 4 can be used for two different tasks, namely for the detection of the force caused by the cardiopulmonary resuscitation and for the detection of, e.g., the weight of the patient for detecting overload of the surgical table 1. In an alternative embodiment, the first sensor 4 is provided only for detecting the forces due to the cardiopulmonary resuscitation.

[0034] The controller 5 is configured to control drives (not shown) of the surgical table 1 to move the tabletop 3 with respect to the base 2 in order to perform a height adjustment of the tabletop 3 in order to tilt the tabletop 3. Further, the controller 5 is configured to evaluate the force exerted to the tabletop 3.

[0035] The force sensor 4 is configured to output a force signal, in dependence on the force exerted to the tabletop 3, and transmit that force signal to the controller.

[0036] Furthermore, the controller 5 is configured to execute a predefined routine for determining cardiopulmonary resuscitation for a patient lying on the tabletop 3. This predefined routine is configured to distinguish forces caused by the cardiopulmonary resuscitation from other forces exerted to the tabletop 3.

[0037] Moreover, the controller 5 is configured to store occurrence and duration of the cardiopulmonary resuscitation. In alternative embodiments, the controller 5 does not store the occurrence and duration of the cardiopulmonary resuscitation but transfers the occurrence and duration to, e.g., a hospital's Electronic Medical Record system (EMS). Where the controller is configured to store data relating to the occurrence and duration of the cardiopulmonary resuscitation, the controller comprises storage memory, such as non-volatile memory. In the alternative embodiments, the controller may only comprise volatile memory configured to temporarily store the data relating to the occurrence and duration of the cardiopulmonary resuscitation before transferring the data to an external device, or permanent storage facility such as a hospital's (EMS).

[0038] The predefined routine is configured to stop evaluation during motion of the surgical table 1. In an alternative embodiment, the routine does not stop evaluation during motion of the surgical table 1 but, e.g., it performs the evaluation but it does not store or transfer the result of the evaluation.

[0039] Furthermore, the predefined routine is configured to determine the exerted forces as forces of the cardiopulmonary resuscitation when force peaks values are within a predefined force peak value range RFP (see FIG. 3) and a force peak interval is within a predefined force peak interval range.

[0040] In alternative embodiments, the routine is configured not to be focused on the force peaks but, e.g., on other portions of the force curve.

[0041] FIG. 2 shows a principal view of a second embodiment of the surgical table 1 according to the present disclosure.

[0042] The surgical table 1 according to the second embodiment differs from the surgical table 1 according to the first embodiment in that the force sensor 4 is not arranged in the base 2 but it is arranged in the tabletop 3.

[0043] FIG. 3 shows a diagram including an example of a force curve 6 of a force caused by the cardiopulmonary resuscitation. On the abscissa, an elapsed time t is plotted and, on the ordinate, a force value F is plotted.

[0044] The predetermined force peak value range RFP is defined by an upper limit value Lu being 5% more than a first detected force peak value F1 and a lower limit value Ll being 5% less than the first detected force peak value F1. In this embodiment, the predetermined force peak interval is formed by a range of 80 to 120 force peaks/minute. In alternative embodiments, the ranges are defined as having other limits.

[0045] As to be seen in FIG. 3, all values of the force peaks P1, P2, P3 of the force curve 6 are within the range RFP. Furthermore, as to be seen from the time course, two oscillations are detected within 1 second which corresponds to a force peak interval of 120 force peaks/minute. Thus, the exerted force is determined as force of the cardiopulmonary resuscitation.

[0046] FIG. 4 shows a diagram including an example of a force curve 6′ of a force not caused by the cardiopulmonary resuscitation.

[0047] Also here, on the abscissa, the elapsed time t is plotted on and, on the ordinate, the force value F is plotted. Also, the indications concerning the upper limit value Lu′ being 5% more than the first detected force peak value F1′ and the lower limit value Ll′ being 5% less than the first detected force peak value F1′ are plotted corresponding to FIG. 3.

[0048] As to be seen in FIG. 4, the value of the consecutive force peaks P2′, P3′ following the first force peak P1′ are not within the range RFP′ having the upper limit value Lu′ and the lower limit value Ll′. Therefore, the exerted force is not determined as being a force of a cardiopulmonary resuscitation.

[0049] In use, several consecutive force peaks P1, P2, P3, P1′, P2′, P3′ are detected by the force sensor 4. The consecutive force peaks P1, P2, P3, P1′, P2′, P3′ are determined as cardiopulmonary resuscitation if their force peak values are within the predefined force peak value range RFP, RFP ‘.

[0050] The predefined force peak value range RFP, RFP’ is defined by the upper limit value being 5% more than the first detected force peak F1, F1′ and by the lower limit value being 5% less than the first detected force peak value F1, F1′. As already mentioned above, alternatively, the ranges are defined as having other limits or the routine may be configured not to be focused on the force peaks but on other portions of the force curve.

[0051] An end of the cardiopulmonary resuscitation is determined if, within a predefined interval after the last force peak determined as being a force peak of the cardiopulmonary resuscitation, there are no force peaks, or the force peak values of the consecutive force peaks are outside the predefined force peak value range RFP, RFP′ and/or outside the predefined force peak interval. Alternatively, an end of the cardiopulmonary resuscitation is not determined.

[0052] The occurrence of the cardiopulmonary resuscitation is stored by the controller 5. Alternatively, the occurrence of the cardiopulmonary resuscitation is not stored by the controller 5 but, e.g., transferred to another database.

[0053] Except the occurrence of the cardiopulmonary resuscitation, a duration of the cardiopulmonary resuscitation is detected and stored by the controller 5. Alternatively, the duration is not stored by the controller 5, but, e.g., transferred to another database.

[0054] Optionally, the occurrence of the cardiopulmonary resuscitation and/or the duration of the cardiopulmonary resuscitation are/is transferred to a hospital's Electronic Medical Record System.

[0055] While the present disclosure has been illustrated and described in detail in the drawings and the foregoing description, such illustration and description are to be considered illustrative or exemplary and not restrictive. The invention is not limited to the disclosed embodiments. From reading the present disclosure, other modifications will be apparent to a person skilled in the art. Such modifications may involve other features, which are already known in the art and may be used instead of or in addition to features already described herein. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality.