EMS Setup - Endpoints Configuration

EMS Setup - Endpoints Configuration

Purpose Statement

The Endpoints Configuration within EMS Setup enables Fire/EMS agencies to establish automated data export connections to external systems such as state reporting databases, hospital networks, and compliance systems. This functionality ensures seamless data transmission for NEMSIS compliance, billing processes, and inter-agency communication while maintaining data integrity and security standards.


Background Information

Endpoint configuration is critical for EMS agencies that must transmit patient care data to multiple external systems for regulatory compliance, billing, and operational coordination. The system supports various connection types including SOAP web services and SFTP file transfers, allowing agencies to meet diverse technical requirements from different receiving organizations. Proper endpoint setup ensures automated, reliable data transmission while reducing manual data entry and improving compliance with state and federal reporting requirements.


Required Permissions

Users must have administrative permissions within the EMS module to access and configure endpoints. Required permissions typically include:

  • EMS module administrative access
  • Setup section permissions
  • Endpoints Configuration permissions
  • System integration management permissions
  • Data export permissions

Contact your system administrator if you cannot access the Endpoints Configuration section


Video




Step-by-Step Guide


1. Navigate to EMS Setup -> Endpoints Configuration






2. Click on Add to add a new endpoint.


Click on Add to add a new endpoint.



3. Under the General tab, input endpoint information and your agency's credentials







4. For SOAP and SFTP type endpoints, set the options for:
  1. "Exclude eOther FileGroup"
  2. "Attach PDF" 
  3. "Export Once" 

Info
If the Attach PDF field is switched to YES, the export email will include an attachment with a PDF version of the ePCR along with the XML file.





5. For the SFTP type endpoint, also set the options for:
  1. "Send Attachments as Separate files"
  2. "SFTP Demographic files path"
  3. "SFTP EMS files path" 




6. To trigger incident exports tied to specific criteria, click on the Criteria tab, then Add Condition.





7. Use the disposition list to enable export to the endpoint for only the dispositions selected.

IdeaInfo
This field is useful if your agency's billing company only bills for specific dispositions.




8. An additional condition will allow to trigger an export only when an Incident Report is changed to a specific status and or based off of the Unit Patient Evaluation/Care.








9.  Automation may be utilized to change the incident status upon completion of a successful import.




10. Use the pencil icon to edit the criteria for any existing endpoints.

Use the pencil icon to edit the criteria for any existing endpoints.



Best Practices

Do:

  • Test endpoint connections before placing them into production use
  • Configure appropriate export criteria to avoid unnecessary data transmission
  • Document endpoint configurations and credentials securely
  • Regularly review and update authentication credentials
  • Monitor endpoint performance and transmission success rates

Don't:

  • Configure endpoints without verifying receiving system requirements
  • Enable automatic exports without proper testing
  • Share endpoint credentials inappropriately
  • Configure overlapping export criteria that might cause duplicate transmissions
  • Ignore failed transmission notifications or error logs

Troubleshooting & FAQs

Q: Why are my ePCRs not exporting to the configured endpoint? A: Check that the ePCR meets all criteria configured in the Criteria tab, including disposition and status requirements. Also verify the endpoint connection is active and credentials are correct.

Q: What's the difference between SOAP and SFTP endpoint types? A: SOAP endpoints use web service protocols for real-time data transmission, while SFTP endpoints transfer files to secure file servers. Choose based on the receiving system's technical requirements.

Q: Can I configure multiple endpoints for the same receiving organization? A: Yes, you can create multiple endpoints with different criteria or configurations for the same organization if needed for different data types or transmission requirements.

Q: How do I know if my data exports are successful? A: Monitor the system logs and any error notifications. Most endpoints provide transmission status feedback that can be reviewed in the system.

Q: What should I do if authentication credentials change? A: Update the endpoint configuration immediately with new credentials to prevent transmission failures and maintain compliance requirements.


Additional Considerations

Data Security and Compliance

When configuring endpoints:

  • Ensure all connections use appropriate encryption protocols
  • Verify receiving systems meet HIPAA and other privacy requirements
  • Document data sharing agreements and technical specifications
  • Implement appropriate access controls for endpoint configuration

Integration Testing

Before production deployment:

  • Test endpoints with sample data in a controlled environment
  • Verify data formatting meets receiving system requirements
  • Confirm transmission timing and frequency settings
  • Validate error handling and retry mechanisms

Monitoring and Maintenance

Establish procedures for:

  • Regular monitoring of endpoint performance
  • Periodic testing of connection integrity
  • Updating credentials and certificates as needed
  • Reviewing and adjusting export criteria based on operational changes

Compliance Considerations

Endpoint configuration impacts:

  • NEMSIS reporting compliance requirements
  • State and local reporting obligations
  • Billing and reimbursement data transmission
  • Quality assurance and performance monitoring

Performance Optimization

To ensure efficient operations:

  • Configure appropriate export criteria to minimize unnecessary transmissions
  • Schedule large data exports during off-peak hours when possible
  • Monitor system resources during high-volume export periods
  • Implement appropriate retry and error handling mechanisms
    • Related Articles

    • EMS Setup - Auto Number Setup

      Purpose Statement This article guides users through configuring the Auto Number Setup for EMS Incident and Response numbers within the EMS Setup section of the Incident Documentation module. This setup ensures consistent and automated numbering ...
    • EMS Setup - Enabling ePCR QA/QI Notifications

      Purpose Statement The purpose of this article is to explain how to enable and configure QA/QI (Quality Assurance/Quality Improvement) notifications in the EMS Incident Documentation module. Enabling these notifications ensures that personnel ...
    • EMS Setup - General - General subsection

      Purpose Statement This article provides step-by-step guidance on configuring EMS-related system settings within the Incident Documentation > EMS Setup area. These settings help agencies tailor ePCR behavior, CAD integration, and compliance-related ...
    • EMS Setup - Default Time Setup

      Purpose Statement The purpose of this article is to explain how to configure the Default Time Setup within the EMS Setup section of the Incident Documentation module. This setting allows agencies to streamline documentation by pre-selecting which ...
    • EMS External Resources

      Purpose Statement To demonstrate how to setup an External Resource to be accessed from within an ePCR. External Resources allow agencies to provide field personnel with quick access to important reference materials, protocols, or websites directly ...