Every family practice has a preventive care backlog. Patients overdue for annual physicals. Patients who missed their flu shot last season. Patients who need a colonoscopy referral. Patients whose diabetes follow-up slipped. The clinical value of getting these patients back into the practice is enormous, both for patient health and for practice revenue. And yet most family practices leave the recall work half-done because it feels like it requires touching PHI, which triggers a compliance burden most practices are not equipped to handle.
Quick Answer: Preventive care recall automation does not require touching PHI. The clinical context (why a patient is due) stays in your EHR. The outreach layer (contacting the patient with a scheduling nudge) only needs non-PHI identity data: name, contact info, appointment scheduling status. MiOpsAI handles the outreach layer at $250 per chair per month, with a 60-day cancellation notice, and never touches ePHI.
This article walks through the architecture that makes non-PHI recall automation work, what data crosses the boundary, and how a family practice can run recall campaigns to hundreds of overdue patients without a BAA.
The PHI Boundary in Recall Campaigns
The word "recall" makes practice owners nervous because the clinical context of why a patient is due for a visit is obviously PHI. Diabetes follow-up, cancer screening, mental health check-in: these are protected health information under HIPAA. Sending an email that references any of that clinical context is a compliance issue.
But the outreach itself does not require the clinical context. A message that says "Hi Sarah, it has been a year since your last visit at Prairie Family Health. We would love to see you for your annual check-in. Book online here or call us." contains no PHI. It contains a name, a practice name, and a scheduling nudge. That is exactly the kind of non-PHI outreach MiOpsAI is built for.
The clinical decision about who is overdue and what they are overdue for happens inside your EHR. The list of "patients due for a visit" gets exported as a non-PHI identity list (name, email, phone, last visit date). MiOpsAI receives that list, sends the scheduling nudges, tracks responses, and hands booked appointments back to your front desk. At no point does MiOpsAI see the clinical context. See the HIPAA Journal for the specifics of what qualifies as PHI in patient outreach.
The Non-PHI Data Layer That Makes This Work
The architecture depends on a clean separation between the clinical system (EHR) and the marketing system (MiOpsAI). The EHR holds everything HIPAA-regulated. MiOpsAI holds the non-PHI identity layer: name, contact info, source of acquisition, marketing opt-in status, appointment scheduling status, campaign history, response history.
The sync between them is one-directional and filtered. The EHR pushes non-PHI patient identity into MiOpsAI's CRM when patients are created or updated. MiOpsAI never pushes anything back into the EHR that touches clinical data. Booked appointments come back into the EHR through your normal scheduling workflow, not through MiOpsAI.
What a Recall Campaign Actually Looks Like
Here is a typical annual physical recall campaign in a MiOpsAI-powered family practice:
Step 1: Your EHR generates a list of patients whose last annual physical was more than 12 months ago and who are still active in the practice. This is a clinical decision made inside the EHR by your practice manager or a delegated staff member.
Step 2: The list gets exported as non-PHI identity data (name, email, phone, last visit date) into MiOpsAI's CRM. No diagnoses, no clinical notes, no reason for the recall.
Step 3: Sally, MiOpsAI's marketing chair, runs the outreach campaign. Segment the list by preferred communication channel. Send email to patients who prefer email, SMS to patients who prefer text. Personalize with first name and last visit date. Include a scheduling link and a call-to-action to book.
Step 4: Patients respond. Some book directly through the online scheduling link. Some call the front desk. Some ignore the outreach. Some request more information.
Step 5: Lizzi, MiOpsAI's operations chair, tracks responses and coordinates follow-up. Patients who booked get a confirmation. Patients who did not respond get a second nudge in two weeks. Patients who requested more info get routed to your front desk with the context.
Step 6: Marcus, MiOpsAI's growth chair, reports on outcomes. How many patients contacted, how many booked, average booking cost per patient, how the recall campaign compared to prior campaigns.
The Results You Should Expect
A well-run preventive care recall campaign to 500 to 1,000 overdue patients typically produces 100 to 200 booked appointments in the first month. That is a 20 percent booking rate, which is high because these are already-existing patients who have a prior relationship with the practice. The clinical value is significant (catching preventive care gaps) and the revenue value is meaningful (each annual physical typically generates $150 to $400 in reimbursement plus the downstream visits that follow).
The American Academy of Family Physicians has published guidance on preventive care outreach that reinforces the value of proactive recall systems. Family practices that run recall campaigns consistently see measurably higher quality scores in CMS reporting programs. The CMS quality reporting resources cover the specific measures.
The Chair-Based Pricing
MiOpsAI is priced at $250 per chair per month. A three-chair family practice pays $750 per month for the full platform. Seven chairs runs $1,750 per month. That includes all four chairs (Sally, Lizzi, Marcus, Milo) and all four functional areas (marketing, operations, growth, projects). No per-campaign fees, no per-patient fees, no additional charge for volume.
Cancellation requires 60-day written notice. There is no free trial. Setup is done through a walkthrough with your team, and billing only begins after you sign off that the configuration is right.
Setting Up the First Campaign
The first recall campaign is usually the annual physical backlog because it is the largest and highest-value opportunity. Start there. Export the list from your EHR. Get it into MiOpsAI. Run the campaign. Measure the results. Then move to seasonal campaigns (flu shots in fall, wellness checks in January) and then to condition-specific campaigns as needed.
Milo, our projects chair, handles the initial setup and coordinates with your team on the export process. This is a two-to-four-week project depending on your EHR and staff availability. Once the first campaign runs, the ongoing cadence is largely automated.
Learn more about MiOpsAI for family healthcare practices or request access.
Frequently Asked Questions
Can MiOpsAI receive data from my EHR without a BAA?
Yes, as long as the data being transferred is non-PHI. Name, email, phone, last visit date, appointment scheduling status: these are not PHI in isolation. The clinical context (diagnoses, notes, lab results) never leaves your EHR. If your EHR export process would transfer PHI, that export needs to be filtered before it reaches MiOpsAI.
What if a patient replies to a recall message with clinical information?
MiOpsAI's inbound message handling routes any message that appears to contain clinical information (symptom descriptions, medication questions, etc.) to your front desk immediately and does not process it further in the marketing layer. Your front desk handles the clinical response through your EHR's messaging system.
How long does it take to see results from a recall campaign?
First response wave typically comes within 48 hours of send. Peak booking activity happens in the first week. Full campaign results are usually measurable within 30 days. Practices with large overdue lists (500+ patients) often see 100 to 200 additional preventive care visits in the first month.
What about patients who no longer want to hear from us?
All MiOpsAI campaigns include one-click unsubscribe for email and STOP handling for SMS, in compliance with CAN-SPAM and TCPA. Unsubscribes propagate across MiOpsAI immediately and get flagged for your team so you can update the patient's communication preferences in your EHR as well.
Can we run recall campaigns for specific conditions, like diabetes follow-up?
Yes, but the segmentation happens inside your EHR before the list gets exported. Your practice manager or medical director decides which patients belong on the "diabetes follow-up due" list, exports that list as non-PHI identity data, and MiOpsAI runs the outreach. The outreach message itself must be non-specific: "It is time for your regular check-in with Dr. Smith" rather than "Your diabetes follow-up is due." Same clinical outcome, no PHI in transit.