EMS Setup - Endpoints Configuration

EMS Setup - Endpoints Configuration

Purpose Statement

The Endpoints Configuration feature within EMS Setup enables Fire/EMS agencies to establish automated data export connections to external systems such as state reporting databases, hospital networks, billing vendors, and compliance systems. This functionality ensures seamless data transmission for NEMSIS compliance, billing workflows, and inter-agency data sharing 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 multiple connection types, including SOAP web services and SFTP file transfers, allowing agencies to meet diverse technical requirements imposed by receiving organizations.

When properly configured, endpoints enable automated, reliable data exports, reduce manual data entry, and improve compliance with state and federal reporting requirements.

Required Permissions

Users must have administrative permissions within the EMS module to access and configure endpoints, including:
  • EMS module administrative access
  • EMS Setup permissions
  • Endpoints Configuration permissions
  • System integration management permissions
  • Data export permissions
If you cannot access the Endpoints Configuration section, contact your system administrator.

Video



Step-by-Step Guide


1. Navigate to Endpoints Configuration
  • Navigate to EMS Setup
  • Click Endpoints Configuration





2. Add a New Endpoint
  • Click Add to create a new endpoint

Click on Add to add a new endpoint.



3. Configure General Endpoint Information
  • Under the General tab:
    • Enter endpoint details
    • Enter your agency’s authentication credentials
    • Select the appropriate endpoint type (SOAP or SFTP)





4. Configure SOAP and SFTP Options
  • For SOAP and SFTP endpoints, configure the following options as needed:
    • Exclude eOther FileGroup
    • Attach PDF
    • Export Once
  • Info:
    • If Attach PDF is set to Yes, the export email will include:
      • A PDF version of the ePCR
      • The associated XML file





5. Configure Additional SFTP Options
  • For SFTP endpoints, also configure:
    • Send Attachments as Separate Files
    • SFTP Demographic Files Path
    • SFTP EMS Files Path





6. Configure Export Criteria
  • Click the Criteria tab
  • Click Add Condition to define export triggers




7. Configure Disposition-Based Exports
  • Use the Disposition list to enable exports only for selected dispositions
  • Idea Info:
    • This is useful when a billing vendor processes only specific dispositions





8. Configure Status-Based or Care-Based Triggers
  • Add conditions to trigger exports when:
    • An Incident Report reaches a specific Status
    • Based on Unit Patient Evaluation / Care criteria








9. Automate Status Updates (Optional)
  • Configure Automation to update the incident status automatically after a successful export or import




10. Edit Existing Endpoint Criteria
  • Click the Pencil icon to edit criteria for an existing endpoint

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 endpoint?
  • Verify the ePCR meets all configured criteria (disposition, status, care conditions)
  • Confirm the endpoint is active and credentials are valid
Q: What is the difference between SOAP and SFTP endpoints?
  • SOAP: Uses web services for near real-time data transmission
  • SFTP: Transfers files to a secure file server
  • Choose based on the receiving organization’s technical requirements
Q: Can I configure multiple endpoints for the same organization?
  • Yes, multiple endpoints can be configured with different criteria or data requirements
Q: How can I verify export success?
  • Review system logs and transmission status messages
  • Monitor error notifications for failed exports
Q: What should I do if credentials change?
  • Update the endpoint configuration immediately to prevent export failures

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 - General subsection

      Purpose Statement The EMS Setup - General Subsection provides fire and EMS administrators with comprehensive configuration options for managing electronic Patient Care Reports (ePCRs) and related EMS documentation processes. This centralized ...

    • Fire Incident Setup - EMS Module - Configuration Fields

      Purpose Statement The Configuration Fields section of the Fire Incident EMS Module allows administrators to customize treatment and medication options to align with local protocols and operational standards. This feature enables departments to: ...

    • 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 Setup - Adding Custom Values for NEMSIS Questions

      Purpose Statement This article demonstrates how to create custom values for NEMSIS questions within an EMS report, allowing agencies to add localized options to standard NEMSIS fields while maintaining compliance and proper data mapping. Background ...