Purpose Statement
The EMS Workflow Conditions feature enables administrators to create dynamic, conditional logic within ePCR forms that automatically hide fields, set default values, or trigger validation warnings based on specific criteria. This functionality enhances data quality, streamlines provider workflows, and ensures appropriate clinical documentation by adapting form behavior to match real-world EMS scenarios and protocols.
Background Information
Workflow Conditions introduce advanced logic that makes ePCR documentation more intelligent and responsive to provider input. By implementing conditional rules, agencies can reduce clutter by hiding irrelevant fields while ensuring critical information is captured when applicable.
This system supports four workflow types, each designed to meet different operational and clinical needs:
- Hide workflows
- Default value assignment
- Error validations
- Warning validations
These tools help improve documentation accuracy, provider efficiency, and overall data quality.
Required Permissions
Users must have administrative access within the EMS module to configure workflow conditions, including:
- EMS module administrative access
- EMS Setup permissions
- Workflows configuration permissions
- ePCR customization permissions
- Field validation management permissions
If you cannot access the Workflows section, contact your system administrator.
Video
Step-by-Step Guide
1. Navigate to EMS Setup
Click EMS Setup within Incident Documentation
2. Open Workflows
Click Workflows
3. Filter Options for Workflow List
There are 4 filter options to help locate workflows from the list of currently active workflows.
Field- Field that the workflow is built upon.
Referenced Field - This will list all workflows that use a field as a condition. For example, Transport Disposition can be used in multiple workflow conditions.
Nemsis Element - Find the workflow based on the field's Nemsis number.
Workflow - Filter by types of workflows. For example, if only Hide rules are needed to be seen in the list.
3. Add a New Workflow
Click Add
4. Select an ePCR Field Code
Choose the ePCR Field Code you want to apply the workflow to
5. Select Workflow Type
- Select one of the following workflow types:
- Hide Workflow
- Hides the field in the ePCR when conditions are met
- Default Value
- Automatically assigns a default value when conditions are met
- Error Validation
- Displays a red validation error
- Prevents report completion until resolved
- Warning Validation
- Displays a yellow warning
- Allows report completion
6. Add the Workflow
- Click Add
7. Define Workflow Details
- Enter a Description for internal reference
- For Error or Warning Validation workflows:
- Enter a Validation Message displayed to providers in the ePCR
8. Add Conditions
- Click Add Condition to create a single rule
- Click Add Group to create multiple linked rules
9. Configure Grouped Conditions
- Within an Add Group, click Add Condition for each rule you want to include
10. Set Condition Logic
- Define how conditions relate by selecting:
- AND
- OR
11. Define Conditional Rules
- Specify:
- When/If - Field
- Condition/Is - Operator
- Parameter/Value(s)
- Ensure rules match the real-world scenarios you want to trigger the workflow
Note: the Choices that are selected in the Parameters will now group at the top making it easier to see what has been selected already.
12. Save Workflow
- Click Save to apply the workflow condition
Best Practices
Do’s
- Test workflow conditions thoroughly before production use
- Use clear descriptions and validation messages that providers understand
- Document complex logic for future reference and training
- Design workflows that align with real clinical workflows
- Use Warning Validations for recommendations and Error Validations only for critical requirements
Don’ts
- Avoid overly complex conditions that may confuse users
- Do not block report completion for non-critical fields
- Avoid implementing workflows without provider input
- Do not forget to test edge cases and uncommon scenarios
- Avoid creating conflicting workflows on the same field
Troubleshooting & FAQs
Q: Why isn’t my workflow condition triggering?
- Verify field codes, operators, and values are correct
- Test with the exact data combinations expected to trigger the workflow
Q: What’s the difference between Error and Warning validations?
- Error Validation: Red flag, blocks report completion
- Warning Validation: Yellow flag, allows completion
Q: Can I edit an existing workflow?
- Yes, workflows can be edited at any time from the Workflows configuration screen
Q: How should workflows be tested?
- Use a test environment or sample reports with matching conditions
Q: Can workflows affect multiple fields?
- Each workflow applies to one field, but multiple workflows can be created using similar conditions
Additional Considerations
Workflow Type Applications
- Hide Workflow: Remove irrelevant fields based on call type, age, or protocol
- Default Value: Prepopulate common values tied to incident characteristics
- Error Validation: Use only for mandatory safety or compliance requirements
- Warning Validation: Encourage best-practice documentation without blocking completion
Clinical Integration
Workflow conditions can support:
- Protocol-based documentation
- Age- or condition-specific relevance
- Medication safety checks
- Quality improvement initiatives
Performance Considerations
- Minimize condition complexity to maintain form responsiveness
- Test workflows under typical usage scenarios
- Monitor system behavior after deploying multiple workflows
Change Management
Establish processes for:
- Testing before deployment
- Communicating changes to providers
- Monitoring effectiveness and feedback
- Updating workflows as protocols evolve