Care conversations: audience change, duplicate send, clinical routing
When someone new joins the thread just before a clinical update, the send pauses. Duplicate reminders are caught, and dose questions go to a nurse instead of an automated reply.
Care conversations
Someone new joins. The send waits.
When someone new joins a thread, a pending clinical message waits until the recipients are confirmed.
Maya Chen · care-team group
In this threadMaya ChenCare coordinatorScheduling group member · just joined
Can the group get the schedule for next week here too?
A new participant joined the thread
Here is your plan for next week, including the visit times we discussed.
Held: the audience changed. Confirm who should see this.
How it works
Inside the inbox, three more moments
One list for every modeled channel, then two moments where a message should wait. Each screen is an illustration of designed behavior with fictional patients.
One inbox
Every channel, one list
Messages from the patient portal and the clinic's modeled messaging channels appear in a single episode-linked thread with channel permission tags.
Care conversations- Maya ChenCare-team group · schedulingPatient portal
- Elena RiveraAppointment reminderWhatsApp Business
- Elena RiveraQuestion about tonightText message
- Maya ChenReply staged for the clinic iPhoneiPhone Messages
- Maya ChenAppointment updateApple Messages for Business
Check before sending again
A reminder isn't sent twice
If a reminder may already have gone out, the original is found before anything is resent.
Elena Rivera · appointment reminderReminder: your visit is tomorrow morning. Reply here if you need to change it.Delivery not confirmed yetDelivered · found in the delivery log
Check before sending again
- Looking for the original reminder
- Original found in the delivery log
- Not resent · one verified delivery
Not needed: the original reminder was deliveredClinical questions go to a person
Dose questions reach a nurse
Dose and symptom questions are routed to a nurse, never answered by an automated reply.
Elena Rivera · questionCan I take tonight’s injection later? I’m leaving work late.
Medication timing questionRouted to Nora Ruiz, RNA nurse answers. No automated reply is sent.Automated replies: off for dose and symptom questions
For your team
What changes for your team
Patients reach out across portal threads, text messages and voicemail while household members or billing contacts join shared threads. Slow delivery receipts invite duplicate reminders, and medication or symptom messages need clinical eyes rather than automated replies.
- Who is in the thread
TodayA clinical update goes to a group that changed a minute ago.
With OvaFlowThe send waits until the recipients are confirmed.
- Slow delivery
TodayA reminder looks lost, so it goes out again.
With OvaFlowThe original is traced first, and one verified delivery is shown.
- Channel rules
TodayReminders go out without the patient's opt-in or an approved template.
With OvaFlowReminders wait until the opt-in and an approved template are in place.
- Clinical questions
TodayDose or symptom messages sit in an unmonitored bot or general inbox.
With OvaFlowMedication and symptom questions route to a named nurse and show the 24/7 line and 911.
Modeled clinic channels
Where the conversations happen
- Patient portal
- Text message
- Apple Messages for Business
- iPhone Messages
One inboxEvery channel arrives in the same list, with the same checks before anything clinical goes out.
Messages stay inside each channel’s own rules: opt-ins and approved templates are checked before a reminder goes out, and a group update stays within what the group agreed to receive. These are modeled workflow examples, not live connections.
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.
Messaging across the care team
Why fertility messaging requires recipient checks, duplicate-send guards, and human nurse triage
Fertility care frequently involves multi-party threads: a patient, a spouse or support person, an egg or gestational carrier coordinator, and financial or scheduling staff. When someone new is added to a thread for scheduling or billing, sending a prepared clinical lab result into that same thread without re-confirming the audience can disclose sensitive medical details to the wrong recipient.
At the same time, outpatient communication studies show that delayed delivery receipts cause staff to resend reminders (confusing patients with duplicate instructions) [1], while patient questions about injection timing or post-retrieval abdominal pain require clinical triage by a nurse rather than an automated chatbot [2]. OvaFlow brings portal and modeled clinic messaging channels into one episode-linked inbox that pauses on audience changes, traces original sends before repeating, checks channel opt-in and approved templates, and routes every dose or symptom message to a named nurse alongside the clinic’s 24/7 line and 911.
Three conversation boundaries in one inbox
Human nurse routing · 24/7 line & 911 visibleHow group scheduling threads, private callbacks, and clinical questions stay separated
1 · Shared group threadAudience check
When someone new joins a thread, sending waits
If a billing or scheduling contact joins Maya Chen’s shared thread while a clinical update is staged, the Send button freezes until staff confirm who is authorized to see medical details.
Audience change pause2 · Confidential support requestPrivate channel
Kept separate from household threads
When Maya Chen requests a confidential callback or chooses a pause in treatment, her private thread stays separate from shared household messages and routine cycle reminders stop.
Explicit clinician or nurse ownership3 · Dose & symptom messages17:24 & 20:22 PDT
A question is not a dose—and goes to a nurse
Elena’s 17:24 syringe question and 20:20 PDT dose report (received 20:22 PDT) route directly to Nora Ruiz, RN or Alex Kim, RN with the clinic’s 24/7 line (202) 555-0141 and 911 shown.
Zero automated clinical adviceStep-by-step walkthrough
Pausing when a thread’s recipients change and routing Elena’s 8:20 PM report to a nurse
- Audience change pauseNew thread participant detected
While Nora Ruiz, RN is preparing a clinical lab update for Maya Chen, a household billing contact is added to the shared thread. OvaFlow immediately freezes the Send button until Nora confirms who should receive clinical details.
- Check before sending againOriginal 17:16 PDT send surfaced
At 18:40 PDT, a coordinator wonders if Elena Rivera received her version 3 trigger reminder and clicks to send another copy. OvaFlow surfaces the verified 17:16 PDT delivery first so a second conflicting text is not sent.
- Channel permission checkHolds when SMS opt-in is missing
For a patient who has consented to portal messages but has not opted in to text reminders, OvaFlow holds the outbound text message and routes the update through the approved portal channel instead.
- Routed to nurse + 24/7 lineNo automated clinical reply
When the clinic receives Elena’s message at 20:22 PDT on Oct 30 that she injected at 8:20 PM, Oct 30 (20:20 PDT), OvaFlow never sends an automated clinical reassurance. It routes the report directly to Nora Ruiz, RN and displays the clinic’s 24/7 on-call line and 911.
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
- Pauses any pending clinical message the instant a new participant joins or leaves the conversation thread.
- Searches the delivery log and displays the original message before allowing a reminder to be resent.
- Checks patient channel opt-in and approved clinic templates before releasing outbound messages.
- Routes every dose, medication, or symptom question to a named nurse while displaying the clinic’s 24/7 line and 911.
What OvaFlow never does
- Never uses an automated bot or language model to give patients dose adjustments or symptom advice.
- Never sends clinical details into a group thread after the recipient list changes without staff confirmation.
- Never sends SMS or external channel messages when patient opt-in or an approved template is missing.
- Never hides urgent escalation numbers (clinic 24/7 on-call line and 911) on recovery check-ins.
Questions & primary sources
Answers for clinicians, practice leaders, and patients
How does the inbox stop a coordinator from resending a trigger reminder that already went out 20 minutes ago?Clinicians & coordinators
When staff click to send a reminder for an instruction that already has a delivery record or an in-flight attempt, the duplicate-send check opens the original 17:16 PDT send record and its status before anything is repeated.
Can patients ever receive automated AI answers to clinical or medication questions in Care conversations?Practice leaders & owners
Never. OvaFlow’s AI boundary is strictly operational and non-clinical. Any message mentioning doses, injection timing, bleeding, pain, or symptoms routes to a named nurse and surfaces the clinic’s 24/7 phone line and 911.
What if I share a thread with a family member for scheduling, but want my test results kept private?Patients & families
Whenever the list of people in a conversation changes, the nurse’s screen pauses before sending any medical update so your care team can confirm exactly who is on the thread.
Primary clinical & safety references (2 sources)View citations
- Office of the National Coordinator for Health IT (ONC) (2025). SAFER Guide: Clinician Communication & Test Results Reporting. HealthIT.gov Safety Assurance Factors for EHR Resilience. — Establishes safety practices for verifying message recipients, tracking delivery states, and escalating urgent clinical communications.
- Practice Committee of the American Society for Reproductive Medicine (ASRM) (2026). Artificial intelligence in the in vitro fertilization laboratory and clinical practice. Fertility and Sterility / ASRM Committee Opinion. — Emphasizes clinician oversight, clear scope boundaries, and human responsibility for clinical communication and medical decisions.
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
Care channels: iPhone Messages handoff, templates and opt-ins
A desktop draft goes to the clinic iPhone with recipients checked, and templates and opt-ins are enforced before anything is sent.
Care coordination: procedure team, cost changes, consent and access
Every member of the procedure team commits to the slot, a mid-cycle insurance change rebuilds the estimate, consent lands on the right person's chart, and the interpreter is booked for every visit.
Maya's iPhone: a chosen pause and a private support call
“Your pause, your pace”: routine reminders stop, and asking for a private call doesn't restart treatment.
Next step
Walk us through your messaging rules.
Groups, templates, opt-ins and who answers clinical questions. Fictional records only; please don't send patient data.