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.
What a pilot needs
Tested one operation at a time.
No EMR is switched on as a whole. Before go-live, a clinic would test each operation it wants on its own licensed build, and anything that can't meet its rules stays a step a person does.
Before go-live
Seven steps a clinic would take
This is the path we would follow with a clinic. None of it has happened at a clinic yet; it is what “ready” has to mean before anything touches a real chart.
- Step 01
Choose the operations
Start from the work, not the vendor: which sources to read, which drafts to prepare, which saves to check. Each one is its own decision.
Signed off by Clinical lead and practice manager
- Step 02
Pin the clinic's own build
Record the licensed EMR version, the workstations, browsers and any remote desktop. A reference screen is never treated as the clinic's build.
Signed off by Clinic IT
- Step 03
Pick a route for each operation
Use the first route the clinic and vendor permit, in order: structured API, approved browser extension, UI Automation, bounded visual fallback. Otherwise, human continuation.
Signed off by Clinic IT and the EMR's administrator
- Step 04
Test it on the clinic build
With test records, run each operation: read the source, prepare the draft, check the change in the EMR, pause and hand off. Record what counts as done.
Signed off by Nursing, lab and physician reviewers
- Step 05
Break it on purpose
Unplug the headset, change the chart mid-draft, drop the session, block the remote-desktop clipboard. Each failure must keep the draft and the right patient.
Signed off by Clinic IT and super-users
- Step 06
Review and agree
A formal security and privacy review, and signed commercial and data-handling agreements with the clinic's legal and IT teams.
Signed off by Legal, privacy and IT
- Step 07
Accept in a bounded pilot
Staff use the tested operations on real days, within the agreed scope. Anything not tested stays an explicit human step, labeled as one.
Signed off by The staff who do the work
Operation by operation
Where each modeled EMR stands
The same four steps, shown in the three modeled EMRs. “Modeled workflow example” means it appears in a prototype walkthrough. Checking a change in the EMR needs a clinic's own build before it means anything.
| Step | nAbleIVF | eIVF (V6 reference) | Artisan (separate modeled example) | Who keeps authority |
|---|---|---|---|---|
| 01Read the signed source | Modeled workflow exampleDay 8 ultrasound and hormone results shown beside the flowsheet. | Modeled workflow exampleA consult draft and the cycle readiness checklist beside the chart. | Modeled workflow exampleDr. Priya Shah's 17:07 PDT approval beside the unchanged fields in the EMR. | Read-only. Viewing a source never edits the chart. |
| 02Prepare a draft | Modeled workflow exampleA cycle progress note prepared for review. | Modeled workflow exampleAn unsigned consult summary waiting for the physician. | Modeled workflow exampleUpdated trigger and pre-op continuation prepared across the time change. | A draft is never treated as sent or signed. |
| 03Check the change in the EMR | Tested in your clinic firstChecks that the note is saved before follow-ups are released. | Tested in your clinic firstChecks where an unsigned draft landed and what is still open. | Tested in your clinic firstHolds the task unverified after the 17:08 interruption until the 17:11 read-back. | Write and read-back behavior must be tested on each clinic's build. |
| 04Pause and hand off | Modeled workflow exampleStops review on a specimen label mismatch; the checks happen in nAble Witness. | Modeled workflow exampleStops embryo review when the biopsy label differs from the chart's embryo label. | Modeled workflow exampleA message read at 17:22 doesn't move ownership; acceptance at 17:25 does. | Responsibility moves only on explicit acceptance. Clinical review stays with the physician. |
The Artisan column replays Elena's trigger change as its own modeled example, where Dr. Priya Shah is the approving practitioner. Names and times are fictional. The Artisan example was rebuilt from public help articles and has not yet been checked against a real Artisan clinic build, so how it edits an existing instruction is our own stand-in. About the Artisan example
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.
Honest status
What exists today, and what doesn't
What exists today
- 29 prototype walkthroughs (a design-artifact count)
- An interactive sandbox at /demo
- Product requirements and a 33-gap workflow research audit
What this site does not claim
- No live clinic deployment or running clinical software
- No live connection to any EMR or vendor system
- No measured time savings, outcomes or customer counts
Step 05, up close
Breaking it on purpose
The recovery walkthrough shows the failures a clinic would drill before go-live. Each one keeps the draft and the right patient instead of losing it or forcing it into the wrong chart.
- 0:00The headset unplugs
- 0:01The patient changes mid-draft
- 0:05Saves and sends not yet verified
- 0:13An expired session
- 0:14A remote desktop blocks transfer
- 0:20Recovering an interrupted capture
- 0:24Every partial draft kept
Workstation qualification & failure governance
Worked example: testing one operation on two clinic workstation builds
How a clinic's clinical lead, EMR administrator and IT engineer would qualify a single operation—“Day 8 monitoring note save check”—across a managed Windows 11 + Microsoft Edge workstation versus a Citrix virtual desktop.
Worked qualification example · Two clinic workstation builds
How one operation (“Day 8 monitoring note save check”) is tested across two different clinic desktop environments
Even when two clinics license the same fertility EMR, their workstation and Citrix policies differ. Qualification tests each operation on the clinic's actual desktop build before any pilot shift.
Operation under test20 synthetic patient charts · Zero live PHI
Day 8 monitoring note save check (signed ultrasound & hormone source → reviewed draft → EMR save readback)
Clinical lead, EMR administrator and Clinic IT pin the exact licensed EMR version and run intentional failure drills before deciding which route rung is permitted on each workstation build.
Branch A · Local managed browserRung 02 (Approved browser extension) + Rung 05 (Human continuation)
Build A · Managed Windows 11 + Microsoft Edge
- 01Pin the exact licensed EMR version and Edge extension policy in the clinic's non-production test tenant.
- 02Verify with 20 synthetic patient charts that the patient-banner check blocks placement 100% of the time when a different chart tab is focused.
- 03Run Step 05 failure drills: pull the USB headset mid-dictation, expire the browser session cookie, and close the tab before clicking Save.
- 04Sign off only when every interrupted save lands in “Text placed, save not verified” and never auto-submits.
Qualification sign-off outcome
Qualified for bounded pilot use: nurse places reviewed draft; companion verifies save readback.
Branch B · Locked-down virtual desktopRung 05 (Human continuation with local draft retention)
Build B · Citrix Virtual Apps desktop with clipboard redirection disabled
- 01Inspect Citrix ICA policy settings [2]: clinic IT policy blocks host-to-session clipboard redirection.
- 02Attempt automated field placement in test environment → blocked by Citrix policy as expected.
- 03Verify that OvaFlow detects the blocked transfer, displays “Transfer blocked” (amber), and holds Maya Chen's reviewed draft intact on the local companion.
- 04Confirm that staff can view the structured draft side by side or resume in an authorized session without losing a word.
Qualification sign-off outcome
Qualified as explicit human continuation: zero silent failures, zero lost drafts.
Qualification terms & definitionsPlain-language terms for per-operation qualification and failure drills
Questions
Clinic testing & IT governance questions
Frequently asked questions5 questions on clinical authority, verification and pilot boundaries
Why qualify one operation at a time instead of approving an entire EMR at once?
Fertility clinics customize templates, role permissions, browser policies and virtual desktops heavily. Even two clinics running the same EMR vendor often have different flowsheet layouts or Citrix rules. Qualifying each operation (read source, prepare draft, check save, hand off) on the clinic's actual build ensures every safeguard holds in practice.
What if a vendor or clinic policy forbids browser extensions and UI Automation?
The operation steps down the route ladder to Rung 05: Human continuation. OvaFlow still keeps the signed source, the prepared text, the owner and the follow-up checklist beside the chart while a staff member completes the step in the EMR.
Who signs off on each of the seven qualification steps?
Clinical leadership and the practice manager choose the operations (Step 01); Clinic IT pins the workstation and EMR build (Step 02) and selects permitted routes with the EMR administrator (Step 03); nursing, lab and physician reviewers validate clinical behavior on test records (Step 04); IT and super-users run intentional failure drills (Step 05); legal, privacy and IT complete formal reviews and agreements (Step 06); and frontline staff accept the bounded pilot (Step 07).
Can a pilot start before all seven steps are finished?
Walkthroughs and sandbox sessions use fictional patients and need no clinic setup. Touching a clinic's own environment or patient records requires completing the build pinning, route testing, failure drills and formal legal and privacy agreements first.
What happens when the clinic upgrades its EMR version during a pilot?
Because each operation record pins the exact EMR build and browser version it was tested against, an EMR upgrade triggers a re-check of the affected operation before automated observation resumes—falling back safely to human continuation in the meantime.
Public references & technical standardsExternal vendor & standards documentation cited on this page (3 verified sources)Retrieved 2026-11-03 · No vendor affiliation, endorsement or live connection.
- [1]
Microsoft Learn · Windows UI Automation Accessibility Framework Specification (verified 2026-11-03)
Operating-system specification for window, control and focus inspection on Windows workstations.
- [2]
Citrix Documentation · ICA Policy Settings — Client Clipboard Redirection Policy (verified 2026-11-03)
Reference for virtual desktop clipboard redirection rules that govern text transfer across remote sessions.
- [3]
HL7 International · SMART App Launch Framework & EHR Context Specifications (verified 2026-11-03)
Standardized framework for clinical context binding and scoped authorization beside an EHR.
Pilot conversations
Start with the operations that matter to you.
Tell us which EMR and which steps your team cares about first. We'll walk through what testing them on your own build would take.