5. Enhanced QA/QI List Filtering and Columns

• What - The QA/QI incident list now includes three additional clinical data fields that can be added as columns and used for filtering: Procedures (eProcedures.03), Medications (eMedications.03), and Cardiac Arrest (eArrest.01). These fields are fully integrated into the existing configurable incident list view infrastructure, allowing you to customize your list display and create filtered views based on specific clinical criteria. The filters can be applied independently to focus on a single clinical element or combined to create complex categorization scenarios, such as viewing all cardiac arrest incidents where specific procedures were performed. All custom view configurations, including the new columns and filters, persist across page refreshes and user sessions, ensuring a consistent workflow experience. The Clear Filter option works seamlessly with these new fields, restoring the full incident list view without errors or data loss.
• Why - This enhancement was implemented due to customer requests for more efficient QA/QI workflow management and reviewer assignment capabilities. Agencies reported that they needed to categorize incidents into distinct review buckets based on clinical criteria such as specific procedures performed, medications administered, or cardiac arrest cases, and then assign appropriate QA reviewers based on their clinical expertise and the type of review required. Without the ability to filter by these critical clinical fields, QA coordinators were manually reviewing large numbers of incidents to identify cases requiring specialized review, creating significant workflow inefficiencies. By leveraging the existing configurable list infrastructure and adding these three most-requested clinical fields, the enhancement enables agencies to streamline their QA assignment processes without requiring extensive system restructuring.
• How - Configure these new fields in your QA/QI list custom views
  • Navigate to QA/QI > Incident List to access the enhanced list view
  • Click the Custom View configuration option to modify your list display
  • Add any of the three new columns to your view: Procedure Name (eProcedures.03), Medication Name (eMedications.03), or Cardiac Arrest (eArrest.01)
  • Configure filter criteria using the new fields by selecting them from the available filter options
  • Apply a single filter to create focused incident buckets (e.g., filter by Cardiac Arrest = "Yes" to view only cardiac arrest cases)
  • Combine multiple filters for complex scenarios (e.g., filter for cardiac arrest incidents where epinephrine was administered)
  • Click Clear Filter to restore the full incident list view when needed
  • Save your configured views for repeated use in your QA workflow
  • Note: Your custom view configurations will persist across sessions, so you don't need to reconfigure each time you access the list
  • Note: All three fields work independently and can be combined in any configuration to meet your agency's specific QA categorization needs
• Use Case - A QA coordinator at a busy EMS agency needs to assign weekly chart reviews to specialized reviewers based on clinical criteria. The cardiac arrest specialist reviewer needs all resuscitation cases, the airway management expert needs cases involving advanced airway procedures, and the medication safety reviewer needs cases with specific controlled substance administrations. The coordinator navigates to the QA/QI Incident List and creates a custom view filtering for Cardiac Arrest = "Yes" to generate a bucket of 12 cardiac arrest cases from the past week, which are immediately assigned to the cardiac arrest specialist. Next, they create another view filtering by Procedure Name containing "endotracheal intubation" to identify 8 advanced airway cases for the airway expert. Finally, they filter by Medication Name containing "fentanyl" or "morphine" to find 15 cases requiring medication safety review. These saved custom views can be reused each week, dramatically reducing the time spent manually sorting through hundreds of incident reports to identify cases requiring specialized review and ensuring that each incident is assigned to the most appropriate reviewer based on the clinical interventions documented.
  

6. Field Name Search in EMS Field Customization

