Frequently asked questions
Answers to common questions about EDFlow from patients, families, staff, hospital leaders and IT: results, wait times, privacy, costs to staff time, and integration.
For patients and family
No. You see when a result is back, never what it is. Your care team talks with you about results. After your visit, your hospital's patient portal may show them. See Tests.
No. The sickest people are always seen first, so the order changes all the time. You see the usual wait for your step at this hospital on this day and hour. See Wait estimates.
Tell a staff member in person right away, or go to the triage desk. The "I feel worse" button also lets your care team know, but never wait for a reply on your phone. See If you feel worse.
No. Scan the QR code on your wristband or visit card with your phone's camera. The app is optional. See App or browser.
Yes, if you choose. You can share a link with up to five people and stop sharing at any time. They see much less than you do: never tests, results or where you are. See Share with family.
You can see your visit read-only for a limited time after you leave, then access ends and the app clears what it stored on your phone. See Privacy.
For staff
It is designed to remove questions, not add them. Requests are structured and routed to the right person, "Where I am" messages (stepping out, back, washroom) create no task at all, and duplicates merge. Most states come from the EHR feed. See Requests.
No free text reaches patients from the chart. Patients see stages, test steps, names and roles, tasks from approved templates, and the going-home summary you compose from approved templates. See What patients see.
Patients see that updates may be delayed, estimates freeze, and the charge nurse can run the department from the console until the feed recovers. See When the feed is down.
Yes. Opening a patient's detail, unmasking a confidential name, and every action on a visit are recorded in the audit log that the privacy office reviews. See Privacy at work.
For hospital leaders and IT
Any EHR that can send HL7 v2 or FHIR R4 through an integration engine, including Epic, Oracle Health Millennium and MEDITECH, plus normalized JSON events. Sites without a feed run from the manual console. See For hospitals.
Hospital production runs in Canada, in AWS ca-central-1 with disaster recovery in ca-west-1. The demo and sandbox hold synthetic data only. See Data residency.
No. The event contract forbids them: events that contain prohibited fields are rejected before anything is stored. See Data flow.
EDFlow does not diagnose, triage, predict clinical outcomes or recommend treatment. It communicates logistics. AI features follow the same boundary and are off until a site approves them. See AI governance.
Request it from compliance documents. It includes the architecture, the controls matrix, the TRA summary, subprocessors and the questionnaire answers.
Still stuck?
Patients and family: ask any nurse or the registration desk. Staff: ask your charge nurse or your site's EDFlow champion. Hospitals and developers: use the contact page on the product site.
Last updated on