Signed instruction · Elena Riverav
Trigger · Ovidrel 250 micrograms subcutaneous, once
PDT · Oct 30
Signed by Dr. Mira Lee · 17:10 PDT
v2 · 20:30 PDT · retrieval 07:30 PSTSuperseded · kept for history
Sources & signed changes
Every instruction, traced to what was signed.
When a signed plan changes late in the afternoon, the patient instruction, the procedure room slot, anesthesia and the embryology lab all need to know, and older drafts or links must stop being used.
[ Signed change ]
One amendment, four commitments.
When the trigger time changes, everyone who depends on it needs to know. One signed amendment flags each linked commitment for the person who owns it.
Trigger to retrieval36h 00m
From 20:00 PDT October 30 to 07:00 PST November 1. Counted across the clock change at 02:00 on Nov 1. Every clinical decision stays with the care team.
- Patient instructionRe-prepared from version 3 for ElenaFlagged for Nora Ruiz, RN
- Procedure slotRetrieval Nov 1 · 07:30 → 07:00 PSTFlagged for Procedure desk
- AnesthesiaPre-op instructions follow the 07:00 PST retrievalFlagged for Anesthesia team
- Embryology labChange order acknowledgment pending for 07:00 PSTFlagged for Embryology
From the daily-care walkthrough.Fictional patient data
For your team
What changes for your team
The same work, with the source, the owner and the next step in view.
- The new time
TodayA revised trigger time arrives as a message, and someone retypes it.
With OvaFlowThe signed version 3 shows exactly which field changed, who signed it and when.
- Everyone affected
TodayThe OR, anesthesia and the lab hear about the change one by one, or not at all.
With OvaFlowOne signed amendment flags every linked commitment for the person who owns it.
- Old instructions
TodayVersion 2 keeps circulating in texts and printouts.
With OvaFlowThe superseded version stays visible for history, marked as superseded, and can't be sent again.
- What the patient reports
TodayA reported injection time quietly overwrites what was signed.
With OvaFlowThe report is kept as said, next to the signed instruction, for the care team to review.
When a signed plan changes
Why late-day protocol amendments and stale patient links jeopardize retrieval timing
Oocyte maturation trigger timing is tightly coupled to follicular retrieval—typically scheduled 36 hours after trigger administration under ESHRE ovarian stimulation guidelines [1]. When late afternoon estradiol or progesterone results prompt a clinician to move a trigger time by 30 minutes (or convert a fresh transfer to a freeze-all cycle for OHSS prevention), every downstream surface must reflect the newly signed revision immediately.
Two failure modes are especially common in ambulatory fertility care: first, a patient taps an earlier text notification link that still opens the superseded v2 time; second, when a patient reports taking their injection 20 minutes late, a staff member overwrites the signed order field to match what happened, erasing the distinction between what the clinician ordered and what the patient reported [2]. OvaFlow keeps every field tethered to its signed EMR revision, redirects stale links to the current signed version, and records patient-reported timing in its own dedicated lane.
Elena Rivera · Oct 30 PDT to Nov 1 PST
36-hour interval across the clock changeHow the retired 8:30 PM plan, the signed 8:00 PM order, and Elena’s 8:20 PM report stay separate
1 · Retired version 2Superseded at 17:10 PDT
Earlier plan: 20:30 PDT (8:30 PM, Oct 30)
Signed at 14:20 PDT before Elena’s late afternoon estradiol result arrived. Kept visible in a secondary history band for audit context.
Old text links redirect to version 32 · Current signed version 3Signed 17:10 PDT · Dr. Mira Lee
Signed order: 20:00 PDT (8:00 PM, Oct 30)
Ovidrel 250 mcg SC once at 20:00 PDT on Oct 30 for a Nov 1, 2026 retrieval at 07:00 PST (36h 00m across the PDT-to-PST clock fallback).
Prescribed order stays as signed3 · Separate patient reportReported 20:20 · Received 20:22 PDT
Patient-reported use: “8:20 tonight”
Elena reports injecting at 8:20 PM, Oct 30 (20:20 PDT)—35h 40m before the 07:00 PST retrieval, 20 minutes after the signed 20:00 PDT time.
Opens Clinical review pending for Dr. LeeStep-by-step walkthrough
Keeping the old 8:30 PM plan, the signed 8:00 PM order, and Elena’s 8:20 PM report separate
- Signed version 2 (20:30 PDT)Initial plan before afternoon E2
Earlier in the afternoon, version 2 scheduled Elena Rivera’s trigger for 20:30 PDT (8:30 PM, Oct 30). When late monitoring data arrives, version 2 is no longer the intended plan.
- Ready for review in the EMRSigns version 3 (20:00 PDT → 07:00 PST)
Dr. Mira Lee signs version 3 moving the trigger from 20:30 PDT to 20:00 PDT on Oct 30 so retrieval on Nov 1 at 07:00 PST sits at 36 hours across the PDT-to-PST clock change. OvaFlow marks version 2 superseded and highlights the 20:30 → 20:00 difference.
- Old link opens current instructionSuperseded version 2 link blocked
At 8:05 PM on Oct 30, 2026, Elena taps the older text notification link on her phone. OvaFlow blocks the outdated 8:30 PM view from acting as current and opens the signed version 3 instruction (8:00 PM, Oct 30).
- Patient-reported use · 20:20 PDTKept separate from version 3 order
Elena reports she injected at 8:20 PM, Oct 30 (20:20 PDT), and the clinic receives the report at 20:22 PDT. OvaFlow logs “Patient-reported use · 20:20 PDT” (35h 40m before the Nov 1, 07:00 PST retrieval) and opens “Clinical review pending” for Dr. Mira Lee without rewriting the 20:00 PDT signed order.
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
- Displays a field-level comparison between superseded and newly signed EMR revisions (such as 20:30 PDT → 20:00 PDT).
- Fans out a signed revision to every dependent commitment across patient portal, procedure room, anesthesia, and embryology.
- Redirects older patient links to the current signed instruction while keeping superseded versions in a secondary history band.
- Stores patient-reported medication timing with both reported and received timestamps, completely separate from the signed order.
What OvaFlow never does
- Never treats an unsigned clinician proposal as the active instruction.
- Never allows a patient’s self-reported dose time to overwrite or alter the clinician’s signed order in the chart.
- Never silently deletes a superseded version from the clinical timeline.
- Never changes procedure or anesthesia times without explicit human review of the downstream tasks.
Questions & primary sources
Answers for clinicians, practice leaders, and patients
What happens if a nurse stages a proposed trigger time change while waiting for the physician to sign?Clinicians & coordinators
It is labeled “Awaiting clinician approval” and kept visually separate from the active v2 instruction. Neither the patient nor downstream teams receive it as an instruction until the physician signs revision v3 in the EMR.
How does OvaFlow handle Daylight Saving Time transitions during the 36-hour trigger-to-retrieval window?Practice leaders & owners
Every timestamp carries its explicit timezone offset (such as PDT vs PST) and computes elapsed clinical hours across the clock change—so a 20:00 PDT trigger before fallback to a 07:00 PST retrieval is shown accurately as 36 hours 00 minutes.
If I take my injection 20 minutes later than planned and report it in the app, does the clinic see my exact words?Patients & families
Yes. Your exact words and the time you report taking the medication are kept as you said them and routed to your nurse and physician, without erasing the original instruction.
Primary clinical & safety references (2 sources)View citations
- European Society of Human Reproduction and Embryology (ESHRE) (2020). ESHRE Guideline: Ovarian Stimulation for IVF/ICSI. Human Reproduction Open / ESHRE Guidelines. — Establishes clinical coordination requirements around ovarian stimulation monitoring, OHSS prevention, and timed oocyte maturation trigger intervals.
- Office of the National Coordinator for Health IT (ONC) (2025). SAFER Guide: Test Results Reporting and Follow-Up. HealthIT.gov Safety Assurance Factors for EHR Resilience. — Specifies version traceability, clear identification of amended orders/results, and separation of patient-originated communications from signed clinical orders.
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
Elena's episode: one change, four commitments, recovery and freeze-all
One signed change reaches instructions, the OR, anesthesia and the lab. Later an outside emergency visit for OHSS turns a planned fresh transfer into freeze-all.
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.
Daily care: a changed trigger, the wrong chart and an unknown outcome
A late estradiol result, a newly signed trigger time, the wrong chart caught before publishing, and a lost confirmation checked rather than blindly resent.
Next step
Show us a change that got missed.
Bring a signed change that didn't reach everyone it affected. We'll show how the prototype marks what changed and what it touches. Fictional records only; please don't send patient data.