Outpatient AI operations - Lawrenceville, GA

The operational layer underneath everything your systems can't see.

ARFA is a healthcare operations consulting and product studio building the outpatient version of enterprise AI operations: workflow architecture, data interoperability, governed automation, and human-in-the-loop execution. We wire together the tools your practice already runs: phone, fax, intake, scheduling, billing, documents, and reporting. None of them were built to talk to each other. We build the workflows that bridge them, then keep the important decisions visible to staff.

Request a workflow leak review See what we build
Or call 678-730-2173  ·  book a 15-minute call
BAA-gated by default
14-day narrow pilot
No rip-and-replace
Workflow-mapped, not templated
Human-approved, audit-logged
Inbound call → Triage → Schedule
DEMO
📞 Voice In 🤖 Triage AI 📋 Scheduler 📊 Dashboard ✓ Logged · 1.4s
12:42:01 ● Call received, first ring
12:42:03 ● Recognized: booking request → scheduler
12:42:04 ● Booking created in scheduler
12:42:05 ● Audit row written, 1.4s end-to-end
Watch the overview

The AI layer your practice is missing

Administrative burden and burnout are real, and they rarely come from the care. They come from the busywork between your systems: the calls nobody catches, the faxes that pile up, the follow-ups that slip. A short look at everything ARFA can build, and how AI can safely take that load off your team without ever touching a clinical decision. Tailored to how your facility already runs.

Synthetic patient data only. No real PHI in any demo.

The work your software doesn't see
Who this is for

Independent practices leaking revenue through broken workflows.

Every vertical below leaks revenue in a slightly different place. If a card describes something you have seen in your own practice, that is the conversation worth having, because your version of it is specific to how you run, and that is what we map first. Click a card with a link to see the specific automations.

🩸
Clinical lab & phlebotomy
A 15% Medicare cut is coming. The margin is in the workflow.
Independent labs take work three ways: fax, web form, and phone. Revenue leaks to preventable pre-analytical errors before a test runs. ARFA puts all three doors on one live board with a STAT clock on every urgent order.
View automations
📋
ABA / Behavioral Therapy
Clean clinical work. Denied anyway.
Most ABA denials aren't about care quality. They're a missing modifier, an unsynced note, or an auth that lapsed. RBTs write from memory hours after the session, and the defect surfaces 60 days later as a denied claim nobody traces back.
View automations
🏥
Direct primary care
Slow onboarding kills retention. Missed calls kill acquisition.
Patients paying monthly expect immediate onboarding and an answer on the first ring. Every delay creates a cancellation before loyalty ever forms. See the full system that closes both gaps.
View walkthrough
✨
Aesthetics & med spa
Five things your EHR cannot see.
Expiring vials, patients who never rebooked, consults that went cold, and consent gaps the FDA cares about. Your EHR tracks the treatment, not the operation around it. See the operations layer that runs all five.
View walkthrough
💉
Med spa
Speed closes. Voicemail doesn't.
A patient DMs your Instagram. If you don't reply in five minutes, they book the next IG-active spa on their feed. Which channel is losing you the most depends on where your bookings actually come from. That is the first question worth answering together.
💧
IV / Wellness
Same-day demand or nothing.
Most IV bookings happen the day they call. Miss the first ring and the patient books somewhere else within minutes. How often that window closes on you depends on your call volume and when your staff is stretched thinnest. That is what the first conversation is for.
🦷
Dental
Miss one cosmetic call. Lose a multi-thousand-dollar case.
High-value cosmetic patients rarely leave a second voicemail. They book the next cosmetic dentist on the search results. Which call types you are losing and when they are hitting voicemail is specific to your schedule and your front-desk coverage. That is where we start.
View automations
🦴
Physical therapy
Empty treatment hours compound fast.
Expired auths, missed reactivations, and gaps in the schedule compound into lost revenue nobody notices until quarter close. Which of those is bleeding the most depends on your payer mix and how your scheduler is managing the cancellation queue. That is the first thing worth mapping.
⚕️
Specialty & weight loss
GLP-1 demand buries front desks.
High-volume weight loss inquiries overwhelm small admin teams in days. Manual triage creates bottlenecks before anyone realizes it.
🌀
Chiropractic
Pain doesn't wait for voicemail.
Acute injury calls after-hours route to urgent care the second voicemail picks up. Most book with whoever answers first.
View automations
👁️
Optometry / eye care
The exam and reorder you lose today, caught.
Exam bookings, contact reorders, and recall reminders scatter across the phone, the request form, and your reminder tool. A missed call at lunch is a recurring patient buying glasses somewhere else.
View automations
What we build

