Skip to main content

Product preview · Fictional patient data

OvaFlow

Recovery & continuity

Pull the plug. The draft stays.

When a headset unplugs, a session expires or the network drops, the draft and the right patient stay put.

In the first pilot · 5 prototype walkthroughsFictional patient dataInteractive illustration of designed behavior
Pull the plug on this workstation before these are placed.

OvaFlow workspace · Elena Rivera

Reviewed, waiting to be placed

  • Earlier visit note (reviewed)Visit note fieldReady to place
  • Nursing taskNursing worklistReady to place
  • Callback requestPatient contact logReady to place

Clinic EMR · Elena Rivera

Modeled workflow example
  • Visit note fieldNothing placed yet
  • Nursing worklistNothing placed yet
  • Patient contact logNothing placed yet

Continue on another device

iPhone opens the draft once it arrives.

The workstation keeps its copy until the next device confirms it arrived, so a dropped connection never leaves the note in two half-finished places.

Offline The note stays on this device and reviewed actions are held in a local queue. Nothing is guessed or pushed to another chart.Back online Each held action is placed one at a time, shows as “Native update not yet verified”, and is only counted once it is read back from the record. Then the draft opens on the next device.

How it works

14 ways a workstation fails mid-note

A tour of the ways a clinic workstation can fail mid-note, and how each one is handled. Disconnected microphones, changed charts, unverified saves, expired sessions and blocked remote-desktop transfers all hold the draft instead of losing it or forcing it into the wrong place.

  1. Keep what was capturedWhen a microphone disconnects or a voice memo stops mid-sentence, every captured second is preserved and the exact gap is marked for review.
  2. Hold instead of forcingExpired EMR sign-ins, remote-desktop clipboard blocks and mid-draft chart changes hold the draft in place rather than injecting text into an unverified field.
  3. Queue for laterWhen a mobile device or hallway workstation goes offline, the recording and draft stay on the originating device until the receiving desk confirms arrival.
  4. Reconcile after downtimeAfter a scheduled or unexpected EMR outage, paper downtime logs and verbal orders are reconciled item-by-item against the live EMR chart before tasks close.
Prototype walkthrough · Fictional patient data

Workstation failure and recovery catalog

Fourteen designed recovery states, from an unplugged headset to a blocked remote-desktop clipboard, each keeping the draft and the right patient.

0:26Desktop

Recovery here is designed behavior shown in a prototype, not a guarantee about any clinic’s systems. How it behaves on real workstations is part of testing in each clinic.

0:00The headset unplugs

  1. A USB microphone disconnects mid-visit. The audio already captured is kept.At 0:00

0:02The patient changes mid-draft

  1. The active patient changes mid-draft, so placement is blocked.At 0:02
  2. The target field changes, so the destination has to be confirmed again.At 0:04

0:06Saves and sends not yet verified

  1. The save in the EMR isn't verified yet, so the task stays open.At 0:06
  2. A monitoring cycle-sheet save is unverified, so the task isn't closed quietly.At 0:08
  3. A previous visit is still paused, so the two encounters don't mix.At 0:09
  4. A portal message send is unverified, so a duplicate resend is held.At 0:11

0:13An expired session

  1. The eIVF session expires. The draft is kept through sign-in.At 0:13

0:15A remote desktop blocks transfer

  1. A remote desktop blocks text transfer.At 0:15
  2. The remote window's connection and clipboard policy are shown.At 0:17
  3. The reviewed draft stays in OvaFlow until the local session resumes.At 0:19

0:20Recovering an interrupted capture

  1. Capture is interrupted unexpectedly, and the partial audio is recovered.At 0:20
  2. The recovered partial transcript and notes are reviewed.At 0:22

0:24Every partial draft kept

  1. Partial drafts are kept together in one place, designed so that nothing captured is thrown away.At 0:24

When workstations or networks drop

Why clinical software must survive unplugged headsets, remote-desktop blocks, and EMR outages

In real fertility clinics, nurses and physicians move between ultrasound rooms, procedure bays, and remote-desktop (Citrix/VDI) terminals. Published analyses of EHR downtime patient-safety reports show that laboratory orders/results (48.7%) and medication events (14.5%) are the primary failure points during outages, and that downtime contingency and reconciliation procedures are missing or bypassed in 46% of analyzed incidents [1].

At the single-workstation level, small hardware and session failures—a USB headset yanked mid-dictation, an EMR session timing out after 15 minutes, a remote-desktop window blocking clipboard paste, or hallway Wi-Fi dropping between an Apple Watch and the desk—routinely destroy half-written notes [2]. OvaFlow preserves every captured second of audio with an explicit gap marker, holds drafts inside the rail when a remote window or expired session blocks placement, keeps mobile captures on the originating device until the desk confirms receipt, and reconciles paper downtime logs item-by-item when the EMR comes back online.

From interruption to verified EMR record

How interrupted audio, remote-desktop blocks, and paper downtime logs recover cleanly

Nothing discarded · Nothing guessed
Stage 1 · During the interruptionLocal preservation

Every captured second and timestamp is kept

  • Headset unplugs at 01:42: Keeps the first 102 seconds of audio and marks the exact gap without guessing missing words.
  • Watch or iPhone offline: Keeps the voice note on the device until the desk confirms it arrived.
  • EMR outage: Logs monitoring and cryotank checks on paper with original timestamps.
Stage 2 · Held in OvaFlow railWaiting for chart

Never forced into an unverified window

  • Expired EMR sign-in: Draft survives re-authentication pinned to Elena Rivera.
  • Protected remote desktop: When Citrix or VDI blocks paste, the draft waits in the holding rail.
  • Post-outage queue: Paper downtime items enter as “EMR change not yet checked”.
