IP Library Granted Patent US 10,665,078
Granted Patent B1
US 10,665,078 · App. 16/741,277 · Granted May 26, 2020

Responder network

Inventors: David Picco (San Marcos, CA); Sameer Jafri (San Diego, CA); Micah R. Bongberg (Kirkland, WA); Rory M. Beyer (San Mateo, CA); Gordon Moseley P. Andrews (Ross, CA)
Assignee: Avive Solutions, Inc.
G08B21/02G08B25/006G08B25/14G08B27/001H04W4/90
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,665,078
App. No.
16/741,277
Granted
May 26, 2020
Kind
B1
Abstract

A variety of methods, medical devices, responder network servers, emergency services interfaces and call center related processes are described that can help improve responder networks designed to get a medical device such as an automated external defibrillator and/or volunteer responders to the scene of a potential medical incident.

Claims (58)

1. A method of handling a request for assistance using an emergency services interface that is configured to communicate with a multiplicity of different emergency call centers, the emergency services interface being further configured to receive real-time incident data from connected devices and communicate the real-time incident data directly to appropriate ones of the emergency call centers, the method comprising:

receiving at the emergency services interface, the request for assistance from a first selected one of the emergency call centers, the request for assistance including a location of an incident for which assistance is desired; and

in response to the receipt of the request for assistance, sending an incident network notification message from the emergency services interface to a responder network server, the incident network notification message including the location of the incident, wherein the responder network server, is configured to identify and notify a set of devices of the incident.

2. A method as recited in claim 1 further comprising, at each device that receives the nearby incident message, generating a nearby incident alert that indicates that there is an emergency incident nearby for which the device may be useful, wherein the nearby incident alert includes at least one of an audio alert and a visual alert, the visual alert being displayed on a display screen associated with the device.

3. A method as recited in claim 1 wherein each of the devices in the identified set of devices has recently provided its location and operational status to the responder network server.

4. A method as recited in claim 1 wherein:

the responder network server is configured to send status inquiries to a multiplicity of devices in response to reception of the incident network notification message; and

the set of devices to be notified is a subset of the multiplicity of devices that were sent and responded to the status inquiries.

5. A method as recited in claim 1 wherein the emergency services interface is RapidSOS.

6. A method as recited in claim 1 , wherein the devices in the set of devices are defibrillators.

7. A method as recited in claim 1 wherein the devices in the set of devices include a kit that includes at least one of:

an anti-venom;

an antidote;

an opioid overdose treatment;

a medicine;

a bleeding suppression mechanism; and

an epinephrine injector.

8. A method as recited in claim 1 wherein the devices in the set of devices includes a device selected from the group consisting of a first aid kit, a safety kit, an epinephrine injector and a medical instrument.

9. A method as recited in claim 1 wherein each of the devices in the set of devices has an associated communication unit, the communication unit being configured to receive messages from and transmit messages to the responder network server.

10. A method as recited in claim 9 wherein each of the communication units are one of:

a component of the associated device;

part of an interface unit that is detachably mounted on the associated device to form a unitary portable system;

physically attached to the associated device;

not physically attached to the associated device; or

part of a dock or cabinet that holds the associated device.

11. A method as recited in claim 6 wherein each of the defibrillators has an associated communication unit configured to receive messages from and transmit messages to the responder network server, each of the communication units being one of:

a component of the associated defibrillator;

part of an interface unit that is detachably mounted on the associated defibrillator to form a unitary portable defibrillator system; or

part of a dock or cabinet that holds the associated defibrillator.

12. A method as recited in claim 6 wherein each of the defibrillators has an associated communication unit configured to receive messages from and transmit messages to the responder network server, each of the communication units being one of:

physically attached to the associated defibrillator; or

not physically attached to the associated defibrillator.

13. A method of transmitting selected defibrillator incident data to an emergency call center, the method comprising:

at a defibrillator network server, electronically receiving the selected defibrillator incident data; and

