Release Notes - ePCR Incident Documentation

Release Notes - ePCR Incident Documentation

Info
In order to provide you with more detailed information on our updates, we have broken the Release Notes down by module.




New Features

1. Form Builder for printing EMS reports.

What:  This new feature allows those with the permissions to create and manage EMS print forms by creating customizable templates with all ePCR fields, EMS tables and custom questions.
Why: This provides greater flexibility in how reports are generated and printed, instead of relying solely on hardcoded print format.
How: With four new permissions added to the ePCR bucket, one can access the form builder from the Incident Documentation. From there, you can create new templates or modify existing ones. Once saved, you can select which template to use when printing the report.  If no selection is made, the default system form will be used.  NEMSIS exports will always use the default system form.









2.  Other Agency on scene drop-down and Resource Setup.

What:  The EMS setup has a new setup page that allows users to manage a list of frequently encountered agencies by replacing the free-text input with a pre-configured drop-down list.
Why:  This allows users to predefine aiding agencies.
How:  A new setup area in EMS Setup titled Other Agencies At Scene will allow you to add, edit, or delete agencies.  When users are completing a report, they will be able to select an agency from a drop-down list in the Scene Responder grid.









3.  Add sub-sections to current EMS sections.

What:  The ability to create and assign custom sub-sections to existing EMS sections.
Why:  This provides greater flexibility in organizing EMS reports by grouping related fields under structured sub-sections.
How:  From the Custom Sections within EMS Setup, select an existing EMS section.  Selecting the + at the top right of ePCR subsections will create a new subsection and then define its fields.









4.  Import Crew members when pulling information from Fire Incidents.

What:  Allows users to import crew members from the NFIRS apparatus assignment into the ePCR report.
Why:  To reduce duplicate documentation for clients who document NFIRS first and then complete the ePCR.
How:  When using the CAD button, the system will pull the crew assigned to the apparatus documented in the NFIRS Incident Report.









5.  Incident Summary Feature/Radio Report.

What:  The incident summary feature provides a chronological overview of critical event timestamps that allows you to review and verify key milestones, medications, procedures, and response times quickly without navigating multiple sections.
Why:  To streamline EMS documentation, improving efficiency and patient care quality by faster documentation review.
How:  A dedicated button, when clicked, opens a modal displaying a chronological timeline of key events that will allow you to view and navigate events to edit.









Enhancements

1.  Remove the Required Toggle.

What:  The Required toggle from field customization has been removed; users can no longer mark non-NEMSIS fields as required through field customization.
Why:  To streamline field customization and encourage using workflows to enforce required fields.  This ensures that all required field logic is managed centrally within workflows, reducing confusion and improving consistency.
How:  From the Workflows setup section, create or edit a workflow rule to enforce required fields based on specific conditions.


2.  Add Laboratory Fields to RIT Setup.

What:  The ability to create lab fields within RIT, improving documentation and workflow.
Why:  With the introduction of laboratory testing in ambulances, users need the ability to document lab results efficiently within RIT.
How:  Navigate to the RIT setup, edit an existing template or create a new one, then enable laboratory fields.





3. Adjust mapping for response times coming from NFIRS/Fire.

What:  This update improves the mapping of response time when importing data from NFIRS through the CAD download.
Why:  Previously, the Clear time from NFIRS was automatically mapped to Unit Left Scene in ePCR, which did not always reflect the correct sequence of events. With this enhancement, Patient Left Scene will now be prioritized over Clear Time, ensuring more accurate data alignment.
How:  When importing an incident, Download CAD from NFIRS, the system will check for time fields.  If "patient left scene" exists "unit left scene" will populate times in ePCR.  If "patient left scene" is missing then "clear" time is used instead.  If both are missing, then no value will import.









4.  Do not auto-fill "Not Recorded" when Arrived at patient is missing.

