Key takeaways
- Map tools against jobs, not vendors: the overlap shows up where two tools do the same job for the same patients.
- Decide keep, merge or retire with four tests: integration, use, cost and the cost of leaving.
- Retire one tool at a time, in the quiet season, with a data export and a records plan for each.
- Tell patients only what changes for them, and tell staff exactly which screen replaces which.
How practices end up with too many tools
No practice sets out to run twelve systems. It happens one sensible decision at a time. The EHR came first. Then a reminder service because the EHR's was weak, a texting tool for two-way messages, an intake form product, a payment link vendor, a separate fax service, a phone system with its own voicemail and app, and a telehealth platform from the pandemic years. Each solved a real problem. Together they mean staff log in to many places, patients receive messages from several senders, and patient data lives in more systems than anyone can list from memory.
Cost pressure makes this worth fixing now. In 2026, 84% of medical groups reported operating costs higher than a year earlier[1], and automation and process fixes topped practice leaders' planned cost-cutting moves[2]. Consolidation is often the cheapest process fix available: fewer contracts, fewer logins, fewer integrations to maintain and fewer places for errors to hide.
- Reported higher operating costs than in 2025 84%
Source: Medical Group Management Association (MGMA), 2026[1]
Show the data
| Item | Value |
|---|---|
| Reported higher operating costs than in 2025 | 84% |
Map tools against jobs, not vendors
Start from the inventory described in our technology budget guide, then turn it sideways. List the jobs your front office does down one side, and the tools across the top. Mark which tool does each job today, and which tools could do it if you switched on a feature you already pay for.
| Job | EHR or PM | Reminder tool | Texting tool | Phone system | Intake tool |
|---|---|---|---|---|---|
| Appointment reminders | Could | Does | Could | No | No |
| Two-way patient texting | Could | Does | Does | Could | No |
| Intake forms | Could | No | No | No | Does |
| Payment links | Does | No | Could | No | No |
| Voicemail and call logs | No | No | No | Does | No |
| Recall outreach | Does | Could | Could | No | No |
The overlap is wherever two or more tools are marked Does for the same job, or where an unused Could in a core system could replace a separate subscription. In the example map, reminders and two-way texting are done by two tools, and the PM could handle both. That is the first candidate for consolidation.
Four tests for keep, merge or retire
For each overlapping pair, score both tools on the same four tests. Do it with the people who use them, not only the manager who pays the invoices.
- Integration: does the tool read from and write to the EHR or PM reliably, or does someone retype data?
- Use: how many staff use it each week, and do they prefer it for a real reason?
- Cost: what is the full annual cost, including interface fees and administration time?
- Cost of leaving: what does it take to export data, retrain staff and tell patients about the change?
A tool that is well integrated and widely used survives even if it costs more. A tool that duplicates a core system feature, has few active users and stores little unique data is the easiest to retire. The hard cases are tools staff like that do not integrate. For those, test whether the core system's version is genuinely worse or just unfamiliar.
When consolidating is the wrong move
Fewer tools is not always better. Nearly every office-based physician already uses an EHR, 91% with a certified system in 2024[3], and EHR suites now offer modules for almost everything. Some of those modules are weaker than specialist tools. Keep the specialist tool when it does something the core system cannot, when it measurably saves staff time, or when patients clearly prefer it. A reminder tool that cuts no-shows is worth its subscription even if the EHR has a basic reminder feature.
- Do not consolidate onto a module nobody has tested with your own visit types.
- Do not retire a tool in the middle of flu season or your busiest month.
- Do not merge two changes at once; patients and staff can absorb one at a time.
- Do not cancel the old contract before the new setup has run for a full cycle.
Plan the work, not just the tools
Consolidation is a chance to fix workflows, not only contracts. Practices often add software without changing roles. In a 2026 poll, 68% of practice leaders said their organization had not redesigned a role or adjusted staffing with the help of AI in the past year[4]. The same pattern applies to ordinary software: a new tool is layered on top of the old routine. When you retire a tool, write down who did what in it, and decide who will do that job in the surviving system, on which screen, at what time of day.
A 90-day consolidation plan
Weeks 1 to 2: decide
Complete the overlap map and the four tests. Pick one tool to retire first, ideally the simplest with the clearest overlap.
Weeks 3 to 4: prepare the replacement
Configure the surviving system to do the job: templates, message wording, schedules, permissions. Test with fictional patients.
Week 5: export and plan records
Export all data from the outgoing tool in a usable format. Decide what is filed to the chart, what is kept as an archive and for how long.
Weeks 6 to 7: run in parallel
Turn on the new setup for one location, provider or visit type while the old tool still runs elsewhere.
Week 8: switch over
Move everyone. Update website links, phone messages and printed materials. Keep read-only access to the old tool if the contract allows.
Weeks 9 to 12: confirm and cancel
Check that nothing was missed, then give notice on the old contract and remove its access and integrations.
Records and data when you retire a tool
Retired tools often hold patient information: messages, forms, call recordings, payment records. Before you cancel, decide what happens to each. Information used to make decisions about patients may be part of the record patients can request. A covered entity must act on a patient's request for access no later than 30 days after receipt, with one extension of no more than 30 days[5], and that clock does not pause because the data sits in an old vendor's system.
- Ask the vendor for a full export in a documented format, and test that you can open it.
- File anything clinically relevant into the chart before cancellation.
- Agree in writing how and when the vendor deletes your data after the contract ends.
- Keep the decision record: HIPAA requires covered entities to retain required policy and compliance documentation for six years[6].
- Remove the tool's integrations and service accounts on the day you stop using it.
Telling staff and patients
Staff need specifics: which screen replaces which, what to click, what to tell a patient who asks. Give them a one-page before-and-after sheet for each job that moves. Patients need much less. Tell them only what changes for them, such as a new sender name on texts or a new payment link, and tell them before the first message arrives so they do not mistake it for a scam.
Example patient notice: 'Starting March 3, appointment reminders from Cedar Grove Pediatrics will come from our patient portal number. You can still reply C to confirm. If you have questions, call the office number on our website.'
What success looks like
Example: a fictional five-provider family practice retired its separate reminder and texting tools and moved both jobs into its PM over one quarter. Staff went from four logins to two for daily patient communication, patients received messages from one number, and the practice removed one EHR interface it had been paying to maintain. No-show rates stayed flat through the change, which was the main risk it had tracked.
- Fewer logins per front desk workstation.
- Fewer integrations to maintain and pay for.
- One sender identity for patient messages.
- No drop in the measures the old tool was bought to improve.
- A current inventory that matches what you actually pay for.
Frequently asked questions
How do we know if we have too many tools?
Map each front office job against the tools you pay for. If two tools do the same job for the same patients, or a core system could do it with a feature you already own, you have overlap.
Should we move everything into the EHR?
Not automatically. Keep specialist tools that do something the EHR cannot or that measurably save time. Consolidate where the EHR or PM does the job well enough with your own visit types.
What happens to patient data in a tool we cancel?
Export it before canceling, file anything clinically relevant into the chart, and agree in writing how the vendor will delete what remains.
How long does a consolidation take?
About a quarter per tool is realistic for a small practice, including a parallel run. Retire one tool at a time and avoid your busiest season.
References
Medical Group Management Association (MGMA) (2026). Operating costs keep climbing for medical practices in 2026 (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2026). Automation, process fixes top list of cost-cutting moves for medical practices in 2026 (opens in a new tab) ↑
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) ↑
Medical Group Management Association (MGMA) (2026). AI is slowly redesigning work in medical practices rather than replacing workers (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.524 - Access of individuals to protected health information (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.530 - Administrative requirements (opens in a new tab) ↑