Video
Coming Soon
New Features
1. ePatient.25 Patient's Sex
This critical patch implements NEMSIS 3.5.0 compliance requirements by introducing the new ePatient.25 - Patient's Sex field in response to federal regulatory changes. Due to a Presidential Executive Order, NEMSIS is deprecating gender-related terminology from federal documentation, requiring the transition from ePatient.13 - Gender to the new ePatient.25 - Patient's Sex field.
How it works:
Setting Configuration: Navigate to EMS Setup > General and enable "Enable ePatient.25 - Patient's Sex" setting:
- Open image-20250606-124331.png
Field Activation: Once enabled, the ePatient.25 field becomes available and required in the ePCR
Response Options: Field includes standardized options:
Refused, Unable to Complete, Not Applicable, Not Recorded, Not Reporting, Female, Male, Unknown
- Open image-20250606-124552.png
Workflow Configuration: Configure field visibility, defaults, and validation rules through standard workflow settings
XSD Validation: System enforces updated NEMSIS 3.5.0 schema requirements when setting is active
XML Output: Both ePatient.13 and ePatient.25 fields appear in XML output during transition period
Report Display: New field appears in ePCR interface and generated reports when enabled
2. dPersonnel.40 EMS Personnel's Sex
This critical patch implements NEMSIS 3.5.0 compliance requirements by introducing the new dPersonnel.40 - EMS Personnel's Sex field in the Personnel section. This field complements the patient-side ePatient.25 implementation and addresses federal regulatory changes requiring the transition from gender-based terminology to sex-based terminology in NEMSIS documentation.
How it works:
Field Access: Navigate to Personnel Section > NEMSIS to access the new EMS Personnel's Sex field
Field Positioning: The new field appears adjacent to the existing Gender field for easy reference
Response Selection: Choose from standardized options: Not Applicable, Not Recorded, Not Reporting, Female, Male, Unknown
Data Entry: Update personnel records with the new sex designation as required
Export Integration: Field data automatically includes in demographic exports without additional configuration
XSD Validation: System validates data against updated NEMSIS 3.5.0 schema requirements
Open image-20250606-130038.p
3. The ability to tag contacts within the QA/QI
Introducing a modern tagging system that allows users to mention and notify specific contacts directly within QA/QI comments using the "@" symbol. This feature enhances communication workflows by enabling targeted notifications to crew members and key personnel.
How it works:
Creating Mentions: While typing in a QA/QI comment field, enter the "@" symbol to trigger the contact suggestion dropdown.
Selecting Contacts: Either continue typing to filter results and select a specific contact, or use predefined shortcuts like "@Crew" for group notifications.
Auto-completion: Use TAB or Enter keys to complete the selection, or navigate with arrow keys
Notification Delivery: Tagged contacts automatically receive notifications containing the message "You have been mentioned in the following ePCR Record [IncidentNumber]" with a hyperlink to the record.
Contact Type Setup: Ensure contact types are properly configured in EMS Setup > Contacts and linked to staff profiles for role-based tagging to function.
4. Endpoint Configuration
Introducing automated ePCR status updates that trigger after successful endpoint exports. This feature enables a cascade workflow where incident statuses automatically progress through defined stages as data is successfully exported to various endpoints, ensuring accurate tracking of incident progress without manual intervention.
How it works:
- Access Automation Settings: Navigate to EMS Setup > Endpoint Configuration and select the "Automation" tab.
- Configure Status Update: Use the "Upon successful export, Change the Incident Status to:" dropdown to select the desired target status.
- Status Validation: System ensures selected status is not already used by another endpoint's automation for the same client
- Automatic Processing: When export to the configured endpoint succeeds, system automatically updates incident status
- Audit Trail Creation: System creates two audit log entries:
- "Automated Exported Record" event documenting successful export
- "Status Change" event documenting the status transition with from/to details
- Cascade Triggering: New status automatically triggers evaluation of other endpoints that match the updated status criteria
- Workflow Continuation: Process continues through configured endpoint chain, allowing multi-stage automated workflows
Enhancements
1. Form Language Validation
This enhancement introduces comprehensive validation and user guidance for signature block configuration, ensuring that all selected Reasons for Signature have associated Form Language.
How it works:
Setup Interface Enhancements: Navigate to signature block setup to see new tooltips explaining each section's purpose and the critical relationship between reasons for signature and form language
- Open image-20250604-185549.png
- Open image-20250604-185707.png
- Open image-20250604-185818.png
Validation Triggers: When selecting reasons for signature in a signature block, the system immediately validates for associated form language.
Error Resolution: If validation fails, red error indicators appear with specific messages listing which reasons need form language associations.
- Open image-20250604-190035.png
Partial Save Workflow: Incomplete signature blocks can be saved but will be flagged in the interface with error counts
End-user Verification: Once properly configured, signature reasons and their form language will correctly display in the ePCR UI and appear in PDF/XML outputs
2. QA/QI Form and Form Builder Addendum
This enhancement adds Addendum functionality to both the Form Builder and QA/QI review process, providing reviewers with the ability to capture additional documentation and commentary during the quality assurance workflow.
How it works:
EMS Report Assignment: Assign EMS reports to QA/QI reviewers through the standard workflow
QA/QI List Access: Open EMS QA/QI List to view assigned incidents requiring review
Review Process: Completed ePCRs with "review requested = Yes" appear on the QA/QI list
Comment Addition: Add comments with severity levels:
ERROR (Red): Critical issues that must be resolved before approval
WARNING (Yellow): Issues requiring attention but not blocking approval
GOOD (Green): Positive feedback and commendations
Text Area Management: Utilize text area expansion for detailed commentary
Approval Workflow: Submit approval only after resolving all ERROR comments
Comment Resolution: Resolve comments individually to clear approval blockers
Report Generation: Print reports from EMS QA/QI List for documentation with resolved comments
3. Short Form Label Updates
This enhancement introduces support for NERIS (National Emergency Response Information System) short form functionality while maintaining existing NFIRS compatibility. The feature includes updated labeling to reflect the broader fire reporting standards and ensures seamless operation across both NFIRS and NERIS configurations.
How it works:
Configuration Access: Navigate to EMS Setup to access updated "Enable Fire EMS Short Form" and "Fire Short Form Requirement" settings
Open image-20250610-172625.png
NFIRS Mode: Continues to operate with existing field requirements and restrictions
NERIS Mode:
Reduced required field set compared to NFIRS
No restrictions on Actual Incident Type Found field
Streamlined reporting process
Required Fields Management: System enforces appropriate required fields based on selected standard
Custom Fields Integration: Custom required fields display with proper error workflow rules regardless of standard
Report Transition: Incomplete reports automatically adopt new standard when configuration changes
Open image-20250610-172826.png
NERIS Required Fields (Non-Custom):
Response > Dispatch > Incident Number
Response > Dispatch > Dispatch Number
Response > Dispatch > PSAP Call
Response > Dispatch > PSAP
Response > Dispatch > Primary Incident Type Found
Response > Dispatch > Secondary Incident Type Found
Response > Dispatch > Tertiary Incident Type Found
Response > Location > Address Line 1
Response > Location > State
Response > Location > City
Response > Location > Zip Code
Sizeup > Scene > Property Type where Incident Occurred
Information > Information > Presence of AES
Wrap Up > Signatures > Member Completing Report
4. Current Medications (eHistory.12)
This feature introduces configurable medication lists for the Current Medications (eHistory.12) field, providing you with the flexibility to either use the comprehensive First Due suggested list or create your own customized medication list. This enhancement supports state-specific requirements for field customization while maintaining the robust medication database that most clients rely on.
How it works:
Configuration Access: Navigate to field customization for eHistory.12 - Current Medications
List Selection: Choose between "First Due Suggested List" or "Configure my own values list"
- Open image-20250610-171859.png
First Due Mode:
Utilizes existing comprehensive medication database (9,000+ options)
No values displayed in Values tab due to volume
Only offline-marked medications available in offline mode
Custom List Mode:
Activates Values section for full customization
Pre-loads 295 commonly used medications as starting point
Enables adding, sorting, and re-labeling medications
All custom list medications available offline
- Open image-20250610-171936.png
Medication Management: Add new medications to custom list as needed for specific client requirements
Report Integration: Selected medications appear in ePCR interface and generated reports
Historical Data: Previous reports continue displaying medications even if removed from current custom list
5. Stations and Devices Filtering and Performance Optimization
This enhancement significantly improves the performance and usability of the Stations and Devices sections within EMS Setup by implementing pagination, optimized data loading, and comprehensive filtering capabilities. These improvements address performance issues experienced by agencies with large numbers of stations and devices while providing better search and navigation functionality.
How it works:
Enhanced List Views: Navigate to Stations or Devices sections to see paginated, optimized lists
Pagination Navigation: Use page controls to browse through records in groups of 20
Filter Application:
Stations: Filter by Station Number, Address, or Phone
- Open image-20250610-173748
Devices: Filter by Name, Device Serial #, or Manufacturer
- Open image-20250610-173606.png
Partial Text Matching: Enter partial text in filter fields to narrow results
Active Filter Management: View applied filters and clear/reset as needed
Optimized Loading: Experience faster initial page loads with targeted data retrieval
Detail Access: Select records for editing to load complete station/device information
Search Efficiency: Quickly locate specific records using multiple filter criteria
6. QA Status Filter Option
This enhancement adds a "NULL/Is Empty" filter option to the QA Status dropdown in the Incident List view, addressing a gap in QA workflow reporting. This new filter allows users to identify incidents that have never entered the QA process, improving visibility into potential missed records and enhancing quality assurance oversight.
Use Cases:
QA Workflow Auditing: Identify incidents that bypassed standard QA processes
Compliance Monitoring: Ensure all required incidents enter appropriate QA workflows
Performance Analysis: Track QA workflow coverage and identify improvement opportunities
Administrative Review: Regular monitoring of unprocessed incidents for quality oversight
How it works:
Filter Access: Navigate to Incident List and locate the QA Status dropdown filter
Option Selection: Choose "NULL/Is Empty" from the QA Status filter options
- Open image-20250610-174314.png
Results Display: View incidents where QA status is NULL or empty, indicating no QA workflow entry
Combined Filtering: Use alongside other filters (date ranges, incident types, etc.) for targeted analysis
Gap Identification: Identify potential workflow gaps or missed QA assignments
Saved Views: Include the NULL/Is Empty filter in saved views for regular monitoring
Dynamic Updates: Filter results update immediately upon selection without page refresh
7. Apparatus Status Filtering
This enhancement improves apparatus management in ePCR by implementing intelligent status-based filtering for apparatus dropdown selections. The system now automatically filters apparatus based on their current operational status, ensuring only active, in-service units are available for assignment while maintaining complete historical data integrity.
How it works:
Dropdown Filtering: Navigate to Response > Apparatus > Add to see only active, in-service units
Status Validation: System validates apparatus status before displaying in selection list
Real-time Updates: Status changes (In Service ↔ Out of Service) immediately affect dropdown availability
Historical Integrity: Previously assigned apparatus remain visible in historical incidents regardless of current status
Multi-Status Exclusion: System excludes:
Archived apparatus
Deleted apparatus
Out-of-service apparatus
Active Unit Display: Only apparatus with "In Service" status appear for new incident assignments
Immediate Reflection: Changes to apparatus status update dropdown options without system restart
Active/In-Service Units: Available in dropdown for new incident assignments
Archived Units: Hidden from dropdown, preserved in historical data
Deleted Units: Hidden from dropdown, preserved in historical data where applicable
Out-of-Service Units: Hidden from dropdown until status changed to active
Historical incidents maintain original apparatus assignments
Past data remains accessible and accurate
Unit status changes don't affect completed incident records
Reporting maintains full historical accuracy
8. Vehicle Dispatch Location Field
This enhancement improves the Vehicle Dispatch Location field functionality by implementing a hybrid input control that supports both free text entry and predefined location selection. The field now accommodates NEMSIS requirements for capturing ambulance location at dispatch time while providing flexible input options for various operational scenarios.
Input Options:
Free Text Entry: Custom locations for operational flexibility
EMS Stations: Select from configured station locations
Facilities: Choose from setup facility locations
How it works:
Field Access: Navigate to Vehicle Dispatch Location field in the ePCR form
Free Text Entry: Type directly into the field for custom locations (businesses, gas stations, etc.)
- Open image-20250610-175601.png
Dropdown Access: Use slider popup to access predefined EMS locations
Location Selection: Choose from configured stations, facilities, or other setup locations
Seamless Switching: Switch between free text and dropdown selection as needed
Character Limit: System enforces 100 character maximum per NEMSIS requirements
Save and Continue: Enter information and proceed with normal workflow
9. Crew Member Level (eCrew.02)
This enhancement enables crew members to edit their certification level directly within individual incident records, addressing scenarios where personnel operate under temporary licenses or elevated certifications that differ from their base personnel profile. This feature supports the State of Michigan's requirement for accurate documentation of the actual certification level used during specific incidents.
How it works:
Crew Modal Access: Open crew member details within the incident record
Certification Editing: Modify eCrew.02 Crew Member Level field as needed for specific incident
- Open image-20250610-175930.png
Temporary License Documentation: Select elevated certification level when operating under temporary licenses
Value Persistence: System saves edited certification level for the specific incident
Workflow Application: Field respects configured Hide, Error, and Warning rules
- Open image-20250610-175951.png
Report Generation: Updated certification level appears in PDF reports and XML output
Personnel Profile Integrity: Changes don't affect base personnel profile settings
10. Custom Value - Sort Orders
This enhancement allows for prioritized organization of custom values according to specific workflow requirements, improving user experience and data entry efficiency. Introducing customizable sort ordering for values in custom questions, giving system administrators complete control over how dropdown options are displayed to end users.
How it works:
Access Configuration: Navigate to Custom Elements and when adding or editing a custom question that is Text/String Data Type, enable the Dropdown Field toggle.
Set Sort Values: Enter numeric values in the "Sort Order" field for each custom value (optional - defaults to 0 if left empty)
Use Auto-Numbering: Click the "+" button to automatically assign the next sequential number based on the highest existing value.
Validation Process: System validates numeric input and prevents non-numeric entries
Apply Sorting: Custom values display to end users in ascending numerical order based on Sort Order values
Handle Duplicates: Items with identical sort order values appear consecutively using existing sort logic
Default Placement: Values without sort order assignments automatically appear at the end of dropdown lists
Universal Display: Sort order applies consistently across all locations where custom questions appear (reports, modals, sections, groups)
11. Vendor Directory
Streamlining the Vendor Directory setup interface by removing non-functional fields that serve no purpose within ePCR operations. This cleanup eliminates confusion and simplifies the vendor configuration process by focusing only on fields that are actively used by the system.
How it works:
- Streamlined Setup Interface: Access Vendor Directory setup to see the cleaned interface with only functional fields displayed
- Reduced Configuration Complexity: Configure vendors without unnecessary fields that previously caused confusion
- Focused Data Entry: Enter only relevant vendor information that is actually used by ePCR operations
- Improved User Experience: Navigate a cleaner, more intuitive vendor setup process
- Maintained Functionality: All existing ePCR vendor-related functions continue to work normally with the remaining functional fields
12. Print Reports
Introducing enhanced logo management capabilities that provide users with greater flexibility in controlling header elements for EMS forms. This enhancement addresses layout issues by adding a "None" option alongside existing logo configuration choices, eliminating the need to create entirely new forms when logo removal is required.
How it works:
- Access Logo Options: Navigate to EMS Setup > Form and locate the header/logo configuration section
- Select "None" Option: Choose "None" from the expanded options list (Logo+Text, Header as Image, None)
- Save Configuration: Save the form settings to remove existing title and uploaded image elements
- Automatic Fallback: When "None" is selected and no header information is defined, system automatically displays call information and customer logo from Admin > Agency Setup on PDF first page
- Clean Output: Generate PDF reports with streamlined header layout without custom logos or titles
- Easy Restoration: Switch back to Logo+Text or Header as Image options at any time to restore custom branding
13. Custom Element - Memo Field
Introducing the ability to toggle between memo and regular string field presentation for existing custom questions with string data type. This enhancement provides flexibility in form layout optimization without affecting data storage or existing field configurations, allowing users to adapt field display based on space requirements and user experience needs.
How it works:
- Access Custom Element Settings: Navigate to existing custom questions with string data type configuration
- Locate Memo Toggle: Find the memo option toggle control in the custom element setup interface
- Switch Display Mode: Toggle between memo (multi-line text box) and regular string field presentation