• What - The EMS Field Customization interface now includes a dedicated field name search bar positioned in the header alongside the existing NEMSIS Section search bar. This new search functionality enables you to type field names directly and see real-time filtering of the field list as you enter characters, matching the proven search behavior already available in the Workflows section. The field name search works independently or can be combined with the NEMSIS Section search to narrow results using both criteria simultaneously. As you type in the Field search bar, the field list updates immediately to display only matching fields, and you can refine your search by continuing to type or broaden results by deleting characters. Both search bars remain available to support different search approaches, whether you prefer searching by specific field names or browsing by NEMSIS sections.
• Why - This enhancement was implemented due to customer requests highlighting that the vast majority of administrators search for fields by their field names rather than by NEMSIS Section when configuring field customizations. Usage patterns indicated that most customers know the specific field they want to configure and need to locate it quickly, but the existing interface only provided NEMSIS Section filtering, requiring administrators to remember which section contained their target field or browse through multiple sections to find it. This limitation created workflow inefficiencies and frustration, particularly when configuring commonly-used fields or making quick adjustments. By adding field name search functionality that mirrors the successful implementation already proven in the Workflows section, the enhancement addresses the primary search pattern used by administrators and significantly improves efficiency when managing field configurations.
• How - Use the new field search functionality in Field Customization
  • Navigate to Incident Documentation > EMS Setup > Field Customization > EMS Field Customization
  • Locate the two search bars in the header section: the existing NEMSIS Section search and the new Field search bar
  • Click in the Field search bar and begin typing the name of the field you want to configure
  • View real-time filtering results as the field list automatically updates to show only matching fields
  • Continue typing to narrow results further or delete characters to broaden your search
  • Alternatively, use the NEMSIS Section search bar to filter by section if preferred
  • Combine both search methods by entering criteria in both search bars to filter by section and field name simultaneously
  • Click the Clear option in either search bar to restore the full field list
  • Select and configure your filtered fields with improved efficiency
  • Note: The search functionality performs identically to the field search in the Workflows section for consistency
  • Note: Both search bars remain available so you can use whichever search method best fits your workflow
• Use Case - An EMS agency administrator needs to configure several specific fields across different NEMSIS sections to support a new clinical protocol for stroke assessment. Rather than remembering that the Cincinnati Stroke Scale field is in section eExam, the Blood Glucose field is in section eVitals, and the Last Known Well field is in section eTimes, the administrator simply types "stroke" into the Field search bar and immediately sees all stroke-related fields filtered in real-time. They configure the Cincinnati Stroke Scale field, then clear the search and type "glucose" to quickly locate and configure the Blood Glucose field requirements. Next, they type "last known" to find the Last Known Well timestamp field without needing to navigate through multiple NEMSIS sections. What previously required browsing through multiple sections and scrolling through long field lists now takes seconds, as the administrator can jump directly to each needed field by typing its name. This streamlined approach is particularly valuable during time-sensitive configuration updates or when supporting field crews who need immediate clarification on how specific fields are configured in the system.
  

7. Crew Member Completing Report Field Added to QA Review

• What - The QA review interface now displays the "Crew Member Completing this Report" field (eOther.08) as the final element in the review section, positioned immediately after the signatures. This field shows which crew member completed the report documentation and supports full review workflow functionality consistent with all other fields in the QA review process. QA reviewers can now view the crew member information, add comments specific to report completion accountability, request corrections if the information is incorrect or requires clarification, and include this field in their overall approval decision. The field displays accurately retrieved crew member data and integrates seamlessly with existing QA review patterns, enabling reviewers to perform the same actions on this field as they can on any other reviewed element throughout the interface.
• Why - This enhancement was implemented due to customer requests identifying that the crew member completing the report was a critical data element missing from the QA review interface. QA reviewers need to evaluate report completion accountability as part of their comprehensive quality assurance process, including verifying that the appropriate crew member documented the incident and ensuring that report completion responsibilities are properly assigned and tracked. Without access to this field during the review process, QA coordinators could not fully assess documentation accountability or flag potential issues where incorrect crew members were listed as completing reports. By adding this field to the QA review interface with complete workflow functionality, reviewers can now perform thorough quality assurance evaluations that include accountability tracking for report completion.
• How - This field appears automatically in all QA reviews with no configuration required
  • Navigate to QA/QI and open any incident requiring quality assurance review
  • Scroll to the end of the QA review section, past all other reviewed elements including signatures
  • Locate the Crew Member Completing this Report field displayed as the final element in the review
  • Review the crew member information to verify who completed the report documentation
  • Click the Add Comment option to add notes specific to report completion accountability if needed
  • Use the Request Correction functionality to flag the field if the crew member information is incorrect or requires clarification
  • Include this field in your overall approval decision when completing the review workflow
  • Note: The field supports all the same review workflow operations available for other QA review fields
  • Note: This information helps verify that appropriate crew members are completing report documentation and supports accountability tracking across your QA program
