When the EHR Moves Into the Access Layer
The EHR you already run is moving into AI scheduling. Why that changes build vs buy at the front door, and where to actually compete.

Photo by Cottonbro on Pexels
When the EHR you already run starts doing AI SMS scheduling itself, the question for a patient-access team stops being whether to build a scheduling bot and becomes what to build on top of the one you are about to get for free. My take: do not fight the incumbent on the commodity layer. Differentiate above it, on the workflow, the trust, and the parts of the patient journey the EHR will not own.
A while back, Epic previewed a conversational AI agent that texts patients to schedule follow-ups: it opens an SMS in about twenty seconds, offers appointment options, and sends a MyChart link, with a handful of health systems already live and rebooking of canceled appointments on the roadmap. When I saw it, my first thought was not that it is impressive, though it is. It was that the ground just shifted for every patient-access team building a scheduling bot, because the EHR they already pay for is about to hand them one.
Here is how I read it. When the incumbent moves into the access layer, the commodity part of the job, the SMS bot that offers a slot, stops being where you compete. It becomes table stakes you will get from the platform. So the question is not whether to build a scheduling bot. It is what to build on top of the one you are about to get. And the answer, almost always, is the layer above the commodity: the workflow, the trust, and the parts of the journey the EHR will not own for you.
The commodity layer moved under you
Patient-access technology is a stack, and the incumbent just claimed the bottom layer, which changes what is worth building on the top. Think of it in three layers. At the bottom are the access primitives: send a text, offer a slot, book it, send a link. Those are becoming a commodity, and when the EHR ships them, competing there is a losing game. In the middle is your workflow and trust layer: how the whole journey fits together, how it handles the messy cases, how it earns a patient's confidence and a clinician's. At the top is the patient experience that actually differentiates you. When the platform takes the bottom layer, you do not mourn it. You move your effort up.
Do not fight the incumbent on commodity
The mistake is to rebuild what the platform now gives you, so I sort every access capability into let-it-do-it and own-it, and I do not blur the line. Some things I am happy to let the EHR handle, because it will do them well enough and everywhere: the basic text-to-schedule, the slot offer, the confirmation. Others I insist on owning, because they are where the experience is won or lost and where the platform's generic version will disappoint: the messy reschedule, the multi-step journey across services, the escalation to a human, the trust and tone. The build-versus-buy call is not once, it is capability by capability, and the incumbent moving in should make you sharper about the line, not scared of it.
The instinct, when a giant like the EHR moves into your space, is to panic or to compete head-on. Both are wrong. The commodity scheduling bot was never your moat, and now you get it for free, which is a gift if you take it as one. Let the platform carry the primitives. Spend your team on the workflow, the trust, and the whole patient journey, the layer above the commodity where access is actually good or bad. That is the build-on-the-platform move, applied to the front door, and it is how you stay ahead of an incumbent instead of behind it.
- When the EHR ships AI SMS scheduling, the commodity layer of patient access moves under you.
- Do not compete with the incumbent on the basic scheduling bot; you will get it for free.
- Differentiate on the layer above: workflow, trust, escalation, and the whole patient journey.
- Decide build vs buy capability by capability, not once for the whole product.
- Own the messy reschedule, the human handoff, and the cross-service path, where the platform disappoints.
- Treat the incumbent's move as a gift that frees your team for higher-value work.
Frequently asked
What is Epic doing in patient access?
Epic previewed a conversational AI agent that texts patients to schedule follow-ups, offers slots, and sends a MyChart link, with rebooking of canceled appointments planned.
How does this change build vs buy?
The basic scheduling bot becomes a commodity you get from the platform, so you should stop building it and invest in the workflow and trust layer above it.
What should a patient-access team own?
The messy reschedules, escalation to a human, trust and tone, and the cross-service journey, which the EHR's generic version will not handle well.
Should I compete with the EHR's scheduling bot?
No. Competing on the commodity layer is a losing game. Build on top of it, where the patient experience is actually differentiated.
Is this the same as build-on-platform strategy?
Yes. It is the agent-era build-on-the-platform idea applied to the front door: let the incumbent carry the primitives and own your differentiating layer.