Always-on clinic workspace: routines people release
Routine follow-through runs under rules your team sets, pauses on request, and re-checks the open chart before it resumes.
My work
The queue that tells you why it moved.
A quiet inbox looks like nothing is wrong. Late morning labs, open evening callbacks and unverified portal sends hide in separate lists where arrival order buries overdue work.
Needs action
- Elena RiveraOutside monitoring resultCheck the late result and route it for clinical reviewNora Ruiz, RNReceived late
Waiting
- Elena RiveraTreatment decisionClinical decision stays with the clinicianDr. Mira LeeWaiting for source review
- Elena RiveraProcedure commitmentsCurrent source plan governs the commitmentProcedure deskv2 · Nov 1 at 07:30 PST
- Maya ChenPartner consent follow-upOpen work from the existing care-team taskNora Ruiz, RNAwaiting signer
Completed
- Elena RiveraEarlier portal-update reminderSaved coordination note; no further administrative actionApproved clinic routineRecorded quietly
What moved: Elena’s outside monitoring result arrived late, so it moved from Waiting to Needs action. Its tracker now reads received. Checking it, and Dr. Mira Lee’s clinical review, are still open.
For your team
What changes for your team
The same work, with the source, the owner and the next step in view.
- Missing results
TodayA quiet inbox looks like nothing is due.
With OvaFlowExpected results are tracked, so one that hasn't arrived shows up as work.
- Order
TodayTasks sit in the order they arrived.
With OvaFlowNeeds action, Waiting and Completed, sorted by when each item is due.
- Duplicates
TodayThe same request lands in two lists and gets done twice, or not at all.
With OvaFlowOne task, with both sources attached.
- Linked work
TodayClosing one task quietly closes the ones that depend on it.
With OvaFlowEach linked commitment stays open until its own evidence arrives.
How it works
A missing result is work, not silence.
Every expected result passes five checkpoints. The row stays in My work until the last one, and each checkpoint names who closes it.
- 01
Expected
The plan says a result is coming. Its absence is visible, so a quiet inbox cannot hide it.
Coordinating nurse follows up
- 02
Collected
The sample has been taken. There is still nothing to read, and the row keeps waiting.
Outside lab or clinic
- 03
Received
The result reached the clinic. The row moves to Needs action and says why it moved.
Coordinating nurse
- 04
Checked
Staff confirm it belongs to the right patient and cycle, then route it for review.
Coordinating nurse
- 05
Clinically reviewed
The clinician reviews the result and decides. OvaFlow shows it; it never interprets it.
The clinician
Rules the queue keeps
- Needs action, Waiting, CompletedEvery task sits in exactly one bucket for its current owner, sorted by clinical urgency and due window rather than arrival timestamp.
- Expected results are trackedEach ordered lab or ultrasound moves from expected to collected, received, checked and clinically reviewed, so an unreturned result surfaces before afternoon sign-off.
- Duplicates are mergedWhen a portal message and a voicemail carry the same patient question, they collapse into one task with both source timestamps attached.
- Linked work survivesVerifying a portal publication closes only the send task; linked procedure, anesthesia, lab and callback tasks stay open until their own evidence arrives.
Keeping late results in view
Why arrival-ordered inboxes bury overdue estradiol results and unverified sends
In a standard clinic inbox or task list, new routine messages push older items down the screen, and an expected morning lab that never arrived from the reference analyzer generates no row at all. Systematic reviews of outpatient diagnostic tracking show that 6.8% to 62% of abnormal lab tests lack documented timely follow-up when clinics rely on passive arrival queues [1].
Furthermore, when a single clinical change—like moving a trigger shot by 30 minutes—requires actions from nursing, procedure scheduling, anesthesia, and embryology, checking off a single shared task hides the remaining uncompleted steps [2]. My work gives each role three clear buckets (Needs action, Waiting, Completed), tracks every ordered result through five explicit stages (Expected → Collected → Received → Checked → Clinically reviewed), and keeps linked cross-team obligations independent.
Queue comparison · Afternoon monitoring sign-off
Due-window buckets vs. arrival orderWhy an arrival-ordered inbox buries a missing estradiol result—and how My work surfaces it
Ordinary arrival-ordered inboxWhat gets buried
Sorted by newest message received
- 16:48 PDT · Routine refill question: Sits at the very top of the list only because it arrived last.
- 16:42 PDT · Duplicate patient outreach: A portal message and a voicemail about the same question appear as two separate rows for two nurses to pick up.
- 15:55 PDT · Shared checkmark: Marking a portal message “Sent” hides the remaining operating room and embryology tasks.
- 07:30 PDT · Elena Rivera’s outside estradiol draw: Because the result has not arrived by 16:45 PDT, no new message exists in the inbox.
My work role-scoped queueSorted by due window
Needs action · Waiting · Completed
- Needs action (16:45 PDT · Top of queue): Elena Rivera’s expected morning estradiol lab has not reached Received by cutoff and rises to the top for Nora Ruiz, RN.
- Needs action (16:50 PDT · Merged row): Portal message and voicemail collapse into one task with both sources attached.
- Completed (17:16 PDT · Scoped closure): Nora’s verified portal post closes only her publication row.
- Waiting (17:16 PDT+ · Independent rows): Procedure room, anesthesia, lab prep, and evening callback stay open until each has its own evidence.
Step-by-step walkthrough
How a late afternoon estradiol result and a revised trigger move through My work
- Expected result overdueSurfaces before afternoon sign-off
Morning monitoring labs due by 14:30 PDT that are still at Stage 2 (Collected) automatically move to the top of Nora Ruiz’s Needs action queue, even though no new message arrived.
- One task · Two sources attachedPortal message and voicemail combined
When a patient sends both a portal message and a voicemail asking about evening injection supplies, My work merges them into one obligation with both timestamps attached so two nurses do not call back separately.
- Four linked tasks openedPortal, OR, Anesthesia, and Lab
Dr. Mira Lee’s signed version 3 trigger amendment creates four linked obligations across the respective role queues, sorted by their due windows rather than arrival order.
- One matching publication verifiedOnly the portal send task closes
When Nora’s portal publication is verified in the EMR at 17:16 PDT, only her publication row moves to Completed. The procedure room, anesthesia, lab prep, and evening callback rows remain active until each has its own evidence.
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
- Separates every role’s queue into Needs action, Waiting, and Completed, ordered by clinical due window.
- Tracks expected labs and ultrasounds across Expected, Collected, Received, Checked, and Clinically reviewed.
- Collapses duplicate notifications for the same obligation into one row while preserving every source record.
- Keeps linked obligations across nursing, procedure room, anesthesia, and embryology independent when one task finishes.
What OvaFlow never does
- Never auto-closes a clinical review or lab notification because a patient message was sent.
- Never hides an unaccepted handoff inside the Waiting bucket without showing who still owns it.
- Never merges financial prior-authorization clearance with clinical medical clearance.
- Never deletes completed or superseded tasks from the episode audit history.
Questions & primary sources
Answers for clinicians, practice leaders, and patients
How does My work prevent a missing morning estradiol lab from going unnoticed on a 40-patient monitoring day?Clinicians & coordinators
Because the lab is entered as Expected when ordered, it does not wait for an inbound HL7 or portal message to appear. If it has not advanced from Collected to Received by the clinic’s cutoff window, it rises to the top of Needs action.
Can nursing leads see whether afternoon callbacks are backed up before the day shift clocks out?Practice leaders & owners
Yes. Every row in My work shows its current named owner, the due window, the specific blocker (for example, awaiting clinician approval vs awaiting EMR readback), and whether coverage has been offered or accepted.
Why does it matter if I leave both a voicemail and a portal message?Patients & families
In many clinics those land in two different staff lists, leading to confusion or conflicting callbacks. OvaFlow links both to the same care item so one nurse sees your full message history and responds clearly.
Primary clinical & safety references (2 sources)View citations
- Callen JL, Westbrook JI, Georgiou A, Li J (2012). Failure to follow-up test results for ambulatory patients: a systematic review. Journal of General Internal Medicine 27(10):1334-1348. — Documents the high rate of missed outpatient lab follow-up when tracking relies on passive inbox arrival rather than expected-to-reviewed state tracking.
- 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 shared or dual-routed notifications without a single explicit task owner increase unfollowed results.
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
Lab & specialty pharmacy: accession hold, amended PGT, cryo signal
Accession holds, amended PGT reports, cryo tank signals and pharmacy change requests land in one queue, each with a named owner.
Two-person intake, sperm source and urgent preservation
Two people's workups run in parallel, the sperm-source prerequisite is flagged early, and an oncology referral gets a retrieval window both teams accept.
Next step
Bring a queue that hides a late result.
We'll sort it the way My work does: one owner, the latest update, the blocker and the next step for each item. Fictional records only; please don't send patient data.