Product preview · Fictional patient data
Integrations
OvaFlow is designed to sit next to the chart a clinic already uses. The fertility EMR keeps the system-of-record chart, orders, prescriptions and signatures. OvaFlow keeps the signed source, the named owner and the next step in view across labs, pharmacies and patient channels, and checks the chart before it calls anything done.
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.
[ Architecture ]
Scroll to take the screen apart. What looks like one window is the clinic's EMR, a companion beside it, and two rules that decide when work is really done.
Route order
Each thing OvaFlow does beside an EMR is decided on its own, using the first route the clinic and vendor permit. Switch a route off to see where an operation lands.
This operation would usePermitted structured API
Standards, protocols & worked trace
Hospital EHRs and specialty IVF systems use different generations of healthcare standards side by side. Understanding what each layer carries explains why a clinical companion must qualify operations individually rather than claiming a single universal plug.
Oct 30, 2026 (16:45–20:28 PDT) across the Nov 1 daylight-saving change to 07:00 PST retrieval · Every clinical save and signature stays in the source system.
Actor: Automated lab interface
Elena Rivera's Day 10 afternoon estradiol (2,980 pg/mL) and progesterone (0.9 ng/mL) post to the West Clinic cycle flowsheet.
Expected-result timer clears; Dr. Mira Lee is notified to review trigger timing.
Actor: Dr. Mira Lee, MD
Signs hCG trigger instruction v3 for 20:00 PDT on Oct 30 (superseding v2 at 20:30 PDT) so egg retrieval stays aligned 36 hours later at 07:00 PST on Nov 1 across the daylight-saving change.
Version v2 is marked superseded; four linked follow-up tasks open with named owners.
Actor: Nora Ruiz, RN → Lab
Submits the retrieval schedule change order in the EMR and checks that the embryology lab acknowledges the 07:00 PST maturity window.
Lab schedule task stays open in amber until embryology records acknowledgment.
Actor: Nora Ruiz, RN → Elena Rivera
Nora releases v3 (8:00 PM PDT) to the portal while older links to v2 (8:30 PM) are blocked. Elena reports taking her trigger shot at 8:20 PM PDT (received 20:22 PDT).
Shown as patient self-reported at 8:20 PM PDT until evening nursing follow-up.
Actor: Nora Ruiz, RN → Alex Kim, RN
Nora offers the 20-minute trigger offset callback to on-call nurse Alex Kim, RN at 20:26 PDT. Alex explicitly accepts at 20:28 PDT.
Ownership moves only on explicit acceptance at 20:28 PDT; clinical order authority stays with Dr. Lee.
Across reference labs (Quest Diagnostics, Labcorp) and hospital interfaces, HL7 Version 2 messages carry patient registration (ADT), specimen orders (ORM) and structured immunoassay or endocrine results (ORU). Amendment flags arrive here, but complex embryology cohorts and multi-follicle diagrams rarely fit flat segments.
Fast Healthcare Interoperability Resources (FHIR) and the SMART App Launch Framework let hospital EHRs such as Epic launch external tools with patient and encounter context. Fertility EMRs adopt APIs selectively, so API access is always Rung 01 when licensed—and never assumed where absent.
Electronic prescriptions, pharmacy clarification requests (RxChange) and cancellation messages (CancelRx) travel between the clinic's EMR prescribing module and specialty fertility pharmacies. OvaFlow surfaces open clarifications and patient delivery confirmations without ever transmitting prescriptions itself.
When an operation lives inside a web-based flowsheet or a Windows desktop window, an approved browser extension or Microsoft Windows UI Automation inspects the open chart header and target field so staff can review, place and read back saves without losing custody across Citrix or browser timeouts.
HL7 International · HL7 Version 2.x (V2) Messaging Standard Product Brief (verified 2026-11-03)
Clinical messaging standard governing ADT registration, ORM order and ORU observation result exchanges.
HL7 International · FHIR Overview (Fast Healthcare Interoperability Resources) (verified 2026-11-03)
Modular healthcare resource definitions and RESTful API exchange architecture.
HL7 International · SMART App Launch Framework Implementation Guide (verified 2026-11-03)
Open specification for launching clinical applications alongside an EHR session with OAuth 2.0 context.
Surescripts, LLC · E-Prescribing Network Capabilities (NewRx, RxChange, CancelRx) (verified 2026-11-03)
Electronic prescription routing, change request and cancellation messaging between prescribers and pharmacies.
Microsoft Learn · UI Automation Overview (Win32 & .NET Accessibility Framework) (verified 2026-11-03)
Operating-system accessibility framework for programmatic inspection of Windows desktop controls.
Citrix Documentation · ICA Policy Settings — Client Clipboard Redirection (verified 2026-11-03)
Virtual desktop policy controls governing clipboard transfer between host endpoints and remote sessions.
Modeled EMR contexts
nAbleIVF, eIVF and Artisan screens were reconstructed from reference material so the walkthroughs could show where OvaFlow sits. They are modeled workflow examples, not live connections.
Fictional patient dataModeled workflow exampleAllergy history, a monitoring note with a save check, and a specimen label stop.4 prototype walkthroughs
Fictional patient dataModeled workflow exampleV6 referenceA note save check, a financial hold on cycle start, the clinic's own e-prescribing and a PGT stop.3 prototype walkthroughs
ArtisanFictional patient dataModeled workflow exampleNot yet checked against a real clinic buildA trigger approval, a wrong-chart stop and an interrupted view that is never assumed done.3 prototype walkthroughsEcosystem
Shown with each owner's own logo where one is available; others appear as plain names. OvaFlow is designed to work beside them, and none of them is affiliated with OvaFlow. Open a system to see what stays there and what OvaFlow keeps in view.
Where the clinic documents: the chart, orders, signatures and every save.
Accessioning, results, amended reports and the lab's own determinations.
Witness records, specimen custody, cryostorage inventory and tank monitoring.
Prescription routing, dispensing and delivery.
Benefit eligibility, authorizations and reimbursement.
Education modules and signed consent.
The channel itself: messages, templates, delivery and calls.
The workstation, browser and remote desktop the clinic manages.
The phone and watch people already carry.
Run something else?
Tell us which systems your clinic uses, and we will show what testing in your clinic would involve.
Request a walkthroughThird-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.
Touchpoints
Microsoft Teams
Apple Messages for BusinessThird-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.
Walkthroughs
Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional.
Four fictional patient examples across three modeled EMRs, a map of 300+ designed product states, and the research behind each boundary.
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.
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.
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.
Questions
No. OvaFlow is designed to sit beside the fertility EMR your team already documents in. Physicians, nurses and embryologists keep working in their system of record. The EMR screens on this site are modeled reconstructions with fictional patients, not live clinic connections or vendor endorsements.
Preparing a draft never marks it as saved or sent. Switching to another patient's chart pauses drafting immediately so text can't cross between patients. If the view is interrupted before the chart confirms a change, the item is held for a person to inspect instead of being tried again in the background.
No EMR is marked as broadly supported, and no off-the-shelf connection is claimed. Each operation would be tested on a clinic's own licensed EMR build and workstations, after a formal privacy review and signed agreements.
They are the systems IVF clinics commonly run—fertility EMRs, reference and PGT genetics labs, electronic witnessing systems, automated cryostorage, e-prescribing networks, specialty pharmacies, fertility benefit managers and patient channels—so they show where OvaFlow would sit in a real day. Showing them implies no affiliation, endorsement or live connection.
General hospital EHR standards such as HL7 FHIR R4 and SMART on FHIR cover demographics, problems, medications and standard diagnostic reports well, while HL7 v2 messages commonly carry lab orders (ORM) and results (ORU). However, daily fertility coordination spans multi-follicle ultrasound flowsheets, minute-specific trigger amendments across daylight-saving transitions, embryo cohort biopsy lineage, two-person lab witnessing and specialty-pharmacy cold-chain delivery checks that often live across several specialized tools. OvaFlow therefore qualifies each operation individually along a five-rung route ladder where human continuation is always available.
In a fertility cycle, moving a trigger injection by even thirty minutes touches the signed EMR order, the retrieval room and anesthesia schedule, the embryology lab's 36-hour maturity window, the patient portal instruction, and the evening on-call nursing handoff. OvaFlow keeps all of those downstream follow-ups linked to the new signed version, blocks older links from showing superseded times, and tracks each follow-up separately until the receiving person or system confirms it.
Many clinics publish their EMR or lab applications through Citrix virtual desktops where IT policies restrict clipboard redirection or browser extensions. When clipboard transfer is blocked or a browser session times out, OvaFlow holds the reviewed draft attached to the patient's task rather than losing it or pasting blindly into an unverified window.
Evaluation starts with the recorded walkthroughs and clickable sandbox using fictional records (Elena Rivera, Maya Chen, Jordan Patel, Avery and Sam), followed by a seven-step pilot qualification process on a test environment of the clinic's own licensed EMR build—including intentional failure drills—before any operation is used on a clinical shift.
Your EMR, your build
Walk through the modeled nAbleIVF, eIVF or Artisan examples with our team, and what testing in your clinic would involve on its own EMR build.