Product preview · Fictional patient data
Modeled workflow example
Reconstructed from Artisan's public reference articles, with fictional patients. It shows a trigger approval, a wrong-chart stop and a view that drops mid-check, and how none of them is ever assumed done.The Artisan walkthrough replays Elena's trigger change as its own modeled example, with Dr. Priya Shah approving. That is why its names and times differ from the daily-care story.
From the Artisan walkthrough
The trigger update is prepared for Elena Rivera. If Maya Chen's chart is the one open when staff continue, OvaFlow blocks the step, keeps Elena's prepared update and says which chart it expected.
OvaFlow
Prepared for Elena
The wrong chart is open
The approved trigger update is ready. A person continues it in Artisan.
The open chart doesn't match. The step is blocked and not attempted. Elena's update is kept.
Staff return to Elena's chart, it is rechecked, and the update continues in Artisan.
What was modeled
Reconstructed from Artisan's public reference articles on trigger and retrieval scheduling, schedule change orders and staff messaging. No clinic build was available. How an existing trigger is edited or regenerated, and what follows from it, is synthetic until checked on a licensed clinic build.
Dr. Priya Shah's 17:07 PDT approval moving Elena Rivera's trigger from 20:30 PDT to 20:00 PDT is compared read-only with the unchanged 20:30 field in the EMR. OvaFlow leaves the EMR's own fields alone.
Watch it inArtisan: trigger approval, the wrong chart and an interrupted viewWhen Maya Chen's chart is open on the workstation instead of Elena Rivera's, placement stops immediately and holds the draft until Elena's chart is in front of staff.
At 17:08 PDT the workstation view drops right after the save in Artisan. The status says so plainly, and the Artisan record is read back at 17:11 PDT before anything closes.
Saving a trigger in the chart doesn't tell the patient or the lab. The portal release, the embryology lab's schedule change order and the evening nursing handoff are each tracked on their own.
Watch it inArtisan: portal distribution, lab change order, read vs acceptChloe Park, RN reads the staff message at 17:22 PDT. Nora Ruiz, RN stays responsible for the evening trigger follow-up until Chloe explicitly accepts at 17:25 PDT.
Check in the EMR
An interrupted view stays unverified
In the modeled trigger amendment, the companion loses sight of the chart after the save. It says so, and waits for a read-back.
Status wording matches the product exactly. Times and names are fictional.
Stays in the EMR
OvaFlow can prepare, compare and remind. These steps stay with qualified staff in the system of record.
Artisan · Public reference profile & swimlane trace
Artisan Medical Solutions, LLC publicly documents Artisan as a cloud-based fertility EMR and practice management platform covering ART cycle calendars, trigger and retrieval scheduling, cryostorage inventory and patient portal communications [1]. Because no real clinic Artisan build was available to us, our Artisan walkthroughs were reconstructed from Artisan's public reference articles and carry an explicit qualification banner.
Reconstructed from Artisan public reference articles (not yet tested on a live clinic build) · Standalone modeled example with fictional patient Elena Rivera and Dr. Priya Shah.
Artisan ART Cycle Day Sheet and Trigger/Pre-op Instruction fields (still showing 20:30 PDT) [1].
Compares Dr. Priya Shah's 17:07 PDT approval (20:00 PDT) read-only against the unchanged 20:30 field in Artisan.
OvaFlow never overwrites the EMR's instruction template; staff update the field in Artisan.
Patient banner and MRN header inside the active browser tab (Maya Chen's chart is open) [1][2].
Detects that Maya Chen's chart is focused while Nora Ruiz, RN is working on Elena Rivera's trigger update.
Hard stop: placement is blocked and Elena's draft is held until Elena Rivera's chart is active.
Database commit of the updated 20:00 PDT record on the Artisan ART Day Sheet [1].
At 17:08 PDT the workstation view drops right after Save; status turns amber (“Observation interrupted”).
No blind retry. At 17:11 PDT Nora restores the view and reads back the saved 20:00 PDT record in Artisan.
Portal publish control, lab schedule change order form and internal staff messaging in Artisan [1].
Tracks portal release, lab acknowledgment and evening RN handoff as three independent checklist items.
Chloe Park, RN reading the message at 17:22 PDT leaves Nora as owner; Chloe clicking Accept at 17:25 PDT moves ownership.
Every Artisan workflow shown here is reconstructed from public reference articles and must be checked against a real clinic build before use.
| Clinical workflow | Stays in Artisan (system of record) | Kept in view by OvaFlow | Why the boundary matters |
|---|---|---|---|
| Trigger & pre-op instructions | Practitioner approval, editing or regenerating Trigger/Pre-op Instructions in Artisan [1]. | Read-only comparison between the signed approval and the current field value. | Prevents an unverified script from overwriting a clinic's custom instruction template. |
| Active chart identity check | Patient banner, MRN and cycle identifier inside the open Artisan tab [1]. | Continuous patient-context verification that halts placement if another chart is in front of staff. | Eliminates cross-patient copy-paste errors when nurses juggle multiple monitoring tabs. |
| Interrupted save recovery | Database commit of the ART Day Sheet and instruction record [1]. | Holds “Observation interrupted” state on connection drop until a fresh readback confirms the chart. | Avoids both silent failure (thinking a save happened when it didn't) and blind retry (double entry). |
| Portal, lab & nursing handoffs | Portal publish button, lab schedule change order form and internal staff messaging [1]. | Tracks portal release, lab acknowledgment and explicit RN handoff acceptance (17:22 read vs. 17:25 accept) as three independent items. | Saving a chart field never guarantees the patient saw the change or the evening nurse took ownership. |
Questions
Because we built our Artisan walkthroughs from Artisan Medical Solutions' public help and reference articles rather than a live licensed clinic environment. In particular, how an existing Trigger/Pre-op Instruction is edited or regenerated in our prototype is our own synthetic stand-in until a clinic tests it on its own Artisan build.
In the main daily-care story, Dr. Mira Lee signs Elena Rivera's trigger amendment at 17:10 PDT and Alex Kim, RN accepts the evening handoff. The Artisan walkthroughs replay Elena's trigger amendment as a self-contained modeled example where Dr. Priya Shah approves at 17:07 PDT and Chloe Park, RN accepts the handoff at 17:25 PDT.
Instead of assuming the save worked or re-submitting the form in the background, OvaFlow displays “Observation interrupted” with the last verified timestamp (17:07 PDT) and waits for staff to re-open the chart and read back the saved record at 17:11 PDT.
A read receipt only proves a message was opened on a screen—not that the receiving nurse has capacity or has agreed to take the clinical follow-up. Nora Ruiz, RN remains the named owner until Chloe Park explicitly clicks Accept at 17:25 PDT.
Artisan Medical Solutions, LLC · Artisan Fertility EMR — Cloud ART Cycle Management, Lab & Portal Overview (verified 2026-11-03)
Public overview of Artisan's fertility EMR, cycle calendars, cryostorage inventory, patient portal and SART reporting.
Microsoft Learn · UI Automation Overview for Windows Desktop Applications (verified 2026-11-03)
Technical reference for inspecting window focus, patient banners and control states without stealing keyboard input.
Walkthroughs
Artisan appears as a modeled workflow example built from public references. It has not yet been checked against a real Artisan clinic build, and how an existing instruction is edited is our own stand-in. These walkthroughs replay Elena's trigger change as a separate modeled clinic example, with Dr. Priya Shah as the approving physician; times are fictional.
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.
Saving a trigger doesn't tell the patient or the lab. Portal distribution, the lab change order and a message that was read but not accepted are each tracked separately.
Four fictional patient examples across three modeled EMRs, a map of 300+ designed product states, and the research behind each boundary.
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.
Run Artisan?
We'll show the modeled workflow, then talk through what testing it on your clinic's own build would involve.