Mobile defibrillator

Abstract

To provide a method for performing CPR using a mobile defibrillator (AED) unit.SOLUTION: The method includes: detecting, via an application on a user device 101, a connection of a mobile AED unit 100 to the user device; detecting, via the application, that pads 106a-b have been attached to a subject, the pads comprising at least one accelerometer; recording, via the application, EKG measurements of the subject made by the pads; receiving accelerometer data from the at least one accelerometer; analyzing the accelerometer data to determine a breathing pattern of the subject; and based on the determined breathing pattern, initiating a CPR protocol.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] Priority claims This application claims priority to U.S. Patent Application No. 16 / 938,275, filed July 24, 2020, which is incorporated by reference in its entirety. [Background technology]

[0002] Sudden cardiac arrest (e.g., heart failure) can involve the sudden loss of heart function, breathing, and consciousness. Often, electrical disturbances in the heart can result in a condition that interferes with the heart's pumping action, which can cause blood flow within the body to stop. In the United States alone, more than 300,000 people die from cardiac arrest outside of a hospital each year. Summary of the Invention [Means for solving the problem]

[0003] According to one aspect of the present disclosure, a mobile defibrillator system for use with a subject may include a device capable of executing an application and a mobile defibrillator (AED) unit configured to connect to the device, the mobile AED unit including a plurality of pads. The device may be configured to detect, via the application, when the mobile AED unit is connected to the device, analyze health data related to the subject, the health data being stored on the application, determine whether a plurality of pads have been attached to the subject, determine a shock pattern to be administered to the subject based on the health data, and administer the shock pattern to the subject. In some embodiments, the determined shock pattern may include a plurality of shocks. Each shock may include a duration and an energy level. The shock pattern may further include a time between the determined shocks.

[0004] In some embodiments, the health data may include at least one of data associated with pulse frequency, pulse variability, cardiac rhythm, EKG complex composition, ST elevation, deficit, cardiac ischemia, ventricular tachycardia, or ventricular fibrillation. In some embodiments, the device may be configured, via the application, to measure the current flowing between the pads and display on the device a recommendation to modify the distance between the pads based on the measured current. In some embodiments, determining a shock pattern to administer to the subject based on the health data may include analyzing the health data using a machine learning model trained on historical defibrillator performance data and the health data.

[0005] In some embodiments, the device can be configured to transmit performance and health data related to the performance of the AED to a server over a network. In some embodiments, the server can be configured to receive performance and health data from a plurality of user devices and a plurality of mobile AEDs and at least one of retrain or update machine learning models based on the received performance and health data. In some embodiments, the performance and health data can include at least one of data associated with pulse frequency, pulse variability, cardiac rhythm, EKG complex composition, ST elevation, deficit, cardiac ischemia, ventricular tachycardia, ventricular fibrillation, user interface, and user experience optimization.

[0006] According to another aspect of the present disclosure, a method for performing self-saving using a mobile defibrillator (AED) unit may include detecting, via an application on a user device, connection of the mobile AED unit to the user device, detecting, via the application, that a plurality of pads have been attached to a subject, recording, via the application, EKG measurements of the subject obtained by the pads, determining, via the application, an action to be taken with the mobile AED based on the recorded EKG measurements and preprogrammed risk factors associated with the subject, and performing, via the application and the user device, the action on the subject. In some embodiments, the action may include at least one of administering an electric shock pattern to the subject, continuing to record EKG measurements, and initiating a CPR protocol.

[0007] In some embodiments, the action may include administering an electric shock pattern to the subject, and the method may include determining an electric shock pattern to administer to the subject based on health data about the subject and pre-programmed risk factors. The electric shock pattern may include multiple electric shocks. Each electric shock may include a duration and an energy level. The electric shock pattern may further include a time between the determined electric shocks. In some embodiments, the pre-programmed risk factors are received as user input to the application via a user interface on the user device.

[0008] In some embodiments, the method can include transmitting, via the device, performance and health data associated with the AED performance over a network to a server. In some embodiments, the pad can include at least one accelerometer, and determining an action can include receiving accelerometer data from the at least one accelerometer, analyzing the accelerometer data to determine a breathing pattern of the subject, and initiating a CPR protocol based on the determined breathing pattern.

[0009] In some embodiments, the server can be configured to receive performance and health data from the plurality of user devices and the plurality of mobile AEDs, and at least one of retraining or updating the machine learning model for analyzing EKG measurements and the machine learning model for determining pad placement based on the received performance and health data. In some embodiments, determining that the action is to administer an electric shock pattern to the subject can include displaying a notification to the subject at a predetermined frequency by the device via an application in response to detecting that pads have been attached to the subject; determining that the subject has not responded to at least one message within a period of time; and determining that the subject has not responded in response to determining that the subject has not responded that the action is to administer an electric shock pattern to the subject. Each message can indicate a period of time for response.

[0010] According to another aspect of the present disclosure, a method for performing CPR using a mobile defibrillator (AED) unit may include detecting, via an application on a user device, connection of the mobile AED unit to the user device, detecting, via the application, that a plurality of pads have been attached to a subject, the pads including at least one accelerometer, recording, via the application, EKG measurements of the subject obtained by the pads, receiving accelerometer data from the at least one accelerometer, analyzing the accelerometer data to determine a breathing pattern of the subject, and initiating a CPR protocol based on the determined breathing pattern. In some embodiments, initiating the CPR protocol may include displaying, on the device, instructions to a user for providing CPR to the subject.

[0011] In some embodiments, the received accelerometer data can be first accelerometer data, and the method can further include receiving second accelerometer data from the at least one accelerometer while CPR is being administered to the subject, analyzing the second accelerometer data to determine a frequency and force of compressions, and displaying, on the user device, a recommendation to modify at least one of the frequency and force of compressions. In some embodiments, the method can include determining a shock pattern to administer to the subject based on the health data and the EKG measurements, and administering the shock pattern to the subject in cooperation with the CPR protocol.

