Skip to main content

Search

Knowledge Center

EMS Setup - Integrations With Third-Party Connections

Purpose Statement

This article explains how to configure First Due third-party EMS integrations within EMS Setup. Proper configuration allows agencies to securely connect external systems and import data directly into ePCRs, reducing manual entry and improving data accuracy.
📝

Important Note:

You will need to reach out to your CS Manager or Account Executive to determine associated costs and steps needed to establish Integrations with third-party vendors.  

Background Information

First Due supports multiple third-party EMS integrations that enhance clinical documentation and interoperability. These integrations are configured at the agency level and, once enabled, become available within the ePCR toolbar for authorized users.

Common use cases include:
  • Importing clinical or operational data from partner platforms
  • Reducing duplicate data entry
  • Improving report completeness and timeliness
Prerequisites:
  • Agency access to EMS Setup
  • Valid credentials provided by each third-party vendor

Required Permissions

Users must have:
  • ePCR - EMS Setup - Allow

Step-by-Step Guide
 

1. Access the Module Stacks
  • Select the First Due logo.
  • Open the available module stacks.
 
Access the Module Stacks
 
 
 
2. Open EMS Setup
  • Select Incident Documentation.
  • Select EMS Setup.
     
Open EMS Setup
 
 
 
3. Navigate to Integrations
  • Select Integrations.
  • Review the list of available third-party integrations for your agency.
 
Navigate to Integrations
 
 
 
4. Configure Kno2 Integration
  • Enter the required information:
    • Key
    • Secret Key
    • APID
    • Assigning Auth OID
    • From Address
    • Kno2 API URL
    • Select Save.
 
Kno2 Integrations
 
 
 
5. Configure Handtevy Integration
  • Enter the required information:
    • Agency ID
    • Environment (Production or Development)
    • Select Save.
 
Handtevy Integrations
 
 
 
6. Configure Pulsara Integration
  • Enter the required information:
    • API Key
    • URL (Production or Development)
    • Select Save.
 
Pulsara Integrations
 
 
 
7. Configure OneDose Integration
  • Enter the required information:
    • Vendor Key
    • Agency Key
    • URL (Production or Development)
    • Select Save.
 
OneDose Integrations
 
 
8. Configure Zoll UI Integration
  • Enter the required information:
    • Data Access Key
    • Password
    • Select Save.
 
9. Configure Peak Response
  • Enter the required information:
    • Agency State ID
    • Agency State Unique ID
    • URL
    • Select Save.
 
 
 
10.  Verify Integration Availability in ePCR
  • Open an ePCR.
  • Confirm the configured integrations now appear in the toolbar.
  • Use the toolbar options to begin importing data into the report.
 
Once configured within an ePCR across the toolbar will now display the integrations to begin importing information into the report.

Best Practices

Do’s
  • Verify credentials with each vendor before saving.
  • Use the correct environment (Production vs. Development).
  • Test integrations in a sample ePCR after configuration.
Don’ts
  • Do not share API keys or secret keys with unauthorized users.
  • Do not configure integrations without vendor confirmation.
  • Avoid using Development URLs in a live production environment.
Tips & Recommendations
  • Keep integration credentials documented securely.
  • Revalidate integration settings after vendor updates.
  • Limit configuration access to administrative users only.

Troubleshooting & FAQs

Integration does not appear in the ePCR toolbar
  • Confirm the integration was saved successfully.
  • Verify the user has permission to access integrations.
  • Refresh the ePCR or log out and back in.
Data is not importing
  • Validate API keys and URLs.
  • Confirm the correct environment is selected.
  • Contact the third-party vendor to verify service availability.
Which environment should I use?
  • Use Production for live reporting.
  • Use Development only for testing or vendor-guided setup.