Product preview · Fictional patient data
Safety model
Most coordination mistakes happen when one fact is mistaken for another: a read message for an accepted handoff, a published instruction for an understood one. OvaFlow is designed to keep each fact distinct.
Nine facts
A read receipt is not an acknowledgment. A booked room is not a clearance. Each of these needs its own evidence before anyone relies on it.
| Fact | Evidence needed | Does not establish |
|---|---|---|
| Source received | An identifiable source and the time it was received | That anyone reviewed it, or that it is valid |
| Clinician signed | The authorized signer, the revision and the signing event | That follow-up work is done |
| Published | A matching record in the destination system, for the right revision | Delivery, reading or acknowledgment |
| Delivered | The channel's own delivery evidence | Who read it, or whether it was understood or used |
| Read receipt | The channel's own read evidence | Acknowledgment, understanding, reported use or accepted responsibility |
| Acknowledged | An attributed acknowledgment of the current instruction | Correct performance or completed clinical review |
| Patient reported use | The original report, the reported time and the received time | A rewritten prescription or a verified administration |
| Coverage accepted | A named person, scope, time and acceptance | Closure of separately owned clinical work |
| Clinically resolved | An authorized clinical resolution with current evidence | That every administrative or lab task is complete |
Design rules
Uncertainty
When OvaFlow can't establish the current patient, source or outcome, the affected action is held and the uncertainty is shown, rather than guessed.
How tasks pause and close
Clinical safety incidents rarely come from a single broken database; they happen when software conflates delivery with understanding or retries blindly after a timeout [1, 2, 3].
Common shortcut: Marking a task reassigned as soon as the on-call nurse opens the message thread.
OvaFlow rule: 'Coverage offered' at 20:26 PDT stays in Nora Ruiz's queue until Alex Kim explicitly clicks Accept at 20:28 PDT.
Prevents orphaned evening follow-ups during shift change [1].
Common shortcut: Re-submitting a portal message when the browser spinner times out after 10 seconds.
OvaFlow rule: Enters 'Publication outcome unknown' and prompts an EMR readback check before any repeat send.
Prevents duplicate or out-of-order medication messages reaching the patient.
Common shortcut: Allowing 'Confirm' on any older text notification link in the patient's inbox.
OvaFlow rule: Version 3 (20:00 PDT) immediately retires Version 2 (20:30 PDT) as a superseded instruction; old links redirect to Version 3.
Prevents a patient from confirming an outdated 8:30 PM trigger time after the 8:00 PM amendment was signed.
Common shortcut: Showing only arrived lab results so a delayed outside draw looks like a quiet afternoon.
OvaFlow rule: Tracks every ordered draw or PGT biopsy as an 'Expected result' and shows the last verified check time.
Aligns with ONC SAFER Test Results Reporting guidance [3].
See it
Recordings of the interactive design prototype, with fictional patients and staff.
A late estradiol result, a newly signed trigger time, the wrong chart caught before publishing, and a lost confirmation checked rather than blindly resent.
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.
Saving a trigger doesn't tell the patient or the lab. Portal distribution, the lab change order and a message that was read but not accepted are each tracked separately.
Safety model
Tell us the fact your team most often mistakes for another. We will show how it stays separate.