[0012] In the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements throughout the respective views, and together with the following detailed description, which is incorporated into and forms a part of the specification, serve to further illustrate embodiments of the concepts comprising the claimed invention and to explain various principles and advantages of these embodiments. [Brief explanation of the drawings]

[0013] [Figure 1]FIG. 1 is a diagram of an exemplary mobile automated external defibrillator (AED) system according to some embodiments of the present disclosure.

[0014] [Figure 2] FIG. 1 is an exemplary circuit schematic diagram of a mobile AED according to some embodiments of the present disclosure.

[0015] [Figure 3] FIG. 1 is a block diagram of a system of a mobile AED device according to some embodiments of the present disclosure.

[0016] [Figure 4] FIG. 1 is a diagram of an exemplary process for using a mobile AED according to some embodiments of the present disclosure.

[0017] [Figure 5] FIG. 1 is a diagram of an exemplary process for assisting CPR with a mobile AED according to some embodiments of the present disclosure.

[0018] [Figure 6] FIG. 1 is a diagram of an exemplary process for self-saving using a mobile AED according to some embodiments of the present disclosure.

[0019] [Figure 7] FIG. 1 is a diagram of an example process for providing updates to multiple mobile AEDs according to some embodiments of the present disclosure.

[0020] [Figure 8] FIG. 4 is a diagram of an exemplary computing device that can be used within the systems of FIGS. 1 and / or 3, in accordance with some embodiments of the present disclosure.

[0021] [Figure 9] 4 is an exemplary server device that can be used in the system of FIG. 3 according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0022] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present disclosure.

[0023] Structural components of the security system are represented in the drawings by conventional symbols where appropriate, and only certain details relevant to understanding the embodiments of the present disclosure are shown so as not to obscure the disclosure with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0024] The availability of public defibrillators or automated external defibrillators (AEDs) can have a significant impact on the survival of a person experiencing cardiac arrest. Cardiac arrest patients who receive an electric shock from a publicly available AED have a much higher survival rate. Mortality can increase by 10% for every minute without cardiopulmonary resuscitation (CPR). However, AEDs are still not widely accessible to the public in a viable manner. Other challenges to widespread AED accessibility are that many members of the "public" do not have the training necessary to resuscitate and / or treat cardiac arrest patients, the knowledge threshold for initiating CPR is excessively high, and current AED solutions can be expensive, bulky, and can result in an unfamiliar user experience.

[0025] Accordingly, embodiments of the present disclosure relate to a mobile AED that can be controlled via an application on a device (e.g., a smartphone, tablet, laptop, watch, car entertainment system). In some embodiments, the mobile AED of the present disclosure can be carried by a user (e.g., in a pocket or purse) and connected to a mobile device by plugging into a cord connector, such as a USB-C connection. In some embodiments, some of the AED's operational logic can be offloaded to the mobile device, and a user interface that allows the user to control the AED can be provided via an application. This can lower the cost and threshold for use of such devices. The mobile AEDs described herein can utilize the existing battery, operating system (e.g., iOS, Android, etc.), speaker, voice assistant, video, GPS, WiFi, and / or mobile network connectivity of the device to which the AED is connected. In some embodiments, the mobile AED can also include an additional port to facilitate connection to a power bank or other external power source for charging and / or power.

[0026] The mobile AED of the present disclosure may be smaller and more widely available than any previous attempt. It may be used by anyone with access to a device with a microphone, speaker, data storage, and power source. The pads / electrodes used in conjunction with the mobile AED may include an accelerometer, and the defibrillator unit may include an electric shock circuit. This may make the mobile AED more portable and versatile. The mobile AED and application / device system may be configured to analyze whether a subject has a cardiac rhythm requiring defibrillation, automatically call for help (e.g., locally using a speaker / alarm or to emergency personnel via the telephone network), guide local responders in CPR and resuscitation by showing what to do on the device's screen and providing instructions via the speaker, find other nearby mobile AEDs, generate a voltage strong enough for an effective electric shock, generate repeated shocks, and compile all data in the process, using the data to operate algorithms that can continuously learn new AED behaviors and improve the device.

[0027] FIG. 1 illustrates an exemplary mobile AED 100 according to some embodiments of the present disclosure. The mobile AED 100 may include a defibrillator unit 102 removably connected via a connection 103 to a device 101. The defibrillator unit 102 may include circuitry configured to generate specific pulses or shocks to be administered to a patient to treat a cardiac arrest patient (see FIG. 2). In this illustration of the mobile AED 100, the device 101 is a smartphone, but it should be noted that this is not a limitation. The device 101 may be a tablet, laptop, computer, watch, or other device with an operating system capable of running applications, such as an automobile entertainment system. In some embodiments, the connection 103 may include a USB-C connection or other similar connection. When the device 101 and the defibrillator unit 102 are connected, the connection 103 may allow the defibrillator unit 102 to be controlled via a user interface and applications on the device 101. In some embodiments, the defibrillator unit 102 may optionally include an additional connection port to a power bank 104 (e.g., a portable charger, a wall outlet, etc.), which may be a USB-C port but may be different from the port for connection 103.

[0028] The defibrillator unit 102 may include an additional port for connection to wires 105, which may serve as a medium through which shocks determined and / or generated by circuitry within the defibrillator 102 may be transferred to the pads 106a-b. The pads 106a-b may be any standard defibrillator pads known in the art and may be configured to adhere to the patient's body and act as electrodes for delivering current from the defibrillator unit 102 into the patient's body. In some embodiments, the pads 106a-b may also include an accelerometer. In some embodiments, when the defibrillator unit 102 is connected to or plugged into the device 101, the user may connect to a video assistant specialist 107. In some embodiments, a team of specialists may be on call and communicate with the device user. For example, if a person experiences sudden cardiac arrest, a nearby person can connect the defibrillator unit 102 to the device 101, navigate to the application (or the application can automatically open upon connection), and select an option to quickly enter a video session with a professional who can assist the person in administering a shock and / or CPR to the patient. In some embodiments, the person can also connect to emergency services (e.g., call 911) via the application on the device 101. In some embodiments, the application on the device 101 can be configured to be remotely controlled by a paramedic or mobile AED professional. This can allow the paramedic to substantially control and administer an electric shock to a subject connected to the defibrillator unit 102, as the defibrillator unit 102 is controlled by the application on the device 101. In some embodiments, the defibrillator unit 102 can be configured to receive power from a 220V power source or socket, or from a 12V socket in a vehicle.