• Use Case - A QA coordinator is reviewing a complex multi-casualty incident report involving three ambulance crews who responded to a motor vehicle accident with four patients. During the review, the coordinator needs to verify that the primary attending paramedic on the most critical patient completed the report documentation, as agency policy requires the highest-level provider on scene to complete reports for serious incidents. After reviewing all clinical documentation, medications, procedures, and signatures at the end of the QA review interface, the coordinator sees the Crew Member Completing this Report field showing that an EMT-Basic from a supporting unit completed the report rather than the lead paramedic. The coordinator adds a comment noting "Per agency policy, lead paramedic should complete MCI reports - please clarify crew assignment" and requests a correction to ensure proper documentation accountability. This visibility into report completion responsibility enables the QA coordinator to identify potential training needs around documentation policies and ensure that report completion duties are appropriately assigned based on crew qualifications and incident complexity, supporting overall quality improvement initiatives.
  

8. Improved Workflow Field Labels for Enhanced Clarity

• What - The workflow configuration interface now displays enhanced field labels in the condition builder that include additional descriptive terminology to clarify each field's purpose. The When field label now reads When/If to better convey that it represents the trigger condition being evaluated, the Condition field label now reads Condition/Is to indicate it defines the comparison operation being performed, and the Parameter field label now reads Parameter/Value(s) to clarify that it represents the expected input values that the condition evaluates against. These improved labels apply consistently across all workflow types including Default Value Workflows, Error Validation Workflows, and Warning Validation Workflows, providing contextual hints that help users understand workflow logic construction more intuitively without affecting any underlying workflow functionality or behavior.
• Why - This enhancement was implemented due to customer requests indicating that the original single-word field labels (When, Condition, Parameter) did not clearly convey their purpose and function to all users, particularly those new to the workflow system or building complex workflow rules. Administrators reported confusion when constructing workflow conditions because the labels provided minimal context about what information should be entered in each field and how the fields related to each other in the overall workflow logic. By adding alternative terminology that users naturally think of when building conditional logic—such as "if" for triggers, "is" for comparisons, and "values" for parameters—the enhanced labels reduce the learning curve and improve comprehension during workflow configuration, enabling administrators to build accurate workflow rules more efficiently and with greater confidence.
• How - The improved labels appear automatically in all workflow configurations with no action required
  • Navigate to Incident Documentation > EMS Setup > Workflows and select any workflow type (Default Value Workflows, Error Validation Workflows, or Warning Validation Workflows)
  • Click Add Group or Add Condition to access the condition builder interface
  • Observe the enhanced field labels: When/If, Condition/Is, and Parameter/Value(s)
  • Use the When/If field to select the trigger condition that represents when something occurs if specific criteria are met
  • Use the Condition/Is field to configure the comparison operation that defines the condition being evaluated
  • Use the Parameter/Value(s) field to enter the values that the condition evaluates against
  • Build your workflow rules with improved understanding of each field's purpose and function
  • Note: These label enhancements apply consistently across all three workflow types for a uniform experience
  • Note: The improved labels do not change any workflow functionality—they only provide additional clarity about field purpose
• Use Case - An EMS agency administrator is configuring a new Error Validation Workflow to ensure that crews document patient refusal signatures whenever the disposition is recorded as "Patient Refused Care." The administrator, who is relatively new to building workflows, accesses the workflow configuration interface and clicks Add Condition to begin constructing the validation rule. With the improved labels, they immediately understand that the When/If field is where they specify the trigger condition (Disposition equals "Patient Refused Care"), the Condition/Is field is where they define how to evaluate it (equals/is), and the Parameter/Value(s) field is where they enter the specific values to check against. The contextual hints provided by the enhanced labels eliminate the confusion they previously experienced when trying to determine what information belonged in each field, allowing them to successfully build the workflow rule on the first attempt without needing to reference documentation or contact support. This improved clarity is especially valuable when building complex workflows with multiple nested conditions and groups, where understanding the logical structure is critical to creating accurate validation rules.