Daily care: a changed trigger, the wrong chart and an unknown outcome
A late estradiol result, a newly signed trigger time, the wrong chart caught before publishing, and a lost confirmation checked rather than blindly resent.
Walkthrough 8 of 29 · Desktop
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.
- Length
- 0:26
- Chapters
- 7
- Shown on
- Browser with the compact recovery companion
- In the first pilot
- Prototype walkthrough · Fictional patient data
- nAbleIVF · Modeled workflow example
- eIVF · Modeled workflow example
- Tested in your clinic first
Workstation failure and recovery catalog, muted recording of the design prototype. Fictional patient data.
Chapter 1 of 7
Chapter 1 of 7: The headset unplugs
Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional, EMR screens are modeled reconstructions, and nothing shown is a live connection to any clinic or vendor system.
Clinical & operational context
The situation on screen, why it matters, and where OvaFlow stops.
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.
What clinical situation this depicts
Real clinic workstations fail in mundane ways every day: a USB headset gets bumped mid-dictation, a nurse clicks a different patient's tab while a draft is open, a clinic portal or EMR session times out over lunch, or a hospital Citrix/remote-desktop window blocks clipboard transfer. When tools hide these interruptions or discard partial work, staff either re-type notes from memory or accidentally paste Patient A's draft into Patient B's chart.
This walkthrough tests seven workstation failure and recovery states in sequence: an unplugged headset mid-capture, a patient chart switch while a draft is open, saves and sends whose outcome has not yet been verified, an expired authentication session, a remote-desktop boundary that blocks direct field transfer, step-by-step recovery of an interrupted capture, and preservation of every partial draft segment.
Step-by-step workflow
Workstation failure recovery without losing partial drafts or mixing charts
Step 1Active dictation
Workstation audio
Headset unplugs at 00:04; capture pauses cleanly
Step 2Browser tab switch
OvaFlow safeguard
Different patient opens while Elena's draft is active
Step 3EMR / portal link
OvaFlow companion
Detects expired session or remote-desktop block
Step 4Recovery tray
Nora Ruiz, RN
Resumes preserved segments and verifies save
How OvaFlow handles hardware disconnects, mid-draft chart switches, session timeouts, and remote-desktop boundaries.
Guardrail: Every partial audio and text segment is preserved, and switching patients mid-draft locks the draft to its original patient.
What OvaFlow coordinates in this recording
- Pauses immediately and keeps all prior audio when a headset or microphone disconnects.
- Locks open drafts to the original patient when the background chart changes mid-draft.
- Preserves partial drafts across session timeouts and surfaces clear recovery steps when remote desktop blocks placement.
What stays with clinicians & the clinic's own systems
- Never discards a partial dictation or call draft on session expiry.
- Never allows a draft begun under one patient to be placed into a newly opened patient chart.
- Never hides unverified saves or sends inside the completed list.
Terms in this walkthrough
Full glossary- Wrong-chart stopOvaFlow termIf the open chart isn't the patient the work belongs to, placement stops and the draft is kept.
- Observation interruptedOvaFlow termOvaFlow lost sight of the EMR screen. It shows the last verified time and doesn't assume anything changed.
Show 3 more glossary terms in this walkthrough
- Publication outcome unknownOvaFlow termA send may or may not have happened. The task stays open and the EMR is checked before anything is repeated.
- Save checkOvaFlow termConfirming that text placed in the EMR was actually saved, rather than assuming it.
- Visit captureOvaFlow termOpt-in recording of a visit or call, after consent, that produces a draft for a clinician to review.
What to watch for
What could go wrong, and what you'll see instead.
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.
The problems it is designed around
- A headset disconnect losing part of a consultation.
- A chart or field change mid-draft putting text into the wrong record.
- An expired session or a remote-desktop clipboard policy silently dropping a note.
What you'll see in the recording
- Microphone disconnect with the audio kept
- Changed patient and changed field stops
- Unverified saves and sends held open
- Expired session and remote-desktop blocks
- Interrupted capture recovered
Chapter-by-chapter guide
Every chapter in this 0:26 walkthrough (7 chapters)
Follow the exact timestamps, UI status changes, and coordination safeguards as the recording plays.
The headset unplugs
What to watch for: When the headset unplugs mid-sentence, capture pauses immediately and preserves the recorded audio up to that second.
Boundary rule: Hardware loss never corrupts or discards the existing recording.
On-screen narration: A USB microphone disconnects mid-visit. The audio already captured is kept.
Show chapters 2–7 (6 more chapters with timestamps & boundary notes)
The patient changes mid-draft
What to watch for: Switching the browser to another patient while a draft is open triggers a patient-mismatch banner.
Boundary rule: A draft started for Elena Rivera remains locked to Elena Rivera.
On-screen narration: The active patient changes mid-draft, so placement is blocked. The target field changes, so the destination has to be confirmed again.
Saves and sends not yet verified
What to watch for: Items whose save or send response did not return appear in a dedicated 'Unverified outcome' section.
Boundary rule: Unverified actions are separated from both 'To do' and 'Done'.
On-screen narration: The save in the EMR isn't verified yet, so the task stays open. A monitoring cycle-sheet save is unverified, so the task isn't closed quietly. A previous visit is still paused, so the two encounters don't mix. A portal message send is unverified, so a duplicate resend is held.
An expired session
What to watch for: An expired workstation session prompts re-authentication without wiping the in-progress draft.
Boundary rule: Session expiry never erases unsaved clinical coordination work.
On-screen narration: The eIVF session expires. The draft is kept through sign-in.
A remote desktop blocks transfer
What to watch for: When a remote-desktop window blocks direct field placement, the companion explains why and offers verified step-by-step copy/check controls.
Boundary rule: Technical boundaries are surfaced honestly rather than failing silently.
On-screen narration: A remote desktop blocks text transfer. The remote window's connection and clipboard policy are shown. The reviewed draft stays in OvaFlow until the local session resumes.
Recovering an interrupted capture
What to watch for: After reconnecting audio, the nurse resumes the interrupted capture from the exact pause point.
Boundary rule: Interrupted recordings stitch cleanly with visible segment markers.
On-screen narration: Capture is interrupted unexpectedly, and the partial audio is recovered. The recovered partial transcript and notes are reviewed.
Every partial draft kept
What to watch for: The recovery list shows every preserved partial draft with its patient tag and timestamp.
Boundary rule: No partial note is silently deleted in the background.
On-screen narration: Partial drafts are kept together in one place, designed so that nothing captured is thrown away.
OvaFlow never makes the clinical call in these recordings. Physicians sign, the person taking a handoff accepts it, and the lab keeps its own holds. The companion tracks, checks and stops; staff decide.
In this walkthrough
The people on screen
Every patient, family member, clinician and clinic in these stories is fictional. Names, times and screens come from prototype walkthroughs, not from real care.
- IVF nurseWrites the note
- REI physicianCaptures the visit
- Clinic IT and operationsSupports the workstation
Systems in this recording
Named or shown on screen. An EMR here is a modeled workflow example built for the prototype, not the vendor's own software. OvaFlow is designed to work beside these systems.
Modeled workflow exampleFertility EMR & practice management
Modeled workflow exampleFertility EMR & practice suite
Show 1 more systems shown in this recording
Microsoft TeamsClinician calls & collaboration
eIVF: V6 reference.
Show 2 systems often found around this workflow
Systems a clinic running this workflow often uses. They do not appear in this recording.
Clinic workstation OS
Virtual desktop & remote app host
Third-party names and logos are trademarks of their respective owners, shown to illustrate systems commonly used in IVF clinics. No affiliation, endorsement or live integration is implied. nAbleIVF, eIVF and Artisan appear as modeled workflow examples.
Where this appears
Read the page around it.
This recording is part of these pages. Each one explains the step in more depth.
Show all pages where this walkthrough appears
Surfaces
Modeled EMR pages
Guided tours
Questions & answers
Common questions about this walkthrough
What clinicians, coordinators, practice leaders, and patients ask when reviewing Walkthrough 8.
What happens if my headset battery dies halfway through a 5-minute patient call?
OvaFlow pauses capture the instant the audio input drops, saves the segment captured so far, and lets you switch microphones and resume without losing the first half of the call.
If I click into another patient's EMR tab to check a schedule slot while drafting a note, does the draft follow me?
No. The draft stays bound to the original patient and displays a mismatch stop until you return to that patient's chart.
Show 1 more walkthrough questions
How does OvaFlow behave when a clinic runs its EMR inside a locked-down remote desktop?
When direct field placement is blocked by a remote-desktop boundary, OvaFlow shows that constraint explicitly and provides structured field-by-field review rather than pretending placement succeeded.
Related
Watch these next.
Show 2 more related walkthroughs
Artisan: trigger approval, the wrong chart and an interrupted view
Beside a modeled Artisan view, the companion compares Dr. Priya Shah's approval with the unchanged Artisan fields, stops on Maya's open chart, and won't assume an update it didn't see.
nAbleIVF: allergy check, monitoring note, save check, specimen stop
A patient-reported penicillin rash is surfaced against the chart, a monitoring note is confirmed saved rather than assumed, and a specimen label mismatch stops review.
Next step
Walk through it with your own team.
We'll replay this flow against your roles and handoffs, using fictional records. Please don't send patient data.