Purpose Statement

The Configuration Fields section of the Fire Incident EMS Module allows administrators to customize treatment and medication options to align with local protocols and operational standards. This feature enables departments to:

• Streamline patient care documentation by pre-configuring relevant treatments and medications
• Reduce documentation errors through controlled medication parameters (routes, dosages, units)
• Improve field efficiency by setting default values that auto-populate during incident reporting
• Ensure compliance with local medical protocols through customized labeling
• Enhance patient safety by restricting available medication options to department-approved formularies

Background Information

The EMS Module Configuration Fields serve as the foundation for accurate patient care documentation within First Due. By configuring these fields during initial setup, administrators create a tailored environment that reflects their department's specific protocols and scope of practice.

Common Use Cases:

• Initial EMS Module setup for new First Due implementations
• Updating medication formularies when protocols change
• Restricting available treatments to match certification levels (BLS vs. ALS)
• Creating region-specific medication naming conventions
• Standardizing dosage ranges across all field personnel

Prerequisites:

• EMS Module must be activated in your First Due account
• Basic Fire Incident types should be configured
• Familiarity with your department's medical protocols and approved medication list
• Understanding of medication administration parameters (routes, dosages, units)

Key Benefits:

• Error Reduction: Pre-set dosage ranges and routes minimize administration mistakes
• Protocol Compliance: Custom labels ensure documentation matches local medical direction
• Efficiency: Default values reduce data entry time during critical patient care moments
• Consistency: Standardized options across all users improve data quality for reporting

Required Permissions

• Fire Incident Setup - Edit (required)
• Administrator role (recommended for full configuration access)

Video

---

Step-by-Step Guide

Best Practices

• Involve Medical Direction: Consult with your medical director or EMS coordinator when configuring medication parameters to ensure protocol compliance
• Start with High-Use Medications: Configure your most commonly administered medications first to see immediate field benefits
• Use Clear, Consistent Labels: Ensure medication and treatment names match what's in your written protocols to avoid confusion
• Set Realistic Dosage Ranges: Configure ranges that account for both pediatric and adult patients when applicable
• Enable Multiple Routes When Appropriate: If a medication can be given multiple ways per protocol, enable all valid routes
• Test Before Deployment: Always test configurations in a non-live environment before rolling out to field personnel
• Document Your Configuration: Keep a record of which medications are enabled and their parameters for quality assurance purposes
• Regular Protocol Reviews: Schedule quarterly reviews to ensure configurations match current medical protocols

• Don't Enable All Medications: Only activate medications your personnel are trained and authorized to administer
• Don't Skip Default Values: While optional, default values significantly improve documentation efficiency
• Don't Use Abbreviations Inconsistently: If you abbreviate one medication name, maintain that style across all similar medications
• Don't Set Unrealistic Dosage Limits: Overly restrictive ranges may prevent documentation of clinically appropriate doses
• Don't Forget Pediatric Considerations: Ensure dosage ranges accommodate your patient population demographics
• Don't Configure Without Training: Ensure staff are trained on any label changes before deployment to avoid documentation confusion
• Don't Overlook Less Common Medications: While prioritizing high-use medications, don't neglect configuring rarely-used but critical medications

1. Forgetting to Save Settings: Always click "Update Medication Settings" before closing the configuration window
2. Inconsistent Unit Selection: Mixing mg and mcg for similar medications creates confusion
3. Too Many Active Medications: An overwhelming medication list slows field documentation - only enable what's truly needed
4. Not Testing Mobile View: Configuration should be tested on mobile devices since most field documentation occurs on tablets
5. Label Changes Without Staff Notice: Communicate any terminology changes to field personnel before implementation
6. Copying Settings Across Medications: Each medication has unique parameters - don't assume settings from one apply to another

Troubleshooting & FAQs

• Solution: Verify the medication is selected (active) in the Configuration Fields dropdown. Navigate back to EMS Module setup and confirm selection is saved.

• Solution: Check that default values are set in Medication Settings AND that you clicked "Update Medication Settings" to save. Re-enter and save if necessary.

• Solution: Verify you have "Fire Incident Setup - Edit" permissions. Contact your system administrator to request appropriate access.

• Solution: Administrators can modify maximum dosage limits in Medication Settings. For immediate situations, document actual dosage given and follow up with protocol review.

• Solution: Field users may need to sync their mobile app or log out and back in for configuration changes to populate. Ensure cellular/wifi connection is active.

• Solution: Ensure you're clicking the save/update button after editing labels. Browser cache may need to be cleared if issue persists.

• Solution: Revisit Medication Settings and disable routes not approved by your protocols. Fewer options improve documentation speed and accuracy.

Frequently Asked Questions

Q: How many medications should we activate? A: Activate only medications in your department's approved formulary that personnel are trained to administer. Most departments enable 15-30 core medications. Quality over quantity improves field efficiency.

Q: Can different user roles see different medication lists? A: Configuration applies system-wide. Use permissions and training to ensure personnel only administer medications within their scope of practice, but the full list will be visible to all users.

Q: Should we use brand names or generic names for medications? A: Use whatever terminology matches your written protocols. Consistency between First Due and your protocol documentation is more important than brand vs. generic naming.

Q: What happens if we need to administer a medication not in the active list? A: Field personnel can document medication administration in notes sections. However, this indicates a need to add the medication to your configuration for future incidents.

Q: How often should we review and update these configurations? A: Review configurations whenever protocols change (typically annually) or when new medications are added to your formulary. Quarterly reviews are recommended as a best practice.

Q: Can we configure different dosages for pediatric vs. adult patients? A: Set dosage ranges that accommodate both populations. Field personnel select appropriate dosages based on patient assessment. Some departments use dose ranges (e.g., 0.01-1.0 mg) to cover all scenarios.

Q: What if our protocols change mid-year? A: Update configurations immediately when protocols change. Communicate changes to field personnel and consider requiring acknowledgment of updates before next shift.

Q: Do configuration changes affect historical incident data? A: No. Changes only affect future incident documentation. Past incidents retain the medications and treatments documented at that time.

Q: Can we export our medication configuration list? A: Contact First Due support for assistance exporting configuration details for quality assurance or protocol review purposes.

Related Articles

• Fire Incident Setup--EMS Module (NFIRS): Signatures Language
  
• Fire Incident Setup - Narrative Template
  
• Fire Incident Setup - Size up and Operations