[0029] In some embodiments, an application on device 101 may also be configured to receive data from an external device connected to user device 101, such as a smartwatch or other similar device monitoring the subject. For example, a person's smartwatch may continuously monitor the person's heart rate and transmit this information to user device 101. Application 304 may be configured to monitor and analyze the subject's heart rate and potentially identify and / or detect dangerous rhythms (e.g., rapid ventricular tachycardia, ventricular fibrillation, or other rhythm indicators that the neural network is trained to detect). In response to detecting a dangerous rhythm, the application may be configured to notify the subject via device 101, connect the subject's mobile AED and pads, and potentially instruct the subject to initiate a self-rescue protocol.

[0030] FIG. 2 is an exemplary circuit schematic 200 of a mobile AED according to some embodiments of the present disclosure. Circuit 200 can be included within defibrillator unit 102 of FIG. 1. In some embodiments, circuit 200 can include charger 201, switches 202 and 203, inductor 204, resistor 205, through resistor 206, and capacitor 207. In some embodiments, through resistor 206 can represent the resistance within a person's body that exists between pads 106a and 106b while the pads are connected. When switches 202 and 203 are in the left position (shown in FIG. 2), charger 201 can charge capacitor 207. In some embodiments, charger 201 can represent the battery of a connected device (e.g., device 101 of FIG. 1), an external power bank (e.g., power bank 104 of FIG. 1), or a combination of both. Switches 202 and 203 can be controlled via logic within device 101 and via applications that a user can navigate on device 101. For example, the application can determine the time at which a shock (e.g., a pulse of current / energy) should be administered to the patient, and to administer the shock, switches 202 and 203 can be moved to the right position (not shown in FIG. 2 ), thereby allowing current to flow from capacitor 207 through the patient, inductor 204, and resistor 205. As the current flows through the patient's heart, it can serve to resuscitate the subject until paramedics or other emergency response teams can stabilize the subject. In some embodiments, circuit 200 can be configured to deliver pulses of up to 200 J repeatedly for up to one hour.

[0031] 3 is a block diagram of a system 300 of mobile AED devices according to some embodiments of the present disclosure. In some embodiments, the system 300 may include multiple user devices 302a-n (collectively, user devices 302) communicatively coupled to a server device 310 via a network 308. While the system 300 includes two user devices 302a-n for illustrative purposes, it should be noted that any number of user devices may be included in a system of the present disclosure.

[0032] In some embodiments, network 308 may include one or more wide area networks (WANs), metropolitan area networks (MANs), local area networks (LANs), personal area networks (PANs), or any combination of these networks. Network 308 may include a combination of one or more types of networks, such as the Internet, intranet, Ethernet, twisted pair, coaxial cable, fiber optic, cellular, satellite, IEEE 801.11, terrestrial, and / or other types of wired or wireless networks. Network 308 may also use standard communication technologies and / or protocols.

[0033] In some embodiments, the user device 302 can be similar to or the same as the device 101 of FIG. 1 . For example, the user device 302 can include a smartphone, tablet, laptop, watch, automobile entertainment system, or a combination of similar types of devices capable of running software applications and utilizing an operating system. The user device 302 can include one or more computing devices capable of receiving user input, transmitting and / or receiving data over a network 308, or communicating with a server device 310. In some embodiments, the user device 302 can include a traditional computer system such as a desktop or laptop computer. Alternatively, the user device 302 can include a device with computer functionality, such as a personal digital assistant (PDA) or other suitable device. Additionally, each user device 302 can include a specially installed application 304 for use in conjunction with a connected mobile AED 306. The application 304 may include software instructions that may be stored on a non-transitory computer-readable medium that, when executed by a processor (e.g., a processor within the user device 302), may perform various processes related to administering a shock as an AED and reading an EKG in cooperation with the mobile AED 306. Note that further details regarding AED processing are described with respect to FIGS.

[0034] The server device 310 may include any combination of one or more of a web server, a mainframe computer, a general-purpose computer, a personal computer, or other types of computing devices. The server device 310 may represent a distributed server that is remotely located and communicates through a communications network or through a dedicated network such as a local area network (LAN). The server device 310 may also include one or more back-end servers for performing one or more aspects of the present disclosure. In some embodiments, the server device 108 may be the same as or similar to the server device 700 described below in connection with FIG. 7.

[0035] 3 , the server device 310 can include an AED improvement module 312, an update module 314, and an AED tracking module 316. Additionally, the server device 310 can be communicatively coupled to a database 318. In some embodiments, the AED improvement module 312 can include one or more models / algorithms trained via machine learning that can be used to continuously improve AED and / or CPR performance over time. In some embodiments, the AED improvement module 312 can be configured to continuously receive performance data from the user device 302 and retrain or update the models to reflect the newly received performance data. In some embodiments, the AED improvement module 312 can also have access to Emergency Health Records and other external databases to obtain additional training data. In some embodiments, the AED improvement module 312 can be configured to analyze, retrain, and / or update various machine learning models related to AED performance, such as models that determine the length and level of the initial pulse, pad placement, body part detection, the frequency at which to deliver additional pulses, the amount of energy in each pulse, and various other decisions related to electrocardiogram (EKG) readings. This will be explained in more detail with reference to FIGS.

[0036] In some embodiments, the update module 314 can be configured to package or incorporate the updated / retrained model from the AED improvement module 312 into a software update and deliver the update to the user device 302. In some embodiments, the update can be received by the user device 302 via a download from an application store. Additionally, the AED tracking module 316 can be configured to track the location of each mobile AED 306. In some embodiments, the AED tracking module 316 can utilize GPS coordinates obtained from the user device 302. In some embodiments, the AED tracking module 316 can enable a user to search for nearby mobile AEDs 306 via an application 304 on the user device 302.

