Skip to main content

Product preview · Fictional patient data

OvaFlow

Ownership & handoffs

Offer is not accept.

At shift change, a message that was sent or read gets mistaken for a handoff that was accepted. When the on-call nurse is in a room, the evening callback can end up belonging to nobody. In OvaFlow, responsibility moves only when the next person says yes.

In the first pilot · 12 prototype walkthroughsFictional patient data

Handoff · Elena Rivera

Evening callback

Nora Ruiz, RNIVF nurse coordinator
Owner

Drag the baton to Alex, or press it.

Alex Kim, RNEvening on-call nurse

Handoff history

Nothing has happened yet: Nora Ruiz, RN is responsible.

Clinical review pendingDr. Mira Lee keeps the clinical decision in every state.

Illustration · Fictional patient data

For your team

What changes for your team

The same evening callback, with one named owner from the first offer to the last answer.

  1. Reading

    TodayA message that was read is taken as a yes.

    With OvaFlowReading changes nothing. Only an explicit Accept moves the work.

  2. Declines

    TodayA declined callback belongs to nobody.

    With OvaFlowA decline or an expired offer leaves the original owner responsible.

  3. Scope

    TodayHanding off a callback blurs who owns the clinical decision.

    With OvaFlowAcceptance moves only the named work. Clinical review stays with the clinician.

  4. Someone leaves

    TodayA departing colleague's open work goes quiet.

    With OvaFlowTheir open work moves only when a named successor accepts it.

How it works

Someone is responsible at every moment.

  1. 01Before 20:26 PDT

    Owner · Nora Ruiz, RN

    One owner to start

    The evening callback for Elena Rivera belongs to Nora. Her name is on it, and so is the scope.

    ResponsibleNora Ruiz, RN

  2. 0220:26 PDT

    Coverage offered · Nora Ruiz, RN remains responsible

    Offer with a scope

    Coverage is offered for a named piece of work with patient summary and action context. On screen it reads “Coverage offered · Nora Ruiz, RN remains responsible”.

    ResponsibleNora Ruiz, RN

  3. 0320:27 PDT

    Coverage offered · Nora Ruiz, RN remains responsible

    Read is not accept

    Opening, previewing or reading the offer on mobile or desktop changes nothing about who owns the task.

    ResponsibleNora Ruiz, RN

  4. Then either20:28 PDT

    Alex Kim, RN accepted evening nursing follow-up

    Accept moves only that scope

    An explicit accept transfers only the named nursing or operational scope at a recorded time, while clinical review stays with the clinician.

    ResponsibleAlex Kim, RN

  5. Or20:28 PDT

    Offer declined · Nora Ruiz, RN remains responsible

    Decline leaves no gap

    If the receiving person declines or an offer expires unanswered, responsibility stays visibly with the outgoing owner until another route is confirmed.

    ResponsibleNora Ruiz, RN

Clinical review pendingIn every column, the clinical decision stays with Dr. Mira Lee. A handoff moves nursing follow-up, never the clinician’s review.

Illustration · Fictional patient data

Safeguards in play

  • Read is not acceptSeeing or reading a handoff never transfers responsibility. Only an explicit accept does.
  • Decline keeps the ownerIf an offer is declined or expires, the original owner stays responsible, so there is never a gap.
  • Successor acceptanceWhen someone leaves, their open work moves only when a named successor accepts it.
  • Sent isn't acceptedA referral or transfer of care counts only when the receiving team accepts it.

Passing work between shifts

Why reading a message is not accepting a shift handoff

In landmark multi-center research published in the New England Journal of Medicine, implementing the structured I-PASS handoff bundle—which pairs a standardized action list and contingency plan with explicit synthesis and acceptance by the receiving clinician—reduced medical errors by 23% and preventable adverse events by 30% across 10,740 admissions without adding time to the shift change [1].

By contrast, informal chat messages and passive read receipts suffer from the acknowledgment fallacy: outpatient safety studies show that even opened alerts fail to result in timely action when ownership is ambiguous or split across multiple recipients [2]. OvaFlow models every handoff as an explicit contract: offering coverage or opening a message leaves the outgoing nurse visibly responsible (“Coverage offered · Nora Ruiz, RN remains responsible”), declining or timing out leaves zero unowned gap, and accepting transfers only the named scope while clinical review stays with the physician.

Four-role responsibility swimlane · Oct 30, 16:45 → 20:28 PDT

Who owns Elena Rivera’s follow-up at each moment of the afternoon and evening

Read is never accept · Decline leaves no gap
Nora Ruiz, RNDay nurse coordinator
16:45 PDT

Offers afternoon lab follow-up to Lee Park, RN. Nora still owns it when Lee declines.

20:26 → 20:27 PDT

Offers evening callback to Alex Kim, RN. Nora remains responsible while Alex reads the card.

20:28 PDT

Released from evening nursing callback only after Alex explicitly presses Accept.

Lee Park, RNCoverage nurse
16:45 PDT

In an ultrasound room and declines the offer. Zero unowned gap—responsibility stays with Nora Ruiz, RN.

Alex Kim, RNEvening on-call nurse
20:27 PDT

Opens the handoff card on mobile to read Elena’s summary. Viewing never transfers ownership.

20:28 PDT

Presses Accept: status updates to “Alex Kim, RN accepted evening nursing follow-up”.

Dr. Mira LeeREI physician
20:22 → 20:28+ PDT

Retains “Clinical review pending” for the 20-minute trigger interval difference (35h 40m vs. 36h 00m). Nursing handoff never closes the physician’s decision.

