Purpose Statement
This article explains how to configure EMS Outcome Settings to control how Hospital Data Exchange (HDE) return data from ESO updates existing PCR records. Proper configuration ensures accurate data synchronization while preventing unintended overwrites that could impact patient safety.
Background Information
The EMS Outcome Configuration feature supports ESO HDE data imports by allowing agencies to define node-level update rules for incoming NEMSIS data. When abbreviated NEMSIS files are received via SFTP, the system matches records using the PCR Record ID (eRecord.01) and applies update rules to specific NEMSIS nodes.
Supported NEMSIS groups include:
- DemographicGroup
- eRecord
- eResponse
- ePatient
- ePayment
- eDisposition
- eOutcome
- eOther
Each node can be configured with one of four update behaviors:
- Always Update
- Never Update
- Update if Blank
- Conditional Update
All settings default to Never Update to protect existing PCR data and ensure patient safety.
Required Permissions
To configure EMS Outcome Settings, users must have:
- ePCR - Manage Outcome Configuration
Video
Step-by-Step Guide
1. Access the Module Stacks
- Select the First Due logo to open the module stacks.
2. Open EMS Setup
- Select the Incident Documentation module.
- Select EMS Setup.
3. Navigate to the General Section
- From the EMS Setup menu, select General.
4. Locate Outcome Configuration
- Scroll within the General section until Outcome Configuration is visible.
5. Configure NEMSIS Node Update Behavior
- Review each listed NEMSIS node.
- Select the appropriate update behavior:
- Always Update – Incoming data always overwrites existing values.
- Never Update – Incoming data is ignored (default setting).
- Update if Blank – Incoming data updates only empty fields.
- Change settings only for nodes that should accept updates.
6. Save Configuration
- Select Save to apply changes.
Best Practices
Do’s
- Review each NEMSIS node individually before changing defaults.
- Use Update if Blank when supplementing incomplete PCR records.
- Coordinate configuration changes with QA or compliance staff.
Don’ts
- Do not change settings globally without understanding downstream impacts.
- Do not use Always Update for critical patient data unless required.
- Avoid configuring Conditional Updates without clearly defined rules.
Tips & Recommendations
- Start with a limited set of nodes and expand gradually.
- Monitor History logs after changes to confirm expected behavior.
- Document configuration decisions for audit and compliance purposes.
Troubleshooting & FAQs
Why isn’t ESO data updating my PCRs?
- Confirm the node is not set to Never Update.
- Verify the PCR Record ID (eRecord.01) matches between systems.
How can I see what was updated?
- Review the History log, which records update attempts, results, and field-level changes.
What happens if configurations conflict?
- Conflicts are logged in the History log, and no updates are applied for affected fields.
Additional Considerations
- Changes take effect immediately for newly received ESO files.
- Defaulting to Never Update helps ensure compliance and patient safety.
- Periodically review configurations as ESO or NEMSIS requirements evolve.