Skip to main content

Product preview · Fictional patient data

OvaFlow

Walkthrough 6 of 29 · Desktop

eIVF: note save, financial blocker, e-prescribing handoff, PGT stop

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.

Length
0:27
Chapters
6
Shown on
Browser with the 384-pixel compact companion
  • In the first pilot
  • Prototype walkthrough · Fictional patient data
  • eIVF · Modeled workflow example
  • Tested in your clinic first

eIVF: note save, financial blocker, e-prescribing handoff, PGT stop, muted recording of the design prototype. Fictional patient data.

Chapter 1 of 6

Chapter 1 of 6: Confirm where the note goes

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.

Beside a modeled eIVF (V6 reference) view, a consultation note is placed and its save is checked. An unresolved financial authorization is visible before the cycle starts, a dictated dose change is handed to eIVF's own e-prescribing workflow, and a PGT biopsy label mismatch stops review.

What clinical situation this depicts

Before a patient starts gonadotropin injections or undergoes embryo biopsy and transfer, several cross-departmental gates must align: clinical note placement in the right chart section, prior authorization or financial clearance for specialty medications, electronic prescribing inside the EMR, tracking of outside diagnostic labs, and exact identifier matching on preimplantation genetic testing (PGT) reports. In clinics using comprehensive EMRs such as eIVF, each of those activities lives in a different module.

Recorded beside a modeled eIVF interface, this walkthrough shows six distinct safeguards in sequence: confirming the exact chart destination before placing a note, verifying the saved note, holding cycle start when a required financial authorization item is still pending, routing gonadotropin dose changes back to eIVF's own e-prescribing module rather than handling prescriptions in the companion, tracking overdue outside lab follow-ups with named owners, and stopping immediately when a PGT report label does not match the patient's chart identifiers.

Step-by-step workflow

Modeled eIVF gates: note save check, readiness hold, EMR e-prescribing, and PGT stop

Step 1Modeled eIVF note

Nora Ruiz, RN

Confirms chart destination and checks save

Save check passed
Step 2Cycle start checklist

OvaFlow safeguard

Holds start on pending prior authorization

Readiness hold
Step 3eIVF e-prescribing

Dr. Mira Lee

Completes dose order inside the EMR

Review in the EMR
Step 4PGT report review

OvaFlow safeguard

Stops on sample identifier mismatch

Identifier mismatch stop

Four coordination boundaries demonstrated beside a modeled eIVF workspace.

Guardrail: Prescribing always returns to the EMR's own e-prescribing module, and PGT identifier mismatches halt review immediately.

What OvaFlow coordinates in this recording

  • Confirms target chart destination and verifies note persistence in the modeled eIVF view.
  • Surfaces pending financial / prior-authorization gates before cycle start and routes dose changes to the EMR's e-prescribing tool.
  • Tracks outside lab follow-ups with named owners and halts review on a PGT report label mismatch.

What stays with clinicians & the clinic's own systems

  • Does not claim a vendor affiliation or live bidirectional feed with eIVF.
  • Never generates, signs, or transmits electronic prescriptions.
  • Never allows a PGT report with mismatched sample identifiers to be marked reviewed.

What to watch for

What could go wrong, and what you'll see instead.

Beside a modeled eIVF (V6 reference) view, a consultation note is placed and its save is checked. An unresolved financial authorization is visible before the cycle starts, a dictated dose change is handed to eIVF's own e-prescribing workflow, and a PGT biopsy label mismatch stops review.

The problems it is designed around

  1. A cycle starting while prior authorization or financial clearance is unresolved.
  2. Dose changes that skip the clinic's prescribing controls.
  3. An outside PGT biopsy label discrepancy slipping past the follow-up queue.

What you'll see in the recording

  1. Destination confirmed, note placed, save checked
  2. A financial authorization holding cycle start
  3. A dose change handed to eIVF e-prescribing
  4. A PGT biopsy label mismatch stop
Chapter-by-chapter guide

