This page provides an overview of the steps required to implement the PulsePoint mobile application. Since every agency is unique, you should view these steps as a general roadmap for building a successful implementation plan, not as a rigid or exhaustive strategy for your specific agency.
PulsePoint has partnered with Physio-Control to provide your agency with the high-quality, professional support needed to successfully deploy PulsePoint in your community, by:
- Providing project management
- Helping you integrate the program into your CAD system
- Aiding in public outreach efforts
- Supplying a suite of professionally developed community launch materials that you can customize for your agency
Step 1: Planning your implementation
Your PulsePoint implementation begins with developing an implementation plan and registering online. Therefore, you should kick off your implementation by taking these first two steps:
The first step includes building consensus for the app in your community. Determine who should be involved in such a decision and assemble them to discuss the matter and ask questions. Typical attendance might include representatives from Fire, EMS, Communications, Information Technology, Public Information/Outreach, Leadership/Elected Officials, Labor, and affiliated non-governmental organizations such as the local heart association chapter, hospital board/foundation, etc., in addition to interested members of the community. Your implementation will be more successful if it has broad support within your agency and community. You should also review the costs involved in becoming a PulsePoint agency, develop a draft budget, and explore local sponsorship opportunities.
Once you’ve ensured that your agency is committed to a PulsePoint implementation, complete the online registration form. Completing the registration marks the formal start of your implementation with PulsePoint and gives us and our implementation partner, Physio-Control, the information needed to support you. After contacting you to confirm the information and establish a formal business relationship, we provide you with a unique key and password to share with your CAD vendor to access PulsePoint’s “sandbox” (pre-production) server.
Step 2: Establishing your CAD-to-PulsePoint interface
A key step in the implementation process will involve the configuration of your Computer-aided Dispatch (CAD) system to interface with the PulsePoint service.
Connect Your CAD System to the PulsePoint Sandbox Server
Most CAD vendors provide a ready-made interface to PulsePoint. If one is not yet available for your system we will work closely with you and your vendor to develop an interface. We also commonly work with experienced third-party developers to create CAD-to-PulsePoint interfaces. You can also use internal programming staff to develop the interface. Our Application Programming Interface (API) specification is available here. Successful completion of this step occurs when you can flow CAD incident data from your production system to the PulsePoint sandbox server.
Step 3: Integrating local AED location information and optional components
Integrate AED Location Information
One of the hallmark capabilities of the PulsePoint app is its ability to improve the frequency and speed of AED deployment by providing precise mapping of nearby devices to citizen rescuers in context with their present location. Providing information about the location of nearby AED devices can help users be much more effective when responding to an cardiac arrest incident. You provide this information via a spreadsheet or other database and PulsePoint will transfer it directly into the application. PulsePoint has a powerful AED maintenance portal that will enable you to visually position each device and maintain your AED data as it changes in the future. See the Public AED Locations Page for more details.
Enable Streaming Dispatch Radio
The PulsePoint app supports streaming radio so mobile users can hear dispatch communications. Including a streaming radio feed in your deployment will likely increase community interest and involvement which may ultimately result in better adoption rates and thus better patient outcomes. You enable streaming dispatch radio by selecting the Streaming Radio Functionality checkbox on your PulsePoint registration page and entering the URL of your radio stream. See the Streaming Radio Channels Page for complete details.
Prepare Agency Photo Gallery
The Agency Profile page within the app contains photo albums that allow PulsePoint users to view incident, event, station, apparatus, and other photos that your agency chooses to share. While implementing the photo sharing capability is optional, display of organization photos may increase community awareness around the critical work performed by public safety agencies. Such knowledge may cultivate public support and increase civic engagement and participation in the Chain of Survival. Detailed instructions on enabling agency photos are available on the In-App Agency Photos Page.
Step 4: Testing and acceptance
A formal test plan is provided to verify that your PulsePoint interface meets its design specifications and other requirements. Along with this plan, PulsePoint will provide both a browser-based tool and a special app version for end-to-end testing. Using these tools you will be able to verify that incidents are properly displaying and that event notifications are functioning as intended before public release.
Testing is complete when both PulsePoint and your agency are satisfied with the capabilities of the interface and all other required elements are in place (logos, agency profile, jurisdiction cities, AED locations, etc.). When both parties are satisfied PulsePoint will provide you with production API credentials for you to share with your CAD vendor.
Step 5: Internal training and orientation (soft launch)
Stage Your Production System
Staging provides a final technical validation before going live. Using the issued production credentials your CAD vendor will redirect the interface from PulsePoint’s sandbox end-point to our production end-point. This enables us to verify the implementation in the actual environment that end users will experience. Data at the stage is only visible to the PulsePoint technical staff.
Perform a “Soft” Launch
You should view the soft launch as your final end-to-end validation before your public go live. We “flip the switch” in PulsePoint’s production system making your agency’s incident data accessible via the public mobile apps. From a technical perspective this is your go live. However, the soft launch provides a brief period to train your internal staff and notify your effected stakeholders ahead of the public announcement. A effective soft launch helps ensure a well-supported and surprise-free public rollout.
Step 6: Announcing PulsePoint to your community
Go Live with PulsePoint in Your Community
For the app to be successful in any agency it must be embraced by the community. Effective implementation requires a comprehensive community outreach strategy to be planned and executed. Our implementation partner, Physio-Control, provides resources for this effort including a Public Service Announcement video and a suite of professionally developed community launch materials that you can customize for your agency. A typical launch event includes a wide variety of tools including press releases, possibly a press conference, and extensive use of agency web and social media resources.
Step 7: Promoting the initiative on an ongoing basis
Awareness efforts related to the PulsePoint app should be integrated within traditional CPR and AED training efforts and related community events. Such programs are most effective within the framework of a comprehensive, ongoing, and consistent outreach program.