Six categories of broken workflows. Most facilities recognize at least two.

Most operational pain in an independent practice comes from work that happens between systems your existing software does not connect. At the enterprise level, this is an AI operations problem. ARFA brings the outpatient version to smaller facilities: workflow architecture, clean handoffs between systems, governed automation, and human-in-the-loop execution. Every workflow here runs on tools with signed BAAs where PHI is involved, every important action is logged, and your staff stays in control of decisions that matter. Start with one workflow. Add the rest as confidence grows.

📞
Phone & SMS
Inbound voice + recovery
  • Voice receptionist (first-ring pickup, 24/7)
  • Missed-call recovery with text-back in 2 minutes
  • Two-way SMS triage and booking
  • Outbound no-show reactivation calls
  • Insurance verification call routing
📠
Fax automation
Inbound fax intake
  • Faxed referrals parsed into structured intake
  • Lab results routed to the ordering provider
  • Records-release fax automation
  • Referring physician confirmation cascades
  • Auto-classification by document type
📋
Intake & scheduling
New patient onboarding
  • Online booking, synced to the schedule (demo)
  • New patient intake forms, pre-populated
  • Pre-visit document chase (insurance card, ID)
  • Appointment reminders by SMS or email
  • Reschedule and cancel cascades
💳
Billing & authorization
Revenue cycle workflows
  • Prior auth tracking dashboard
  • Insurance denial alert workflows
  • Claim resubmission triage
  • Patient statement follow-ups
  • Eligibility verification automations
📊
Operations & reporting
Staff dashboards and KPIs
  • Role-filtered staff queue (front desk, clinical, billing)
  • Daily and weekly KPI reports
  • Stuck-deal and aging-task alerts
  • Custom revenue leak audits
  • Exportable report bundles (CSV, PDF)
📄
Documents & compliance
Document workflows
  • Records release automation
  • Document expiration tracking (licenses, insurances)
  • BAA-gated document intake portal
  • E-signature workflows
  • Audit log export for compliance review
How a pilot starts. You pick the one workflow leaking the most revenue or staff hours right now. We build that on BAA-gated tools, and within about two weeks you can see from the first real operating signals whether it is worth expanding. The other workflows follow only when the first one is stable and the math is on the table. That pick is not something I can make from the outside. It comes from 60 minutes of mapping it together.
Patterns from independent-practice research, operator conversations, and mock-data builds

Three workflows. Walk through any of them with me.

Synthetic patient data, BAA-gated tools, end-to-end traceable. Same pattern extends to every category above.

01

Voice receptionist

Your front desk is with a patient. The phone rings. Three seconds of silence later, voicemail. The caller heard the beep and hung up. This is what happens instead: every call answered on the first ring, booking, refill, billing, or urgent triaged in under 2 seconds. Last-name plus date-of-birth verification before any patient info is disclosed. Emergency cases route to 911 with an audit trail.

📞
02

Missed-call recovery

It is 5:48pm. Someone called. Nobody picked up. By the time your coordinator checks voicemail in the morning, they have already called the practice down the street. This closes that window: if a call drops, rings out, or comes in after-hours, the patient gets a text back within 2 minutes. The lead lands in the dashboard automatically. Nothing leaks even when something upstream breaks.

✕
Missed call · 7:42 PM · 678-730-2173
↓
✓
SMS sent · "Hi, we missed your call, book here"
03

Staff queue and routing

Right now, when a call ends, where does the information go? Sticky note, mental note, or a voicemail nobody transcribed? This is what a staffed queue looks like instead: every appointment, refill request, callback, or escalation flows to the right person. Categorized, tagged with an action verb, audit-logged. Front desk only sees scheduling. Clinical only sees medical. Billing only sees insurance.