[0037] The various system components, such as modules 312-316 and 304a-n, may be implemented using hardware and / or software configured to cooperate therewith to perform and execute processes, steps or other functions.

[0038] 4 is an exemplary process 400 for using a mobile AED according to some embodiments of the present disclosure. In some embodiments, process 400 can be performed by a user device (e.g., user device 302 and / or user device 101). In some embodiments, execution of process 400 can be assisted by a user interacting with the user device. For example, in response to a person experiencing sudden cardiac arrest, a bystander, friend, or other individual can execute process 400 using a mobile AED of the present disclosure and an application (e.g., application 304) on the user device. In block 401, the user device 302 can detect an AED connection (e.g., via application 304). For example, a user can locate a mobile AED (e.g., defibrillator unit 102) and connect the defibrillator unit 102 to the user device, such as by plugging in a connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via application 304. In block 402, the user device 302 can open the application 304. In some embodiments, the application 304 can be opened automatically upon detection of a defibrillator connection, and in some embodiments, the application can be opened manually by a user.

[0039] In block 403, the application 304 can analyze data associated with a subject (e.g., a person who recently suffered a cardiac arrest). For example, the application 304 can store demographic and health information associated with the subject, pre-enabling access for the subject to enter self-descriptive information. The application 304 can store various types of information, such as height, weight, age, blood pressure, previous EKG assessments, medical history, etc. In some embodiments, the application 304 can be configured to utilize machine learning algorithms to analyze the subject information and make various decisions related to the remaining steps for administering AED treatment. In some embodiments, the analysis can be performed external to the user device 302; for example, the subject data can be transmitted and processed by a server (e.g., server 310), and the results of the processing can be transmitted to the user device 302 to affect treatment.

[0040] In block 404, the application 304 can detect pad placement. In some embodiments, the application 304 can be configured to detect whether a human body is connected between two pads based on electrical measurements (e.g., current) from the pads 106a-b. In some embodiments, detecting pad placement can include the application 304 detecting an amount of current flowing through the subject and between the pads (e.g., pads 106a-b) when the pads are placed on the subject's body (e.g., under the subject's right collarbone and under the subject's left armpit). Based on the strength of the detected current, the application 304 can determine whether the pads are too far apart or too close to each other. For example, the application 304 can utilize a threshold current range and compare the detected current to the threshold. If the detected current is above or below the threshold, the application 304 can display a warning to the user on the device recommending moving the pads closer or farther apart.

[0041] In block 405, the application 304 can be configured to determine a shock pattern to administer to the subject. In some embodiments, determining the shock pattern can include the application 304 utilizing a machine learning model to analyze data associated with the subject (e.g., height, weight, pad placement, EKG measurements, etc.) and output a shock pattern for resuscitating the subject. In some embodiments, the application 304 can acquire and analyze data via connected pads (e.g., operating as an EKG machine) before determining the shock pattern and use the acquired data to determine the shock pattern. For example, the machine learning model can be trained to determine the shock pattern based on data such as pulse rate (both frequency and variability), all types of cardiac rhythm, EKG complex composition, ST elevation (e.g., vertical distance within the EKG tracing and baseline), deficits, and signs of cardiac ischemia, ventricular tachycardia, and ventricular fibrillation. The application 304 can also be configured to detect that certain breathing patterns occurring in association with ventricular premature contractions can be triggering events. In some embodiments, the machine learning model may include a neural network with multiple nodes trained to map the types of health data described above to various factors in shock patterns (e.g., duration, timing, and energy level). In some embodiments, application 304 may be configured to estimate the subject's body fat percentage based on electrical measurements received from pads 106a-b, which may be used in determining the electrical shock pattern. In some embodiments, the machine learning model may also be configured to predict whether the subject will achieve "return of spontaneous circulation (ROCS)," which may include the resumption of sustained perfused cardiac activity. This may be predicted by analyzing respiration, movement, pulse, and blood pressure.

[0042] In some embodiments, the shock pattern can include the duration and level (e.g., energy level in joules) of multiple energy pulses. In some embodiments, an initial pulse to a subject experiencing cardiac arrest can be important for resuscitation. In block 406, the application 304 can cause the defibrillator unit 102 to deliver the determined shock pattern to the subject. Delivering the shock pattern can include utilizing a power source in the user device 302 to power circuitry (e.g., circuit 200) within the defibrillator unit 102. A possible advantage of utilizing power circuitry within a mobile device is that a less expensive device can be provided, ultimately making it more accessible to a larger number of people and increasing its widespread use. In some embodiments, the application 304 can be configured to warn nearby people before the shock pattern is delivered. For example, while the shock is being delivered, the application 304 can utilize the device's speaker and user interface to sound and display a warning to stay away. This can prevent the current from shocking and harming others. In some embodiments, after the shock pattern is complete, the application 304 may display and sound another message indicating the alarm is cleared.

[0043] In some embodiments, before determining the shock pattern in block 406, the mobile AED can be configured to operate as an EKG for a period of time. An application can be configured to receive the data and EKG measurements and make various decisions related to the shock pattern based on these measurements. In some embodiments, upon completion of any administered shock pattern, all data / information associated with the process can be sent from the user device 302 to the server 310, specifically to the AED improvement module 312. The AED improvement module 312 can use the received information to update and / or retrain any machine learning models related to determining shock patterns and pad placement based on both demographic and health data and EKG measurements. In some embodiments, a large number of mobile AEDs are utilized, providing a large and rich data set on which algorithms and models related to AED performance can be continuously updated. Due to the nature of the operation of the present disclosure (utilizing an application interface in a standard operating system to administer the AED), this can allow for continuous updates and improvements to AED performance.

