1. Step 1: Enable Permissions
1. Speak with your Client Success Manager to activate the “Kno2 Premium Plus” permission.

1. Step 2: Run Carequality Search
1. When users perform a Carequality patient search through Kno2:
1. The system checks if the Operations Query is enabled
2. If enabled, it executes both:
1. Treatment Query (standard clinical data)
2. Secondary Payment Query (new)
   

1. Step 3: Retrieve and Process Payment Documents
1. The system identifies the most recent Payment document from the search
2. It automatically parses the returned CCDA/CDA document for:
1. Insurance Information
2. Relative/Guardian Information
   

1. Step 4: Import to ePCR
1. Parsed insurance data is automatically inserted into the ePCR Insurance grid
2. Guardian information is placed into the appropriate demographic fields
3. Data is immediately available before locking or exporting the report
   

---

Enhancements

1. Previously, users customized protocol display names, active/inactive status, and sort order directly within the EMS Setup → Protocols section. This functionality has now been moved to the centralized Field Customization area, allowing for a more consistent and intuitive configuration experience across multiple field types.
   

1. Ensures a consistent administrative workflow across ePCR custom fields
   
2. Replaces the broken display name editing in the Protocols section
   
3. Prevents visibility errors by allowing precise active/inactive control
   
4. Maintains compliance with state-specific data export standards (DEM files)
   
5. Reduces fragmentation by consolidating protocol configuration into a single UI
   

1. An agency needs to rename a protocol from "Universal Patient Care" to "Basic Life Support Protocol" and hide a rarely used protocol from field staff. The admin accesses Field Customization, updates the display name, marks the old protocol as inactive, and reorders the dropdown—all without navigating through the old EMS Setup → Protocols section. The form updates instantly and exports remain compliant with state DEM requirements.
   

1. Automatic Migration
1. If your agency does not have eProtocols.01 customizations, your existing protocol list, display names, and sort order are automatically migrated to Field Customization during deployment.
2. Access Protocol Management
   
1. Navigate to:
   
1. EMS Setup > Field Customization
3. Configure Protocol Visibility
1. Use the Active/Inactive check box to control whether a protocol appears in the “Protocols Used” dropdown during EMS report entry
4. Customize Display Labels
1. Use the Display Description field to update the protocol’s display name—this replaces the now-deprecated label editor in the Protocols section
5. Adjust Sort Order
1. Drag and drop protocols to control their order of appearance in dropdowns and reports
6. Maintain DEM File Exports
1. Protocols still export with appropriate eProtocols.01 values and state-specific formatting as required for compliance
   

2. Upload and Parse .crd Files from Zoll AED Devices

This enhancement expands the EKG import capabilities within the First Due platform by enabling support for .crd files from Zoll Automated External Defibrillators (AEDs). It allows EMS providers to include critical cardiac data from AEDs in their ePCRs using the same streamlined import process already used for .zol files.

What:

1. Users can now upload .crd files generated by Zoll AEDs and automatically extract and display essential cardiac data, ECG strips, patient identifiers, and treatment markers. The system uses optimized SDK parameters to remove prior import barriers, providing a seamless, consistent workflow for importing AED data into the patient care report.
   

Why:

1. AEDs are frequently used in field responses where a full cardiac monitor is unavailable. Capturing AED data is critical for:
1. Supporting medical direction review
2. Enhancing legal documentation
3. Ensuring complete cardiac event reporting
4. Improving continuity of care during hospital handoff
2. Prior to this enhancement, .crd files from Zoll AEDs could not be processed due to SDK limitations. This fix ensures these life-saving devices are fully supported in the First Due platform.
   

Use Case:

1. A Zoll AED is used during a cardiac arrest response. After the incident, the .crd file is downloaded from the AED device. During ePCR completion, the provider uploads the file via the EKG import tool. The system parses the data, inserts treatment markers, displays ECG strips, and auto-populates patient metadata—ensuring that vital data is documented without manual transcription.
   

How it works:

