Product preview · Fictional patient data
Windows workstation
On the clinic workstation, OvaFlow can be a small floating pill, a 384-pixel rail docked beside a modeled nAbleIVF, eIVF or Artisan chart, or a full workspace. Each view keeps the same patient, signed source, owner and next step in view without taking over keyboard focus.
What it's for
A floating companion, a rail beside the chart and a full workspace, all on the same task. Nurse coordinators, physicians and front-desk staff who live in the EMR all day.
A compact pill at the bottom-right or left edge of a Windows desktop, positioned clear of EMR Save buttons and form footers so staff never mis-click.
A 384-pixel companion docked next to the open chart in a managed browser or Windows session, read-only until a person reviews and places a draft in the EMR.
My work, patients, cycle boards and care conversations, with the signed source, amendment history and activity trail beside every task.
Honest Windows system-tray readiness, a one-click pause during shared screens, microphone check before calls, and manual launch when autostart is off.
Pill, rail, workspace
Scroll to open it: the same window grows from a pill on the desktop into a panel beside a modeled chart, then into the full workspace. Every screen is a frame from the recorded prototype.
The companion starts as a small pill at the bottom right of the Windows desktop, clear of EMR controls. It can dock on the left edge instead, and it never takes keyboard focus.
nAbleIVF · Modeled workflow example · Fictional patient data
The panel sits next to the EMR window instead of on top of it: the current patient, visit notes, dictation and the day's open work. Nothing in the chart changes until staff act there.
nAbleIVF · Modeled workflow example · Fictional patient data
Elena's row carries across. In My work it shows her outside result and who owns it, beside Nora's other items sorted into what needs action and what is waiting. The treatment decision stays with Dr. Mira Lee.
Prototype walkthrough · Fictional patient data
Device anatomy & visibility matrix
On a clinic Windows desktop (1728×1120 recording viewport), OvaFlow sizes itself to the moment—from a system-tray icon to a floating edge pill, a 384-pixel rail beside the chart, or a full workspace—without covering EMR Save controls or stealing keyboard focus [1][2].
Across the desktop consultation, monitoring, call-capture and workstation-recovery walkthroughs, the Windows workstation surface handles four everyday clinical desk realities.
Joins a telehealth consult on Windows. The pill prompts quietly at the screen edge clear of EMR footers; Dr. Lee tests her USB headset, confirms Maya Chen's encounter, and records verbal consent before capture starts.
No global keyboard shortcut hijacks the desk; recording never starts before consent.
Places the reviewed consultation note into the modeled nAbleIVF editor. The rail immediately shows “Text placed, save not verified” in amber.
Task closes only after Dr. Lee clicks Save Draft in the EMR and the saved state is read back.
Mid-draft for Maya Chen, another chart tab opens, then the EMR session times out and Citrix blocks clipboard redirection [2].
Wrong-chart stop blocks cross-patient placement; reviewed draft survives both timeout and clipboard block.
Right after saving Elena Rivera's trigger update in the modeled Artisan chart at 17:08 PDT, the workstation view drops.
Status switches to “Observation interrupted” (never assumed done) until the 17:11 PDT readback.
| Sub-surface / state | What is shown | What is hidden or redacted | Allowed action | Stays at the desk or EMR |
|---|---|---|---|---|
| System tray & background state | Readiness dot, microphone status, pause toggle for screen-sharing, and manual launch control. | Zero patient names or clinical notes until the clinician opens a companion panel. | Pause observation during a shared screen, run a 3-second mic check, or open the pill. | All clinical charting, session sign-in and workstation lock policies [1]. |
| Floating companion pill (bottom-left / bottom-right) | Active patient match badge, quiet Teams/Zoom call prompt, and active dictation timer. | Full multi-line note body stays collapsed so the EMR chart remains unobstructed. | Confirm patient and consent to start call capture, or practice dictation outside a chart. | EMR Save, Sign and e-prescribing buttons (pill docks clear of form footers). |
| 384-pixel rail beside the chart | Signed source document, side-by-side field compare, reviewed draft, and save-check status. | Blocks and hides placement controls if the open EMR chart belongs to a different patient. | Compare intake/approval fields read-only, place reviewed text, and verify EMR save readback. | Clicking Save / Save Draft, signing orders, updating structured allergies, and e-prescribing. |
| Full desktop workspace | Role-scoped My Work queue, cycle boards, care-conversation gates, and full amendment history. | Superseded instruction versions are watermarked and cannot be re-staged as current. | Triage daily queues, assign owners, review multi-system readiness gates, and audit changes. | System-of-record chart commits, lab witnessing records, and portal publication. |
| Citrix / expired browser recovery state [2] | Amber “Transfer blocked” or “Signed out of EMR” banner with the reviewed draft preserved. | Never writes to the Windows clipboard when Citrix ICA policy forbids redirection [2]. | Keep the draft attached to Maya Chen's task until the EMR session is restored. | Re-authentication into the EMR and final field save. |
Designed to do on Desktop & Windows
Explicit boundary
Questions
In our Windows workstation layout, the 384-pixel rail docks beside the browser or EMR viewport rather than floating over the center of the form, and the compact pill is pinned to reserved corner coordinates with an explicit keep-out zone around form footers.
No. Named-field dictation and read-only comparisons use non-activating window inspection so the clinician's cursor and keyboard focus remain inside the EMR until they explicitly click the companion.
When autostart is off, the system-tray readiness indicator states plainly that OvaFlow is paused until launched manually. If extensions or UI Automation are restricted, operations step down to human continuation where staff review the draft side by side.
When an EMR runs inside a remote Citrix session whose ICA policy blocks clipboard redirection, OvaFlow detects that transfer is blocked, shows an amber “Transfer blocked” chip, and keeps the reviewed draft safe in the local companion rather than losing it.
Microsoft Learn · Windows UI Automation (UIA) Accessibility Framework Overview (verified 2026-11-03)
Operating-system specification for inspecting desktop windows, control trees and keyboard focus on Windows.
Citrix Documentation · ICA Policy Settings — Client Clipboard Redirection (verified 2026-11-03)
Virtual desktop policy controls governing clipboard transfer between local endpoints and hosted clinical desktops.
In the walkthroughs
In the first pilot, Windows first. Each EMR step is tested in a clinic's own setup before it is turned on, and the Artisan example has not yet been checked against a real clinic build.
Walkthroughs
Recordings of the interactive design prototype with fictional patients. Open one to play it with chapters and captions.
A floating companion designed to dock away from Save buttons, stay out of keyboard focus, ask before listening, and let staff practice outside any chart.
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.
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.
A note isn't done until it's saved, a cycle doesn't start with prior authorization unresolved, dose changes go to eIVF's own e-prescribing, and a PGT label mismatch stops the review.
Fourteen designed recovery states, from an unplugged headset to a blocked remote-desktop clipboard, each keeping the draft and the right patient.
Routine follow-through runs under rules your team sets, pauses on request, and re-checks the open chart before it resumes.
Next step
We'll walk one of your shifts through the desktop workspace design, next to a modeled EMR screen. Fictional records only; please don't send patient data.