[0044] In some embodiments, the process 400 can be performed in accordance with a video assistant and / or a voice assistant. For example, the application 304 can be configured to utilize any voice assistant functionality on the device (e.g., Alexa, Google Assistant, Siri, an in-vehicle voice system, etc.). For example, if a person opens the app but does not know how to administer an AED to a patient, the person can communicate with the application 304 via a voice assistant to request help. In some embodiments, the application can connect to an expert via video and activate the camera on the mobile device 302. In some embodiments, a team of experts can be assembled to handle the inflow of video connections. Each expert can be equipped with knowledge of how to operate the mobile AED 306, thereby providing fast, effective assistance and reliable information in an emergency. This can be more beneficial than being able to connect to a doctor or similar individual because there are no availability issues. In some embodiments, the application 304 can also enable the user to quickly connect to law enforcement and / or emergency personnel. In some embodiments, in response to notifying law enforcement or emergency personnel through application 304, GPS and medical data associated with the subject can be rapidly forwarded to law enforcement via application 304. This can provide valuable information to emergency personnel upfront, potentially saving valuable time when emergency personnel arrive on scene.

[0045] In some embodiments, the application 304 can also assist in the performance of CPR in accordance with the delivery of shock patterns. In some embodiments, the application 304 can be configured to detect the strength of compressions an individual is applying to the subject's chest cavity by analyzing the force on the pads 106a-b. The application 304 can provide instructions to the user, such as "compress harder" or "compress less." Further details regarding CPR are described in connection with FIG. 5.

[0046] 5 illustrates an exemplary process 500 for assisting CPR using a mobile AED according to some embodiments of the present disclosure. In some embodiments, process 500 can be performed by an application 304 on the device 101. Additionally, in some embodiments, process 500 can be performed in conjunction with (e.g., simultaneously or sequentially with) process 400. In some embodiments, execution of process 500 can be assisted by a user interacting with the user device. For example, in response to a person experiencing sudden cardiac arrest, a bystander, friend, or other individual can execute process 500 using a mobile AED of the present disclosure and an application (e.g., application 304) on the user device. In block 501, the user device 302 can detect an AED connection (e.g., via the application 304). For example, a user can locate a mobile AED (e.g., defibrillator unit 102) and connect the defibrillator unit 102 to the user device, such as by plugging in a connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via the application 304. In block 502, the user device 302 may open the application 304. In some embodiments, the application 304 may open automatically upon detecting the connection of a defibrillator, and in some embodiments, the application may be opened manually by a user.

[0047] In block 503, the application 304 can detect pad placement. In some embodiments, the application 304 can be configured to detect whether a human body is connected between two pads based on electrical measurements (e.g., current) from the pads 106a-b. In some embodiments, detecting pad placement can include the application 304 detecting an amount of current flowing through the subject and between the pads (e.g., pads 106a-b) when the pads are placed on the subject's body (e.g., under the subject's right collarbone and under the subject's left armpit). Based on the strength of the detected current, the application 304 can determine whether the pads are too far apart or too close to each other. For example, the application 304 can utilize a threshold current range and compare the detected current to the threshold. If the detected current is above or below the threshold, the application 304 can display a warning to the user on the device recommending that the pads be moved closer or farther apart.

[0048] In block 504, with the pads 106a-b connected to the individual's body, the pads 106a-b can act as electrodes, and the application 304 can record EKG measurements of the person's cardiac activity. In some embodiments, recording EKG measurements can include sensing the electrical activity of the subject's heart while the pads are attached. The detected electrical activity can be transmitted to the application 304 for various analytical purposes. The application 304 can be configured to monitor and analyze the EKG measurements to detect irregularities / abnormalities or any disturbances or factors that may indicate a high likelihood of a heart attack or cardiac arrest. The analysis can be performed using machine learning models trained on a significant amount of patient data obtained from emergency health records and real-time data from other mobile AEDs 306 connected to the server device 310. In some embodiments, the application 304 can acquire and analyze data (e.g., operate as an EKG machine) via connected pads, such as pulse rate (both frequency and variability), all types of cardiac rhythms, EKG complex composition, ST elevation (e.g., vertical distance within the EKG trace and baseline), deficits, and signs of cardiac ischemia, ventricular tachycardia, and ventricular fibrillation.

[0049] In block 505, the application 304 may determine that CPR is needed to resuscitate the patient. In some embodiments, determining that CPR is needed may include detecting a cardiac rhythm, such as ventricular tachycardia and / or ventricular fibrillation, through recorded EKG measurements that may indicate a lack of blood circulation. In some embodiments, determining that CPR is needed may include detecting abnormal breathing. In some embodiments, the application 304 may be configured to receive accelerometer data from the pads 106a-b when the pads are placed on the subject. The application 304 may be configured to use the accelerometer data to map, analyze, and estimate breathing patterns. For example, the application 304 may use the accelerometer data to model chest movement and analyze breathing frequency; if the movement frequency differs significantly from approximately 10-20 breaths per minute, this may be considered an abnormal breathing pattern and may indicate that CPR is needed. In block 506, the application 304 may initiate a CPR protocol. In some embodiments, the CPR protocol can include video, instructions, or a connection to a video expert to guide the user in administering CPR to the subject. The instructions can be presented on the screen of the user device and / or via a spoken voice assistant on the device. In some embodiments, when process 500 is performed in conjunction with administering an electric shock pattern to the subject (e.g., as shown in FIG. 4 ), application 304 provides a warning immediately before and during the electric shock and then indicates to the user that it is safe to perform chest compressions. In some embodiments, application 304 can be configured to receive accelerometer data from pads 106a-b while CPR is being administered. Application 304 can be configured to analyze the accelerometer data to detect the rhythm in which cardiac compressions are being administered and can provide feedback to the user on both frequency and force.For example, cardiac compressions may be administered at too high or too low a frequency (e.g., below 100 Hz or above 120 Hz), or the cardiac compressions may not be forceful enough. In some embodiments, initiating a CPR protocol may also include prompt notification to law enforcement and / or emergency personnel.

