Product preview · Fictional patient data
Walkthrough 5 of 29 · Desktop
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.
nAbleIVF: allergy check, monitoring note, save check, specimen stop, muted recording of the design prototype. Fictional patient data.
Chapter 1 of 6: Maya's intake history
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
Beside a modeled nAbleIVF view, a reported allergy is compared against the chart and handed to the nAbleIVF allergy section without saving anything automatically. Elena's Day 8 monitoring note is dictated, reviewed and placed, and the patient message counts as sent only once nAbleIVF's message history shows it.
Morning monitoring and intake review in high-volume IVF clinics move through dozens of patients per hour. While working beside an EMR such as nAbleIVF, nurses reconcile patient-reported allergies from intake forms, check specimen labels for semen analysis or bloodwork, document transvaginal ultrasound follicle counts and estradiol notes, and send portal updates. Two failure modes are especially dangerous: proceeding when a specimen container label does not match the open chart, and assuming a clicked Save or Send button persisted when the EMR rejected or dropped the request.
In this walkthrough beside a modeled nAbleIVF screen, the nurse reviews Maya Chen's intake history and flags a patient-reported latex/medication allergy that is not yet in the chart's allergy banner, holding it for clinician verification. Next, a specimen barcode/label mismatch triggers an immediate hard stop before laboratory review can continue. Turning to Elena Rivera's Day 8 monitoring visit, the nurse places the ultrasound and estradiol follow-up note, checks the saved record in nAbleIVF, spawns the resulting follow-up tasks, and verifies the patient message in the portal's sent history.
Nora Ruiz, RN
Spots reported allergy missing from chart banner
OvaFlow safeguard
Detects label mismatch against active chart
Nora Ruiz, RN
Places monitoring note and checks saved state
Nora Ruiz, RN
Verifies sent message in portal history
How the companion separates patient-reported allergies from verified chart banners, halts on specimen mismatches, and checks saved notes in a modeled nAbleIVF view.
Guardrail: Specimen label discrepancies halt the workflow immediately, and placed notes are checked against the saved EMR record.
What to watch for
Beside a modeled nAbleIVF view, a reported allergy is compared against the chart and handed to the nAbleIVF allergy section without saving anything automatically. Elena's Day 8 monitoring note is dictated, reviewed and placed, and the patient message counts as sent only once nAbleIVF's message history shows it.
Follow the exact timestamps, UI status changes, and coordination safeguards as the recording plays.
What to watch for: Maya Chen's structured intake summary sits in the 384 px companion beside her modeled nAbleIVF chart.
Boundary rule: Intake capture organizes patient-provided history for staff review; it does not auto-populate the legal chart.
On-screen narration: Maya Chen's intake history opens in a modeled nAbleIVF view.
What to watch for: A patient-reported allergy is highlighted against the empty EMR allergy list and routed for clinician verification.
Boundary rule: OvaFlow flags the discrepancy visibly rather than silently overwriting the EMR allergy banner.
On-screen narration: A penicillin rash Maya reported is compared against the allergy list in her chart. The allergy is handed to the nAbleIVF allergy section without saving anything automatically. The allergy item stays open in the open-work queue.
What to watch for: When a specimen label does not match the active patient record, a red stop banner blocks further review.
Boundary rule: No specimen task can advance while identifiers disagree.
On-screen narration: A specimen label for Jordan Patel doesn't match the original report, so review stops.
What to watch for: Switching to Elena Rivera's Day 8 monitoring visit, the nurse places the note and runs a save check.
Boundary rule: Placing text into an EMR field is distinct from confirming the EMR saved it.
On-screen narration: Elena Rivera's Day 8 monitoring review opens. The clinician dictates the Day 8 cycle note. The transcribed note is reviewed against the monitoring ultrasound and labs. The reviewed text is placed in the nAbleIVF cycle-note field.
What to watch for: Approved follow-up tasks and the patient portal message are prepared from the verified Day 8 note.
Boundary rule: Downstream tasks link back to the verified monitoring note.
On-screen narration: Linked care-team and patient follow-up tasks are prepared. The patient monitoring message draft is reviewed. Staff continue in the nAbleIVF message composer.
What to watch for: After sending the portal update, the companion checks the portal's message history to confirm delivery.
Boundary rule: The task closes only after the message appears in the clinic portal's sent log.
On-screen narration: Staff press Send in nAbleIVF. The task waits for a person to check the sent log. The sent entry is confirmed in the nAbleIVF message history.
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
Every patient, family member, clinician and clinic in these stories is fictional. Names, times and screens come from prototype walkthroughs, not from real care.
Maya ChenPatient
Elena RiveraPatient
Jordan PatelPatientNamed 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 managementSystems a clinic running this workflow often uses. They do not appear in this recording.
Microsoft EdgeManaged browser
Google ChromeManaged browserThird-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
This recording is part of these pages. Each one explains the step in more depth.
Questions & answers
What clinicians, coordinators, practice leaders, and patients ask when reviewing Walkthrough 5.
Allergy banners drive prescribing alerts in the clinic's EMR. OvaFlow highlights the patient-reported allergy and holds it for a clinician or nurse to verify and record in the EMR.
The companion blocks the workflow step immediately and keeps the mismatch visible until laboratory and nursing staff reconcile the specimen in the clinic's own system.
After the nurse saves the note in the modeled nAbleIVF screen, the companion reads the committed record state back to confirm the note persisted.
Related
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.
Consult notes captured with consent, paused for private moments, reviewed, then checked as saved rather than assumed.
From duplicate barcodes to cold-chain delivery and the patient's own “received”, every handoff to the clinic's own system has an owner and a confirmation.
Next step
We'll replay this flow against your roles and handoffs, using fictional records. Please don't send patient data.