BOOK Sarah Chen, new patient 2s
VERIFY Mark Johnson, insurance 5s
REFILL Lisa Park, lisinopril 8s
CALL D. Wilson, followup 12s
What runs in the background

Built for control, not just automation.

Putting AI into a clinic safely comes down to one thing: control. What each part is allowed to do, who it answers to, and what gets written down. (The technical term is AI governance.) Every ARFA pilot is assembled from the same set of controls, and every component that could touch patient data sits behind a signed Business Associate Agreement before a single real record moves. That BAA gate is not a nice-to-have. It is the filter that decides what is even allowed on the path.

Intake capture

A BAA-covered voice and messaging layer answers the phone, has the conversation in real time, and verifies identity (last name plus date of birth) before disclosing anything. Adversarial-tested against social engineering, profanity, and controlled-substance probes.

Triage and routing

An enterprise-hosted, BAA-covered language model works out what each request is actually about and decides where it goes next. A workflow engine then carries it there: book it, log it, send the message, page the on-call clinician, or hold anything uncertain for a person. Nothing consequential happens without a human confirming it first.

Human review and status dashboard

A custom, role-filtered dashboard is what your team opens in the morning: front desk sees scheduling, billing sees insurance, every item one click from done. An optional browser panel docks the same queues beside whatever EHR or system your staff already use, so there is no new tab and no new system to learn.

Audit log, exception handling, exportable records

Every action is timestamped, attributed, and queryable, so a compliance review can reconstruct exactly what happened. Anything that fails is caught and surfaced for a person, never dropped silently. Your records export cleanly, so you are never locked in.

Every component that could touch HIPAA-covered data is chosen because it offers a signed Business Associate Agreement. Tools without one, like standard public LLM APIs and open-routing aggregators, are never on the path. The exact tools depend on the workflow we pilot first and the data involved; the full signed BAA matrix is part of every proposal.

📞
Voice & messaging layer
Intake · first-ring pickup, identity check
BAA-gated
🤖
Language model
Enterprise-hosted · triage, refusal
BAA-gated
⚡
Workflow engine
Routing, audit, exception handling
BAA-gated
🗄️
Internal database
Patient data, audit log
BAA before go-live
📨
Telephony & SMS
Calls in, messages out
BAA-gated
📊
Staff dashboard
Custom-built · role-filtered queues, drag-to-update
Internal · no PHI in transit
🧩
Browser panel
Live board in-browser · alerts, beside any EHR
Internal · no PHI in transit
HIPAA & compliance

Every tool that touches patient data has a Business Associate Agreement before the first real call.

The question every healthcare operator should ask any vendor: what happens to patient data, specifically, and who is legally responsible for it? Below is the answer for every tool in the stack. The guardrails on this page, what the industry calls AI governance, are simply the rules that keep the AI safe: what it is allowed to do, a human approving anything that matters, and a record of every action. Synthetic data only until all agreements are signed. No real PHI in any demo. The matrix below is exhibit A in every proposal.

Defaults that protect you

  • ✓
    BAA-gated by default No real patient data touches anything until every Business Associate Agreement is signed. Synthetic data only for demos.
  • ✓
    Audit log on every access Every PHI touch is timestamped, user-tagged, and queryable per call, per row, per minute. Designed to preserve the evidence a compliance review would ask for.
  • ✓
    Verification before disclosure Voice agent verifies last name and date of birth before any patient-specific information is disclosed. Wrong DOB means the agent refuses politely.
  • ✓
    Graceful degradation If the model has an outage, the voice agent falls back to a scripted hold sequence and pages the practice cell. The patient never knows anything broke.
  • ✓
    Exportable data, always Every row, every transcript, every audit entry is yours. Standard formats. No vendor lock-in. Walk away with everything at any time.

BAA matrix, exhibit A

Tool / layer Status
Production language modelSIGNED
Voice gatewaySIGNED
SMS gatewaySIGNED
Intake / schedulingSIGNED
Compute / database hostSIGNED AFTER CONTRACT
Public LLM APIsNEVER USED
Open-routing aggregatorsNEVER USED

Two tools at the bottom (public LLM APIs and open-routing aggregators) are never used for any practice we work with. They don't have BAAs. They aren't on the path.

