# US 11,908,553 B2 · Apparatus and method for emergency response data acquisition and retrieval

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,908,553 B2
- Document ID: US11908553B2
- Status: Granted
- Kind: B2
- Application number: 16/786,962
- Filed: 2020-02-10
- Published: 2020-08-13
- Granted: 2024-02-20
- Earliest claimed: 2019-02-11
- Assignees: Rapidsos, Inc.
- Applicants: Rapidsos, Inc.
- Inventors: Zvika Ferentz; William Pellegrini; Gabe Mahoney; Nicholas Edward Horelik; Jee Yoon Choi
- Web page: https://patentgrep.com/patent/US11908553B2

## CPC

- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G06F 16/245: Query processing
- G06Q 50/265: {Personal security, identity or safety}
- G16H 40/67: for remote operation
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A disclosed method includes receiving an emergency data request with a patient identifier; retrieving protected data from a database corresponding to the patient identifier; and displaying the protected data on an emergency responder device display. Another disclosed method includes pushing a plurality of anonymized candidate profiles associated with a device identifier to an emergency network entity, in response to initiation of an emergency session by a device having the device identifier where the anonymized candidate profiles provide anonymized patient information without exposing protected data related to a patient and correspond to a non-anonymized medical profile for the patient; receiving a request from the emergency network entity for a specific non-anonymized medical profile corresponding to one of the plurality of anonymized candidate profiles; and providing a non-anonymized medical data profile corresponding to the specific anonymized candidate profile to the emergency network entity in response to the request.

## Claims

### Claim 1

A method comprising:
detecting an emergency at a cloud-based server by receiving an emergency alert from a mobile device, sent by the mobile device over an internet connection, where the emergency alert comprises mobile device hybrid location data generated by the mobile device and a mobile device identifier;
providing by the cloud-based server to a public safety answering point (PSAP), an instance of a software-as-a-service emergency response application having a graphical user interface (GUI) associated therewith;
pushing the emergency alert comprising the mobile device hybrid location data and the mobile device identifier to the instance based on the mobile device hybrid location data and displaying the emergency alert on the GUI at the PSAP;
receiving protected medical profile data at the cloud-based server, corresponding to at least one patient medical identifier associated with the mobile device identifier contained in the emergency alert; and
displaying an anonymized candidate profile list in the GUI at the PSAP having at least one list entry for the medical profile corresponding to the at least one patient medical identifier, the anonymized candidate profile not exposing protected medical information related to the patient medical identifier.

### Claim 2 (depends on 1)

The method in claim 1, wherein retrieving protected medical profile data corresponding to at least one patient medical identifier, comprises:
retrieving a plurality of anonymized candidate profiles corresponding to the at least one patient identifier, the anonymized candidate profiles providing anonymized protected medical information for a plurality of patients, without exposing protected medical information related to the plurality of patients.

### Claim 3 (depends on 1)

The method in claim 1, further comprising:
receiving a medical data request at the cloud-based server from an emergency responder mobile device associated with the PSAP and dispatched to a location based on the mobile device hybrid location data, the medical data request comprising the patient identifier and authentication data for the responder mobile device; and
providing the protected medical information related to the patient medical identifier to the emergency responder mobile device in response to the medical data request and based on an authorization level specified in the authentication data to comply with access requirements for the protected medical information.

### Claim 4 (depends on 2)

The method in claim 2, further comprising:
displaying the anonymized candidate profiles on a display of the emergency responder mobile device in response to the medical data request;
receiving a selection input corresponding to a selected one of the anonymized candidate profiles; and
displaying non-anonymized protected medical information corresponding to the selected one of the anonymized candidate profiles on the display of the emergency responder mobile device in response to the selection input.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
retrieving and transmitting the non-anonymized protected medical information in compliance with requirements for protection of personally identifiable information (PII) and protected health information (PHI).

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
receiving the patient medical identifier from a device of a bystander caller.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving the medical data request from the emergency responder mobile device, the medical data request comprising emergency responder credentials; and
providing limited access to the protected medical information by the emergency responder mobile device based on data access limitations specified in the emergency responder credentials.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
receiving the medical data request from the GUI at the PSAP on behalf of the emergency responder mobile device, the medical data request comprising emergency responder credentials; and
providing limited access to the protected medical information by the emergency responder mobile device based on data access limitations specified in the emergency responder credentials.

