Skip to main content

Product preview · Fictional patient data

OvaFlow

Walkthrough 12 of 29 · iPhone

Elena's iPhone: the current instruction, an old link, an honest report

An old text link can't send Elena to a superseded injection time. Reporting a late dose is simple and honest, and urgent help is one tap away.

Length
0:13
Chapters
6
Shown on
iPhone, patient companion concept
  • Planned after the pilot
  • Prototype walkthrough · Fictional patient data

Elena's iPhone: the current instruction, an old link, an honest report, muted recording of the design prototype. Fictional patient data.

Chapter 1 of 6: The current instruction comes first

Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional, EMR screens are modeled reconstructions, and nothing shown is a live connection to any clinic or vendor system.

Clinical & operational context

The situation on screen, why it matters, and where OvaFlow stops.

The patient side of the daily-care story. Elena sees her current signed trigger instruction first, and an older text link opens the current version instead of the old time. She can ask for a call without marking the dose taken, report what actually happened, and see who has her evening callback.

What clinical situation this depicts

From the patient's perspective, trigger night is often overwhelming: she is managing refrigerated syringes, reading portal notifications on her iPhone, and worrying about making a mistake that could cancel her retrieval. If she taps an email or SMS link from two hours earlier before her physician adjusted her trigger time, or if she is afraid to admit she injected 20 minutes late, the care team loses visibility at the exact moment it matters most.

This iPhone walkthrough shows the same evening from Elena Rivera's hand: her current signed instruction (8:00 PM PDT, version 3) sits prominently at the top in 12-hour patient time with a clear strike-through of the older 8:30 PM PDT version. When she taps an older notification link from earlier in the afternoon, OvaFlow intercepts the stale link and redirects her to version 3. She can request a nursing call without marking the dose taken, honestly report that she took the injection at 8:20 PM PDT on Oct 30, see that Nora Ruiz, RN and then Alex Kim, RN own her callback, and later complete her post-retrieval symptom check-in with direct urgent clinic numbers `(202) 555-0141` and `(202) 555-0140` always in reach.

Step-by-step workflow

Elena's iPhone companion: stale-link interception and honest 8:20 PM report

Step 1iPhone notification

Elena Rivera

Taps an older v2 link from earlier in the afternoon

Stale link intercepted
Step 2Tonight's card

Patient companion

Shows 8:00 PM PDT (v3) and retires 8:30 PM PDT (v2)

Current v3 shown
Step 3Dose log

Elena Rivera

Logs actual injection at 8:20 PM PDT, Oct 30

Reported 8:20 PM PDT
Step 4iPhone status card

Care team banner

Shows Alex Kim, RN accepted her evening callback

Alex Kim, RN owns call

What Elena Rivera sees on her iPhone when her trigger time moves from 8:30 PM PDT (v2) to 8:00 PM PDT (v3).

Guardrail: Tapping an old notification link never opens a superseded medication instruction.

What OvaFlow coordinates in this recording

  • Intercepts clicks on older email/SMS links so Elena only ever acts on the current signed v3 instruction.
  • Lets Elena log her real 8:20 PM PDT injection time without fear and shows which nurse owns her callback.
  • Displays post-retrieval check-in prompts with the clinic's urgent phone lines always visible.

What stays with clinicians & the clinic's own systems

  • Never tells Elena whether her 8:20 PM PDT injection changes her retrieval time — that stays with her clinician.
  • Never triages post-retrieval pain, bloating, or fever algorithmically.
  • Never hides the clinic's direct phone number behind a chatbot or automated tree.

What to watch for

What could go wrong, and what you'll see instead.

The patient side of the daily-care story. Elena sees her current signed trigger instruction first, and an older text link opens the current version instead of the old time. She can ask for a call without marking the dose taken, report what actually happened, and see who has her evening callback.

The problems it is designed around

  1. Tapping an older 8:30 PM text link and injecting at a superseded time.
  2. Being afraid to report a late injection, or unsure who owns the evening callback.
  3. Being left to judge symptoms alone after retrieval.

What you'll see in the recording

  1. Version 3: Ovidrel 250 micrograms, subcutaneous, 8:00 PM PDT Oct 30
  2. An old link opening the current instruction
  3. A call request that doesn't mark the dose taken
  4. An honest 8:20 PM report
  5. A recovery check-in with the 24/7 line and 911
Chapter-by-chapter guide

Every chapter in this 0:13 walkthrough (6 chapters)