Common questions

The questions every clinic owner asks. Answered before the call.

If you watched the demo and you're thinking about it, the questions below are almost certainly the ones in your head. We wrote down our actual answers, the same ones we give on a call, so you can read them on your own time before booking anything. If a question you have isn't here, the demo line answers in real time (678-730-2173) and so does the booking call.

Don't we already have an answering service?
You probably do, and we don't replace it. An answering service is a callback queue: it takes a message and queues the follow-up for the next morning. ARFA answers in the moment. It books into your scheduler while the patient is still on the line, runs intake, texts back any missed call within two minutes, and writes the call to the patient record. Most practices keep their service for after-hours human routing and add ARFA for the routine calls the service can't close. On day 30 the dashboard shows you which calls each one is actually handling.
People like talking to a human.
They do, until they're on hold. Industry studies put hang-up rates around 60-70% after a 30-second wait, and most of those callers go to the next clinic in the search results. ARFA answers on ring one. Any caller who specifically asks for a person gets routed to your team during business hours. Nothing about this removes the human option. It stops the voicemail-to-callback-to-phone-tag loop that frustrates the membership patients who joined for concierge access.
How is this different from what my answering service already does?
Three things. ARFA books live into your scheduler while the caller is on the line. It triggers refills through your existing EHR workflow. It texts back missed calls within two minutes. An answering service takes a message and queues the callback for tomorrow morning. ARFA finishes the call.
We're a small practice. Do we even need this?
Small is where this lands hardest. A 10-doc practice has rotating front-desk coverage. A 1-doc or 2-doc practice has the same phone problem the larger group does, with none of the headcount. Membership models in particular leak fastest at small scale, because every missed inquiry is a recurring member you don't have for a year. You're not too small for this. You're exactly the size this helps most.
I answer my own phone. That's the membership.
You should keep doing that for the calls that need you. ARFA handles the calls that don't: booking confirmations, refill triage, after-hours rebook, new-member inquiries that come in while you're in a visit. The phone protects the patient who actually needs you. The agent handles the rest. You stop being interrupted mid-visit because the agent only routes calls that genuinely need a clinician.
My medical assistant handles the phone fine.
Probably. The question is what happens to the call that comes in while she's checking in a patient at the window. ARFA picks that one up. It does not replace her. It catches the overflow she physically cannot get to, which both of you know happens during the morning rush and over lunch. Her job becomes the patients in front of her, not the phone she can't always reach.
We don't really miss that many calls.
Most practices believe that until they see the dashboard. The first week shows you exactly how many calls hit voicemail, when, and what they were about. If the number is zero, you cancel and you got a free audit. If it's not zero, you have recovered six months of leaked revenue you didn't know about. The data answers this question better than either of us can.
I use Atlas.md / Hint / Spruce / Athena. I'm not switching EHRs.
You shouldn't. ARFA sits on top of your existing EHR. It books into the scheduler you already use, triggers refills through your existing workflow, and writes call notes to the patient record. No migration, no data move, no replacement. Your EHR stays the source of truth. ARFA is the front door that stops calls from dying before they reach it.
Is this HIPAA compliant? Where do the recordings sit?
BAA-by-default. No patient data touches anything in ARFA before every Business Associate Agreement is signed. Recordings encrypted at rest. Audit log on every access. The BAA matrix above in the HIPAA section is exhibit A in every proposal, including which tools we use, which tools we never use, and the legal status of each. Your compliance person can review the full stack before you sign anything.
Are you a clinician?
No. ARFA is built by an operations engineer (Arfa McClain, CAHIMS credentialed). The agent never makes clinical decisions. Clinical questions get routed to a clinician. The architecture is intentional: anything that touches clinical judgment is a hard no, including the agent itself. Clinical decisions stay with you.
Who else is using this?
Founder cohort. The rate is half what it will be in six months. References available at the second meeting after a mutual NDA. If you want a vendor with 200 logos, this is not the one. If you want to shape the product and lock in a lower long-term rate, this is the window.
We're not adding software right now.
ARFA is not software in the way most vendors mean. No new EHR, no new scheduler, no new CRM, no new login for your team. It is the layer that makes the systems you already have actually answer the phone. Setup is roughly two hours. The change-management cost on your team is close to zero. If the resistance is integration time or training overhead, this specifically avoids both.
What happens in the first 30 days?
Week 1 is BAA signing, EHR read/write access, and a 90-minute setup call where we map your specific call types and route them. Week 2 is shadow mode: the agent runs alongside your current setup and the dashboard logs everything without taking action, so you see what would have happened. Week 3 the agent goes live on a narrow scope (one call type, like new-member inquiries). Week 4 we expand to the next call type only if the data from week 3 supports it. No big-bang go-live. No surprises.
What if the AI gets a clinical question wrong?
The agent does not answer clinical questions. By design. If a caller asks something clinical, the agent confirms identity, takes the question, and routes it to your team for response. The agent's hard rules are written, audited, and shown to you in the compliance section of every proposal. Disclosing patient information requires verified identity (last name plus date of birth match). Anything outside the agent's scope gets a human handoff. The architecture protects you from the failure mode you're picturing.
I'd have to ask my partner.
You should. We'll send a one-paragraph summary you can forward, or schedule a 15-minute joint call with both of you. Most husband-wife or two-doc practices, the partner running ops is the one with the strongest read on this. Looping them in early is the right call.
Send me a one-pager.
We will. The honest version: most one-pagers die in the inbox. Two minutes on a screen share, or a 60-second call to 678-730-2173 to hear the agent answer as if it were your practice, will tell you in 30 seconds whether this fits. The one-pager goes in the same email. The number does the work the PDF cannot.
Don't see your question? Two ways to find out fast: call the demo line at 678-730-2173 and ask the agent directly, or book a 15-minute workflow review. The questions clinic owners ask most often come back into this page within a week, so the next operator who reads this has one less question to figure out alone.
ARFA mark
Arfa McClain
MHA - Outpatient AI operations
Lawrenceville, GA
About