Stage 3 · Verified EMR readbackItem-by-item closure

Closed only when the live EMR shows it

  • Chart identity re-checked: Confirms Elena Rivera’s chart is open after sign-in.
  • Placed one at a time: Staff review and save each held note or downtime entry in the EMR.
  • Readback confirmed: Tasks close only after the saved EMR record is observed.
Figure 1 · Whether a USB headset unplugs, a remote desktop blocks clipboard paste, or an EMR outage forces paper logging, work is held with its patient context and closed only after live EMR readback.

Worked example from the cast

Keeping a consult note intact when a headset unplugs, a session expires, or Wi-Fi drops

How OvaFlow keeps drafts tied to Elena Rivera and reconciles paper logs after a clinic outage without losing or guessing data.

Read Elena’s full episode story →
Step-by-step walkthrough

Keeping a consult note intact when a headset unplugs, a session expires, or Wi-Fi drops

  1. Step 0110:14 PDT

    Dr. Mira Lee

    Consult Workstation
    Audio kept · Gap markedUSB headset unplugs at 01:42

    While Dr. Mira Lee dictates Elena Rivera’s consult note, the USB headset cord is bumped unplugged at 01:42. OvaFlow preserves all 102 seconds of audio and transcript already captured, inserts a visible audio gap marker at 01:42, and resumes cleanly.

  2. Step 0210:19 PDT

    Dr. Mira Lee

    Protected Remote Desktop
    Draft held in OvaFlowRemote window blocks paste

    When Dr. Lee tries to place the reviewed note into a protected remote EMR window whose session just expired, OvaFlow does not drop the draft or force keystrokes into the login box. It holds the draft in the rail until she signs back in and re-confirms Elena’s chart.

  3. Step 0311:05 PDT

    Nora Ruiz, RN

    Apple Watch → iPhone → Desk
    Kept until desk confirmsOffline hallway voice memo

    Nora captures a voice note on her Apple Watch in an elevator with no Wi-Fi. The recording stays on the watch, relays through her paired iPhone when in range, and clears from mobile storage only after her desktop workstation confirms receipt.

  4. Step 0414:40 PDT

    Nora Ruiz, RN & Lab Lead

    Post-Outage Reconciliation
    EMR change not yet checkedPaper log matched to live EMR

    After a 40-minute EMR outage where two monitoring updates and a cryotank check were logged on paper downtime forms, OvaFlow stages each paper entry in a reconciliation queue and closes each item only after the live EMR record is read back.

Figure 2 · Four-step walkthrough showing who holds responsibility, which screen is active, and which status applies at each timestamp.

System boundaries

What OvaFlow handles and what stays with your EMR and clinical team

Clear operational boundaries keep clinical authority, prescribing, and laboratory witnessing inside your clinic’s own systems. See AI & clinical boundaries for full governance rules.

What OvaFlow does here

  • Preserves all captured audio and transcript prior to a microphone disconnect and marks the exact time gap.
  • Holds the prepared draft in the rail when an EMR session expires, a chart changes, or a remote desktop blocks text transfer.
  • Retains offline mobile and wrist captures on the originating device until the receiving workstation confirms arrival.
  • Stages paper downtime notes in a structured reconciliation list that requires EMR readback before closure.

What OvaFlow never does

  • Never uses AI to guess or fill in missing words across an unplugged-microphone audio gap.
  • Never forces blind keystrokes into a protected Citrix/RDP window or an expired EMR login screen.
  • Never deletes a mobile voice recording on upload start—deletion waits for end-to-end desk confirmation.
  • Never marks paper downtime entries resolved until the corresponding live EMR chart has been verified.

Questions & primary sources

Answers for clinicians, practice leaders, and patients

What happens if my EMR logs me out for inactivity while I am finishing a 3-minute consultation note?Clinicians & coordinators

Under the “Drafts survive sign-in” safeguard, your reviewed draft stays pinned to that patient and encounter in the OvaFlow rail. Once you sign back into the EMR and open the patient’s chart, OvaFlow verifies the chart match and lets you place the note in one step.

How does OvaFlow help our clinic recover after an unplanned 1-hour cloud EMR outage during morning monitoring?Practice leaders & owners

Consistent with ONC SAFER Contingency Planning guides, paper downtime sheets and verbal updates are entered into a dedicated reconciliation queue where each item is matched to the patient’s live chart and held as “EMR change not yet checked” until readback confirms it.

If the clinic’s internet or computer system has a brief outage on the day of my procedure, how is my plan kept safe?Patients & families

Your care team’s notes and timing records are held locally with their exact timestamps and then checked item-by-item against your official chart as soon as the main system reconnects.

Primary clinical & safety references (2 sources)View citations
  1. Larsen E, Fong A, Wernz C, Ratwani RM (2018). Implications of electronic health record downtime: an analysis of patient safety event reports. Journal of the American Medical Informatics Association 25(2):187-191. — Found that 46% of EHR downtime safety reports involved missing or unfollowed contingency and post-outage reconciliation procedures.
  2. Office of the National Coordinator for Health IT (ONC) (2025). SAFER Guide: Contingency Planning for Electronic Health Record Downtime. HealthIT.gov Safety Assurance Factors for EHR Resilience. — Details best practices for preserving clinical work during partial or complete system interruptions and reconciling paper downtime records into the live EHR.

See it

Walkthroughs that show it

Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional, and EMR screens are modeled reconstructions.

Prototype walkthrough · Fictional patient data

Next step

Show us how your workstations fail.

Headsets, remote desktops, timeouts, downtime. We will walk through each one in a modeled workflow example, with fictional records only.