
For years, the promise was that you could run your entire practice on a closed-loop system – meaning a single-vendor platform handling records, scheduling, billing, and patient communication all in one place. With just one login, one contract, and one number to call, it seemed like the safe call.
Then AI arrived.
Suddenly, tying your practice to that closed-loop system meant different problems. The Practice of 2036 report puts a number on the pace of technology: the tools now improve every 12 to 18 months.
There’s another way to build, and it moves the question behind your next technology decisions from what a single system can do to what the same system can do with everything else you run.
It’s about building a practice that’s open enough to add the best new tools, while keeping your practice management system at the center, your data secure, and everything else connecting around it.
For decades, your practice management system sat at the center for one reason: it held your data, and you couldn’t get it out. Everything from patient records to financial arrangements all lived there, in what the industry calls your “system of record.” Moving that data anywhere else was just too risky for most practices to try.
That system of record isn’t going anywhere. It’s still where your patient history lives, and it’s the main source of truth your practice runs on. But AI-assisted tools can now move and map the messy clinical data (unstructured notes, histories, and chart records) that used to take a six-figure migration and weeks of downtime. That one change is a big reason the next decade will reshape how your practice runs more than the last 75 did.
That frees you from a hard limit: you no longer need to settle for whatever your main system does well. You can add the best tool for each job and let them share the same records. This matters as much for a two-person practice as a three-hundred-location group. A solo office can add one tool to handle patient texts, keep the practice management system it already knows, and skip the migration entirely. You don’t need scale for the open approach to pay off.
When your AI Receptionist books an emergency visit, it works across several systems at once: it finds an opening in your scheduling system, applies your booking rules, pulls the patient’s file from your system of record, checks insurance eligibility, and sends a co-pay link through your payments tool. No single system did that job. An agent ran all of them from a layer above, in what the Practice of 2036 report calls the orchestration layer. That is where AI agents get managed, routed, and governed.
Picture your technology in two layers. Underneath is the system of record, holding your charts, history, and billing. Above it sits everything that runs the day: the tools handling your calls, text, payments, reminders, and reviews. Now AI agents do that work. Those upper-layer tools don’t hold your records. They connect to and act on them.
Your practice management system feeds that layer and keeps the official record of what happens in it. It’s one of several systems now, not a single place where technology handles some of the work and the humans have to do the rest.
This also changes what you’re really buying. A practice whose systems pass work cleanly between them gets the full benefit of every AI tool it adds. A practice whose systems don’t connect ends up with a drawer full of good tools that can’t help each other, that instead build bottlenecks waiting for a human to move data around.
The AI Receptionist is one kind of AI Agent: an AI program that carries out a task on its own, not just answers questions about it. Think of it as a digital teammate. You can hand it a job, and it will run with it. And because it can message a patient, reschedule a visit, or send a bill in your name, three things start to matter: what the AI teammate handles on its own, where it stops and asks a person, and how every action gets logged.
Platforms like Weave build those controls in and let you set them once, so oversight is something you configure, not something you must police all day.
But many practices today aren’t set up for this. In Weave’s survey, only 3% of practices surveyed have a technology leader who actually owns AI strategy. Nearly half say the owner carries it on top of everything else, and one in five say no one owns it at all. The practices that put someone in charge of it will be years ahead of the ones still treating technology as something you deal with only when it breaks.

For years, the question was some version of which system does the most on its own. Now it’s: How well does your system work with everything else we already run on?
The clearest signal is how a vendor wins. A closed suite wins when you can’t leave: it bundles your records, scheduling, payments, and communication into one sealed package and counts on switching being too painful to attempt.
A connected vendor wins the other way, by doing a few things well and working cleanly with whatever else you run. It has to keep earning its place. A connected vendor can have multiple products, as long as it all works with your stack instead of trying to replace it.
The next time you’re the one signing a contract, a few questions separate the partners built for this decade from the ones hoping you won’t ask:
How many of the systems I already use do you integrate with, and how deeply?
If the vendor can name your systems and show data moving both ways, that’s a strong answer. When a patient reschedules, the change should update your records, your billing, and your reminders without anyone moving the data manually somewhere else. Be wary of “we integrate with everything” with no specifics or a connection that turns out to be a nightly export you run yourself. Ask them to trace what happens to one patient’s file when it changes. If they can’t follow it across your systems, the integration is shallow.
Are those integrations authorized and supported on both sides, or workarounds that can break with the next update?
“Authorized” means both companies maintain the connection and test it when either system ships an update. A workaround is held together by one side and will break the next time the other changes something. Ask who is responsible for tracking changes, and what happened the last time a connected system pushed an update.
What security and compliance evidence stands behind the connection itself, not just the product?
Most vendors will hand you the compliance paperwork for their own software. The connection between two systems is where patient data actually travels, and it needs clarity on how data is encrypted as it moves. Ask about the handoff, not just their own system.
Could you help run the stack I already trust, or only your own tools?
Want to know if a vendor is a true partner or just trying to trap you in their ecosystem? Ask them if they’ll work with the software stack you already trust, or if they insist on using only their own tools.
A closed-suite vendor always has the same solution: replace your current tools with theirs. To test them, pick a critical tool your team relies on that the vendor doesn’t sell, and ask if they will integrate with it. Their answer will instantly reveal whether they want to collaborate with your business or completely take it over.
Within the decade, AI will be everywhere in healthcare. The practices that win will be the ones that can keep changing, swapping in what’s better when it arrives, while others wait on a closed system that won’t budge. Start now, and the lead you build becomes an advantage that’s hard for anyone to close.
This is only part of the picture. Weave’s Practice of 2036 Report maps the rest of the decade: how the shift reshapes your costs, your team, and the care itself.
Get practical insights, patient communication tips, industry trends, and new ways to increase efficiency and revenue—delivered monthly.
See firsthand how Weave can help you grow your practice.