[0050] FIG. 6 illustrates an exemplary process 600 for self-saving using a mobile AED according to some embodiments of the present disclosure. In some embodiments, process 600 can be performed by a person themselves and can be referred to as a “self-saving” operation. In some embodiments, the mobile AED of the present disclosure can be small, lightweight, and convenient enough for a person to easily carry in a purse, bag, or pocket as a potentially life-saving device. However, the mobile AED of the present disclosure can also be used in self-saving applications by a person who is in the beginning or very early stages of a cardiac condition. In contrast to process 400, which can be used to resuscitate a person experiencing cardiac failure or cardiac arrest who is in a state of incapacity to some degree in most cases, process 600 can be used by an individual themselves. For example, if a person begins to experience symptoms of potentially impending cardiac arrest (e.g., tingling, heart flutter, etc.), the person can use a device (e.g., device 302) to perform process 600 and potentially save themselves.

[0051] In response to noticing any disturbing sensations, the user may connect their mobile AED 306 to the device 302. In block 601, the user device 302 may detect an AED connection (e.g., via the application 304). For example, the user may locate the mobile AED (e.g., the defibrillator unit 102) and connect the defibrillator unit 102 to the user device, such as by plugging in a connection cable. The user device may detect, for example, via the application 304, that the defibrillator unit 102 has been connected. In block 602, the user device 302 may open the application 304. In some embodiments, the application 304 may open automatically in response to detecting a defibrillator connection, and in some embodiments, the application may be opened manually by the user.

[0052] In block 603, in response to an individual attaching pads (e.g., pads 106a-b) to themselves (e.g., to both pectoral muscles surrounding the heart), the application 304 can detect the placement of the pads. For example, the application 304 can be configured to detect whether a human body is connected between two pads based on electrical measurements from the pads 106a-b. In block 604, because the pads 106a-b are connected to the individual's body, the pads 106a-b can operate as electrodes, and the application 304 can record EKG measurements of the person's cardiac activity. In some embodiments, recording the EKG measurements can include sensing the electrical activity of the subject's heart while the pads are attached. The detected electrical activity can be transmitted to the application 304 for various analysis purposes. The application 304 can be configured to monitor and analyze the EKG measurements to detect irregularities / abnormalities or any disturbances or factors that may indicate a high likelihood of a heart attack or cardiac arrest. The analysis can be performed by machine learning models trained on a significant amount of patient data obtained from the emergency health record and real-time data from other mobile AEDs 306 connected to the server device 310. Thus, in block 605, the application 304 can determine a course of action based on the recorded EKG measurements and the resulting analysis, as well as pre-specified or pre-programmed risk factors associated with the patient. For example, the patient can present various information and risk factors within the application 304. For example, the application 304 can administer a specific shock pattern with a specific timing or continue to monitor the person's cardiac behavior. In some embodiments, administering a shock pattern can be triggered by detecting a shockable cardiac rhythm (e.g., ventricular tachycardia and / or ventricular fibrillation) from the EKG measurements. In some embodiments, detecting an abnormal breathing pattern (e.g., as described in connection with FIG. 5 ) can indicate that administering an electric shock is appropriate.In some embodiments, the application 304 can be configured to determine whether the patient is unconscious. For example, after the pads are connected to the subject, the application 304 can display a message to the subject and request that the subject respond in a certain manner (e.g., by pressing a button saying "Yes, I'm conscious" or by responding verbally). If the subject does not respond within a predetermined time frame, the application 304 can determine that the subject is unconscious and requires a shock. In block 606, the application 304 can execute the determined course of action.

[0053] 7 illustrates an exemplary process 700 for providing updates to multiple mobile AEDs according to some embodiments of the present disclosure. In some embodiments, the process 700 can be performed by the AED improvement module 312 and the AED update module 314 to continuously, and potentially in real time, maintain and update various machine learning algorithms associated with the AED performance of the mobile AED of the present disclosure. In block 701, the AED improvement module can be configured to receive AED data from multiple devices (e.g., multiple user devices 302). In some embodiments, the AED data can include EKG readings, patient health and demographic data, EKG readings, and other cardiac monitoring-related data recorded during processes performed on an individual (e.g., processes 400, 500, and 600). For example, the data can be compiled by the application 304 and transmitted over the network 308 to the server device 310 and ultimately to the AED improvement module 312. In some embodiments, the application 304 can be configured to anonymize the information before transmitting it to the server device 310. Additionally, in some embodiments, the AED improvement module 312 can also be configured to receive user interface data and user experience optimization data, which can be used to continuously improve application performance along with AED performance. The data received by the AED improvement module 312 can include data from multiple mobile AEDs and from actual CPR and AED use, which can include health and medical results and data (e.g., EKG measurements and other health data as described elsewhere herein), timing data (e.g., time to detection, time to AED ready, time to first shock, etc.), user interface data, user interaction data depending on the number of people and, if possible, who are present, and location data.

[0054] In block 702, the AED improvement module 312 can train or retrain models, actions, and dispositions. For example, the AED improvement module 312 can utilize data received from user devices 302 operating in conjunction with the mobile AED 306 to update or retrain various models maintained within the server 310 (note that models also operate within the application 304 on each user device 302). In some embodiments, the AED improvement module 312 can be configured to utilize certain subsets of data as training data and other subsets of data as test data. The AED improvement module 312 can use the data to update models for determining pad placement, determining shock patterns (e.g., duration and pulse level), analyzing EKG measurements, and determining actions / dispositions to take in response to monitoring individual EKG measurements during self-support procedures.

[0055] In block 703, the update module 314 compiles all updated models and algorithms into a software update and can provide the update for download directly to the user device 302 or via an application store. In some embodiments, blocks 701 and 702 can be performed continuously and in real time; in other words, the various models used for mobile defibrillation can be continuously updated and retrained. However, block 703 can be performed only at various stages or only after a certain level of performance increase is detected by the AED improvement module 312. In block 704, the software update can be delivered to the device 302 for execution on the application 304.

