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 3 of 29 · Desktop
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.
- Length
- 0:29
- Chapters
- 9
- Shown on
- Browser with the 384-pixel compact companion
- In the first pilot
- Prototype walkthrough · Fictional patient data
- Artisan · Modeled workflow example
- Not yet checked against a real clinic build
Artisan: trigger approval, the wrong chart and an interrupted view, muted recording of the design prototype. Fictional patient data.
Chapter 1 of 9
Chapter 1 of 9: A modeled Artisan reference
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 modeled Artisan reconstruction, a separate clinic example from the daily-care story, with the compact companion docked beside it. A proposed trigger change stays “Awaiting clinician approval” until Dr. Priya Shah approves at 17:07 PDT, and the Artisan fields are left untouched. When the workstation drops after the save in Artisan, the status says so plainly instead of guessing.
What clinical situation this depicts
Many fertility clinics work inside web-based IVF electronic medical records such as Artisan, switching rapidly between a clinic-wide Day Sheet and individual patient Cycle Sheets across browser tabs. When a coordinator or nurse prepares a cycle update while multiple patient tabs are open, or when a browser tab refreshes mid-save, staff can easily lose track of whether a change was actually committed to the right patient's Cycle Sheet.
This walkthrough models a 384 px OvaFlow companion docked beside a modeled Artisan reference screen (1056 px). While reviewing Elena Rivera's cycle, a staff proposal is routed to Dr. Priya Shah and approved at 17:07 PDT while the modeled Artisan field remains unchanged until staff place it. When the nurse attempts to place the update while Maya Chen's chart is active in the browser, OvaFlow stops. After switching back to Elena's Cycle Sheet, the companion loses sight of the EMR window during placement, marks the state 'Observation interrupted', and resolves it only by reading the saved value back from the modeled Artisan Cycle Sheet.
Step-by-step workflow
Modeled Artisan side-by-side: proposal, wrong-chart stop, and readback
Step 1384 px companion
Dr. Priya Shah
Approves proposal at 17:07 PDT (EMR still unchanged)
Step 2Modeled Artisan tab
Nora Ruiz, RN
Attempts placement while Maya Chen's chart is open
Step 3Elena's Cycle Sheet
OvaFlow safeguard
Window focus drops mid-save
Step 4Elena's Cycle Sheet
Nora Ruiz, RN
Reads saved field back from Artisan screen
How the 384 px companion checks chart identity and verifies persistence against a modeled Artisan Cycle Sheet.
Guardrail: Losing sight of the EMR window triggers 'Observation interrupted' until the companion reads the saved record back.
What OvaFlow coordinates in this recording
- Distinguishes 'Approved at 17:07 PDT' from 'Saved in the EMR' so staff see what still needs placement.
- Halts field placement when Maya Chen's chart is open instead of Elena Rivera's.
- Marks mid-save focus loss as 'Observation interrupted' and clears it only after reading the saved field back.
What stays with clinicians & the clinic's own systems
- Does not claim a vendor affiliation or live bidirectional feed with Artisan.
- Never silently writes to the Cycle Sheet in the background without staff review.
- Never marks an interrupted EMR save as completed without readback evidence.
Terms in this walkthrough
Full glossary- CompanionOvaFlow termOvaFlow's compact panel beside the chart, which opens into a full workspace on the same task.
- Wrong-chart stopOvaFlow termIf the open chart isn't the patient the work belongs to, placement stops and the draft is kept.
Show 3 more glossary terms in this walkthrough
- Observation interruptedOvaFlow termOvaFlow lost sight of the EMR screen. It shows the last verified time and doesn't assume anything changed.
- ReadbackOvaFlow termChecking the record in the clinic's own EMR to confirm what actually happened.
- Modeled workflow exampleOvaFlow termHow nAbleIVF, eIVF and Artisan appear on this site: reconstructions of how OvaFlow is designed to work beside each EMR, not a live connection or endorsement.
What to watch for
What could go wrong, and what you'll see instead.
A modeled Artisan reconstruction, a separate clinic example from the daily-care story, with the compact companion docked beside it. A proposed trigger change stays “Awaiting clinician approval” until Dr. Priya Shah approves at 17:07 PDT, and the Artisan fields are left untouched. When the workstation drops after the save in Artisan, the status says so plainly instead of guessing.
The problems it is designed around
- An unsigned trigger proposal applied too early to the EMR's fields.
- The browser switched to another patient's Cycle Sheet mid-update.
- A workstation drop after the save in the EMR, tempting a blind repeat.
What you'll see in the recording
- Read-only source views that leave the Artisan fields untouched
- Approval at 17:07 PDT compared with the unchanged Artisan time, 20:30
- A stop when Maya Chen's chart is open
- “Observation interrupted” and “Native update not yet verified”
- Reading the record back from the EMR
Chapter-by-chapter guide
Every chapter in this 0:29 walkthrough (9 chapters)
Follow the exact timestamps, UI status changes, and coordination safeguards as the recording plays.
A modeled Artisan reference
What to watch for: See the modeled Artisan interface on the left (1056 px) and the 384 px OvaFlow companion on the right.
Boundary rule: Artisan is a modeled third-party EMR shown to illustrate how OvaFlow is designed to work beside it.
On-screen narration: The walkthrough opens with Artisan's public help-guide references and a note that this is a modeled reconstruction that has not yet been checked against a real Artisan clinic build.
Show chapters 2–9 (8 more chapters with timestamps & boundary notes)
The companion beside the Day Sheet
What to watch for: The clinic Day Sheet lines up with the companion's active task list.
Boundary rule: OvaFlow does not replace the EMR's Day Sheet; it tracks who owns the next follow-up.
On-screen narration: The ART Day Sheet opens with the compact 384-pixel OvaFlow companion beside it. The Day Sheet evidence opens read-only. The evidence view closes.
Elena's Cycle Sheet
What to watch for: Opening Elena Rivera's Cycle Sheet pairs her active cycle banner with the companion header.
Boundary rule: Patient context is checked continuously against the visible EMR header.
On-screen narration: Elena Rivera's Cycle Sheet opens.
A proposal, awaiting clinician approval
What to watch for: A proposed schedule update is queued for clinician approval before anything touches the EMR.
Boundary rule: OvaFlow never writes unapproved proposals into the clinic's chart.
On-screen narration: A proposed trigger change is shown as “Awaiting clinician approval”. Dr. Priya Shah's unsigned proposal can be inspected without changing any Artisan field. The proposal view closes.
Approved at 17:07 PDT; Artisan field unchanged
What to watch for: Dr. Priya Shah approves at 17:07 PDT; the companion explicitly notes the Artisan field is still unchanged.
Boundary rule: Clinician approval in the companion is never confused with a completed EMR save.
On-screen narration: Dr. Priya Shah approves at 17:07 PDT. The companion compares the approved 20:00 with the Artisan field, which still reads 20:30.
Prepared for staff review
What to watch for: The approved values are formatted for staff review before placement.
Boundary rule: A staff member remains in control of placing updates into the EMR.
On-screen narration: The authorized continuation is prepared and shown as ready for staff review in the clinic's system.
Maya's chart is open, so it stops
What to watch for: When Maya Chen's chart is open in the EMR tab, OvaFlow halts placement immediately.
Boundary rule: Cross-patient chart mismatches trigger a hard stop before any field is touched.
On-screen narration: Maya Chen's Cycle Sheet is open in the browser, so continuation stops. Back on Elena's chart, the modeled Artisan trigger update is reviewed.
Lost sight of the EMR, not assumed done
What to watch for: During placement on Elena's chart, window visibility drops and the status changes to 'Observation interrupted'.
Boundary rule: If OvaFlow loses sight of the EMR mid-action, it never assumes the save finished.
On-screen narration: The workstation drops after the save in Artisan. OvaFlow shows that it lost sight of the EMR and that the EMR update is not yet confirmed, and nothing is repeated. My work still shows Dr. Priya Shah's 17:07 PDT approval under Completed. Back to the reconciliation task.
Reading the record back from Artisan
What to watch for: The companion re-reads Elena's Cycle Sheet and verifies the saved value before marking the step complete.
Boundary rule: Readback from the EMR screen is required to clear an interrupted observation.
On-screen narration: The Artisan Trigger & Pre-op instructions and egg retrieval schedule are read back to confirm the update.
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.
- Nora Ruiz, RNIVF nurse coordinator
- Dr. Priya ShahREI physician
Elena RiveraPatient
Maya ChenPatient
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.
- ArtisanModeled workflow exampleFertility EMR, lab & practice managementNot yet checked against a real clinic build
Artisan: Rebuilt from public help articles; how an existing instruction is edited is our own stand-in.
Show 2 systems often found around this workflow
Systems a clinic running this workflow often uses. They do not appear in this recording.
Microsoft EdgeManaged browser
Google ChromeManaged browser
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.
Journey stages
Show all pages where this walkthrough appears
Questions & answers
Common questions about this walkthrough
What clinicians, coordinators, practice leaders, and patients ask when reviewing Walkthrough 3.
Is this walkthrough showing a live connection to Artisan?
No. It shows a modeled Artisan interface in our design prototype to demonstrate how OvaFlow is designed to work beside a clinic's EMR.
Why does OvaFlow show 'Approved at 17:07 PDT; Artisan field unchanged'?
So coordinators never mistake a physician's approval inside the coordination queue for a completed entry inside the EMR Cycle Sheet.
Show 1 more walkthrough questions
What clears an 'Observation interrupted' status?
Re-establishing sight of the matching patient's Cycle Sheet and reading the saved value back from the screen.
Related
Watch these next.
Show 1 more related walkthroughs
Daily care: the 8:20 PM report and the evening handoff
Elena says she injected at 8:20, not 8:00. Her words are kept as she said them, the signed instruction stays as signed, and the evening callback changes hands only when Alex accepts it.
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.