Product preview · Fictional patient data
Patient channels
Clinics already talk to patients through texts, apps and calls. In the walkthroughs, every send is checked against who is on the thread, the approved template and the patient's opt-in, and a person confirms what actually went out.
Send rules
From the care conversations walkthroughs. The channel still does the sending; these are the checks in front of it.
A change in who is on a group thread holds the outgoing draft until the audience is checked.
A reminder that may already have gone out is traced to the original before anyone resends it.
A question about a dose is routed to Nora Ruiz, RN, never answered automatically.
Staging a message is not sending it. The real outcome is confirmed by the clinician who sent it.
Where each channel sits
Messaging, calls and the clinic workstation each keep doing their own job. One companion layer, designed to work beside them, carries the send checks.
Microsoft Teams
Microsoft Edge
Google Chrome
Each layer stays in its own system. OvaFlow is designed to work beside them as a modeled companion layer.
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
Modeled in the care conversations walkthroughs. OvaFlow stages and checks; the channel sends.
WhatsApp Business PlatformPatient messaging channelA reminder held when the approved template or the patient's opt-in is missing.Calls
Modeled on the Windows companion. Capture starts only after the encounter and consent are confirmed.
Prototype walkthroughs
Microsoft TeamsMicrosoft TeamsClinician calls & collaborationA quiet prompt to take notes. Nothing is captured until the clinician confirms the patient and consent.ZoomTelehealth & consult callsThe same consent step before capture, and the draft compared with the transcript before it is placed.Workstations
Clinic workstations fail in ordinary ways. Pick a failure from the workstation recovery walkthrough and see what the companion does with the draft.
The USB microphone drops. Capture stops instead of guessing, and everything recorded so far stays with the visit.
Prototype walkthroughs
Microsoft WindowsClinic workstation OSA floating companion that docks away from Save buttons and keeps the draft if the workstation fails.Microsoft EdgeMicrosoft EdgeManaged browserA browser rail beside the open chart.Google ChromeGoogle ChromeManaged browserThe same browser rail beside the open chart.CitrixVirtual desktop & remote app hostWhen the session blocks the clipboard, the reviewed draft is held, not lost or forced into the wrong place.Messaging rules, call consent & safeguard traces
Patient messaging and telehealth tools carry strict platform and telecommunications rules. OvaFlow is designed so the clinic's existing channel keeps ownership of delivery while the companion enforces three pre-send checks and explicit human confirmation.
Fictional patients Maya Chen and Elena Rivera · The clinic's messaging channel and call tool keep delivery authority while OvaFlow enforces recipient, template, consent and human-review boundaries.
Channel: Group messaging thread
Nora Ruiz, RN prepares an appointment update for Maya Chen, but an unverified family phone number was added to the group thread.
Gate 01 (Recipients checked) turns amber and blocks staging before any message leaves the desk.
Draft is held until Nora verifies Maya Chen's sharing preferences and participant list.
Channel: Shift handoff message queue
Nora opens a queued reminder from an earlier shift whose gateway delivery status was never confirmed.
Duplicate-send guard blocks a blind resend and links straight to the original channel delivery log.
Nora checks the channel log first so the patient never receives conflicting duplicate instructions.
Channel: Inbound patient reply
Elena replies on the clinic's messaging channel asking whether she should adjust her evening menotropin dose.
No automated medical replies: OvaFlow never generates clinical or dosing advice to patients.
Flagged immediately as a medication dose question and routed to named owner Nora Ruiz, RN.
Channel: Microsoft Teams & Zoom on Windows
Dr. Mira Lee joins a scheduled video consultation while the Windows floating companion sits clear of call controls.
Quiet readiness prompt only: zero audio is captured until the clinician confirms the patient match and verbal consent.
Reviewed draft is checked line by line against the transcript before placement in the EMR.
Under federal Telephone Consumer Protection Act (TCPA) rules (47 CFR § 64.1200), healthcare text messaging relies on documented patient opt-in, clear sender identification and immediate honoring of opt-out requests. OvaFlow checks that the patient's channel opt-in is active before staging any reminder.
Apple Messages for Business routes conversations through an approved Messaging Service Provider (MSP) into the iPhone Messages app. In our modeled care-conversations walkthrough, OvaFlow verifies the recipient list, approved template and opt-in, then waits for the gateway's delivery acknowledgment before counting the update as sent.
Meta's WhatsApp Business Platform requires explicit user opt-in and pre-approved utility templates for business-initiated appointment or medication reminders outside a customer-service window. If an approved template or opt-in is missing, OvaFlow holds the message rather than sending free-form text.
When a clinician joins a Teams or Zoom consult on Windows, OvaFlow shows a quiet readiness prompt clear of meeting controls. No audio is recorded until the clinician confirms the patient identity and records verbal consent—and the resulting draft is checked line by line against the transcript.
Questions
No. In every walkthrough, OvaFlow checks the recipient list, the clinic-approved template and the patient's channel opt-in, then stages the draft for the clinic's existing channel or clinician device. A person confirms what actually went out.
If the participant list on a thread changes from the verified recipient scope, the Recipients gate blocks staging and holds the outgoing draft until staff review the patient's sharing preferences.
OvaFlow never generates automated clinical or dosing advice to patients. Any message mentioning doses, injection timing or symptoms is routed immediately to a named nurse coordinator or on-call clinician.
Never. When a call starts, the Windows floating companion offers a quiet prompt. Recording cannot begin until the clinician confirms which patient encounter is on the line and documents that the patient gave consent.
Because in a real clinic, messaging portals, telehealth calls and the EMR all run side by side on the same workstation. When a headset unplugs, a browser session times out or Citrix blocks the clipboard, the companion must preserve the draft and patient context across all of them.
Electronic Code of Federal Regulations (eCFR) · 47 CFR § 64.1200 — Telephone Consumer Protection Act (TCPA) Delivery Restrictions (verified 2026-11-03)
Federal telecommunications rules governing prior express consent and opt-out handling for telephone and text communications.
Apple Inc. · Apple Messages for Business — Message with Customers Documentation (verified 2026-11-03)
Official Apple specification for business messaging conversations, MSP routing and rich appointment updates.
Meta Platforms, Inc. · WhatsApp Business Platform Overview (verified 2026-11-03)
Official platform documentation for customer opt-in and approved utility message templates.
Citrix Documentation · ICA Policy Settings — Client Clipboard Redirection (verified 2026-11-03)
Virtual desktop policy controls governing clipboard transfer between local endpoints and hosted clinical desktops.
Walkthroughs
Recorded from an interactive design prototype. Every patient, clinician and clinic is fictional, and no channel is connected.
A desktop draft goes to the clinic iPhone with recipients checked, and templates and opt-ins are enforced before anything is sent.
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.
A floating companion designed to dock away from Save buttons, stay out of keyboard focus, ask before listening, and let staff practice outside any chart.
Fourteen designed recovery states, from an unplugged headset to a blocked remote-desktop clipboard, each keeping the draft and the right patient.
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.
Your channels
We'll walk through how the send checks would apply to the messaging and call tools your clinic runs today.