electronically transmitting the selected defibrillator incident data from the defibrillator network server to an emergency services interface that is configured to communicate with a multiplicity of different emergency call centers and to electronically transmit the selected defibrillator incident data to a selected emergency call center, the emergency services interface being further configured to receive real-time incident data from a multiplicity of other connected devices and communicate the real-time incident data directly to appropriate ones of the emergency call centers.

14. A method as recited in claim 13 further comprising electronically transmitting the selected defibrillator incident data from the emergency services interface to the selected emergency call center.

15. A method as recited in claim 13 wherein the selected defibrillator incident data includes at least one ECG segment.

16. A method as recited in claim 13 wherein the selected defibrillator incident data includes an indication of a number of shocks delivered to a patient and information about the nature or timing of each such shock.

17. A method as recited in claim 13 wherein a defibrillator that generated the defibrillator incident data has an associated communication unit configured to receive messages from and transmit messages to the defibrillator network server, wherein the defibrillator network server receives the selected defibrillator incident data from the communication unit, the communication unit being one of:

a component of the defibrillator;

part of an interface unit that is detachably mounted on the defibrillator to form a unitary portable defibrillator system;

physically attached to the defibrillator;

not physically attached to the defibrillator; or

part of a dock or cabinet that holds the defibrillator.

18. A method as recited in claim 13 wherein:

a defibrillator that generated the selected defibrillator incident data is configured to communicate with a mobile communication device; and

the defibrillator network server receives the selected defibrillator incident data from the mobile communications device.

19. A method as recited in claim 18 wherein the mobile communication device is a cellular phone having a defibrillator support app installed thereon that coordinates communications with the defibrillator and with the defibrillator network server.

20. A method as recited in claim 13 wherein the selected defibrillator incident data is received by the defibrillator network server, electronically transmitted from the defibrillator network server to the emergency services interface, and electronically transmitted from the emergency services interface to the selected emergency call center in real time during emergency use of a defibrillator that generated the selected defibrillator incident data.

21. A method of transmitting selected defibrillator incident data to an emergency call center, the method comprising:

at a defibrillator network server, electronically receiving the selected defibrillator incident data generated by a defibrillator during emergency use of the defibrillator; and

electronically transmitting the selected defibrillator incident data from the defibrillator network server to an emergency services interface that is configured to communicate with a multiplicity of different emergency call centers and to electronically transmit the selected defibrillator incident data to a selected emergency call center, the emergency services interface being further configured to receive real-time incident data from a multiplicity of other connected devices and communicate the real-time incident data directly to appropriate ones of the emergency call centers' and

wherein the selected defibrillator incident data is received by the defibrillator network server, electronically transmitted from the defibrillator network server to the emergency services interface, and electronically transmitted from the emergency services interface to the selected emergency call center in real time during the emergency use of the defibrillator that generated the selected defibrillator incident data.

22. A method as recited in claim 21 wherein the selected defibrillator incident data is transmitted to the defibrillator network server by one of:

a communications unit that is an integral part of the defibrillator;

an interface unit that is a separate unit that detachably attached to the defibrillator;

a communication unit associated with the defibrillator that is not physically attached to the defibrillator; and

a mobile communication device having a defibrillator support app installed thereon that coordinates communications with the defibrillator and with the defibrillator network server.

Assignments (2)
SECURITY INTEREST Recorded Mar 31, 2026
From: AVIVE SOLUTIONS, INC.
To: HORIZON TECHNOLOGY FINANCE CORPORATION
Reel/Frame 075305/0214 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 14, 2020
From: PICCO, DAVID; JAFRI, SAMEER; BONGBERG, MICAH R.; BEYER, RORY M.; ANDREWS, GORDON MOSELEY P.
To: AVIVE SOLUTIONS, INC.
Reel/Frame 051506/0066 →
Continuity (3)
Continuation 16562870 · Sep 6, 2019
Provisional Application 62731306 · Sep 14, 2018
Provisional Application 62846346 · May 10, 2019
Cited By (6)
US 12,211,368 US 12,283,170 US 12,285,622 US 12,381,000 US 12,430,998 US 12,594,431