### Claim 9

An emergency data manager comprising:
a cloud-based server having an application server component, operative to provide a plurality of cloud-based, software-as-a-service emergency response application instances to a plurality of public safety answering points (PSAPs) via a graphical user interface (GUI) associated with each emergency response application instance;
a network component, operative to provide Internet Protocol (IP) connections to the plurality of PSAPs and to a plurality of emergency data servers and databases; and
at least one processor, operatively coupled to the network component, the at least one processor operative to:
detect an emergency at the cloud-based server by receiving an emergency alert from a mobile device, sent by the mobile device over an internet connection, where the emergency alert comprises mobile device hybrid location data generated by the mobile device and a mobile device identifier;
pushing the emergency alert comprising the mobile device hybrid location data and the mobile device identifier to an instance based on the mobile device hybrid location data and displaying the emergency alert on a GUI associated with the instance at a PSAP;
receive protected medical profile data corresponding to at least one patient medical identifier associated with the mobile device identifier contained in the emergency alert; and
display an anonymized candidate profile list in the GUI at the PSAP having at least one list entry for the medical profile corresponding to the at least one patient medical identifier, the anonymized candidate profile not exposing protected medical information related to the patient medical identifier.

### Claim 10 (depends on 9)

The emergency data manager of claim 9, wherein the processor is further operative to:
retrieve protected data comprising one or more anonymized candidate profiles corresponding to the patient identifier, the anonymized candidate profiles providing anonymized patient information without exposing protected data related to the patient.

### Claim 11 (depends on 9)

The emergency data manager of claim 9, wherein the processor is further operative to:
receive a medical data request from an emergency responder mobile device associated with the PSAP and dispatched to a location based on the mobile device hybrid location data, the medical data request comprising the patient identifier and authentication data for the responder mobile device; and
provide the protected medical information related to the patient medical identifier to the emergency responder mobile device in response to the medical data request and based on an authorization level specified in the authentication data to comply with access requirements for the protected medical information data.

### Claim 12 (depends on 10)

The emergency data manager of claim 10, wherein the processor is further operative to:
display the anonymized candidate profiles on a display of the emergency responder mobile device in response to the medical data request;
receive a selection input corresponding to a selected one of the anonymized candidate profiles; and
display non-anonymized protected medical information corresponding to the selected one of the anonymized candidate profiles on the display of the emergency responder mobile device in response to the selection input.

### Claim 13 (depends on 12)

The emergency data manager of claim 12, wherein the processor is further operative to:
retrieve and transmit the non-anonymized protected medical information in compliance with requirements for protection of personally identifiable information (PII) and protected health information (PHI).

### Claim 14 (depends on 9)

The emergency data manager of claim 9, wherein the processor is further operative to:
receive the patient medical identifier from a device of a bystander caller.

### Claim 15 (depends on 9)

The emergency data manager of claim 9, wherein the processor is further operative to:
receive the medical data request from the emergency responder mobile device, the medical request comprising emergency responder credentials; and
provide limited access to the protected data by the emergency responder mobile device based on data access limitations specified in the emergency responder credentials.

### Claim 16 (depends on 9)

The emergency data manager of claim 9, wherein the processor is further operative to:
receive the medical data request from the GUI at the PSAP on behalf of the emergency responder mobile device, the medical data request comprising emergency responder credentials; and
provide limited access to the protected medical information by the emergency responder mobile device based on data access limitations specified in the emergency responder credentials.