Follow the exact timestamps, UI status changes, and coordination safeguards as the recording plays.

  1. Chapter 10:00 – 0:02

    The current instruction comes first

    What to watch for: Elena's home card displays tonight's 8:00 PM PDT (Oct 30) trigger instruction in 12-hour time with version 2 (8:30 PM PDT) clearly marked replaced.

    Boundary rule: Patient surfaces always use 12-hour AM/PM time with the calendar date.

    On-screen narration: Elena's current signed trigger instruction, version 3, opens on her iPhone.

Show chapters 2–6 (5 more chapters with timestamps & boundary notes)
  1. Chapter 20:02 – 0:06

    An old link, stopped

    What to watch for: Opening a link from an earlier notification shows a clear notice that version 2 was replaced at 5:10 PM PDT and takes her straight to version 3.

    Boundary rule: Stale links can never display an outdated dose or time as active.

    On-screen narration: She taps an older text link for 8:30 PM. The superseded instruction doesn't open. She is taken back to the current signed version 3: 8:00 PM PDT Oct 30.

  2. Chapter 30:06 – 0:08

    Asking for a call

    What to watch for: Elena taps 'Ask for a call' to check syringe preparation; her dose button stays unconfirmed.

    Boundary rule: Asking a question never marks the medication taken.

    On-screen narration: She asks for a quick call from Nora Ruiz, RN to check her Ovidrel syringe.

  3. Chapter 40:08 – 0:09

    Reporting 8:20 PM, honestly

    What to watch for: After injecting slightly late, she logs 8:20 PM PDT on Oct 30 in plain, supportive language.

    Boundary rule: The UI encourages honest time reporting without alarming or blaming the patient.

    On-screen narration: She reports she injected at 8:20 PM. The 35h 40m interval is kept beside the plan.

  4. Chapter 50:09 – 0:11

    Who has her callback

    What to watch for: Her screen shows who has accepted her callback (Nora Ruiz, RN, then Alex Kim, RN on call).

    Boundary rule: Seeing a named nurse reduces repeated anxious portal messages.

    On-screen narration: She sees that Alex Kim, RN has accepted her evening callback, and that her doctor's review is still open.

  5. Chapter 60:11 – 0:13

    Recovery check-in, with urgent help

    What to watch for: After retrieval, her recovery check-in keeps urgent clinic numbers (202) 555-0141 / (202) 555-0140 and emergency guidance pinned at the top.

    Boundary rule: OvaFlow does not triage symptoms; severe symptom choices direct the patient immediately to live clinical contact.

    On-screen narration: After retrieval, her recovery check-in shows the clinic's 24/7 line and emergency contacts.

OvaFlow never makes the clinical call in these recordings. Physicians sign, the person taking a handoff accepts it, and the lab keeps its own holds. The companion tracks, checks and stops; staff decide.

In this walkthrough

The people on screen

Every patient, family member, clinician and clinic in these stories is fictional. Names, times and screens come from prototype walkthroughs, not from real care.

  • Elena RiveraPatient
  • Nora Ruiz, RNIVF nurse coordinator
  • Alex Kim, RNEvening on-call nurse
Fictional patient data

Systems in this recording

Named or shown on screen. An EMR here is a modeled workflow example built for the prototype, not the vendor's own software. OvaFlow is designed to work beside these systems.

  • Patient and clinician companion concepts (design prototype)

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.

Where this appears

Read the page around it.

This recording is part of these pages. Each one explains the step in more depth.

Show all pages where this walkthrough appears

Questions & answers

Common questions about this walkthrough

What clinicians, coordinators, practice leaders, and patients ask when reviewing Walkthrough 12.

What happens if a patient screenshots or clicks an older SMS link after her trigger time was changed?

Any tap on an older link is intercepted by a full-width notice explaining that her care team signed a newer instruction (version 3, 8:00 PM PDT on Oct 30) and showing the old time crossed out.

Why does the patient app show 8:00 PM PDT while the nurse's screen shows 20:00 PDT?

Clinician and lab screens use 24-hour time (20:00 PDT) to match medical and operating-room schedules, while patient screens use 12-hour time with AM/PM and the date (8:00 PM PDT, Oct 30) to prevent 24-hour conversion mistakes at home.

Show 1 more walkthrough questions
Does the recovery check-in decide whether a patient has OHSS?

No. OvaFlow never triages or diagnoses. It routes check-in answers to the nursing team and keeps direct urgent phone numbers `(202) 555-0141` and `(202) 555-0140` at the top of the screen.

Next step

Walk through it with your own team.

We'll replay this flow against your roles and handoffs, using fictional records. Please don't send patient data.