A practice searching for patient management software may be shopping for six different products without realizing it. The phrase can describe a clinical record, portal, CRM, scheduler, billing system, or longitudinal care platform.
Do not compare vendors yet. Locate the job.
Key takeaways
- The category name does not establish scope. Identify the system of record and the event that needs fixing.
- Portal, CRM, scheduling, billing, and care management can sit around an EHR without replacing it.
- Patient Square covers documentation, scheduling, a bundled EHR by tier, and named communication modules. It is not full RCM, payer care management, or population health.
- Price the complete data path, not the cheapest seat.
The six-category patient-management grid
| Category | Job it owns | Core evidence in a demo | Disqualifier |
|---|---|---|---|
| Clinical record / EHR | Signed chart, history, medications, documents | Create, sign, amend, retrieve, export | Cannot produce a usable complete record |
| Patient portal | Patient access, forms, results, messages, payments | Patient completes the intended task on a phone | Portal is only a staff-facing screen |
| Healthcare CRM / engagement | Outreach, lead or referral follow-up, communication | Consent, routing, opt-out, attribution | Communication cannot be tied to an authorized workflow |
| Scheduling and intake | Appointment inventory, booking, reminders, registration | New, rescheduled, cancelled, walk-in, duplicate | Appointment and chart identities diverge |
| Billing / RCM | Eligibility, charges, claims, ERA, balances, denials | Claim from encounter through correction and payment | Requires retyping or lacks payer workflow |
| Care management / population health | Cohorts, care plans, gaps, tasks, longitudinal work | Attribution, risk or gap logic, task closure, audit | It is merely a patient list or reminder tool |
This grid stops a familiar mistake: buying a portal to solve a claims problem, or buying a CRM and assuming it became the chart.
Start with the event that fails
Write one sentence before opening a demo. Examples:
- “Patients wait on hold because staff cannot expose safe appointment inventory online.”
- “Signed notes remain open until the next morning.”
- “The billing team retypes demographics and codes from the chart.”
- “Patients cannot retrieve results or complete intake on a phone.”
- “Referrals arrive, but nobody owns the next contact.”
- “Care managers cannot see which attributed patients have an unresolved task.”
Each sentence routes to a different row in the grid. A broad suite can cover several rows, but it still has to prove the failing event.
Name the source of truth
Patient data is not one blob. Assign an owner to each object:
| Data object | Source-of-truth system | Who may change it | Where it must go next | Failure owner |
|---|---|---|---|---|
| Patient identity | ||||
| Appointment and status | ||||
| Signed clinical note | ||||
| Consent and communication preference | ||||
| Charge and claim | ||||
| Payment and patient balance | ||||
| Care plan, gap, and task |
One vendor may own several rows. That is fine. One login does not fill the blanks automatically.
That worksheet becomes especially useful when a practice is changing only one system. A scheduler can remain the source of truth for appointments while the EHR holds signed notes. A billing service can own claims while a different system creates the charge data. The important part is not forcing every task into one platform. It is making the handoff and exception owner explicit before a patient is affected.
Records and portals solve different access problems
The EHR is the professional record. It should preserve authorship, dates, amendments, and a usable history. CMS documentation guidance focuses on the completed encounter record and whether it supports the service billed.
A portal exposes selected patient-facing tasks. It may show results, messages, forms, appointments, balances, or records, depending on the product. A portal does not become the EHR because it displays chart data. An EHR does not automatically have a usable portal because a feature list says “patient engagement.”
If patient access is the purchase, test the bundled-versus-standalone portal matrix. Use a real phone and a test patient, not an administrator’s desktop.
CRM and scheduling are not care management
A healthcare CRM often manages outreach, referrals, leads, campaigns, and communication. Scheduling owns appointment inventory and status. Both can improve access.
Care management is a different job. It can involve attributed populations, care plans, assessments, gaps, risk logic, cross-encounter tasks, escalation, and outcome tracking. A reminder to return in six months is useful. It does not prove a population-health platform.
Ask the vendor to show why a patient entered a worklist, who is responsible, what evidence closes the item, and how the action is audited. If the answer is “we can tag patients,” the scope is narrower.
Billing must reach the financial endpoint
A product has not demonstrated billing because it can display ICD-10 suggestions or print a superbill. Follow one encounter through charge, claim, payer response, correction, patient responsibility, and payment.
Record which product handles:
- eligibility and payer enrollment;
- charge and code ownership;
- claim creation and clearinghouse submission;
- rejection, denial, and corrected claim;
- ERA and payment posting;
- statement, payment plan, and patient balance;
- reporting and reconciliation.
If these are the main problems, buy billing or RCM depth. Documentation software should not be stretched into that category.
Where Patient Square maps to the grid
Patient Square’s public Practice Copilot scope maps to several, but not all, rows:
| Grid row | Public Patient Square scope | Boundary |
|---|---|---|
| Clinical documentation | Structured SOAP, ICD-10 suggestions, prescription draft for review | Suggestions and draft are not autonomous coding or prescribing |
| Scheduling | Listed from Assist | Depth, self-booking, intake, and edge cases need an evaluation |
| Clinical record | AI Copilot EHR begins on Copilot | Public pages do not enumerate deep EHR submodules |
| Messaging | WhatsApp begins on Copilot | Exact workflow and consent behavior need proof |
| Front office | AI Receptionist and AI Follow-ups named on Autopilot | Module names do not establish every behavior |
| Portal | Not publicly listed | Do not assume one |
| Billing and RCM | Not a full US claims, clearinghouse, eligibility, or RCM system | Keep a dedicated workflow |
| Care management / population health | Not publicly listed | Do not infer from follow-up naming |
Current US annual monthly equivalents are $79 for Assist, $119 for Copilot, and $199 for Autopilot. Month-to-month rates are $99, $149, and $249. All plans list unlimited visits and notes.
Practice Copilot supports two record paths: use the Patient Square EHR from the Copilot tier or keep an existing EHR while Patient Square handles documentation and front-office workflows. Discovery should confirm the handoff for either path.
That scope is intentionally narrower than the phrase “patient management software” makes it sound. It can be a sensible purchase for a practice that needs ambient documentation, scheduling, or the bundled record. It should not be chosen on the assumption that it includes patient access, billing, or population management that the public pages do not list.
EHR-ready export (PDF · HL7 · FHIR) is a portability claim. It is not proof that another product will ingest every field or that Patient Square writes natively into every EHR.
Security follows the data flow
HHS explains that software sale alone does not create a business-associate relationship, but storing or accessing PHI for hosting or support can. Map every vendor and subprocess that receives PHI. Put required BAAs in place before access.
Patient Square is HIPAA compliant, and Business Associate Agreements are available. The practice still owns consent, access rules, device controls, retention, and its complete workflow.
The contract should identify:
- data types and permitted uses;
- roles, support access, and logs;
- retention and deletion for each data type;
- interface monitoring and incident ownership;
- export format, timing, cost, and termination behavior.
The more categories a suite covers, the more important that map becomes.
The one-week selection exercise
Assign one owner for the decision and one owner for each failing event. A clinician should validate the record and documentation path. Front desk staff should test scheduling and duplicate identities. The person who works claims should test the financial path. A patient or trained staff member should test any patient-facing workflow from a phone. Do not let the buyer who never uses a function certify it for everyone else.
Give the finalists the same short script. Create a patient, make and change an appointment, complete the clinical encounter, move the required information to the next system, then trace any financial or follow-up event to closure. Capture the screens, exception steps, ownership, and time required. The test is not a demand for a giant proof of concept. It is a way to surface the quiet manual work that an attractive feature grid does not show.
Then price only the systems that passed the required events. Include the modules, staff seats, transactions, training, data migration, interfaces, support, and exit terms. A lower subscription with a permanent retyping step can cost more than a higher tier. A broad platform with an unused billing or portal module can cost more too.
Buy the narrowest system that closes the gap
A clinic with a working EHR and a broken appointment line may need scheduling, not replacement. A practice with persistent payer rework needs billing depth, not a prettier patient list. A group building longitudinal programs needs care management, not a reminder module.
Use the six-category grid to route the problem. Use the source-of-truth worksheet to expose integration work. Then price seats, transactions, migration, interfaces, training, support, and exit for only the finalists in the right category.
The medical practice management guide maps operational modules. The patient portal guide handles the patient-facing layer.
Patient Square and your existing record system
Practice Copilot can use the bundled AI Copilot EHR from the Copilot tier, or work alongside an existing EHR. Neither path promises automatic filing or write-back into a third-party EHR.