Connected emergency care

Emergency care.In clearer view.

Keep patients informed, families connected and care teams in sync. Every step of the emergency visit, in one place.

Department overviewSample visit
04All visits
02Needs attention
LocationVisit stageIn stage
A3Tests in progress30 min
W12Waiting to be seen95 min
C2Results back41 min
B7Preparing to go home12 min
Kestrel Bay GeneralEN

Visit updatesSample visit

Tests in progress

Your care team will review your results with you.

Usual time for this testUsually 40–60 min

Most people within 90 min

  1. Checked in
  2. Seen by doctor
  3. Tests in progress1 of 3 results back
  4. Results and next steps
Sample visit
  • Never shows results
  • Works with Epic and Oracle Health
  • English and French
  • Hosted in Canada

One visit. A shared understanding.

The right information for every person involved, from the waiting room to the care team.

Try the demo

The next step, already in view.

A visit card opens a live picture of care. Patients can follow their progress without another trip to the desk.

  • Visit progress and care team
  • Usual time ranges, not countdowns
  • Test status without clinical results
Explore solution
Kestrel Bay GeneralEN

Visit updatesSample visit

Tests in progress

Your care team will review your results with you.

Usual time for this testUsually 40–60 min

Most people within 90 min

  1. Checked in
  2. Seen by doctor
  3. Tests in progress1 of 3 results back
  4. Results and next steps
Sample visit

A simple start. A connected visit.

  1. 01

    Scan the visit card

    At registration, the patient gets a visit card. One scan opens their visit on their own phone: no app to install, no account to create.

  2. 02

    Follow the visit live

    The stage, the care team and each test's progress update live from the EHR, with honest time ranges for this hour. Results are never shown.

  3. 03

    Share with family

    The patient decides who follows along. Family see the stage, the waiting estimate and first names, never tests or results.

  4. 04

    Ask the care team

    Structured requests reach the right person and are acknowledged. "I feel worse" always says: tell a nurse in person now.

Illustration of a nurse speaking with a patient in a calm hospital corridor
Illustrative setting

More clarity in the moments that matter.

A wait feels different when people know what is happening. Give patients a clear view of their visit, while the care team stays focused on care.

118 min
average wait from triage to seeing a physician in Ontario emergency departments in 2022/23, up from 87 minutes in 2013/14 [2]
257 min
the 90th percentile of that wait: one patient in ten waited longer [2]

Built around the questions people ask.

  • Live stage timeline

    Every step of the visit in plain words, with the current step marked and what usually comes next.

  • Care team

    The first names and roles of the people looking after the patient, updated at every handover.

  • Test tracker

    Ordered, collected, in the lab, back: the process of each test, with estimates for this day and hour.

  • "Results are back", without results

    Patients learn that a result exists, never what it says. Their care team explains it.

  • Code-delay notices

    When a very sick patient pulls the team away, people waiting are told calmly that waits may be longer, and why.

  • Requests with acknowledgement

    Predefined requests reach the right staff member and show who saw them, so nobody wonders whether the message arrived.

  • Family sharing

    Patient-controlled links with the minimum necessary information, revocable at any time.

  • Flow analytics

    Times per step, bottlenecks by hour and request response times, with a table view for every chart.

Fits the systems behind your care.

Connect through your hospital’s integration engine, or start with the staff console. The same visit experience, from either source.

Integration engineHL7 v2 / FHIR R4
Visit event
Patient
Family
Care team

Epic and Oracle Health via HL7 v2 or FHIR R4. Only the events needed to follow the visit.

How integration works

Care information, carefully shared.

Never shows results

Patients see that a result is back, never the result.

Minimum-necessary family view

Family see the stage, the waiting estimate and first names, only if the patient shares.

No health information in notifications

Push notifications, texts and links carry no names, tests or locations.

Canadian data residency

Hospital data stays in a Canadian region; the showcase uses synthetic data only.

Full audit trail

Every access to patient data is logged and reviewable by the privacy office.

PIA and TRA ready

Documentation, data inventory and controls ready for your privacy impact and threat risk assessments.

Accessible and bilingual from the first release

  • Plain language at a grade 6 to 8 reading level
  • English and French from day one, with safety messages in more languages
  • Text up to 200%, high contrast and reduced motion respected
Security and privacy in detail

What the research says

Information changes how a wait feels

Findings from published studies by other teams, not results of EDFlow. Each links to its source.

86%
satisfaction with lab turnaround when patients saw digital progress updates, versus 55% without, in an unmatched pilot analysis [4]
1.4–5.5×
Patients who were not told about delays were 1.42 to 5.48 times more likely to give lower ratings [5]
p70
Estimates set at the 70th percentile raised satisfaction the most; estimates at the median had no effect [6]
90%
of surveyed patients wanted wait information in the emergency department, and 77% said it would improve their experience [7]
Read the research

Questions hospitals ask

Does EDFlow show test results to patients?

No. EDFlow shows that a result is back, never what it says. The care team explains results in person, which avoids the worry that unexplained results cause.

Do patients need to download an app?

No. Patients scan the QR code on their visit card and follow their visit in the browser, with no account and nothing to install. A native app for iPhone and Android is optional.

Which EHRs does it work with?

It works with Epic, Oracle Health and any EHR whose integration engine can send HL7 v2 or FHIR R4 events. The hospital's engine sends a small, minimized event feed over HTTPS. A staff console can run every step by hand when there is no feed.

Where is patient data stored?

Hospital data is hosted in Canada. Only the minimum data needed is received: no result values, no notes, no health card numbers. Identifiers are stored as keyed hashes and every access is audit-logged.

Is it a medical device?

It is designed as communication and workflow software: it never shows results, interprets them or gives clinical advice. Each hospital completes its own privacy impact and threat risk assessments before a pilot.

What happens if a patient feels worse while waiting?

The first request tile is always "I feel worse". It tells the patient to tell a nurse or staff member in person right away and alerts the care team at the same time, with no confirmation step. The app is never an emergency channel.

How are wait estimates calculated?

From this hospital's own history for the same step, day of the week and time of day: a usual range, plus the time most people (9 in 10) are done within. Never a countdown, never a promise, and it says what it is based on.

Can we start without an EHR interface?

Yes. A pilot can start with the staff console on day one, before any interface work. The EHR feed follows through the hospital's integration engine, and the console stays available whenever a feed is down.

Bring the whole visit into view.

Explore the patient and staff experience, then plan a pilot around your department’s workflows.