Overrides and corrections
Override EHR data in EDFlow when the feed is wrong, undo a console action, correct a time (including the PIA), reopen a departed visit, cancel a duplicate and link a downtime registration.
When the EHR says one thing and the department is doing another, patients should see what's really happening. These tools fix it, with a full audit trail.
Override the EHR
In any console action form, turn on Override (needs patient.override). The manual value then wins over the EHR for that fact until someone clears the override. The board and the patient page show an Override marker.
Example: the EHR keeps a patient in A12, but they're in hallway H2. Move them to H2 with Override on. Later EHR location updates are recorded but don't change what patients and staff see until you clear it.
Every override and clear is audited. Report persistent feed problems with Report a data problem so the integration team can fix the mapping.
Undo
Every console action shows a 10-second Undo. It restores the previous value and cancels the notification the action would have sent.
Correct a time
Update status → Correct a time re-records a milestone (arrival, triage, assigned, seen, PIA, disposition, departure) with a later record time and a "corrected" marker. Correcting the PIA time affects NACRS-aligned analytics only; patients don't see it. Needs patient.lifecycle.
Reopen a departed visit
If a patient was marked departed by mistake, Reopen visit returns it to the board. The patient's access comes back if it's still within the grace window. Needs patient.lifecycle.
Cancel a visit
Cancel visit (reason required) removes a duplicate or wrong registration. It disappears from everywhere except the audit log.
"No updates in 12 hours"
A visit with no activity for the site's threshold is flagged. Confirm departed if the patient has left; the disposition is recorded as unknown.
Link a downtime registration
A visit registered by hand while the feed was active is marked for linking. When the EHR arrival comes in with the same match key within 12 hours, Link to EHR visit merges them: EHR facts take precedence (except overrides), and sessions, family links, requests, tasks and the summary move to the surviving visit. Unlinked ones are listed under Needs linking on the board.
Related
Dernière mise à jour le
Cette page vous a-t-elle été utile?
Escalations
Request service levels and escalation in EDFlow for charge nurses: urgent requests without a response, Going now timers, thinking of leaving, over-the-usual-wait alerts and reassessments overdue.
When the EHR feed is down
What to do when the EDFlow EHR feed is delayed or down: what patients see, frozen estimates, the downtime procedure and kit, running the manual console, and handing back to the feed.