What exists today
- 29 prototype walkthroughs (a design-artifact count)
- An interactive sandbox at /demo
- Product requirements and a 33-gap workflow research audit
Product preview · Fictional patient data
Readiness & clinic testing
We label maturity the same way everywhere on this site, so nothing is mistaken for more than it is.
Honest status
Four gates
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.
Vocabulary
The same seven labels appear on every page, card and walkthrough.
| Label | Meaning |
|---|---|
| Interactive sandbox | The clickable /demo simulation, with fictional data and no EMR connection |
| Prototype walkthrough | A recording of an interactive design prototype, with fictional data |
| In the first pilot | Planned for the first clinic pilot (daily-care coordination) |
| Planned after the pilot | The treatment and patient expansion, including the patient companion |
| Later phase | Broader lab, cryo and long-term continuity |
| Design prototype | iPhone, Apple Watch and widget app concepts |
| Tested in your clinic first | An EMR operation that must be tested in the clinic's own setup before it is enabled |
Toward a pilot
What a pilot needs, one operation at a time.
Research count
Our IVF workflow gap audit grouped them by where they happen. They are product hypotheses to test with clinics, not findings about any clinic.
Testing & downtime
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].
Fallback rule: Any operation that cannot pass all four steps in a clinic's own EMR stays an explicit manual step.
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.
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.
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.
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.
See it
Recordings of the interactive design prototype, with fictional patients and staff.
Four fictional patient examples across three modeled EMRs, a map of 300+ designed product states, and the research behind each boundary.
Fourteen designed recovery states, from an unplugged headset to a blocked remote-desktop clipboard, each keeping the draft and the right patient.
Readiness
We will map which operations your clinic would test first, and what each one needs.