Figure 1 · Swimlane trace showing how an unaccepted or declined offer keeps Nora Ruiz, RN responsible, how reading at 20:27 PDT transfers nothing, and how Alex Kim’s 20:28 PDT acceptance moves only nursing follow-up while Dr. Mira Lee keeps clinical review.

Worked example from the cast

Passing Elena Rivera’s evening callback from day nursing to on-call

How OvaFlow prevents an orphaned evening callback across a busy afternoon decline, a 20:27 PDT read, and a 20:28 PDT scoped accept.

See the Daily Care handoff →
Step-by-step walkthrough

Passing Elena Rivera’s evening callback from day nursing to on-call

  1. Step 0116:45 PDT

    Nora Ruiz, RN → Lee Park, RN

    Desktop + Mobile Triage
    Coverage offered · Nora Ruiz, RN ownsLee Park declines while in a room

    Nora Ruiz, RN offers late-afternoon nursing coverage to Lee Park, RN. Lee is in an ultrasound room and declines the offer. Responsibility never drops into limbo—Nora remains the visible owner.

  2. Step 0220:26 PDT

    Nora Ruiz, RN → Alex Kim, RN

    On-Call Handoff Queue
    Coverage offered · Nora Ruiz, RN ownsScoped to evening nursing follow-up

    After Elena Rivera reports her 20:20 PDT trigger time (received at 20:22 PDT), Nora offers the “evening nursing follow-up” scope to on-call nurse Alex Kim, RN. On every screen, the status states that Nora Ruiz, RN remains responsible.

  3. Step 0320:27 PDT

    Alex Kim, RN

    Clinician Mobile
    Reading does not transfer ownershipOpens card to review context

    At 20:27 PDT, Alex Kim opens the handoff card on mobile to read Elena’s Cycle Day 11 summary and the 20:20 PDT report. Because reading is never acceptance, ownership does not move at 20:27 PDT.

  4. Step 0420:28 PDT

    Alex Kim, RN & Dr. Mira Lee

    Clinician Mobile + Clinic EMR
    Alex Kim, RN accepted follow-upDr. Mira Lee keeps clinical review

    At 20:28 PDT, Alex presses Accept. The status updates to “Alex Kim, RN accepted evening nursing follow-up”, transferring only the nursing callback while Dr. Mira Lee’s “Clinical review pending” task stays untouched.

Figure 2 · Four-step walkthrough showing who holds responsibility, which screen is active, and which status applies at each timestamp.

System boundaries

What OvaFlow handles and what stays with your EMR and clinical team

Clear operational boundaries keep clinical authority, prescribing, and laboratory witnessing inside your clinic’s own systems. See AI & clinical boundaries for full governance rules.

What OvaFlow does here

  • Keeps the outgoing owner visibly responsible while a handoff offer is pending, read, declined, or expired.
  • Transfers ownership only when the receiving team member explicitly presses Accept for a named scope.
  • Preserves separate ownership for clinical physician review when nursing follow-up changes hands.
  • Requires explicit successor acceptance when a departing staff member’s open queue is reassigned, and requires receiving-clinic acceptance on outbound referrals.

What OvaFlow never does

  • Never transfers responsibility on message send, push notification delivery, or screen read receipt.
  • Never leaves a task in an unowned state between a declined offer and the next assignment.
  • Never allows a nursing handoff acceptance to close or transfer a physician’s clinical decision.
  • Never treats sending a transfer-of-care packet as acceptance by the receiving clinic.

Questions & primary sources

Answers for clinicians, practice leaders, and patients

If I open a handoff request on my phone to check how complex the patient’s cycle is, am I suddenly on the hook for it?Clinicians & coordinators

No. Opening or reading a handoff offer never changes who owns the task. You can inspect the patient summary, signed source, and due window freely; ownership transfers only if you press Accept.

What happens when a coordinator or nurse leaves the practice or goes on extended leave with 30 future cycle tasks?Practice leaders & owners

Under the successor-acceptance safeguard, open tasks do not silently vanish or dump into an unmonitored pool. They stay visibly tied to the outgoing role until a named successor explicitly accepts the reassigned scope.

Why does the clinic separate the evening nurse callback from the doctor’s review when my injection time changes?Patients & families

Your on-call nurse needs to check in with you promptly in the evening, while your physician needs to confirm whether a 20-minute difference affects the procedure room schedule. Keeping those two responsibilities separate ensures neither one gets accidentally checked off.

Primary clinical & safety references (2 sources)View citations
  1. Starmer AJ, Spector ND, Srivastava R, et al. (2014). Changes in Medical Errors after Implementation of a Handoff Program (I-PASS). New England Journal of Medicine 371(19):1803-1812. — Prospective study of 10,740 admissions demonstrating a 23% reduction in medical errors and 30% reduction in preventable adverse events through structured closed-loop handoffs.
  2. Singh H, Thomas EJ, Mani S, et al. (2009). Timely follow-up of abnormal diagnostic imaging test results in an outpatient setting. Archives of Internal Medicine 169(17):1578-1586. — Shows that passive read receipts and shared alerts leave 7.7%–18.1% of critical outpatient findings without timely follow-up action.

See it

Walkthroughs that show it

Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional, and EMR screens are modeled reconstructions.

Prototype walkthrough · Fictional patient data

Next step

Follow one of your handoffs through it.

Bring a handoff that slips today. We'll trace it through My work, verification and the safeguards in the prototype. Fictional records only; please don't send patient data.