1. Step 1: Access the EKG Import Tool
1. Navigate to the EKG section of an EMS report
2. Click Import EKG File
3. Select and upload a .crd file from a Zoll AED device
2. Step 2: Parse AED Data
1. The system uses the Zoll SDK with adjusted parameters to parse the file
2. Extracted data may include:
1. Heart rate
2. Rhythm interpretation
3. ECG strip images (three leads)
4. Event and medication markers
5. Device and incident metadata
6. General patient info (if recorded on device)
3. Step 3: Review & Confirm Data
1. ECG strip images and event timeline entries appear in the EKG viewer
2. Extracted values are auto-populated into relevant ePCR fields
3. Review and adjust entries as needed before completing documentation
   

3. Default Date Prompt for Date/Time Fields

This enhancement improves ePCR data entry efficiency by allowing users to set a session-based default date after entering the first Date/Time value. It significantly reduces redundant manual date input across multiple fields—especially for standard EMS calls that occur entirely within a single day.

What:

1. Upon entering a first Date/Time value during a documentation session, users are prompted with a modal to apply that date as the default. If accepted, all other empty Date/Time fields—standard and custom—will automatically populate with the default date when edited.
2. This functionality persists only during the active documentation session and resets once the report is closed.
   

Why:

1. Most EMS incidents occur on a single calendar day
   
2. Field providers often need to input the same date into multiple Date/Time fields
   
3. This feature eliminates repetitive clicking (e.g., “Today” buttons) or re-typing dates
   
4. It reduces friction in documentation while allowing full flexibility when dates vary
   

Use Case:

1. A paramedic begins documenting an incident that occurred on July 16. After entering “07/16/2025 14:52” in the first Date/Time field, the system prompts to use that date going forward. The medic accepts, and now when entering Arrival, Transfer, and Disposition times, the system pre-fills “07/16/2025” automatically—saving time and clicks without affecting the time entry.
2. Later, when entering a follow-up care note for a treatment that happened after midnight, the medic enters “07/17/2025.” The system asks whether this should now be the new default for future entries, ensuring flexibility and control.
   

How it works:

1. Step 1: Enter the First Date
1. When a user manually types or imports a date (via CAD, monitor, etc.), a modal prompt appears:
   “Apply this date to all future Date/Time fields in this report?”
2. Step 2: Set the Default
1. Choose Yes to set the current date as the session’s default date
2. Choose No to keep each Date/Time field independent
3. Step 3: Auto-Fill & Dynamic Updates
1. When editing any Date/Time field that is currently blank, the field will auto-populate with the default date
2. If a user manually enters or modifies a different date later, the system re-prompts to update the session default
4. Session Behavior
1. The default date only applies to the current documentation session
2. Once the report is closed, the session resets, and no default is carried forward

4. Redesigned EKG Modal with Time Interval Filtering

This enhancement introduces a touch-optimized, redesigned EKG modal with new filtering capabilities that simplify the review and selection of monitoring data. Users can now apply time interval filters to intelligently reduce data volume by displaying only the most complete vitals within each selected interval, improving usability for long-duration cases.

What:

1. The EKG modal has been overhauled with a guided, step-by-step interface, optimized for iPad and touchscreen workflows. A new Time Interval Filter allows users to limit visible vitals to a representative sample every 3, 5, or 10 minutes, based on data completeness. This reduces screen clutter for prolonged cases while retaining access to all raw data via a “Clear Filter” option.
   

Why:

1. Extended incidents can generate hundreds of vitals entries, making manual review inefficient
   
2. Users often face difficulty locating key data points due to repetition or incomplete entries
   
3. Filtering by time interval simplifies clinical review, QA, and documentation workflows
4. Optimizing the interface for touch devices ensures better performance on tablets used in the field
   

Use Case:

1. A provider uploads an EKG file for a cardiac arrest response lasting 70 minutes. Without filtering, the modal would display 400+ vitals records. By selecting the 5-minute filter, the provider sees only the most complete record every 5 minutes, reducing the list to a manageable 14 records. They review, confirm, and import a clean set of relevant vitals, maintaining documentation accuracy without unnecessary noise.
   

