1. QA/QI - AI Generated Feedback Integration for QA/QI Module
What - The QA/QI module now integrates AI-generated feedback capabilities that automatically analyze Patient Care Reports and provide comprehensive review comments displayed alongside ePCR reports. The system generates detailed feedback ranging from approval confirmations to identification of medication administration errors, protocol compliance issues, and documentation gaps, with comprehensive comment management and seamless integration with existing QA/QI workflows including chronological tracking and expandable interface options.
Why - This enhancement was implemented due to customer request to improve QA/QI efficiency and consistency by providing automated analysis of patient care documentation, enabling quality assurance teams to identify potential issues more comprehensively while maintaining established review processes and ensuring protocol compliance validation.
How - Configure and utilize AI-generated QA/QI feedback through enhanced module capabilities:
Reach out to your Client Success Manager to enable "Enable QA/QI AI Reviews" setting in system configuration
Configure active protocol in Setup → External Resources for AI analysis capabilities
System automatically uploads protocol and XML files to support AI analysis
AI analyzes completed ePCR reports against established protocols and generates comprehensive feedback
View AI comments through multiple access points: AI Comments column in QA/QI incident list with "Show More" functionality, side-by-side display with ePCR reports, and expandable tab interface for full details
Access AI comments directly from ePCR reports through "Open Comment" functionality
Note: AI comments appear chronologically with most recent at top including timestamps
Note: All AI comments are stored in database for persistence and audit trail capabilities
Note: Scrollable comment areas accommodate lengthy analysis and recommendations
Use Case - A QA/QI supervisor reviewing a cardiac arrest response can immediately see AI-generated feedback identifying that epinephrine was administered at 0.1mg instead of the protocol-required 1mg dose, along with analysis noting the delay between initial rhythm check and first defibrillation. The AI feedback appears alongside the ePCR, highlighting these critical care deviations and referencing specific protocol sections, allowing the supervisor to focus their review on identified issues rather than manually analyzing every aspect of the lengthy cardiac arrest documentation for potential problems.
2. Return Trip - New Feature for Efficient Return Transport Documentation
What - A new Return Transport feature streamlines the creation of return journey ePCRs by automatically populating relevant information from initial transports while maintaining compliance requirements for fresh clinical documentation. The system allows crews to flag initial transports for return trips, automatically generates return ePCRs with swapped location information, and pre-populates patient data while ensuring separate clinical assessments, with enhanced destination field visibility and dynamic patient tracking capabilities.
Why - This enhancement was implemented due to customer request to address the inefficiency of completing two separate ePCRs for related return transports, reducing documentation burden for EMS crews while maintaining medical protocol compliance requirements for fresh clinical assessment and documentation on return journeys.
How - Access and utilize return transport functionality through enhanced ePCR workflows:
Administrator enables "Enable Return Transport Feature" in EMS Setup → General
During initial transport, check "Will require return transport" toggle to flag patients needing return trips
Access "Add Return Transport" button to view modal displaying flagged patients without completed return trips
Select patient from available return transport candidates to create new ePCR with automatically populated information
Scene and destination locations are automatically swapped from original transport
Patient management information including name, DOB, medications, and allergies pre-populate from original transport
Destination address fields remain always visible and editable for flexible address management
Complete fresh clinical documentation including vitals, assessments, narratives, and signatures as required
Note: Clinical data is NOT transferred to ensure compliance with fresh assessment requirements
Note: If return transport ePCR is deleted, patient reappears in available return transport list
Use Case - An EMS crew transports a dialysis patient from their residence at 123 Oak Street to the dialysis center at Regional Medical Plaza, flagging the transport for return trip. After the patient's dialysis treatment, the crew uses "Add Return Transport" to create a return ePCR that automatically sets Regional Medical Plaza as the scene location and 123 Oak Street as the destination, with the patient's name, date of birth, and medication list already populated. The crew then documents fresh vital signs, conducts a new patient assessment, and writes a narrative specific to the return journey, ensuring complete compliance while eliminating redundant data entry for patient demographics and transport logistics.
1. RIT - Support Custom Questions in RIT Setup/Documentation
What - RIT (Rapid Intervention Tool) functionality has been expanded to support custom questions tied to specific groups including Vitals, Procedures, Medications, Airways, and LAB, enabling comprehensive data collection capabilities during RIT setup and documentation. The enhancement provides group-specific associations with recurrence functionality while maintaining data persistence across RIT creation, editing, import, and report completion workflows.
Why - This enhancement was implemented due to customer request to extend RIT capabilities with organization-specific data collection requirements, allowing EMS agencies to capture additional critical information during rapid intervention scenarios while maintaining the efficiency and speed of the RIT workflow.
How - Configure and utilize custom questions within RIT workflows:
Set up custom questions tied to specific groups: Vitals, Procedures, Medications, Airways, or LAB
Access RIT configuration where custom questions associated with supported groups appear as available fields
Select and configure relevant custom questions within RIT setup to include in rapid intake workflow
During RIT documentation, complete custom questions that were included in the setup configuration
Utilize both PN (Positive/Negative) and NV (Narrative/Value) field types for custom questions
Use recurrence functionality for custom questions requiring repeated entries within the same session
Note: Only active custom questions appear in RIT setup, with deactivated questions hidden from new configurations
Note: Custom question data persists throughout RIT creation, editing, and report completion workflows
Use Case - An EMS agency responding to cardiac arrest calls can configure custom questions in the LAB group such as "Point-of-care glucose level" and "Lactate measurement" that appear during RIT documentation, allowing paramedics to quickly capture critical lab values alongside standard intervention data. These custom fields integrate seamlessly with the existing RIT workflow, enabling comprehensive patient data collection during high-stress emergency situations while maintaining the rapid documentation capabilities essential for effective patient care.
2. Import Hospital Capability from Vendor Setup
What - Hospital Capability field filtering has been enhanced to dynamically display only designations configured for selected facilities in the Vendor Directory, improving decision-making and clinical accuracy by showing relevant facility capabilities based on hospital-specific designations. The system maintains data persistence for existing reports while providing intelligent filtering for new transport documentation with fallback logic for facilities without configured designations.
Why - This enhancement was implemented due to customer request to improve clinical decision-making during patient transport by ensuring only relevant hospital capabilities are displayed based on the selected facility's actual designations, reducing confusion and improving accuracy of transport destination selection.
How - Access enhanced hospital capability filtering through improved transport documentation:
Configure Designations field in Vendor Directory under EMS Setup for each hospital facility
Select transport destination in "Transported To" field during patient documentation
Hospital Capability field automatically filters to show only designations configured for selected facility
When multiple designations exist for a facility, all configured options appear in dropdown
If no designations are configured, all available Hospital Capability options display as fallback
Hospital Capability selections are preserved in existing reports regardless of subsequent vendor configuration changes
Note: System uses the same enumeration list between Vendor Directory Designations and Hospital Capability fields
Note: Data integrity is maintained for both In Progress and Completed reports
Use Case - When transporting a trauma patient, EMS crews selecting "Regional Medical Center" as the destination will only see relevant capabilities like "Trauma Center - Level II" and "Emergency Department" in the Hospital Capability dropdown, rather than irrelevant options like "Labor and Delivery" or "Pediatric ICU." This focused selection helps crews accurately document the specific facility capability that influenced their transport decision, ensuring appropriate patient placement and improved clinical decision support during emergency transport situations.
3. Easy Staff - Assign Role Based on Position from EasyStaff
What - Automated Response Role assignment has been implemented for the Easy Staff integration, using Position data received from the API to automatically populate the eCrew.03 Crew Member Response Role field. The system provides hardcoded position-to-role mapping for four predefined position types while preserving existing workflow functionality for manual crew additions and maintaining integration isolation.
Why - This enhancement was implemented due to customer request to reduce manual data entry and speed up documentation workflows by automatically assigning appropriate response roles based on personnel positions received from the Easy Staff integration system.
How - Response roles are automatically assigned based on Easy Staff position data:
Easy Staff integration receives personnel data including Position field through API calls
System evaluates Position field value against predefined mapping criteria for each imported crew member
"Officer" and "Chief Officer" positions automatically assigned "Primary Patient Care Giver - At Scene" (2403011)
"Driver" position automatically assigned "Driver/Pilot-Response" (2403001)
All other positions (Nozzle, Hydrant, etc.) assigned "Other Patient Caregiver - At Scene" (2403007)
Blank or null position values result in blank response roles, preserving workflow flexibility
Note: Hardcoded mapping takes precedence over default value workflows for imported crew members
Note: Default value workflows remain active for manually added crew members
Note: Changes are specific to Easy Staff integration without affecting other personnel import systems
Use Case - When Easy Staff imports crew data showing Captain Johnson with "Chief Officer" position and Firefighter Smith with "Driver" position for an emergency response, the system automatically assigns Captain Johnson as "Primary Patient Care Giver - At Scene" and Firefighter Smith as "Driver/Pilot-Response" in the eCrew documentation. This eliminates manual role assignment for imported personnel while ensuring accurate NEMSIS compliance and proper crew role documentation for the responding unit.
4. Vitals - Autocalculate Revised Trauma Score (RTS) from GCS, RR, and SBP
What - Automatic calculation of the Revised Trauma Score (RTS) has been implemented based on patient vital signs including Glasgow Coma Scale (GCS), Systolic Blood Pressure (SBP), and Respiratory Rate (RR), providing healthcare providers with immediate trauma severity assessment using the standardized RTS weighted formula. The system offers real-time calculation with dynamic score updates and clinical range conversion for accurate trauma scoring.
Why - This enhancement was implemented due to customer request to improve the speed and accuracy of trauma assessment by providing immediate RTS scoring, enabling faster clinical decision-making and appropriate care prioritization through automated calculation of this critical trauma assessment tool.
How - RTS calculation is automatically performed using standardized clinical parameters:
Enter patient Glasgow Coma Scale (GCS), Systolic Blood Pressure (SBP), and Respiratory Rate (RR) values
RTS score appears immediately in patient record following data entry completion
Dynamic updates occur automatically when any component vital signs are modified
Note: System provides immediate score updates for real-time clinical assessment
Note: Compatible with existing workflow functionality for visual indicators and clinical alerts
Use Case - A paramedic treating a motor vehicle accident victim enters GCS of 8, SBP of 70, and RR of 32, and the system immediately calculates and displays an RTS score of 4.89, indicating severe trauma requiring immediate transport to a trauma center. When the patient's blood pressure improves to 95 mmHg after fluid resuscitation, the RTS automatically recalculates to 6.83, providing real-time assessment of the patient's improving condition and helping guide continued treatment decisions during transport.
5. Form - Add Station List to Vehicle Dispatch Location Dropdown Options
What - The eResponse.16 Vehicle Dispatch Location field has been expanded to include the Stations list alongside existing Vendor Directory and free text options, providing three distinct data sources for populating dispatch locations. The enhancement implements priority logic favoring Stations over Vendors when duplicate names exist and includes GPS coordinate integration for accurate location documentation.
Why - This enhancement was implemented due to customer request to eliminate unnecessary duplication where Stations were only available if built as Vendors, while providing comprehensive dispatch location options and ensuring accurate GPS coordinates are captured for dispatch documentation.
How - Access enhanced dispatch location options through expanded field functionality:
Navigate to eResponse.16 Vehicle Dispatch Location field in ePCR form
Dropdown displays options from three sources: Stations list, EMS-type Vendors, and free text entry
Priority logic ensures Stations take precedence when names match Vendors (case-insensitive)
Select Station from dropdown to automatically populate dispatch location and GPS coordinates
EMS vendor filtering displays only EMS-type vendors to maintain operational relevance
Use free text input when predefined options don't match actual dispatch location
Note: GPS coordinates automatically populate in Vehicle Dispatch GPS Location field when Stations are selected
Note: Selected information persists through page reloads, report completion, and export processes
Note: Station selections appear correctly in XML exports and printed reports
Use Case - When documenting an EMS response dispatched from Fire Station 7, crews can now select "Station 7" directly from the dropdown, which automatically populates both the dispatch location name and the precise GPS coordinates for the station. If both a Station 7 and a Vendor entry named "Station 7" exist in the system, the actual fire station entry takes priority, ensuring accurate location data while eliminating the confusion that previously required maintaining duplicate station entries in the Vendor Directory.
6. EMS Short Form - Add NERIS Impediment Narrative to EMS Short Form
What - The EMS Short Form (Fire Short Form) has been enhanced to include the NERIS Impediment Narrative section alongside the existing standard department narrative, ensuring complete report summaries are visible in short form views. The addition maintains consistent formatting and integrates seamlessly with current short form layout while appearing correctly in all print and export versions.
Why - This enhancement was implemented due to customer request to address the missing NERIS Impediment Narrative section from the EMS Short Form, ensuring consistency between full form and short form narrative sections for comprehensive report review capabilities.
How - NERIS Impediment Narrative is automatically displayed in enhanced EMS Short Form:
Access EMS Short Form (Fire Short Form) interface for report summary viewing
Enhanced narrative section displays both standard department narrative and NERIS Impediment Narrative together
Review complete narrative content including NERIS impediment details directly within short form
Consistent formatting maintains display standards matching other narrative sections
Seamless integration works with existing short form workflows without additional configuration
Note: Enhancement appears correctly in all print and export versions of EMS Short Form
Note: Users can access all narrative components for comprehensive incident documentation review
Note: Addition maintains existing short form layout and functionality
Use Case - Fire department officers reviewing incident reports can now see both the standard incident narrative and any NERIS impediment information (such as "Delayed response due to heavy traffic on Main Street" or "Access restricted by police scene control") directly in the short form summary. This comprehensive view eliminates the need to switch between short and full form views to understand complete incident circumstances, improving review efficiency while ensuring all critical narrative information is readily accessible for supervisory review and documentation purposes.
7. EMS Setup - Add Hover Help on ePatient.25 Setting
What - Contextual hover help has been added to the ePatient.25 setting in EMS Setup > General, providing administrators with critical guidance about proper timing for feature activation and state coordination requirements. The enhancement displays compatibility warnings to prevent premature activation that could cause file compatibility issues with state reporting systems.
Why - This enhancement was implemented due to customer request to prevent configuration errors that could disrupt state reporting workflows by providing just-in-time guidance about the importance of coordinating ePatient.25 activation timing with state system compatibility requirements.
How - Hover help provides contextual guidance for proper ePatient.25 configuration:
Navigate to EMS Setup → General to access ePatient.25 setting
Hover over setting to display informative tooltip with activation guidance
Review state coordination information indicating states will notify when feature should be enabled
Compatibility warning alerts about potential file compatibility issues with premature activation
Just-in-time information provides relevant guidance exactly during configuration process
Note: Hover help maintains clean interface while offering critical configuration guidance
Note: Warning helps prevent premature activation that could affect NEMSIS data exchange
Note: Feature provides error prevention without cluttering the administrative interface
Use Case - An EMS administrator reviewing system settings sees the ePatient.25 option and hovers over it to learn that premature activation could cause file compatibility issues with their state's NEMSIS data exchange system. The hover help explains that the state will coordinate activation timing to ensure system-wide compatibility, preventing the administrator from enabling the feature too early and potentially disrupting the department's ability to submit compliant reports to state agencies until proper coordination occurs.
Fixes
1. AI - AI Transcription Fixes for Social Security Number and Medication Dosage Display
What - AI transcription functionality has been enhanced to address data processing issues affecting Social Security Number display and medication dosage accuracy, ensuring complete SSN display by removing hyphen formatting restrictions and accurate medication dosage capture including decimal values in the eHistory section. These fixes improve data integrity and clinical accuracy in AI-generated reports.
Why - This enhancement was implemented due to customer request to resolve data truncation issues where Social Security Numbers were displaying only partial digits and medication dosages were showing incomplete decimal values, potentially affecting clinical decision-making and data accuracy in AI-generated reports.
How - Enhanced AI transcription processing addresses data accuracy issues:
SSN processing now ignores hyphen formatting and processes all numeric characters for complete display
Full 9-digit Social Security Numbers appear in both AI data generation and final reports
Medication dosage parsing accurately captures decimal values from transcription content
Decimal values (e.g., 2.5) are fully preserved and displayed in eHistory section without truncation
Data validation ensures transcription content matches original for both SSN and medication information
Database integrity maintained without affecting existing database records
Note: Fixes address hyphen-separated SSN format that previously caused truncation
Note: Medication dosage improvements specifically target decimal value processing in transcription workflows
Use Case - When AI processes a patient transcription containing "Social Security Number 123-45-6789" and medication history including "Metoprolol 2.5 mg twice daily," the enhanced system now correctly displays the complete SSN "123456789" and the full medication dosage "2.5 mg" in both the AI data generation and final reports. Previously, these would have appeared as "123" and "2 mg" respectively, potentially leading to medication errors or patient identification issues during clinical care and documentation review.
Video <br> New Features 1. AI-Powered Attachment Data Extraction in ePCR This feature introduces AI-powered image analysis within the ePCR attachment modal, allowing users to automatically extract structured patient data (e.g., name, DOB, ...
In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. Video New Features 1. Transfers What: This feature introduces a streamlined workflow for transferring electronic Patient Care ...
In order to provide you with more detailed information on our updates, we have broken the Release Notes down by module. Video Enhancements 1. QA/QI Notification Center What: Add the option for QA/QI automated emails to go to the Notification Center ...
Video 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 ...
In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. New Features 1. A completed checklist may now be deleted from the Checklist History An option was to delete completed checks from ...