- Save Configuration: Apply changes to update how the field appears in reports and forms
- Verify Display: Review the updated field presentation in reports while maintaining all existing data
- Optimize Layout: Use memo format for fields requiring more text space or regular format for compact display
- Maintain Functionality: Continue normal report printing and XML export operations without any impact from display changes
14. Handtevy - Import Mapping
Enhancing the Handtevy integration with improved mapping capabilities that extend beyond hardcoded configurations to include customer-specific EMS setup configurations. This enhancement ensures comprehensive data import by implementing a robust fallback system that captures all relevant medications and treatments for each agency's unique configuration requirements.
How it works:
- Primary Mapping Check: System first attempts to match medication and treatment codes using the existing hardcoded configuration
- Fallback Mapping: If codes are not found in hardcoded list, system automatically checks customer-specific EMS setup configuration
- Successful Mapping: Located codes are properly mapped and imported into the system regardless of mapping source
- Complete Data Import: All selected medications and treatments from Handtevy now appear correctly in reports
- Patient Type Validation: System ensures accurate import for both adult and pediatric patient scenarios
- Error Prevention: Enhanced logic prevents data loss that previously occurred with unmapped codes
- Seamless Integration: Import process continues to work normally while providing more comprehensive data capture
15. Weight display field
Enhancing the weight field user experience by implementing dual display fields for both kilograms and pounds with automatic bidirectional conversion. This enhancement replaces the toggle-based weight component with a more intuitive dual-field approach that eliminates the need for providers to click buttons or switch between units, while maintaining NEMSIS compliance and workflow integrity.
How it works:
- Dual Field Presentation: Weight field appears as two stacked input fields (KG and pounds) on forms
- Bidirectional Conversion: Enter value in either field to automatically calculate and populate the corresponding unit

