National Emergency AED Registry (NEAR)

AEDs are simple-to-operate lifesaving devices that can significantly improve the chances of surviving a cardiac arrest if promptly deployed. However, when someone witnesses a possible cardiac arrest, awareness of nearby devices should not be left to chance. When a call is placed to emergency services, it is important that the telecommunicator is able to advise the caller of nearby devices. The NEAR registry, in conjunction with public safety solution vendors and other industry partners such as device manufacturers and distributors, empower telecommunicators with knowledge of nearby locations within familiar applications and workflows.

In addition, individuals with access to a registered AED can be notified that their defibrillator may be needed nearby. These individuals may be too far away to be aware of the emergency (e.g, floor above, business next door, neighbor) but still close enough to arrive with their AED well before on duty responders.

In the near future, devices capable of detecting cardiac arrest, such as watches and wearables, will allow nearby responders to be put in motion even before a call to emergency services is initiated.

The NEAR registry works to consolidate data from all available sources to facility a single source of AED locations for emergency use. These sources include AED manufacturers and distributors, program management companies, governmental entities, school districts, airports, and organizations with large numbers of AEDs. Many communities also collect locations in partnership with local businesses and AED owners. A variety of APIs are available to automate AED location sharing in addition browser-based registry building tools and mobile apps from PulsePoint.

The NEAR registry collects data about AEDs – not people. The registry does not require the collection of any personal data. At a minimum, only basic AED location information is required.

If an agency having jurisdiction is using the NEAR registry to satisfy regulatory notifications, they may require additional information to meet their statute requirements (e.g., Access Code/PIN for a locked cabinet, responsible party contact information, last inspection date).

OPTIONAL DATA
Users may choose to provide additional information such as an image of the AED, or resources collocated with the AED (e.g., Bleeding Control Kit). Several optional data fields are available to accommodate various use cases.

ADDING AN AED TO THE REGISTRY
For an individual to add an AED to the registery an email address is required. Individually submitted AEDs require administrative approval/verification before they will be recommended.

To manage one or more AED records in the registry, an email and password is required to create an account. This account can be deleted by the user at any time.

RECEIVING AED-NEEDED ALERTS
AED-needed alerts require mobile app permissions to receive push notifications. AED-needed alerts are based on the AED location and do not require user location permissions. You must be the responsible party, or have the approval of the responsible party, to receive AED-needed alerts. Only registry approved AEDs are eligible for alerts. AED-needed alert subscriber emails are disclosed to registry administrators.

Responders that receive an AED-needed alert are sent a post-incident survey. Participation in the survey is optional. The app-based survey seeks information related to responder actions and offers follow up information and resources. Authorized public safety agency personnel can view responses for all suspected cardiac arrest events within their jurisdiction. Designated agency personnel also receive notifications for key actions reported in the survey such as CPR performed or AED used.

REGISTRY ADMINISTRATORS
To manage an AED in the registry an email and password is required to create/maintain an administrator account. This account can be deleted by the user at any time.

Additional information may be required for optional functionality (e.g., alert me if my AED is needed nearby, notify me if an issue is reported with this AED).

For use of some APIs, the device serial number is required to uniquely identify a device in the registry. This prevents duplicate entries and allows existing records to be updated or removed.

USE OF DATA
AED data is shared with public safety organizations and their technology partners for the purpose of improving device utilization during cardiac arrest emergencies.

AED data is shared with trained responders that participate in community CPR/AED responder programs. When alerted to a nearby cardiac arrest, these responders may be shown non-public information such as the access code to a locked public AED cabinet near them.

No collected information is ever sold or disclosed for marketing or other non-public safety related purposes. To improve the effectiveness of the registry, aggregated data may be used for analysis, reporting, technology development, research and quality control.

Basic AED location data, images, and collocated items, may be displayed to the public for situational awareness and to prevent duplicate submissions. Viewing this information does not require an account or use of an email address.

DATA RETENTION
AED records are retained for as long as the information remains valid or until removed by a registry administrator.

CHANGES TO THIS POLICY
We may revise this Privacy Policy from time to time. The most current version of the policy will govern our use and can always be referenced at pulsepoint.org/near.

QUESTIONS ABOUT THIS NOTICE
If you have any questions about this notice, please contact us at info@pulsepoint.org.