Production-engineering discipline applied to the back of the house.

I built ARFA after watching independent practices try to solve operational problems with software designed for hospital networks. The mismatch is everywhere. Practice management systems that don't know what the phone did. EHRs that can't see after-hours calls. Dashboards that show everything to everyone instead of routing what matters to who needs it. Fax workflows that still rely on someone walking a piece of paper across the room.

The larger version of this discipline already exists in enterprise consulting: workflow architecture, data interoperability, governance, automation, and human review. ARFA is bringing that operating model to outpatient facilities that cannot afford a hospital-scale transformation team, but still have hospital-grade operational pressure.

Enough time watching how independent practices actually run makes the patterns visible. The missed call nobody logged. The fax that sat until someone walked by. The prior auth that expired while the coordinator was covering the front desk alone. But the specific version of that breakdown is different in every practice. So there is no template here. There is a map, and a conversation about where yours lives.

I treat AI in a clinic the way you would treat anyone new touching patients: it gets the least access it needs, a person stays in control of anything that matters, it fails safely, and every action it takes is logged. Keeping the AI on a short leash with a human in charge is as much the product as the automations are.

One operator, deliberate scope, no rip-and-replace. Pilots take 14 days. The math you'll get back when you reply to this page is your own. Your patient volume, your patient lifetime value, your specific workflow leaks. No deck, no slides.

Workflow leak review

Send your numbers. Get a one-page leak estimate.

Your staff already knows where the friction is. This is how we start finding your specific version of it. Tell me your rough weekly patient volume and the one or two places work leaks the most: missed calls, no-shows, intake, insurance and prior-auth follow-up, or patients who never rebook. You will get back a leak estimate and the three workflows worth piloting first. No deck. 15 minutes if the math looks worth talking through.

Prefer to talk? Call 678-730-2173 or book a 15-minute consultation.
Or email info@arfaconsults.com.

Want this mapped to your specific practice? Request a workflow leak review
📅 Live demo

Schedule a live demo

Tell us a bit about your practice and we'll set up a short, guided walkthrough: the AI receptionist answering a call, the lead landing on the board, and the workflows that fit how you already run. We tailor each demo to your practice, so we review every request first.
Synthetic data only. Please don't share real patient information on the call.