- NEMSIS Validation: System validates only the KG field against NEMSIS rules (0.1 kg minimum, 999.9 kg maximum)
- Workflow Processing: All workflow rules (error, warning, default, hide) operate exclusively on the KG field value
- Hide Rule Application: Hide rules affect both KG and pounds fields simultaneously as a unified control
- Export Handling: Data export outputs KG values only while maintaining NEMSIS compliance
- PDF Generation: PDF reports display weight in combined kg/lbs format for comprehensive documentation
- Validation Feedback: Error messages and validation alerts reference the KG field while maintaining user-friendly dual display
16. Patient Activity and Pulse Rhythm Management
Expanding Field Customization capabilities with comprehensive Patient Activity management and Pulse Rhythm sort order control. This enhancement adds Patient Activity to Field Customization with full value display and custom value creation through EMS Setup, while introducing Pulse Rhythm (eVitals.13) sort order capabilities.
How it works:
- Access Field Customization: Navigate to Field Customization interface to locate Patient Activity and Pulse (HR) Rhythm sections
- Patient Activity Management: View all available Patient Activity values and activate those meeting ICD10 pattern constraints.
- Create Custom Values: Use EMS Setup > Custom Elements to add agency-specific Patient Activity values with pattern validation.
- Pulse Rhythm Organization: Configure sort order for the three pulse rhythm values based on clinical workflow preferences.
- Activation Control: Manage which values are available for use in forms and reports across both field types
- Save Configuration: Apply all customization settings for consistent display and functionality across the system