How it works:

1. Step 1: Open the EKG Modal
1. Navigate to the EKG section in an EMS report and click Import
2. The redesigned modal opens with a guided, touch-friendly interface
2. Step 2: Select the Case
1. Choose the appropriate EKG case from the list
2. Click Next to proceed to vitals filtering
3. Step 3: Apply Time Interval Filter
   
1. In the Vitals tab, choose a filter option:
1. 3 minutes
2. 5 minutes (default)
3. 10 minutes
4. Clear Filter (shows all original records)
4. Step 4: Smart Filtering Logic
1. The system divides the data into time blocks starting from the first timestamp
2. Within each block, the system selects the record with the fewest empty fields
3. If there is a tie, the earliest record is chosen
5. Step 5: Review Filtered Vitals
1. View a clean, representative set of vitals with reduced duplication
2. Use Clear Filter at any time to view the full, unfiltered data set
6. Step 6: Select Devices
1. Switch to the Devices tab to select which monitor/device data to include
7. Step 7: Import
1. Click Import to finalize and push selected vitals and device data into the ePCR
   

5. Configurable CAD Incident & Response Number Setup

This enhancement provides EMS agencies with greater flexibility in determining how Response Numbers are populated in ePCRs by introducing a configurable source selector. Agencies can now choose whether the Response Number is pulled from a CAD Incident Number, a CAD Dispatch Number, or generated internally using First Due’s auto-numbering functionality—ensuring alignment with CAD integration preferences and operational workflows.

What:

1. A new "Response Number Source" dropdown is now available under the Auto Response Number Setup section in EMS Setup. This dropdown enables selection from the following options:
1. CAD Incident Number (default for most clients)
2. CAD Dispatch Number (new option)
3. Use Custom Response Number (auto-generated format)
2. Each option dictates how the Response Number field is populated in ePCR reports based on available CAD data or First Due-generated values.
   

Why:

1. Agencies differ in how they use Incident vs. Dispatch Numbers from their CAD systems
   
2. Some require strict, consecutively numbered responses for state or billing compliance
   
3. Ensuring the correct source and format eliminates confusion, supports auditing, and aligns with downstream workflows such as billing, analytics, and NFIRS
   

Use Case:

1. An agency using CAD integration wants to populate the Response Number field with the Dispatch Number, not the Incident Number. The administrator updates the “Response Number Source” to CAD Dispatch Number, and from that point forward, each new ePCR imports the correct value directly from CAD, eliminating manual corrections.
2. Another agency requires sequential response numbers for billing exports and selects “Use Custom Response Number.” They also enable formatting rules to prefix the number with the year and agency code, ensuring consistency across documentation and exports.
   

How it works:

1. Step 1: Navigate to Setup
1. Go to EMS Setup > General > Auto Response Number Setup
2. Step 2: Select Response Number Source
   
1. Use the new Response Number Source dropdown to choose the desired method:
1. CAD Incident Number: (default for non-custom clients) uses the Incident Number from the CAD system
2. CAD Dispatch Number: populates the Response Number with the CAD’s Dispatch Number
3. Use Custom Response Number: generates a unique Response Number using First Due’s internal formatting and sequencing logic
3. Step 3: Configure Custom Numbering (if selected)
1. When Use Custom Response Number is selected, additional options become visible:
1. Generate consecutive response number (checked and read-only)
2. Enable Response Number Format (editable if formatting rules are desired)
4. Step 4: CAD Integration Behavior
1. If a CAD-based option is selected:
1. The system respects existing CAD import priority (Fire Incident → Dispatch or Dispatch → Fire Incident) to determine which CAD value is used
2. The selected CAD number is inserted into the Response Number field in the ePCR
5. Step 5: Populate in Reports
1. Based on the selection, the system automatically inserts the corresponding Response Number into new ePCRs:
1. CAD Incident or Dispatch Numbers from CAD integration
2. Custom, consecutive number from internal sequence logic
   

6. LA County Sequence Number – Visible on ePCR Form

