Ad-Hoc Reporting Data Source Searchable Reference

• What - A new searchable reference is available for Ad-Hoc Reporting data sources and their associated fields. Users can search for data sources, field names, or keywords across the full list, with support for partial matches, fuzzy matches, and multiple keywords. Each button represents a reporting data source category, and matching terms are highlighted after a category is opened. 
• Why - This improvement makes it easier to locate available reporting fields, understand which data sources can be used when building reports, and identify fields that may still exist for historical reporting even if they are no longer active in the system.
• How -
  • Open the Ad-Hoc Reporting data source reference.
  • Use the Search bar to enter a data source, field name, or keyword.
  • Select a data source category button to open the related fields.
  • Review the highlighted matching terms after the category is opened.
  • Review any fields marked Deprecated carefully, as these fields no longer exist in the active system but may still be available in reporting for historical data.
  • For additional details on compatible data source combinations, see Ad-Hoc Reporting: Data Source Configuration.
• Use Case - A user building an ad-hoc report can search for a field name or keyword to quickly identify which data source contains the needed information, confirm whether that source can be used as a primary or child source, and review deprecated fields when working with historical reporting data.

Ad-Hoc Reporting Data Sources Article

Enhancements

AD HOC - Additional Reporting Columns for ePCR Procedure

• What - The ePCR Procedure Ad Hoc data source has been enhanced with additional NEMSIS-related procedure fields, including Size of Procedure Equipment - eProcedures.04, Procedure Authorization - eProcedures.11, Procedure Authorizing Physician - eProcedures.12, Vascular Access Location - eProcedures.13, and Notes. This enhancement adds reporting access to procedure equipment sizing, authorization details, authorizing physician information, vascular access location, and freeform procedure notes without changing the existing procedure-level row structure.
• Why - These additions improve procedure-level reporting by giving users more complete access to documented clinical procedure details for operational reporting, clinical review, audits, filtering, grouping, summaries, and data extraction workflows.
• How -
  • Navigate to Ad Hoc reporting.
  • Select the ePCR Procedure data source.
  • Add the following new columns as needed:
    • Size of Procedure Equipment - eProcedures.04
    • Procedure Authorization - eProcedures.11
    • Procedure Authorizing Physician - eProcedures.12
    • Vascular Access Location - eProcedures.13
    • Notes
  • Use the new columns with existing Ad Hoc capabilities such as filtering, grouping, sorting, criteria building, summary reporting, and exporting.
  • Procedure Authorization - eProcedures.11 and Vascular Access Location - eProcedures.13 are available as list-based fields for standardized reporting and filtering.
  • Existing users with access to Ad Hoc reporting and the ePCR Procedure data source automatically have access to these fields.
  • Existing reports remain compatible and are not affected by this enhancement.
• Use Case - A reporting user can create an ePCR procedure report that groups procedures by authorization type, filters records by vascular access location, reviews the authorizing physician tied to a procedure, and exports procedure notes for clinical review or audit preparation while maintaining the same procedure-level reporting structure already used in existing reports.

AD HOC - New “Incident Report Apparatus Narratives” Data Source

• What - A new Incident Report Apparatus Narratives Ad Hoc data source has been added, allowing users to report on narrative records associated with Incident Report Apparatus entries. This enhancement exposes apparatus-related narrative text and supports reporting where multiple narrative records may be associated with a single apparatus record.
• Why - This enhancement improves access to apparatus-level narrative information for incident review, operational analysis, and reporting workflows that require detailed narrative context alongside apparatus records.
• How -
  • Navigate to Ad Hoc reporting.
  • Select Incident Report Apparatus as the primary data source.
  • From the available child joins, select Incident Report Apparatus Narratives.
  • Add the available fields as needed:
    • ID
    • Narrative
  • Use the narrative data with existing Ad Hoc capabilities such as filtering, grouping, sorting, and tabular reporting.
  • Reports return associated narrative records tied to each apparatus entry in a one-to-many format.
  • Users with existing access to Ad Hoc reporting and the Incident Report Apparatus data source automatically have access to the new Incident Report Apparatus Narratives data source.
  • No new roles or permissions are required.
• Use Case - A reporting user can create an apparatus-focused incident report that includes each apparatus entry with its related narrative records, making it easier to review operational details, analyze incident activity, and include full apparatus narrative context in tabular reports.

AD HOC - New ePCR Airway Data Source

• What - A new ePCR Airway Ad Hoc data source has been added to expose key NEMSIS v3.5.0 airway fields for reporting, including Indications for Invasive Airway, Airway Complications Encountered, Suspected Reasons for Failed Airway Management, Decision to Manage Patient with Invasive Airway, and Invasive Airway Placement Attempts Abandoned. This data source is available as a child dataset of ePCR Reports and supports reporting on multiple airway records associated with a single ePCR.
• Why - This enhancement gives users access to airway intervention data that was previously unavailable in Ad Hoc reporting, supporting clinical performance review, quality assurance, compliance reporting, and operational analysis of airway management documentation.
• How -
  • Navigate to Ad Hoc reporting.
  • Select ePCR Reports as the primary data source.
  • Add ePCR Airway as a child dataset.
  • Add the available airway fields as needed:
    • Id
    • Indications for Invasive Airway
    • Airway Complications Encountered
    • Suspected Reasons for Failed Airway Management
    • Decision to Manage Patient with Invasive Airway
    • Invasive Airway Placement Attempts Abandoned
  • Use the new fields with existing Ad Hoc capabilities such as criteria filtering, sorting, grouping, aggregation, and calculated columns.
  • Indications for Invasive Airway, Airway Complications Encountered, and Suspected Reasons for Failed Airway Management are multi-select list fields and are translated into readable values for reporting.
  • Each airway record associated with an ePCR is returned separately due to the one-to-many relationship.
  • ePCR records marked as deleted or sent to trash are excluded from the data source.
  • No role or permission changes are required for this enhancement.