[0056] 8 is an exemplary server device 800 that may be used in the system of FIG. 3 , according to some embodiments of the present disclosure. The server device 800 may perform various functions and processes described herein. The server device 800 may be implemented on any electronic device that executes software applications derived from compiled instructions, including, but not limited to, a personal computer, a server, a smartphone, a media player, an electronic tablet, a game console, an email device, etc. In some implementations, the server device 800 may include one or more processors 802, volatile memory 804, non-volatile memory 806, and one or more peripherals 808. These components may be interconnected by one or more computer buses 810.

[0057] The processor 802 may employ any known processor technology, including, but not limited to, graphics processors and multi-core processors. Suitable processors for executing programs of instructions may include, by way of example, both general-purpose and special-purpose microprocessors, as well as the sole processor or one of multiple processors or cores of any type of computer. The bus 810 may be any known internal or external bus technology, including, but not limited to, ISA, EISA, PCI, PCI Express, NuBus, USB, Serial ATA, or FireWire. The volatile memory 804 may include, for example, SDRAM. The processor 802 may receive instructions and data from read-only memory or random-access memory, or both. The essential elements of a computer include a processor for executing instructions and one or more memories for storing instructions and data.

[0058] The non-volatile memory 806 may include, by way of example, semiconductor storage devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks, removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The non-volatile memory 806 may store various computer instructions, including operating system instructions 812, communication instructions 815, application instructions 816, and application data 817. The operating system instructions 812 may include instructions implementing an operating system (e.g., MacOS®, Windows®, Linux). The operating system may be multi-user, multi-processing, multi-tasking, multi-threaded, real-time, etc. The communication instructions 815 may include network communication instructions, e.g., software for implementing communication protocols such as TCP / IP, HTTP, Ethernet, telephony, etc. The application instructions 816 may include instructions for administering a shock pattern using the mobile AED, connecting to law enforcement, displaying instructions for administering a shock pattern using the mobile AED, and performing self-help actions in accordance with the systems and methods disclosed herein. For example, the application instructions 816 may include instructions for the components 110-112 described above in conjunction with FIG.

[0059] The peripherals 808 can be included in the server device 800 or can be operatively coupled to communicate with the server device 800. The peripherals 808 can include, for example, a network subsystem 818, an input controller 820, and a disk controller 822. The network subsystem 818 can include, for example, an Ethernet over a WiFi adapter. The input controller 820 can be any known input device technology, including, but not limited to, a keyboard (including a virtual keyboard), a mouse, a trackball, and a touch-sensitive pad or display. The disk controller 822 can include one or more mass storage devices for storing data files; such devices include magnetic, magneto-optical, and optical disks, such as internal hard disks and removable disks.

[0060] 9 is an exemplary computing device 900 that can be used in the systems of FIGS. 1 and / or 3 according to some embodiments of the present disclosure. In some embodiments, the device 900 can be a user device 101. The exemplary user device 900 can include a memory interface 902, one or more data processors, an image processor, a central processing unit 904 and / or a secure processing unit 905, and a peripheral subsystem 906. The memory interface 902, the one or more processors 904 and / or the secure processor 905, and / or the peripheral subsystem 906 can be separate components or can be integrated into one or more integrated circuits. The various components within the user device 900 can be coupled by one or more communication buses or signal lines.

[0061] Sensors, devices, and subsystems can be coupled to the peripheral subsystem 906 to facilitate multiple functions. For example, a motion sensor 910, a light sensor 912, and a proximity sensor 914 can be coupled to the peripheral subsystem 906 to facilitate orientation, lighting, and proximity functions. Other sensors 916 can also be connected to the peripheral subsystem 906, such as a global navigation satellite system (GNSS) (e.g., a GPS receiver), a temperature sensor, a biosensor, a magnetometer, or other sensing devices, to facilitate related functions.

[0062] A camera subsystem 920 and a light sensor 922, such as a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) light sensor, may be utilized to facilitate camera functions such as recording photographs and video clips. The camera subsystem 920 and the light sensor 922 may be used to collect images of a user that may be used, for example, during authentication of the user by performing facial recognition analysis.

[0063] Communication functions can be facilitated through one or more wired and / or wireless communication subsystems 924, which can include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. For example, Bluetooth (e.g., Bluetooth Low Energy (BTLE)) and / or WiFi communications described herein can be handled by the wireless communication subsystem 924. The particular design and implementation of the communication subsystem 924 can depend on the communication network over which the user device 900 is intended to operate. For example, the user device 900 can include a communication subsystem 924 designed to operate over a GSM network, a GPRS network, an EDGE network, a WiFi network or a WiMax network, and a Bluetooth™ network. For example, the wireless communication subsystem 924 can include a hosting protocol such that the device 900 can be configured to act as a base station and / or provide WiFi services to other wireless devices.

[0064] The audio subsystem 926 may be coupled to a speaker 928 and a microphone 930 to facilitate voice-enabled functions such as speaker recognition, voice playback, digital recording, and telephony functions. The audio subsystem 926 may be configured to facilitate processing of voice commands, voice printing, and voice authentication, for example.

[0065] The I / O subsystem 940 can include a touch-surface controller 942 and / or other input controllers 944. The touch-surface controller 942 can be coupled to a touch-surface 946. For example, the touch-surface 946 and the touch-screen controller 942 can detect contact and movement or cessation using any of a number of touch-sensitive technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that identify one or more points of contact with the touch-surface 946.

[0066] Other input controller 944 may be coupled to other input / control devices 948, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointer devices such as a stylus. One or more buttons (not shown) may include up / down buttons for adjusting the volume of speaker 928 and / or microphone 930.

[0067] In some implementations, pressing the button for a first duration can unlock the touchscreen 946, and pressing the button for a second duration longer than the first duration can power the user device 900 on or off. Pressing the button for a third duration can activate a voice control or voice command module, which allows a user to speak commands into the microphone 930 and have the device execute the spoken commands. A user can customize the functionality of one or more buttons. The touchscreen 946 can also be used to implement virtual or soft buttons and / or a keyboard, for example.