To provide Los Angeles County agencies with real-time visibility of the LA County Sequence Number directly within the ePCR form. This identifier—critical for compliance with LA County data requirements—is now displayed as a read-only field during incident documentation, ensuring users can confirm it during processing while preventing accidental changes.

What:

1. This enhancement adds a configurable setting to show or hide the LA County Sequence Number within the ePCR. When enabled, the field appears directly below the Incident and Response Numbers and matches the value exported in the ePatient.01 field of the XML file used for LA County submissions.
   

Why:

1. LA County requires a unique Sequence Number in all EMS report submissions
2. Visibility during documentation helps QA/QI teams, field crews, and admins verify compliance in real time
3. Prevents confusion about whether the sequence number was generated or exported correctly
4. Field is read-only to protect the integrity of the autogenerated number
   

Use Case:

1. An LA County paramedic is completing an ePCR for a call and needs to confirm the system-generated Sequence Number required for county reporting. Because the department enabled the “Make LA County Sequence Number Visible” setting, the medic sees the sequence number just below the Incident and Response Numbers and confirms it before saving the report.
2. Meanwhile, another First Due client in a different region doesn’t see this field at all—keeping their interface clean and specific to their jurisdiction.
   

How it works:

1. Step 1: Access Configuration
1. Go to EMS Setup > General
2. Locate the setting: "Make LA County Sequence Number Visible"
   (Only visible for LA County clients)
2. Step 2: Enable Display
1. Check the box to enable the field’s visibility on the ePCR form
3. Step 3: View in ePCR
1. When enabled, the LA County Sequence Number appears as a read-only field
2. Positioned directly below Incident and Response Numbers
3. Value is generated automatically using internal logic based on ePCR identifiers
4. Remains visible while the incident is in progress
4. Step 4: Save & Export
1. When saving the ePCR, the same value is exported in the ePatient.01 field
2. Users can visually verify it on screen before final submission
   

7. EMS Setup – Pagination & Filters for Custom Elements

To improve performance and usability when managing large sets of Custom Elements, Custom Values, and Custom Groups in EMS Setup. This enhancement introduces pagination, filters, and lazy loading to reduce load times and make it easier for admins to locate and update custom configurations.

What:

1. Previously, the Custom Elements interface loaded all records and full details at once—leading to slow performance for agencies with many configurations. This update introduces:
1. Pagination across all custom configuration subsections (20 records per page)
2. Targeted filters with partial text matching for easy searching
3. Optimized queries to load only essential fields until editing is required
   

Why:

1. Large datasets no longer cause lag or timeout issues
2. Admins can find and edit fields faster using refined filters
3. System aligns with performance standards and UI consistency across First Due
4. Reduces backend load, especially for high-volume clients with extensive custom elements
   

Use Case:

1. An EMS Admin with over 150 custom fields needs to locate and update a discontinued value in the Allergy Type group.
1. Instead of scrolling through hundreds of entries, they now:
1. Filter by Group Name: "Allergy"
2. Filter by Status: Inactive
3. Quickly locate the outdated value and make changes
2. The result: faster load time, targeted updates, and smoother configuration management.
   

How it works:

1. Step 1: Access Custom Elements
1. Go to EMS Setup > Custom Elements
2. Step 2: View Paginated List
1. Each subsection—Custom Elements, Custom Values, and Custom Groups—now displays only 20 records per page
2. Use pagination controls to browse additional pages
3. Step 3: Apply Filters
1. Section
2. Available Filters
3. Custom Questions
1. Title, Usage, Is Active
   

1. Custom Values
1. Selectable Value, Reported Code, Is Active
   

1. Custom Groups
1. Group Name, Is Active
   

1. Filters support partial text matching
   
1. (e.g., entering "Aller" will match "Allergic Reaction")
   
2. Active filters are clearly displayed with options to reset/clear them
   
1. Step 4: Edit Records
   
1. Click to edit a record → system then loads full details on-demand
   
2. This lazy loading ensures performance isn't impacted until deeper access is needed