• Use Case - A reporting user can build an ePCR-based airway report to review invasive airway indications, identify documented complications or suspected reasons for failed airway management, and evaluate decision or abandonment timing across patient encounters for clinical review, quality assurance, and operational trend analysis.

AD HOC - New ePCR Airway Confirmation Data Source

• What - A new ePCR Airway Confirmation Ad Hoc data source has been added to expose airway confirmation data for clinical reporting and quality analysis. This data source is available as a child dataset of ePCR Reports and supports reporting on multiple airway confirmation records associated with a single ePCR, including confirmation methods, related coded values, and confirmation timing where applicable.
• Why - This enhancement gives users access to airway verification details directly within Ad Hoc reporting, supporting clinical review, quality assurance, compliance evaluation, and analysis of airway confirmation practices across patient encounters.
• How -
  • Navigate to Ad Hoc reporting.
  • Select ePCR Reports as the primary data source.
  • Add ePCR Airway Confirmation as a child dataset.
  • Add the available airway confirmation fields as needed for reporting.
  • Use the new data source with existing Ad Hoc capabilities such as criteria filtering, sorting, grouping, aggregations, and calculated columns.
  • Each airway confirmation record associated with an ePCR is returned as a separate row due to the one-to-many relationship.
  • Coded list-based values are translated into readable labels for reporting clarity.
  • Records linked to ePCRs marked as deleted or sent to trash are excluded from the data source.
  • No role or permission changes are required for this enhancement.
• Use Case - A reporting user can build an ePCR-based airway confirmation report to review which confirmation methods were documented for each patient encounter, analyze when confirmation occurred, identify airway verification patterns, and support compliance review for clinical airway management protocols.

AD HOC - New Incident Report Vehicles Data Source

• What - A new Incident Report Vehicles Ad Hoc data source has been added to expose vehicle-related data captured in the Vehicles grid of the Incident Reporting workflow. This data source is available as a child dataset of Incident Report and Incident Report (NERIS) and supports reporting on multiple vehicles associated with a single incident, including vehicle ownership, driver and passenger details, accident involvement, business vehicle status, vehicle type, make, model, year, license plate, state, VIN, and notes.
• Why - This enhancement improves visibility into vehicle involvement within incident records, supporting operational analysis, compliance reporting, incident reconstruction, and review of ownership, driver, passenger, and vehicle attribute patterns across reported incidents.
• How -
  • Navigate to Ad Hoc reporting.
  • Select Incident Report or Incident Report (NERIS) as the primary data source.
  • Add Incident Report Vehicles as a child dataset.
  • Add the available vehicle fields as needed:
    • Id
    • Owner
    • Driver
    • Passenger
    • Is Involved in Accident
    • Is Business Vehicle
    • Vehicle Type
    • Vehicle Make
    • Model
    • Year
    • License Plate Number
    • State
    • VIN
    • Notes
  • Use the new fields with existing Ad Hoc capabilities such as criteria filtering, sorting, grouping, aggregations, and calculated columns.
  • Each vehicle associated with an incident is returned as a separate row due to the one-to-many relationship.
  • Owner, Driver, and Passenger values resolve from related Incident Report People records.
  • Vehicle Type and Vehicle Make display readable values from defined UI value lists.
  • No role or permission changes are required for this enhancement.
• Use Case - A reporting user can build an incident report that lists each vehicle associated with an incident, identifies whether the vehicle was involved in an accident or used for business purposes, reviews owner, driver, and passenger details, and filters by vehicle type, make, model year, license plate, state, or VIN to support incident analysis and reconstruction workflows.

AD HOC - New Incident Report Equipment Data Source

• What - A new Ad Hoc reporting data source, Incident Report Equipment, has been added to expose equipment-related information captured in the Equipment grid of the Incident Reporting workflow. The data source includes equipment ownership, type, brand, model, serial number, year, power source, portability, notes, and other operational details associated with an incident.
• Why - This enhancement provides greater visibility into equipment documented during incident reporting, supporting inventory review, operational analysis, incident documentation, and reporting needs where equipment details must be analyzed alongside incident-level information.
• How
  • Create or edit an Ad Hoc report using Incident Report or Incident Report (NERIS) as the primary data source.
  • Add Incident Report Equipment as a child join data source.
  • Select the desired equipment fields, such as Owner, Equipment Type, Brand, Model, Serial Number, Year, Equipment Power Source, Equipment Portability, and Notes.
  • Use standard Ad Hoc report options to apply criteria filtering, sorting, grouping, aggregation, or calculated columns as needed.
  • Note: Incident Report Equipment has a one-to-many relationship with incident reports, so each equipment item associated with an incident appears as a separate row in report results.
  • Note: Lookup-backed fields such as Equipment Type, Equipment Power Source, and Equipment Portability display readable values instead of raw database codes.
• Use Case - A user can build an Ad Hoc report to review equipment associated with incidents, such as identifying incidents involving a specific equipment type, analyzing equipment power source trends, tracking ownership details, or reviewing notes and observations tied to individual equipment records.