Mobile defibrillator
The mobile AED system addresses accessibility and usability issues by integrating with user devices for portable defibrillation and CPR guidance, enhancing emergency response effectiveness through continuous learning and cost reduction.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- DEFIBRIO AS
- Filing Date
- 2026-02-03
- Publication Date
- 2026-05-19
AI Technical Summary
Existing AEDs are not widely accessible, require specialized training, are expensive, and have a high knowledge threshold for use, limiting their effectiveness in emergencies.
A mobile AED system that integrates with a user's device, allowing for portable and versatile defibrillation using a smartphone or similar device, with an application that analyzes health data, determines shock patterns, and guides users through CPR, connected to a server for continuous learning and improvement.
Enhances accessibility and usability of defibrillation by reducing cost and training barriers, enabling effective self-rescue and CPR assistance, and continuously improving performance through machine learning.
Smart Images

Figure 2026082957000001_ABST
Abstract
Description
Technical Field
[0001] Claims of Priority This application claims the priority of U.S. Patent Application No. 16 / 938,275, filed on July 24, 2020, which is incorporated herein by reference in its entirety.
Background Art
[0002] Sudden cardiac arrest (e.g., heart failure) may be accompanied by a sudden loss of heart function, breathing, and consciousness. In many cases, an electrical disorder in the heart can result in a condition that interferes with the heart's pumping action, which can cause the blood flow in the body to stop. In the United States alone, more than 300,000 people die from out-of-hospital cardiac arrest every year.
Summary of the Invention
Means for Solving the Problems
[0003] According to one aspect of the present disclosure, a mobile defibrillator system for use with a subject can include a device capable of executing an application and a mobile automated external defibrillator (AED) unit configured to be connected to the device. The mobile AED unit can include a plurality of pads. The device can detect when the mobile AED unit is connected to the device via the application, analyze health data regarding the subject, the health data being stored on the application, determine whether the plurality of pads are attached to the subject, determine an electrical shock pattern to be administered to the subject based on the health data, and be configured to administer the electrical shock pattern to the subject. In some embodiments, the determined electrical shock pattern can include a plurality of electrical shocks. Each electrical shock can include a duration and an energy level. The electrical shock pattern can further include the time between the determined electrical shocks.
[0004] In some embodiments, health data may include at least one of the following: pulse frequency, pulse variability, heart rhythm, EKG group composition, ST elevation, depressorrhea, myocardial ischemia, ventricular tachycardia, or ventricular fibrillation. In some embodiments, the device may be configured, via an application, to measure the current flowing between the pads and display recommendations on the device to change the distance between the pads based on the measured current. In some embodiments, determining the electric shock pattern to be administered to the subject based on health data may involve analyzing the health data using a machine learning model trained on historical defibrillator performance data and health data.
[0005] In some embodiments, the device can be configured to transmit performance and health data relating to the AED's performance to a server over a network. In some embodiments, the server can be configured to receive performance and health data from multiple user devices and multiple mobile AEDs, and to retrain or update a machine learning model based on the received performance and health data. In some embodiments, the performance and health data may include at least one of the following: pulse frequency, pulse variability, heart rhythm, EKG group composition, ST elevation, depressor, myocardial ischemia, ventricular tachycardia, ventricular fibrillation, and data associated with user interface and user experience optimization.
[0006] According to another aspect of the present disclosure, a method for performing self-rescue using a mobile defibrillator (AED) unit may include detecting the connection of the mobile AED unit to the user device via an application on the user device; detecting via the application that multiple pads have been attached to a person; recording via the application an EKG measurement of the person obtained by the pads; determining an action to be taken using the mobile AED based on the recorded EKG measurement and pre-programmed risk factors associated with the person; and taking an action on the person via the application and the user device. In some embodiments, the action may include at least one of delivering an electric shock pattern to the person, continuing to record the EKG measurement, and initiating a CPR protocol.
[0007] In some embodiments, the action may include administering an electric shock pattern to a subject, and the method may include determining the electric shock pattern to administer to the subject based on health data and pre-programmed risk factors relating to the subject. The electric shock pattern may include multiple electric shocks. Each electric shock may include duration and energy level. The electric shock pattern may further include the time between the determined electric shocks. In some embodiments, the pre-programmed risk factors are those received as user input to the application via a user interface on a user device.
[0008] In some embodiments, the method may include transmitting performance and health data associated with AED performance to a server via a network through the device. In some embodiments, the pad may include at least one accelerometer, and determining an action may include receiving accelerometer data from at least one accelerometer, analyzing the accelerometer data to determine the subject's breathing pattern, 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 multiple user devices and multiple mobile AEDs, and to retrain or update at least one of a machine learning model for analyzing EKG measurements and a machine learning model for determining pad placement based on the received performance and health data. In some embodiments, determining that the action is to deliver an electric shock pattern to the subject may include the device displaying a notification to the subject via an application at a predetermined frequency in response to detecting that the 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 action is to deliver an electric shock pattern to the subject in response to determining that the subject has not responded. Each message may indicate a period of time for a 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, the connection of the mobile AED unit to the user device, detecting, via the application, that a plurality of pads have been attached to a person, the pads including at least one accelerometer, recording, via the application, the person's EKG measurement obtained by the pads, receiving accelerometer data from at least one accelerometer, analyzing the accelerometer data to determine the person's breathing pattern, and initiating a CPR protocol based on the determined breathing pattern. In some embodiments, initiating a CPR protocol may include displaying instructions on the device for the user to provide CPR to the person.
[0011] In some embodiments, the received accelerometer data may be first accelerometer data, and the method may further include receiving second accelerometer data from at least one accelerometer while CPR is being performed on the subject, analyzing the second accelerometer data to determine the frequency and force of compressions, and displaying a recommendation on the user device to change at least one of the frequency and force of compressions. In some embodiments, the method may include determining an electric shock pattern to be administered to the subject based on health data and EKG measurements, and administering the electric shock pattern to the subject in cooperation with a CPR protocol.
[0012] In the attached drawings, throughout each figure, the same reference numerals indicate identical or functionally similar elements and, together with the following detailed description, are incorporated into and form part of the specification, further illustrating embodiments of the concept including the claimed invention and illustrating the various principles and advantages of these embodiments. [Brief explanation of the drawing]
[0013] [Figure 1]A diagram of an exemplary mobile automated external defibrillator (AED) system according to some embodiments of the present disclosure.
[0014] [Figure 2] An exemplary circuit schematic diagram of a mobile AED according to some embodiments of the present disclosure.
[0015] [Figure 3] A block diagram of a system of a mobile AED device according to some embodiments of the present disclosure.
[0016] [Figure 4] A diagram of an exemplary process for using a mobile AED according to some embodiments of the present disclosure.
[0017] [Figure 5] A diagram of an exemplary process for assisting CPR using a mobile AED according to some embodiments of the present disclosure.
[0018] [Figure 6] A diagram of an exemplary process for self-rescue using a mobile AED according to some embodiments of the present disclosure.
[0019] [Figure 7] A diagram of an exemplary process for providing updates to multiple mobile AEDs according to some embodiments of the present disclosure.
[0020] [Figure 8] A diagram of an exemplary computing device that can be used within the system of FIG. 1 and / or FIG. 3 according to some embodiments of the present disclosure.
[0021] [Figure 9] An exemplary server device that can be used within the system of FIG. 3 according to some embodiments of the present disclosure.
Best Mode for Carrying Out the Invention
[0022] Those skilled in the art will understand that the elements in the drawings are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some of the elements in the drawings may be exaggerated relative to other elements to assist in improving the understanding of the embodiments of the present disclosure.
[0023] The structural components of the security system are represented by conventional symbols where appropriate in the drawings, and only show specific details relevant to the understanding of the embodiments of the present disclosure so as not to obscure the disclosure with details that would be readily apparent to those skilled in the art who benefit from the description herein.
[0024] The availability of a public defibrillator or an automated external defibrillator (AED) can have a significant impact on the survival of a person experiencing cardiac arrest. A cardiac arrest patient who receives an electrical shock from a publicly available AED has a much higher survival rate. If cardiopulmonary resuscitation (CPR) is not performed, the mortality rate may increase by 10% per minute. However, AEDs are still not widely and generally accessible in a practical manner. Other issues related to the widespread availability of AEDs are that many people in the "general" population have not received the training necessary to resuscitate and / or treat a cardiac arrest patient, the knowledge threshold for starting CPR is overly high, current AED solutions can be expensive and cumbersome, 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, or 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 wallet) and can be 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 operating 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 reduce the cost and threshold for using such a device. The mobile AED 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 may 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 this disclosure may be smaller and more widely available than any previous attempts. It can be used by any person with access to a device having a microphone, speaker, data storage and power supply. Pads / electrodes used in conjunction with the mobile AED may include an accelerometer, and the defibrillator unit may include an electric shock circuit. This makes it possible to create a mobile AED that is easily portable and more versatile. The mobile AED and application / device system may be able to analyze whether a person has a heart rhythm that requires defibrillation, automatically call for help (e.g., locally using a speaker / alarm or to paramedics via a telephone network), guide on-site helpers in CPR and resuscitation by showing what to do on the device's screen and giving instructions via the speaker, locate other mobile AEDs nearby, generate a voltage strong enough for an effective electric shock, generate repetitive shocks, compile all data during the process, and be configured to operate an algorithm that can use the data to continuously learn new AED behaviors and improve the device.
[0027] Figure 1 shows an exemplary mobile AED 100 according to several embodiments of the present disclosure. The mobile AED 100 may include a defibrillator unit 102 detachably connected to a device 101 via a connection 103. The defibrillator unit 102 may include a circuit configured to generate a specific pulse or shock to be delivered to a patient in order to treat a patient in cardiac arrest (see Figure 2). Note that in this figure of the mobile AED 100, the device 101 is a smartphone, but this is not limited to it. The device 101 may be a tablet, laptop, computer, watch, or other device having an operating system capable of running applications such as an in-car 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 the 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 wiring 105, which can function as a medium to transfer the shock determined and / or generated by the circuitry within the defibrillator 102 to pads 106a-b. Pads 106a-b can be any standard defibrillator pads known in the art and can be configured to adhere to the patient's body and act as electrodes to deliver current from the defibrillator unit 102 into the patient's body. In some embodiments, pads 106a-b may also include accelerometers. In some embodiments, when the defibrillator unit 102 is connected to or plugged into device 101, the user can connect to a video assistant specialist 107. In some embodiments, the specialist team can work on call and communicate with the user of the device. For example, if a person suddenly experiences cardiac arrest, a nearby person can connect the defibrillator unit 102 to device 101, navigate to an application (or the application can open automatically upon connection), and select the option to quickly enter into a video session with a specialist who can assist this person in delivering 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 device 101. In some embodiments, the application on device 101 can be configured to be remotely controlled by paramedics or mobile AED specialists. This allows paramedics to substantially control and deliver an electric shock to a person connected to the defibrillator unit 102, as the defibrillator unit 102 is controlled by the application on device 101. In some embodiments, the defibrillator unit 102 can be configured to receive power from a 220V power supply or socket, or from a 12V socket in a vehicle.
[0029] In some embodiments, the application on device 101 may also be configured to receive data from an external device connected to the user device 101, such as a smartwatch or other similar device that monitors the subject. For example, a person's smartwatch can continuously monitor the person's heart rate and transmit this information to the user device 101. The 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 trained to detect by a neural network). In response to the detection of a dangerous rhythm, the application may be configured to notify the subject via device 101 and instruct the subject to connect their mobile AED and pads and potentially initiate a self-rescue protocol.
[0030] Figure 2 is an exemplary schematic circuit diagram 200 of a mobile AED according to several embodiments of the present disclosure. The circuit 200 can be contained within the defibrillator unit 102 in Figure 1. In some embodiments, the circuit 200 can include a charger 201, switches 202 and 203, an inductor 204, a resistor 205, a pass-through resistor 206, and a capacitor 207. In some embodiments, the pass-through resistor 206 can represent the resistance in the person's body present between the pads 106a and 106b while those pads are connected. When switches 202 and 203 are in the left position (as shown in Figure 2), the charger 201 can charge the capacitor 207. In some embodiments, the charger 201 can represent the battery of the connected device (e.g., device 101 in Figure 1), an external power bank (e.g., power bank 104 in Figure 1), or a combination of both. Switches 202 and 203 can be controlled via logic within device 101 and via applications that the user can navigate on device 101. For example, the application can determine the duration for which a shock (e.g., a pulse of current / energy) should be delivered to the patient. To deliver the shock, switches 202 and 203 move to the rightward position (not shown in Figure 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, the circuit 200 can be configured to repeatedly deliver pulses of up to 200 J for up to 1 hour.
[0031] Figure 3 is a block diagram of a system 300 of a mobile AED device according to some embodiments of the present disclosure. In some embodiments, the system 300 may include a plurality of user devices 302a-n (collectively, user device 302) that are communicably coupled to a server device 310 via a network 308. The system 300 includes two user devices 302a-n for illustrative purposes, but it should be noted that any number of user devices may be included in the 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 thereof. Network 308 may include one or more combinations of network types, such as the Internet, intranet, Ethernet, twisted pair, coaxial cable, optical fiber, 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 may be similar to or identical to device 101 in Figure 1. For example, the user device 302 may include a smartphone, tablet, laptop, watch, automotive entertainment system, or a combination of similar types of devices capable of running software applications and utilizing an operating system. The user device 302 may include one or more computing devices capable of receiving user input, transmitting and / or receiving data over the network 308, or communicating with the server device 310. In some embodiments, the user device 302 may include a conventional computer system such as a desktop or laptop computer. Alternatively, the user device 302 may include a device with computer capabilities such as a personal digital assistant (PDA) or other suitable device. In addition, each user device 302 may include a specially installed application 304 for use in conjunction with the connected mobile AED 306. Application 304 may include software instructions that can be stored on a non-temporary computer-readable medium and, when executed by a processor (e.g., a processor in user device 302), can perform various processes related to delivering a shock as an AED and reading the EKG in cooperation with the mobile AED 306. Note that further details regarding AED processing will be explained with reference to Figures 4 to 7.
[0034] The server device 310 may include one or any combination 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 located remotely and communicates through a communication network or through a dedicated network such as a local area network (LAN). The server device 310 may also include one or more backend servers for performing one or more embodiments of the present disclosure. In some embodiments, the server device 108 may be the same as or similar to the server device 700 described later in relation to Figure 7.
[0035] As shown in Figure 3, the server device 310 may include an AED improvement module 312, an update module 314, and an AED tracking module 316. In addition, the server device 310 may be communicatively coupled to a database 318. In some embodiments, the AED improvement module 312 may include one or more models / algorithms trained via machine learning that can be used to continuously improve the performance of the AED and / or CPR over time. In some embodiments, the AED improvement module 312 may be configured to continuously receive performance data from the user device 302 and to retrain or update the model to reflect the newly received performance data. In some embodiments, the AED improvement module 312 may also have access to Emergency Health Records and other external databases to acquire additional training data. In some embodiments, the AED improvement module 312 may 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 of providing 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 by referring to Figures 4 to 7.
[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, make it a software update, and deliver this update to the user device 302. In some embodiments, the update can be received by the user device 302 via download from an application store. In addition, 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 the user to search for nearby mobile AEDs 306 via an application 304 on the user device 302.
[0037] Various system components such as modules 312-316 and 304a-n can be implemented using hardware and / or software configured to perform and execute processes, steps, or other functions in cooperation with them.
[0038] Figure 4 shows 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, the execution of process 400 can be assisted by a user interacting with the user device. For example, in response to a person suddenly experiencing cardiac arrest, a person nearby, a friend, or another individual can perform process 400 using the mobile AED of the present disclosure and an application on the user device (e.g., application 304). In block 401, user device 302 can detect the AED connection (e.g., via application 304). For example, the user can connect the defibrillator unit 102 to the user device by locating the mobile AED (e.g., defibrillator unit 102) and plugging in the connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via application 304. In block 402, user device 302 can open application 304. In some embodiments, application 304 can be opened automatically upon detection of a defibrillator connection, and in some embodiments, the application can be opened manually by the user.
[0039] In block 403, application 304 can analyze data associated with a subject (e.g., a person who has recently experienced cardiac arrest). For example, application 304 can store demographic and health information associated with a subject by pre-enabling access for the subject to input self-descriptive information. Application 304 can store various types of information such as height, weight, age, blood pressure, previous EKG assessments, and medical history. In some embodiments, application 304 can be configured to utilize machine learning algorithms to analyze subject information and make various decisions related to the remaining steps for administering AED treatment. In some embodiments, the analysis can be performed outside of the user device 302; for example, 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 influence the treatment.
[0040] In block 404, application 304 can detect pad placement. In some embodiments, application 304 can be configured to detect whether a human body is connected between two pads based on electrical measurements (e.g., current) from pads 106a-b. In some embodiments, detecting pad placement may include application 304 being able to detect the amount of current flowing through the subject between the pads when the pads (e.g., pads 106a-b) are placed on the subject's body (e.g., under the subject's right clavicle and under the subject's left armpit). Based on the intensity of the detected current, application 304 can determine whether the pads are too far apart or too close to each other. For example, application 304 can utilize a threshold current range and compare the detected current to a threshold. If the detected current is above or below the threshold, application 304 can display a warning on the device to the user recommending that the pads be moved closer together or further apart.
[0041] In block 405, application 304 can be configured to determine a shock pattern to be administered to a subject. In some embodiments, determining a shock pattern may involve application 304 using a machine learning model to analyze data associated with the subject (e.g., height, weight, pad placement, EKG measurements, etc.) and outputting a shock pattern for resuscitation. In some embodiments, application 304 may acquire and analyze data via connected pads (e.g., acting as an EKG machine) before determining a shock pattern, and then use the acquired data to determine the shock pattern. For example, a machine learning model can be trained to determine a shock pattern based on data such as pulse rate (both frequency and variability), all types of heart rhythms, EKG group composition, ST elevation (e.g., vertical distance within EKG trace and baseline), deficiencies, and signs of myocardial ischemia, ventricular tachycardia, and ventricular fibrillation. Application 304 may also be configured to detect that certain respiratory patterns occurring in association with ventricular premature contractions may be trigger events. In some embodiments, the machine learning model may include a neural network having multiple nodes trained to map the health data of the type described above to various factors in the shock pattern (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, and this body fat percentage 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 perfusion cardiac activity. This can be predicted by analyzing respiration, movement, pulse, and blood pressure.
[0042] In some embodiments, the shock pattern may include the duration and level of multiple energy pulses (e.g., energy levels in joules). In some embodiments, the initial pulse for a person experiencing cardiac arrest may be critical for resuscitation. In block 406, application 304 can cause the defibrillator unit 102 to deliver a determined shock pattern to the person. Delivering the shock pattern may involve using the power supply of the user device 302 to power a circuit (e.g., circuit 200) within the defibrillator unit 102. A possible advantage of using the power circuit within a mobile device is that it can provide a less expensive device, which will ultimately make it more accessible to more people and increase its adoption rate. In some embodiments, application 304 may be configured to warn nearby people before the electric shock pattern is delivered. For example, while the electric shock is being delivered, application 304 may use the speaker and user interface of device 101 to sound and display a warning to move away from the person. This can prevent the current from shocking and harming other people. In some embodiments, after the electric shock pattern is completed, application 304 may display and sound another message indicating that the alarm has been cleared.
[0043] In some embodiments, the mobile AED can be configured to operate as an EKG for a period of time before determining the shock pattern in block 406. The application can be configured to receive data and EKG measurements and make various decisions related to the shock pattern based on these measurements. In some embodiments, upon completion of any delivered shock pattern, all data / information associated with the process can be transmitted from the user device 302 to the server 310, in particular 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 for 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, thereby providing a large and rich dataset, which allows for continuous updating of algorithms and models related to AED performance on this dataset. Due to the nature of operation of this disclosure (utilizing an application interface in a standard operating system to administer the AED), this allows for continuous updating and improvement of AED performance.
[0044] In some embodiments, process 400 can be performed in accordance with a video assistant and / or voice assistant. For example, application 304 can be configured to utilize any voice assistant function on the device (e.g., Alexa, Google Assistant, Siri, in-vehicle voice system, etc.). For example, if a person opens the app but does not know how to administer the AED to a patient, the person can communicate with application 304 via the voice assistant and ask for help. In some embodiments, the application can connect to a professional via video and activate the camera on the mobile device 302. In some embodiments, a team of professionals capable of handling the inflow of video connections can be assembled. Each professional can have knowledge of how to operate the mobile AED 306, thereby providing quick and effective assistance and reliable information in an emergency. This may be more beneficial than being able to connect to a doctor or similar person because there are no availability issues. In some embodiments, application 304 can also enable the user to quickly connect to law enforcement and / or paramedics. In some embodiments, GPS and medical data associated with a person can be rapidly transferred to law enforcement or paramedics via application 304, in response to notification to the law enforcement or paramedics through application 304. This provides paramedics with valuable information in advance, thereby potentially saving them valuable time when they arrive at the scene.
[0045] In some embodiments, application 304 can also assist in the performance of CPR in accordance with the application of shock patterns. In some embodiments, application 304 can be configured to detect the intensity of the compressions an individual is applying to the patient's chest cavity by analyzing the force applied to pads 106a-b. Application 304 can provide the user with instructions such as "compress harder" or "compress less." Further details regarding CPR are described in relation to Figure 5.
[0046] Figure 5 shows 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 application 304 on device 101. In addition, in some embodiments, process 500 can be performed in conjunction with (e.g., simultaneously or sequentially with) process 400. In some embodiments, the execution of process 500 can be assisted by a user interacting with the user device. For example, in response to a person suddenly experiencing cardiac arrest, a person nearby, a friend, or another individual can perform process 500 using the mobile AED and application on the user device (e.g., application 304) of the present disclosure. In block 501, the user device 302 can detect the AED connection (e.g., via application 304). For example, the user can connect the defibrillator unit 102 to the user device by locating the mobile AED (e.g., defibrillator unit 102) and plugging in the connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via application 304. In block 502, the user device 302 can open application 304. In some embodiments, application 304 can be opened automatically upon detection of defibrillator connection, and in some embodiments, the application can be opened manually by the user.
[0047] In block 503, application 304 can detect pad placement. In some embodiments, application 304 can be configured to detect whether a human body is connected between two pads based on electrical measurements (e.g., current) from pads 106a-b. In some embodiments, detecting pad placement may include application 304 being able to detect the amount of current flowing through the subject between the pads when the pads (e.g., pads 106a-b) are placed on the subject's body (e.g., under the subject's right clavicle and under the subject's left armpit). Based on the intensity of the detected current, application 304 can determine whether the pads are too far apart or too close together. For example, application 304 can utilize a threshold current range and compare the detected current to a threshold. If the detected current is above or below the threshold, application 304 can display a warning on the device to the user recommending that the pads be moved closer together or further apart.
[0048] In block 504, since pads 106a-b are connected to the individual's body, pads 106a-b can function as electrodes, and application 304 can record EKG measurements of the person's cardiac behavior. In some embodiments, recording EKG measurements may include detecting the electrical activity of the subject's heart while the pads are attached. The electrical activity may be detected and transmitted to application 304 for various analytical purposes. Application 304 may be configured to monitor and analyze EKG measurements and detect any irregularities / abnormalities or disturbances or factors that may suggest a high probability of a heart attack or cardiac arrest occurring. Analysis can be performed using a machine learning model trained on a substantial 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, application 304 can acquire and analyze data such as pulse rate (both frequency and variability), all types of heart rhythms, EKG group composition, ST elevation (e.g., vertical distance within EKG trace and baseline), deficiencies, and signs of myocardial ischemia, ventricular tachycardia, and ventricular fibrillation via connected pads (e.g., operating as an EKG machine).
[0049] In block 505, application 304 may determine that CPR is needed to resuscitate the patient. In some embodiments, determining that CPR is needed may include detecting a heart rhythm that may indicate a lack of blood circulation, such as ventricular tachycardia and / or ventricular fibrillation, from recorded EKG measurements. In some embodiments, determining that CPR is needed may include detecting abnormal breathing. In some embodiments, application 304 may be configured to receive accelerometer data from pads 106a-b when the pads are placed on the subject. Application 304 may be configured to map, analyze, and estimate breathing patterns using the accelerometer data. For example, application 304 may use the accelerometer data to model chest movement and analyze breathing frequency, and if the movement frequency differs significantly from approximately 10-20 breaths per minute, this may be considered an abnormal breathing pattern and may suggest that CPR is needed. In block 506, application 304 may initiate a CPR protocol. In some embodiments, the CPR protocol may include video, instructions, or a connection to a video expert to guide the user when administering CPR to a person. Instructions may be displayed on the user device screen and / or by an on-device voice assistant. In some embodiments, when process 500 is performed in conjunction with administering an electric shock pattern to a person (as shown, for example, in Figure 4), application 304 provides warnings 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 may be configured to receive accelerometer data from pads 106a-b while CPR is being performed. Application 304 may be configured to analyze the accelerometer data to detect the rhythm of the cardiac massage being performed and provide feedback to the user in terms of both frequency and force.For example, chest compressions may be performed at an excessively high or low frequency (e.g., below 100 Hz or above 120 Hz), or not with sufficient force. In some embodiments, initiating a CPR protocol may also include rapid notification to law enforcement and / or emergency medical personnel.
[0050] Figure 6 shows exemplary process 600 for self-rescue 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 may be referred to as a “self-rescue” action. In some embodiments, the mobile AED of the present disclosure may be small, lightweight, and convenient enough for a person to easily carry in a wallet, bag, or pocket as a potential life-saving device. However, the mobile AED of the present disclosure may also be used in a self-rescue application by a person at the onset or very early stage of any discomfort regarding their cardiac condition. In contrast to process 400, which can be used to resuscitate a person who is in a somewhat incapacitated state and experiencing heart failure or cardiac arrest, process 600 can be performed by an individual themselves. For example, if a person begins to feel signs of potentially approaching cardiac arrest (e.g., throbbing, cardiac flutter, etc.), the person can potentially save themselves by performing process 600 using the device (e.g., using device 302).
[0051] In response to any disturbing sensation, the user can connect their mobile AED 306 to device 302. In block 601, the user device 302 can detect the AED connection (for example, via application 304). For example, the user can connect the defibrillator unit 102 to the user device by locating the mobile AED (e.g., defibrillator unit 102) and plugging in the connection cable. The user device can detect that the defibrillator unit 102 has been connected, for example, via application 304. In block 602, the user device 302 can open application 304. In some embodiments, application 304 can open automatically in response to the detection of the defibrillator connection, and in some embodiments, the application can be opened manually by the user.
[0052] In block 603, application 304 can detect the placement of pads (e.g., pads 106a-b) as the individual attaches them to themselves (e.g., on both sides of the pectoral muscles surrounding the heart). For example, application 304 can be configured to detect whether the human body is connected between the two pads based on electrical measurements from pads 106a-b. In block 604, since pads 106a-b are connected to the individual's body, pads 106a-b can act as electrodes, and application 304 can record EKG measurements of the person's heart behavior. In some embodiments, recording of EKG measurements may include detecting the electrical activity of the subject's heart while the pads are attached. The electrical activity may be detected and transmitted to application 304 for various analytical purposes. Application 304 may be configured to monitor and analyze EKG measurements and detect any irregularities / abnormalities or disturbances or factors that may suggest a high probability of a heart attack or cardiac arrest occurring. A significant amount of patient data obtained from emergency health records, along with real-time data from other mobile AEDs 306 connected to the server device 310, can be analyzed using a machine learning model. Therefore, in block 605, application 304 can determine an action plan based on recorded EKG measurements and the resulting analysis, as well as pre-specified or pre-programmed risk factors related to the patient. For example, the patient can present various information and risk factors within application 304. For example, application 304 can administer a specific shock pattern with a specific timing, or continue monitoring the person's cardiac behavior. In some embodiments, administering a shock pattern can be triggered by detecting a shockable heart rhythm (e.g., ventricular tachycardia and / or ventricular fibrillation) from EKG measurements. In some embodiments, detecting an abnormal respiratory pattern (as described, for example, in relation to Figure 5) may suggest that it is preferable to administer an electric shock.In some embodiments, application 304 can be configured to determine whether the patient is conscious or unconscious. For example, after the pads are connected to the subject, application 304 may display a message to the subject requesting that the subject respond in a specific manner (e.g., by pressing the button "Yes, I am conscious" or by responding verbally). If the subject does not respond within a given time frame, application 304 may determine that the subject is unconscious and requires an electric shock. In block 606, application 304 can carry out the determined action plan.
[0053] Figure 7 shows an exemplary process 700 for providing updates to multiple mobile AEDs according to several embodiments of the present disclosure. In some embodiments, process 700 can be performed by the AED Improvement Module 312 and the AED Update Module 314 to continuously maintain and update various machine learning algorithms associated with the AED performance of the mobile AEDs of the present disclosure, possibly in real time. 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 may include EKG measurements, patient health and demographic data, EKG measurements and other cardiac monitoring-related data recorded during processes performed on an individual (e.g., processes 400, 500, and 600). For example, the data may be compiled by application 304 and transmitted to server device 310 via network 308, and finally to AED Improvement Module 312. In some embodiments, application 304 may be configured to anonymize this information before transmitting it to server device 310. In addition, in some embodiments, the AED improvement module 312 can also be configured to receive user interface data and user experience optimization data. This can be used to continuously improve application performance along with AED performance. The data received by the AED improvement module 312 may include data from multiple mobile AEDs, as well as from actual CPR and AED use, and may include health and medical outcomes and data (e.g., EKG measurements and other health data as described elsewhere in this specification), timing data (e.g., time to detection, time to AED readiness, time to first shock, etc.), user interface data, user interaction data depending on the number of people and, where possible, who is present, and location data.
[0054] In block 702, the AED Improvement Module 312 can train or retrain models, actions, and procedures. For example, the AED Improvement Module 312 can update or retrain various models maintained in the server 310 using data received from user devices 302 working in conjunction with the mobile AED 306 (note that the models also operate within applications 304 on each user device 302). In some embodiments, the AED Improvement Module 312 can be configured to use 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 regarding pad placement determination, shock pattern determination (e.g., duration and pulse level), EKG measurement analysis, and action / procedure determination in response to monitoring individual EKG measurements during self-rescue.
[0055] In block 703, the update module 314 compiles all updated models and algorithms into a software update, which can then be provided to the user device 302 directly or for download via an application store. In some embodiments, blocks 701 and 702 can run 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 only be run at various stages, or only after a certain level of performance improvement has been detected by the AED improvement module 312. In block 704, the software update can be delivered to the device 302 for execution on application 304.
[0056] Figure 8 shows an exemplary server device 800 that can be used in the system of Figure 3 according to several embodiments of the present disclosure. The server device 800 can perform various functions and processes described herein. The server device 800 can be implemented on any electronic device that runs a software application derived from compiled instructions, including, but not limited to, personal computers, servers, smartphones, media players, electronic tablets, game consoles, email devices, etc. In some embodiments, the server device 800 may include one or more processors 802, volatile memory 804, non-volatile memory 806, and one or more peripheral devices 808. These components can be interconnected by one or more computer buses 810.
[0057] Processor 802 may use any known processor technology, including, but is not limited to, graphics processors and multicore processors. A suitable processor for executing the instruction program may, for example, include both general-purpose and dedicated microprocessors, and one of any single processor or multiple processors or cores of any type of computer. Bus 810 may be any known internal or external bus technology, including, but is not limited to, ISA, EISA, PCI, PCI Express, NuBus, USB, Serial ATA, or FireWire. Volatile memory 804 may include, for example, SDRAM. Processor 802 may receive instructions and data from read-only memory or random access memory or both. The main components of a computer may include a processor for executing instructions, as well as one or more memories for storing instructions and data.
[0058] The non-volatile memory 806 may include, for example, semiconductor storage devices such as EPROMs, EEPROMs, and flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, and CD-ROMs and DVD-ROM disks. The non-volatile memory 806 can 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 for 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 software for implementing network communication instructions, such as TCP / IP, HTTP, Ethernet, and telephony communication protocols. The application instructions 816 may include instructions for applying a shock pattern using a mobile AED, instructions for connecting to law enforcement, instructions for displaying instructions for applying a shock pattern using a mobile AED, and instructions for performing self-rescue actions according to the systems and methods disclosed herein. For example, application instruction 816 may include instructions for the components 110 to 112 described above in conjunction with Figure 1.
[0059] Peripheral device 808 can be included with server device 800 or can be operationally coupled to server device 800 for communication. Peripheral device 808 may include, for example, a network subsystem 818, an input controller 820, and a disk controller 822. The network subsystem 818 may include, for example, an Ethernet for a WiFi adapter. The input controller 820 may 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 may include one or more mass storage devices for storing data files, such devices including magnetic disks, magneto-optical disks, and optical disks, such as internal hard disks and removable disks.
[0060] Figure 9 shows an exemplary computing device 900 that can be used in the systems of Figure 1 and / or Figure 3 according to some embodiments of the present disclosure. In some embodiments, the device 900 may be a user device 101. The exemplary user device 900 may 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, one or more processors 904 and / or secure processors 905, and / or peripheral subsystem 906 may be separate components or may be integrated into one or more integrated circuits. The various components within the user device 900 may be connected 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, illumination, and proximity functions. Other sensors 916 can also be connected to the peripheral subsystem 906 to facilitate related functions, such as a global navigation satellite system (GNSS) (e.g., a GPS receiver), a temperature sensor, a biosensor, a magnetometer, or other sensing devices.
[0062] The camera subsystem 920 and the optical sensor 922, for example, a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) optical sensor, can be used to enhance camera functions such as recording photographs and video clips. The camera subsystem 920 and the optical sensor 922 can also be used to collect images of the user, for example, during user authentication by performing facial recognition analysis.
[0063] Communication functions can be facilitated through one or more wired and / or wireless communication subsystems 924, which may 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 communication as described herein may be handled by the wireless communication subsystem 924. Specific designs and embodiments of the communication subsystem 924 may depend on a communication network, and the user device 900 is intended to operate over this communication network. For example, the user device 900 may include a communication subsystem 924 designed to operate over a GSM network, GPRS network, EDGE network, WiFi network or WiMAX network and Bluetooth® network. For example, the wireless communication subsystem 924 may include a hosting protocol so 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 can be coupled to a speaker 928 and a microphone 930 to facilitate voice-enabled functions such as speaker recognition, voice playback, digital recording, and telephone functions. The audio subsystem 926 can be configured, for example, to facilitate the processing of voice commands, voice prints, and voice authentication.
[0065] The I / O subsystem 940 may include a touch-surface controller 942 and / or other input controllers 944. The touch-surface controller 942 may be coupled to a touch-surface 946. For example, the touch-surface 946 and the touch-surface controller 942 may detect their contact and movement or ceasing using any of several 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 contact points with the touch-surface 946.
[0066] Other input controllers 944 can 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 styluses. 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 embodiments, the touchscreen 946 can be unlocked by pressing a button for a first duration, and the user device 900 can be powered on or off by pressing a button for a second duration longer than the first duration. By pressing a button for a third duration, voice control or voice command module can be activated, allowing the user to speak a command into the microphone 930 and have the device execute the spoken command. The user can customize the functionality of one or more buttons. The touchscreen 946 can also be used, for example, to implement virtual buttons or soft buttons and / or a keyboard.
[0068] In some embodiments, the user device 900 can present recorded audio files and / or video files such as MP3 files, AAC files, and MPEG files. In some embodiments, the user device 900 can include the functionality of an MP3 player such as an iPod®. Therefore, the user device 900 can include a 36-pin connector and / or an 8-pin connector compatible with an iPod. Other input / output devices and control devices can also be used.
[0069] The memory interface 902 can be coupled to the memory 950. The memory 950 may include one or more magnetic disk storage devices, one or more optical storage devices, and / or high-speed random-access memory such as flash memory (e.g., NAND, NOR) and / or non-volatile memory. 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] The operating system 952 may include instructions for handling basic system services and instructions for performing hardware-dependent tasks. In some embodiments, the operating system 952 may be a kernel (e.g., a UNIX kernel). In some embodiments, the operating system 952 may include instructions for performing voice authentication.
[0071] Memory 950 may further store communication instructions 954 to facilitate communication 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 to facilitate graphical user interface processing, sensor processing instructions 958 to facilitate sensor-related processes and functions, telephone instructions 960 to facilitate telephone-related processes and functions, electronic messaging instructions 962 to facilitate electronic messaging-related processes and functions, web browsing instructions 964 to facilitate web browsing-related processes and functions, media processing instructions 966 to facilitate media processing-related functions and processes, GNSS / navigation instructions 968 to facilitate GNSS and navigation-related processes and instructions, and / or camera instructions 970 to facilitate camera-related processes and functions.
[0072] Memory 950 can store application (or "app") instructions and data 972, such as instructions for the app as described above in relation to Figures 1 to 9. Memory 950 can also store other software instructions 974 for various other software applications in place on device 900.
[0073] Specific embodiments have been described in the above specification. However, those skilled in the art will understand that various modifications and changes can be made without departing from the scope of the invention, as described in the following claims. For example, the invention has been described and shown in relation to a school, but is not limited thereto. Therefore, the specification and drawings are considered explanatory rather than restrictive, and all such changes are intended to be within the scope of this teaching.
[0074] No benefit, advantage, solution to a problem, or any element that can cause any benefit, advantage, or solution to occur or become more prominent should be construed as an important, necessary, or essential feature or element of any or all claims. The present invention is defined solely by the appended claims and all equivalents of the issued claims, including any amendments made during the pendency of this application.
[0075] An abstract of this disclosure is provided so that readers can quickly determine the nature of this technical disclosure. To the best of our understanding, this abstract is not intended to interpret or limit the claims or their meaning. Furthermore, as can be seen in the detailed description above, various features are grouped into various embodiments for the purpose of simplifying the disclosure. This method of disclosure is not intended to be interpreted as reflecting an intention that the claimed embodiments require more features than those explicitly described in each claim. Rather, as reflected in the following claims, the subject matter of the invention is less than all the features of a single disclosed embodiment. For this reason, the following claims are incorporated into embodiments for carrying out the invention, and each claim itself is an independent subject matter that is separately claimed.
[0076] It should be understood that the subject matter disclosed is not limited in its application to the structural details and component arrangements described in the following description or illustrated in the drawings. Other embodiments of the subject matter disclosed are possible and can be implemented and performed in various ways. It should also be understood that the nomenclature and terminology used herein are for illustrative purposes only and should not be considered limiting. Accordingly, those skilled in the art will understand that the concepts on which this disclosure is based can be readily used as a basis for designing other structures, methods and systems to serve some of the purposes of the subject matter disclosed. Accordingly, it is important that the claims are considered to include such equivalent configurations, as long as they do not deviate from the spirit and scope of the subject matter disclosed.
[0077] Although the subject matter to be disclosed has been described and shown in the exemplary embodiments described above, it should be understood that this disclosure is merely illustrative and that numerous modifications to the details of the implementation of the subject matter to be disclosed can be made without departing from the spirit and scope of the subject matter to be disclosed.
Claims
1. A computing device comprising one or more processors, configured to be operationally connected to and control a mobile defibrillator (AED) unit, wherein via the one or more processors, The connection of the mobile AED unit is detected, The system detects that one or more electrodes of the mobile AED unit are connected to the person being treated. The EKG measurement value of the subject recorded by the electrode is received. Receiving measured respiratory data related to the chest movement caused by the subject's breathing, The respiratory data is analyzed to determine the respiratory pattern of the subject, The breathing pattern is determined to be an abnormal breathing pattern, Based on the determined abnormal breathing pattern, initiate the CPR protocol. It is configured to be, Analyzing the aforementioned respiratory data to determine the respiratory pattern of the subject is The movement of the chest is modeled, Analyzing the frequency of breathing A computing device that includes the ability to do so.
2. The received respiratory data is the first respiratory data, The computing device is While performing CPR on the aforementioned subject, second respiratory data is received. The second respiratory data is analyzed to determine the frequency and force of compression. Display on the computing device a recommendation to change at least one of the frequency and force of the compression. A computing device according to claim 1, including the following:
3. It is determined whether the respiration frequency is higher or lower than a predetermined respiration range. Based on the above determination, the CPR protocol is initiated. A computing device according to claim 1, including the following:
4. The computing device according to claim 3, wherein the predetermined breathing range is 10 to 20 breaths per minute.
5. Based on the determined breathing pattern and EKG measurement values, the electric shock pattern to be administered to the subject is determined. The electric shock pattern is administered to the subject in conjunction with the CPR protocol. A computing device according to claim 1, including the following:
6. A warning is issued before or during the application of the aforementioned electric shock pattern. It is indicated that it is safe to perform chest compressions after the aforementioned electric shock pattern is completed. A computing device according to claim 5, including the following:
7. By analyzing the aforementioned respiratory data, the rhythm of cardiac massage is detected. The computing device displays feedback related to at least one of the frequency and force of the cardiac massage. A computing device according to claim 1, including the following:
8. The computing device according to claim 1, wherein initiating the CPR protocol includes displaying instructions on the device for the user to provide CPR to a subject.
9. The computing device according to claim 1, wherein initiating the CPR protocol includes displaying at least one of video or instructions.
10. The computing device according to claim 1, wherein initiating the CPR protocol includes initiating a connection to a video specialist.
11. The computing device according to claim 1, comprising notifying at least one of law enforcement or emergency medical personnel in response to the initiation of the CPR protocol.