[0068] In some implementations, the user device 900 can present recorded audio and / or video files, such as MP3 files, AAC files, and MPEG files. In some implementations, the user device 900 can include the functionality of an MP3 player, such as an iPod™. Thus, the user device 900 can include a 36-pin connector and / or an 8-pin connector compatible with an iPod. Other input / output and control devices can also be used.

[0069] The memory interface 902 can be coupled to memory 950. The memory 950 can include high-speed random access memory and / or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and / or flash memory (e.g., NAND, NOR). The memory 950 can store an operating system 952, such as Darwin, RTXC, LINUX, UNIX, OS X, Windows, or an embedded operating system such as VxWorks.

[0070] Operating system 952 may include instructions for handling basic system services and for performing hardware-dependent tasks. In some implementations, operating system 952 may be a kernel (e.g., a UNIX kernel). In some implementations, operating system 952 may include instructions for performing voice authentication.

[0071] Memory 950 may further store communications instructions 954 to facilitate communications with one or more additional devices, one or more computers, and / or one or more servers. Memory 950 may include graphical user interface instructions 956 for facilitating graphical user interface processing, sensor processing instructions 958 for facilitating sensor-related processes and functions, telephony instructions 960 for facilitating telephony-related processes and functions, electronic messaging instructions 962 for facilitating electronic messaging-related processes and functions, web browsing instructions 964 for facilitating web browsing-related processes and functions, media processing instructions 966 for facilitating media processing-related functions and processes, GNSS / navigation instructions 968 for facilitating GNSS and navigation-related processes and instructions, and / or camera instructions 970 for facilitating camera-related processes and functions.

[0072] Memory 950 may store application (or "app") instructions and data 972, such as instructions for an app as described above in connection with Figures 1-9. Memory 950 may also store other software instructions 974 for various other software applications in place on device 900.

[0073] In the foregoing specification, particular embodiments have been described. However, those skilled in the art will recognize that various modifications and changes can be made without departing from the scope of the invention as set forth in the following claims. For example, the invention has been described and illustrated in the context of a school, but is not limited thereto. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present teachings.

[0074] Benefits, advantages, solutions to problems, and any elements that can cause any benefit, advantage, or solution to occur or become more pronounced should not be construed as critical, necessary, or essential features or elements of any or all claims. The present invention is defined solely by the appended claims, including any amendments made during the pendency of this application, and all equivalents of those claims as issued.

[0075] This Abstract of the Disclosure is provided to enable the reader to quickly determine the nature of the present technical disclosure. It is understood that this Abstract of the Disclosure is not intended to interpret or limit the scope or meaning of the claims. Additionally, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as reflected in the following claims, inventive subject matter lies in less than all features of a single disclosed embodiment. Accordingly, the following claims are incorporated into the Detailed Description, with each claim standing on its own as separately claimed subject matter.

[0076] It is to be understood that the disclosed subject matter is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The disclosed subject matter is capable of other embodiments and of being practiced and carried out in various ways. It is also to be understood that the nomenclature and terminology employed herein is for the purpose of description and should not be regarded as limiting. Accordingly, those skilled in the art will appreciate that the conception upon which the present disclosure is based may readily be utilized as a basis for the designing of other structures, methods and systems for carrying out some of the purposes of the disclosed subject matter. It is important, therefore, that the claims be regarded as including such equivalent constructions insofar as they do not depart from the spirit and scope of the disclosed subject matter.

[0077] While the disclosed subject matter has been described and illustrated in the above exemplary embodiments, it will be understood that the disclosure is made by way of example only and that numerous changes in the details of the implementation of the disclosed subject matter can be made without departing from the spirit and scope of the disclosed subject matter.

Claims

1. 1. A computing device comprising one or more processors and configured to operatively connect to and control a mobile defibrillator (AED) unit, the computing device comprising: Detecting the connection of the mobile AED unit; Detecting that one or more electrodes of the mobile AED unit are connected to a subject; receiving EKG measurements of the subject recorded by the electrodes; receiving measured respiratory data relating to chest movement due to breathing of the subject; analyzing the respiratory data to determine a breathing pattern of the subject; determining that the breathing pattern is an abnormal breathing pattern; Initiating a CPR protocol based on the determined abnormal breathing pattern. configured to analyzing the respiratory data to determine a breathing pattern of the subject; modeling the movement of the chest; Analyzing breathing frequency a computing device,

2. the received respiratory data is first respiratory data; the computing device, receiving second respiratory data while administering CPR to the subject; analyzing the second respiratory data to determine the frequency and force of compressions; displaying on the computing device a recommendation to modify at least one of the frequency and force of the compressions. The computing device of claim 1 , comprising:

3. determining whether the breathing frequency is above or below a predetermined breathing range; In response to said determining, a CPR protocol is initiated. The computing device of claim 1 , comprising:

4. The computing device of claim 3 , wherein the predetermined breathing range is 10 to 20 breaths per minute.

5. determining a shock pattern to be administered to the subject based on the determined breathing pattern and the EKG measurements; administering the electrical shock pattern to the subject in conjunction with the CPR protocol; The computing device of claim 1 , comprising:

6. issuing a warning before or during delivery of the shock pattern; Indicates that it is safe to perform chest compressions once the shock pattern is complete The computing device of claim 5 , comprising:

7. Analyzing the respiratory data to detect a rhythm in which cardiac massage is being performed; displaying feedback on the computing device related to at least one of the frequency and force of the cardiac massages; The computing device of claim 1 , comprising:

8. The computing device of claim 1, wherein initiating the CPR protocol includes displaying instructions to a user on the device for providing CPR to the subject.

9. The computing device of claim 1, wherein initiating the CPR protocol includes displaying at least one of a video or instructions.

10. The computing device of claim 1, wherein initiating the CPR protocol includes initiating a connection to a video professional.

11. The computing device of claim 1, further comprising notifying at least one of law enforcement or emergency personnel in response to initiating the CPR protocol.

Images