Skip to main content

Product preview · Fictional patient data

OvaFlow

Readiness & clinic testing

Exactly what exists today.

We label maturity the same way everywhere on this site, so nothing is mistaken for more than it is.

Examples use fictional patient data

Honest status

What is here, and what is not

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

Four gates

What “ready” means

Each stage has to be met in full before the next one starts. This site shows prototype walkthroughs and a sandbox, and claims nothing beyond them.

  1. Demo-readyFictional scenarios and interactions are coherent
  2. Engineering-readyBoundaries, state changes and failures run in controlled tests
  3. Pilot-readyThe exact clinic, operations, devices, permissions and support arrangement have passed their gates
  4. Generally availableThe supported deployments, operations, monitoring and support commitments are demonstrated and documented

Vocabulary

The labels you'll see

The same seven labels appear on every page, card and walkthrough.

Maturity labels used across the site
LabelMeaning
Interactive sandboxThe clickable /demo simulation, with fictional data and no EMR connection
Prototype walkthroughA recording of an interactive design prototype, with fictional data
In the first pilotPlanned for the first clinic pilot (daily-care coordination)
Planned after the pilotThe treatment and patient expansion, including the patient companion
Later phaseBroader lab, cryo and long-term continuity
Design prototypeiPhone, Apple Watch and widget app concepts
Tested in your clinic firstAn EMR operation that must be tested in the clinic's own setup before it is enabled

Toward a pilot

What a pilot needs

What a pilot needs, one operation at a time.

  1. Choose the operations a clinic wants, one at a time
  2. For each EMR: read the source, prepare a draft, check the update in the EMR, pause and hand off
  3. Test each operation in the clinic's own setup
  4. Keep anything that can't meet its contract as an explicit human step

Research count

33 workflow gaps a pilot would test

Our IVF workflow gap audit grouped them by where they happen. They are product hypotheses to test with clinics, not findings about any clinic.

  1. 8Before treatment startsGetting the right path, people and prerequisites in place.
  2. 8During a treatment cycleKeeping the plan, the people and the actual events lined up.
  3. 7In the lab and in storageExact material, exact decisions, across people and facilities.
  4. 5After transferStaying with patients through every outcome.
  5. 5Continuity, access and evidenceWhat keeps a clinic working, and keeps it honest.

Testing & downtime

Tested one operation at a time

Instead of claiming blanket EMR compatibility, OvaFlow tests one operation at a time against a four-step contract and an ONC SAFER-aligned downtime recovery plan [1, 2, 3].

Tested per operation

Four steps an EMR action must pass before a clinic enables it

Tested per clinic
  1. Step 01 · Prepare
    Read signed sourceParse the clinician-signed version, author, and timestamp before staging a draft.
  2. Step 02 · Validate
    Check chart & roleConfirm the open EMR chart matches the draft's patient and the revision is still current.
  3. Step 03 · Commit
    Human action in EMRA qualified staff member reviews, edits, and saves the update in the clinic's own EMR.
  4. Step 04 · Reconcile
    Readback verificationCheck the saved EMR record to confirm what was written before closing the task.

Fallback rule: Any operation that cannot pass all four steps in a clinic's own EMR stays an explicit manual step.

Before a pilot starts

What a clinic team and OvaFlow verify together

01 · EMR screen layout & version drift check (nAbleIVF, eIVF, Artisan examples)

Why it matters: Clinics customize templates, field labels and browser zoom levels across workstations.

Pilot gate: Test each field selector and patient-banner check against the clinic's exact EMR build; halt observation if an unrecognized screen change appears.

Never assumes a modeled demo reconstruction matches a live clinic screen without testing.

02 · Network outage & downtime reconciliation (ONC SAFER Contingency Guide)

Why it matters: During an internet or EMR outage, nurses record trigger confirmations and lab calls on paper or phone logs [1].

Pilot gate: Enter 'Observation interrupted' with the last verified time, freeze automatic closures, and run a structured paper-to-chart reconciliation checklist when service returns.

Never marks an overdue task complete while observation is interrupted.

03 · Time-zone & daylight-saving boundary verification

Why it matters: Retrieval intervals (36.0h, such as Oct 30 20:00 PDT to Nov 1 07:00 PST) cross daylight-saving transitions and state lines.

Pilot gate: Verify that every timestamp stores both local wall-clock time and UTC offset before enabling trigger-to-retrieval scheduling helpers.

Never computes elapsed hours from bare wall-clock strings without an explicit offset.

04 · Scoped permissions & incident audit trail

Why it matters: Medical directors and quality leads need an immutable trace of who prepared, reviewed, accepted or held each step [3].

Pilot gate: Verify role-based access rules and exportable audit logs with clinic IT and quality leadership before pilot launch.

Administrative accounts cannot sign clinical orders or alter historical timestamps.

Common questions

Questions clinics ask about readiness & clinic testing

What does the four-step EMR operation contract (Prepare, Validate, Commit, Reconcile) mean in practice?

Before any EMR-facing operation is enabled in a clinic pilot, we test four steps in that clinic's own environment: (1) Prepare a draft from a verified source, (2) Validate patient identity, role permissions and revision currency, (3) Commit the action with human review in the clinic's EMR, and (4) Reconcile by reading back the saved EMR record. If any step cannot be verified reliably, the operation remains a manual human step.

Does mentioning nAbleIVF, eIVF or Artisan mean OvaFlow has a live vendor partnership or integration?

No. All references to nAbleIVF, eIVF and Artisan on this website are modeled workflow examples reconstructed from public documentation and clinical workflow research to illustrate how OvaFlow is designed to sit beside each system. No vendor endorsement or live connection is claimed.

How does a clinic pilot handle planned EMR maintenance or unexpected network downtime?

Guided by the ONC SAFER Contingency Planning checklist, pilot readiness includes an explicit downtime runbook: when observation is interrupted, OvaFlow freezes automated queue closures, displays the last verified timestamp, and requires line-by-line reconciliation of paper or phone logs before normal operation resumes.

Where do the 33 workflow gaps listed on this page come from?

They come from our October 2026 IVF Workflow Gap Audit synthesizing 2024–2026 guidelines from WHO, NICE (NG257, NG126), ASRM, ESHRE, SMFM, ASA, ASCO and ONC SAFER. They represent product hypotheses to test with clinics during pilot evaluation.

See it

Watch it hold in a walkthrough

Recordings of the interactive design prototype, with fictional patients and staff.

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.

0:26Browser with the compact recovery companion

Readiness

Talk about a pilot, honestly.

We will map which operations your clinic would test first, and what each one needs.