What:  This enhancement refines the "Prior to Arrival" (PTA) functionality by ensuring that when "Arrived at Patient Date/Time" is not documented, PTA remains blank instead of defaulting to "Not Recorded".
Why:  This prevents incorrect autofill behavior and allows you to control how missing values are handled.
How:  
  1. Automatic Calculation of PTA When "Arrived at Patient" Is Documented:

    • If both "Arrived at Patient" and another procedure/med/vital timestamp exist, PTA is calculated normally.

    • If timestamps are the same → PTA is set to "No."

    • If timestamps differ → PTA is set to "Yes" or "No" accordingly.

    • Modifying the timestamp by +1 or -1 second will automatically update the PTA field.

  2. Handling Missing "Arrived at Patient" Data:

    • If "Arrived at Patient" is missing → PTA remains blank.

    • Users can manually update PTA to any available option.

  3. PTA Calculation When Importing from RIT:

    • If timestamps are available → PTA is calculated normally.

    • If timestamps are missing but RIT provides a default PTA value, it is used.

    • If timestamps are missing and no default is provided, PTA remains blank.



5.  Improvements to the comments components with the QA/QI.

What:  The comments component has been enhanced by addressing the UI/UX issues that affected usability, including text visibility, button placement, and preventing unintended data loss.
Why:  These improvements significantly enhance your experience, making it easier to interact and manage comments efficiently.
How:  You can expand the text area while maintaining full visibility of the content.  The send button will remain inside the modal container regardless of the modal's size or position.  Finally a warning message will appear if you click anywhere outside the comment modal for any unsaved comments asking if you want to discard or keep their changes before exiting.









6.  Expand the dropdown value character limit.

What:  This update increases the character limit for drop-down values in Custom Questions, allowing for longer, more descriptive options.
Why:  To improve clarity and flexibility by ensuring that dropdown selections are more informative while remaining NEMSIS-compliant.
How:  When Admin adds a Custom Question with a drop-down data type, the value (displayed text) can now be up to 100 characters.


7.  Add Assessment Fields to Workflows

What:  The eExam.03 (Date/Time of Assessment/Exam) is now available in workflows.
Why:  This ensures documentation follows the same behavior as other date/time fields inside grids (e.g., Medications, Procedures, Devices).
How:  When creating a workflow, select eExam.03 and configure the workflow rules (Error, Warning, or if applicable, Hide).







Fix

1.  GNIS Code Mapping for St Peters & St Charles

What:  This update resolves an issue where the Incident City (eScene.17) field flags red when completing an ePCR, due to CAD-imported city names not matching the system's required GNIS values.
Why:  This fix streamlines ePCR completion, reducing unnecessary manual corrections and improving CAD integration accuracy.
How:  When importing CAD data. cities will automatically converted to GNIS Mapping Codes allowing the ePCR to pass validation.


2.  GNIS Rename "Fort Campbell Division" to "Fort Campbell"

What:  This update modifies the GNIS city name for Fort Campbell Division in Kentucky to align with client preferences and standard naming conventions.
Why:  This fix ensures consistency and eliminates confusion when documenting incidents in Fort Campbell.
How:  Users selecting Fort Campbell Division will now see it as Fort Campbell, any CAD imports referencing Fort Campbell Division will automatically convert to Fort Campbell.






    • Related Articles

    • Release Notes - August 2024

      VIDEO Mobile Application Current Version [iOS 5.6.3/Android 6.7.8] Enhancements Expanded Status Log List: The initial status log list now opens in an expanded view by default, enhancing usability. Preplan Details Title: The ID number has been removed ...
    • Release Notes - December 2023

      App Current Version: iOS: 5.5.0 Enhanced unit list visualization. NFIRS id information added to dispatch details view. Enhanced the "last position known" unit tracking timestamp to be more easily identified. Android: 6.5.8 Optimized incident list ...
    • Release Notes - June 2024

      Video App Current Version: iOS 5.6.1: NEW FEATURE: Added a ruler feature for ArcGIS maps to measure distances. NEW FEATURE: Incident command feature now available from the dispatch details view. NEW FEATURE: Enhanced routing feature with step-by-step ...
    • Release Notes - February 2024

      App Current Version: iOS: 5.5.4 Added radio channel field on dispatch details view. Reworked menu usability. Now you can pin your favorite/most used sections from to shortcuts! Updated menu options reflect the new Scheduling menu and sub-menu. Unit ...
    • Release Notes - March 2024

      Video App Current Version: iOS: 5.5.5 Added a new setting to manage hydrant marker size on the map. Refresh mechanism for all modules. Simply pull down on the screen to refresh. Outside resources will open directly into a browser. Enhanced ability to ...