The Disable Hide Rules feature allows authorized users to temporarily override field visibility restrictions in ePCRs. This tool is essential when workflows require access to fields that are normally hidden by conditional logic rules, enabling users to complete reports that would otherwise be blocked by validation errors. This feature ensures data collection remains flexible while maintaining standard workflow controls for most users.
Background Information
Hide Rules are conditional logic configurations that automatically show or hide specific fields based on user selections within an ePCR. While these rules streamline data entry by displaying only relevant fields, certain situations may require access to hidden fields to complete a report—particularly when custom workflows create dependencies that conflict with existing hide rules.
Common Use Cases:
Resolving validation errors caused by workflow/hide rule conflicts
Accessing fields needed for special documentation scenarios
Completing reports when required fields are inadvertently hidden
Administrative troubleshooting of ePCR completion issues
Prerequisites:
User must have the appropriate role permissions enabled
Hide rules must be configured in the system (Admin module)
Familiarity with your department's ePCR workflow structure
Required Permissions
To access and use the Disable Hide Rules feature, users must have the "Disable Hide Rules" permission enabled for their role. This permission is configured in:
Navigate to the Admin module and locate Roles & Permissions to enable the Disable Hide Rules permission for the specific user role(s) that require this capability.
Step 2: Identify the Hide Rule Conflict
Open the ePCR where the validation error is occurring. In this example, selecting "Transport by Another EMS Unit" in the Transport Disposition field triggers a required field error.
Step 3: Recognize the Validation Error
The system displays a validation error within the Disposition section, preventing report completion.
This occurs because a required field ("How patient was moved to the ambulance") is hidden by a hide rule but is required by the workflow.
Step 4: Locate the Disable Hide Rules Button
Users with the appropriate permission will see the Disable Hide Rules button in the ePCR toolbar at the top of the screen.
Step 5: Access via More Button (If Needed)
Pending or your screen size, the Disable Hide Rules option may be located within the ...More dropdown menu.
Click the More button to reveal additional toolbar options.
Step 6: Disable the Hide Rules
Click the Disable Hide Rules button.
All fields that were previously hidden by hide rules will now become visible within the ePCR, including the required field causing the validation error.
Step 7: Complete the Required Field
With the hide rules disabled, the previously hidden required field is now accessible.
Enter the appropriate information to satisfy the workflow requirement.
Step 8: Re-enable Hide Rules (Optional)
After completing the necessary fields, the Disable Hide Rules button changes to Enable Hide Rules.
Click this button to restore normal hide rule functionality and return the ePCR to its standard field visibility configuration.
Step 9: Access Enable Hide Rules via More Button (If Needed)
Similar to Step 5, if the Enable Hide Rules button is not immediately visible in the toolbar, access it through the ...More dropdown menu.
Best Practices
Do:
Use Disable Hide Rules only when necessary to complete reports with legitimate validation conflicts
Re-enable hide rules after completing the required fields to maintain standard workflow for other users
Document recurring hide rule conflicts and report them to your system administrator for workflow review
Train authorized users on when and how to appropriately use this feature
Review and audit usage patterns to identify systematic workflow issues
Don't:
Leave hide rules disabled permanently—this defeats the purpose of streamlined data entry
Use this feature to bypass intentional data collection restrictions without supervisory approval
Grant this permission to all users—limit access to roles that require troubleshooting capabilities
Ignore recurring conflicts—address the underlying workflow or hide rule configuration issue
Common Mistakes to Avoid:
Forgetting to re-enable hide rules after completing the report
Using Disable Hide Rules as a workaround instead of fixing the underlying configuration problem
Granting this permission too broadly, potentially compromising workflow integrity
Troubleshooting & FAQs
Q: I don't see the Disable Hide Rules button in my toolbar. Why not?
A: This typically means your user role does not have the Disable Hide Rules permission enabled. Contact your system administrator to request this permission if your responsibilities require access to this feature.
Q: After disabling hide rules, I see many additional fields. Is this normal?
A: Yes. Disabling hide rules reveals ALL fields that would normally be hidden by any hide rule in that ePCR. Only complete the specific field(s) required to resolve your validation error. You can re-enable hide rules once those fields are completed.
Q: Will disabling hide rules affect other users working in different ePCRs?
A: No. Disabling hide rules only affects the current ePCR on your session. Other users and other reports are unaffected by your action.
Q: Should I leave hide rules disabled if I frequently encounter this same error?
A: No. Instead, report the recurring conflict to your system administrator. The underlying workflow or hide rule configuration should be reviewed and corrected to prevent ongoing issues.
Q: Can I disable hide rules in a locked or finalized report?
A: This depends on your system configuration and permissions. Generally, locked or finalized reports have additional restrictions that may prevent modifications even with the Disable Hide Rules permission enabled.
Q: What happens if I forget to re-enable hide rules before closing the ePCR?
A: The hide rules will typically be automatically re-enabled when the ePCR is closed or when you open a different report. However, it's best practice to manually re-enable them before completing your work.
Purpose Statement The purpose of this article is to demonstrate how to create a Hide Workflow for fire reports. This workflow enables agencies to streamline fire documentation by automatically hiding certain fields based on predefined conditions. ...
Purpose Statement The purpose of this article is to demonstrate how to create an Error Validation Workflow for fire reports. This workflow helps ensure that required data is completed accurately before a report can be submitted. Background ...
Video <br> New Features 1. AI-Powered Attachment Data Extraction in ePCR This feature introduces AI-powered image analysis within the ePCR attachment modal, allowing users to automatically extract structured patient data (e.g., name, DOB, ...
Video New Features 1. ePatient.25 Patient's Sex This critical patch implements NEMSIS 3.5.0 compliance requirements by introducing the new ePatient.25 - Patient's Sex field in response to federal regulatory changes. Due to a Presidential Executive ...
In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. Video New Features 1. Transfers What: This feature introduces a streamlined workflow for transferring electronic Patient Care ...