Picture the front office of a four-provider clinic at 4:30 on a Wednesday. One staffer is on hold with a payer to check eligibility. Another is keying an insurance denial back into a billing screen. A third is fielding the eleventh reschedule call of the day while a claim from last week sits unworked. Practice management software is the tool that’s supposed to make that afternoon quieter. Whether it does depends entirely on which one you buy and how honestly the vendor drew the boundaries. This guide names the tradeoffs the sales deck skips.
Key takeaways
- A PMS covers five things: scheduling, billing and revenue cycle, insurance eligibility, patient communication, and reporting. Charting is the EHR’s job, even when they share a login.
- The real fork is all-in-one vs best-of-breed, and EHR-coupled vs standalone. There’s no universal winner. A lean two-provider clinic and a billing-heavy specialty group want opposite things.
- Migration is where deals go wrong. The demo is smooth; the go-live weeks are where claims stall and cash flow dips.
- Practice Copilot can cover documentation, scheduling, and a bundled EHR by tier. It still does not run US claims, clearinghouse, eligibility, or full RCM work.
Key facts
- saved per insurance eligibility check by going fully electronic instead of manual (CAQH 2023 Index)
- ~$10/txn
- of provider time saved per patient visit with fully automated admin workflows (CAQH 2024 Index)
- 70min
- median practice no-show rate; automated reminders are the cheapest lever on it (MGMA)
- 5–7%
Sources: CAQH 2023 Index; CAQH 2024 Index (via CAQH); MGMA.
What a PMS actually covers (and what it doesn’t)
Strip away the branding and a practice management system does five jobs. Get clear on these before you compare a single feature list.
Scheduling. The calendar: booking, rescheduling, cancellations, provider templates, and the waitlist. This is the operational spine. If the scheduling module is clumsy, your front desk pays for it every hour of every day.
Billing and revenue cycle. Charge capture, claim submission, denial management, payment posting, and patient statements. For most practices this is the reason a PMS exists. Weak billing is the single most common reason a clinic rips out a system two years in.
Insurance eligibility. Checking coverage before the visit so you’re not chasing a denial after it. The savings here are real and measured: the CAQH found the medical industry saves roughly $10 per eligibility check by running it electronically instead of by phone or portal (2023 CAQH Index). Multiply that across a full schedule and it’s not a rounding error.
Patient communication. Reminders, confirmations, recall for overdue visits, and increasingly two-way messaging. Reminders are the cheapest tool you have against no-shows, and no-shows aren’t small. MGMA puts the median practice no-show rate around 5 to 7% (MGMA Stat, 2023). Every confirmed slot is revenue the reminder paid for.
Reporting. Days in accounts receivable, denial rates, collection ratios, provider productivity. Without it you’re flying blind on the numbers that decide whether the practice is healthy.
Notice what’s not on that list: the clinical note. Charting, orders, results review, the SOAP note, that’s the EHR’s territory. Plenty of ambulatory suites bundle PMS and EHR under one login, which blurs the line, but they’re two different jobs. A PMS runs the business of the visit. An EHR runs the medicine of it. When a vendor sells you a “complete platform,” your job is to figure out which half is strong and which half is along for the ride.
Security requirements cut across both halves. If HIPAA is a purchase condition, use the HIPAA-compliant practice-management software checklist to test contracts, access control, auditability, integrations, and breach responsibilities instead of accepting a compliance badge as the answer.
The two decisions that actually matter
Feature grids are a trap. Every modern PMS checks the same boxes. The decisions that shape your next five years are structural, and there are only two of them.
All-in-one vs best-of-breed. An all-in-one suite gives you scheduling, billing, and comms from one vendor, on one bill, with one support line. Fewer integration seams, fewer finger-pointing matches when something breaks. Best-of-breed means picking the strongest tool for each job and wiring them together, which pays off when one function is critical enough to deserve a specialist. A high-volume billing operation might want a dedicated clearinghouse workflow that a generalist suite can’t match. A three-provider family clinic almost never does.
EHR-coupled vs standalone. A coupled system shares a database with your charting, so a diagnosis flows to a claim without re-entry. Clean, until you want to switch one and not the other. A standalone PMS keeps billing independent, which is exactly right if your EHR’s billing is weak, if you use an outside billing service, or if you just don’t want your revenue cycle held hostage to a charting vendor’s roadmap. The cost is a data bridge you own and maintain.
Here’s the honest version most vendor pages won’t print: for a small, lean practice, a standalone or all-in-one PMS with a tight, unshowy feature set often beats the sprawling enterprise suite. You don’t need forty modules. You need scheduling that doesn’t fight you, billing that gets claims paid, and reminders that fire. Buying a platform built for a 200-provider group to run a two-provider clinic is how software becomes the thing you resent.
| Function | PMS covers it | Lives elsewhere |
|---|---|---|
| Scheduling / calendar | Yes, core | – |
| Billing, claims, denials | Yes, core | Outside billing service (optional) |
| Insurance eligibility | Yes | – |
| Reminders / patient comms | Yes | – |
| Reporting on AR + productivity | Yes | – |
| Clinical notes / charting | Sometimes (coupled EHR) | The EHR |
| Ambient documentation, AI drafts | No | An AI layer (see below) |
| Interoperability / records exchange | Varies | EHR / HIE |
Draw the buy, integrate, or retain boundary first
Before comparing vendors, put every operating job into one of three buckets. This prevents an attractive documentation demo from being mistaken for a revenue-cycle replacement.
| Practice job | What a buyer needs to prove | Patient Square’s current boundary | Decision |
|---|---|---|---|
| Encounter documentation | Draft, clinician review, signature, export, and record ownership | Ambient scribe on every plan; structured SOAP note, ICD-10 suggestions, and prescription draft for review | Buy or trial if the note test passes |
| Clinical system of record | Migration, longitudinal chart, permissions, and exit export | Bundled AI Copilot EHR starts on Copilot; the public product surface doesn’t enumerate deep EHR submodules | Verify before replacing an existing EHR |
| Scheduling | Booking rules, staff overrides, reminders, and failure handling | Scheduling starts on Assist | Buy only after a real calendar test |
| Phone and follow-up automation | Human takeover, emergency boundary, consent, and audit trail | AI Receptionist and AI Follow-ups start on Autopilot | Add after the escalation test |
| Claims and clearinghouse | Eligibility, claim submission, ERA, denial work, and payer connectivity | Not claimed as a Practice Copilot capability | Retain or buy a dedicated PMS/RCM stack |
| Billing history and open balances | Clean migration, reconciliation, parallel run, and ownership | No public claim that this migration is supplied | Retain until a written migration plan exists |
Our opinion: the claims row should be a hard stop. If the project is mainly a clearinghouse or denial-management replacement, this isn’t the right product category. If the practice wants the documentation and record layer while keeping a billing service or PMS, the boundary can be sensible. The integrated EMR and practice-management guide covers that architecture; current pricing shows which Patient Square tier owns each shipped module.
Migration is where the money hides
Every PMS demos beautifully. The screens are clean, the sample data is tidy, the rep clicks through a claim in nine seconds. None of that tells you what the switch will cost you.
The risk sits in two places. First, data migration: moving patient records, open balances, scheduling history, and provider setups from the old system to the new one without losing or corrupting anything. Second, the go-live weeks, when your staff is slow on unfamiliar screens and claims can stall in the transition. A dip in cash flow during a botched go-live is the tax nobody quotes you.
So make the vendor earn it. Ask for a written migration plan, a data-mapping document that says exactly which fields go where, and a parallel-run period where the old system stays reachable while the new one takes over. Ask how open accounts receivable transfers, because half-migrated balances are a collections nightmare. And never, ever go live over a long weekend with no fallback. The clinics that migrate cleanly treat it as a project with a timeline, not a switch you flip.
Where Practice Copilot fits, and where it stops
Here’s where a lot of buyers get confused, so we’ll be blunt about our own product. Practice Copilot is not a full US PMS or revenue-cycle suite. It won’t submit your claims, run a clearinghouse, check eligibility, or replace a billing engine.
What it does claim publicly is narrower. The ambient AI Medical Scribe produces a structured SOAP note, ICD-10 suggestions, and a prescription draft for clinician review. Scheduling starts on Assist. The Copilot tier adds the bundled AI Copilot EHR and WhatsApp messaging; Autopilot adds modules named AI Receptionist and AI Follow-ups. The public pages don’t describe deep behavior for those named modules, so a buyer should make the demo prove the exact calendar, call, message, and handoff behavior it needs.
The safe division is clear at the billing boundary. Your existing PMS or billing service keeps claims, eligibility, statements, balances, and denials. Practice Copilot can be tested for documentation and the tier-scoped record or front-office modules. Whether you keep the old EHR and calendar too depends on migration and workflow evidence, not the word bundle.
We think clinics should keep revenue-cycle ownership separate on purpose unless a vendor can prove every payer workflow. A specialist billing platform can run the money while the clinical layer changes. That cuts the migration blast radius and makes the limitation obvious.
So how do you actually choose?
Boil it down to four questions and ignore the rest of the pitch.
- Is billing the strong half or the weak half? Demo a real denial workflow, not a clean paid claim. If billing is weak, either pick a best-of-breed billing tool or plan to bolt on an outside service.
- Coupled or standalone? Decide whether you want billing chained to your charting vendor. If your EHR’s billing is fine and you like it, coupled is simpler. If it isn’t, keep them independent.
- What’s the migration plan in writing? No plan, no data-mapping doc, no parallel run: no deal. The go-live is where the real cost lives.
- Which Patient Square modules have you actually proved? Documentation, scheduling, a bundled EHR, messaging, receptionist, and follow-up labels don’t prove your exact workflow. Run each claimed handoff before retiring an incumbent.
The verdict is unglamorous and it’s the right one. Keep a PMS or billing partner that’s genuinely strong at claims for your size of practice, insist on a written migration plan, and replace only the modules that pass a real workflow test. For a small clinic, a clear boundary beats a sweeping platform claim.
If you want to test that boundary,
Sources: CAQH 2023 Index Report; CAQH 2024 Index (via CAQH); MGMA no-show benchmark; JAMA Network Open 2022 (via AMA).
How Patient Square fits your existing record system
In the US, an established practice can keep its current EHR as the system of record while Practice Copilot supports documentation and shipped practice workflows. A new practice can instead use Patient Square EHR as its system of record from the Copilot tier. Neither path promises automatic filing or write-back into a named third-party EHR.