Every chapter in this 0:27 walkthrough (6 chapters)

Follow the exact timestamps, UI status changes, and coordination safeguards as the recording plays.

  1. Chapter 10:00 – 0:04

    Confirm where the note goes

    What to watch for: Before placing a clinical note, the companion confirms the target chart and note category in the modeled eIVF screen.

    Boundary rule: Notes are never placed into an ambiguous or unconfirmed chart tab.

    On-screen narration: The destination for the consultation note is confirmed before anything is placed. The reviewed draft is placed in the eIVF note editor.

Show chapters 2–6 (5 more chapters with timestamps & boundary notes)
  1. Chapter 20:04 – 0:08

    Saved, then checked

    What to watch for: Once saved in eIVF, the companion verifies the committed note record.

    Boundary rule: Save verification prevents silent loss of documentation during busy clinic mornings.

    On-screen narration: Staff press Save in eIVF. The task stays open until the saved draft is checked. The saved draft is confirmed in the eIVF record itself.

  2. Chapter 30:08 – 0:13

    A financial item holds cycle start

    What to watch for: A pending financial/prior-authorization requirement holds the cycle-start readiness gate open.

    Boundary rule: Financial holds are visible to the care team early so patients are not surprised at the pharmacy counter.

    On-screen narration: Maya Chen's cycle readiness checklist opens. An unresolved financial authorization blocks cycle start and is shown before anything begins. Back to the clinical and financial readiness overview.

  3. Chapter 40:13 – 0:20

    Dose changes go to eIVF e-prescribing

    What to watch for: When a medication dose change is needed, the companion hands the clinician straight to eIVF's e-prescribing screen.

    Boundary rule: OvaFlow never acts as an e-prescribing system or calculates medication doses.

    On-screen narration: A monitoring review includes a dictated medication change. The details of the dose change are clarified before anything is prescribed. The change is handed to the clinic's own eIVF e-prescribing workflow. OvaFlow does not prescribe. Back to the monitoring overview.

  4. Chapter 50:20 – 0:26

    Outside lab follow-ups

    What to watch for: Pending outside laboratory results appear with expected dates and a single named nurse owner.

    Boundary rule: External diagnostic orders cannot age silently without a responsible owner.

    On-screen narration: The eIVF follow-up queue opens. An order handed to an outside reference lab is tracked. Back to the follow-ups.

  5. Chapter 60:26 – 0:27

    A PGT label mismatch stops review

    What to watch for: A PGT report whose sample identifier disagrees with the chart triggers an immediate stop banner.

    Boundary rule: Embryo genetics documents cannot be attached or cleared when identifiers conflict.

    On-screen narration: A PGT biopsy label doesn't match its source, so review stops.

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.

  • REI physicianDictates and reviews
  • Financial coordinatorOwns the authorization
  • IVF nurseTracks follow-ups
  • Genetics and PGT coordinatorReviews the biopsy label
  • Maya ChenPatient
Fictional patient data

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.

  • Fertility EMR & practice suite

eIVF: V6 reference.

Show 6 systems often found around this workflow

Systems a clinic running this workflow often uses. They do not appear in this recording.

  • Electronic witnessing (RI Witness) & PGT genetics
  • PGT & reproductive genetics lab
  • E-prescribing network
  • Fertility benefits manager
  • Managed browser
  • Managed 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.

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 6.

Why does OvaFlow hand dose changes back to eIVF's e-prescribing module?

Electronic prescribing requires formulary checks, drug-interaction screening, and clinician signature inside the clinic's system of record. OvaFlow tracks the follow-up task around the change but never replaces e-prescribing.

Can a financial or prior-authorization item block emergency clinical care?

No. Readiness gates surface missing financial clearance before routine cycle start so coordinators can resolve coverage or counsel the patient; clinicians always control clinical care.

Show 1 more walkthrough questions
What happens when the PGT report label mismatch fires?

Review stops immediately and the discrepancy is flagged for embryology and clinical verification in the source laboratory record.

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.