Patient Communication for Multi-Site Centricity Practices (2026)

The system your front desk logs into every morning stopped being a GE product in 2018. Centricity EMR is athenaFlow now. Centricity Practice Solution is athenaPractice.

Centricity Business became athenaIDX in 2020, though General Electric still holds the Centricity trademark, which is part of why the old name refuses to die.

Ownership changed hands three times in eight years. The confirmation call never moved. It is still a staffer with a headset, a printed schedule, and a stack of voicemails nobody returns.

Patient communication sits in its own layer, apart from the chart. You can replace that layer without opening an EHR project, and most groups on a legacy platform have simply never been told so.

The stakes are easy to measure. Atlas Medical Center brought no-shows down from 14.20% to 4.91% in three months, based on our internal data. Not one thing changed inside that practice's clinical system.

Multi-site groups feel the gap hardest. Three front desks build three habits. Nobody can tell whether the Tuesday patient at the north office was ever actually reached, or whether two staff called her on the same afternoon.

And if your group ever migrates off Centricity, a communication layer built outside the EHR moves with you instead of getting rebuilt from scratch.

The Legacy Gap: A Communication Stack Frozen at the Version You Bought

Practices that bought Centricity in the early 2010s built a routine around it, then stopped. Confirmations go out by phone. Intake happens on a clipboard. Secure messages route through a portal that a large share of patients never activated in the first place.

None of it is broken. It reflects what counted as normal in 2013.

Version drift keeps it in place. Support for athenaPractice and athenaFlow v19.X ended June 1, 2023, and many groups upgraded the clinical build while leaving every surrounding process alone. Upgrades touched the chart and stopped at the front desk door.

Ask a practice manager what happens when a patient texts the main office line. Usually the answer is that the line does not receive texts, and the message vanishes into a carrier void. Patients keep trying anyway.

Why Every Add-on Started to Feel Risky

Four owners in eight years explains a lot of caution. GE sold the ambulatory products to Virence Health, a Veritas Capital company, in 2018. Virence merged into athenahealth the following year. Bain Capital and Hellman & Friedman took athenahealth private in 2022.

Administrators watching that sequence learned a fair lesson: do not buy anything that only works if this one platform survives. So the texting proposal got tabled.

The intake project waited on clarity that never showed up. Front desk staff kept dialing through the same call list for another two years.

That caution is rational. It also has a price, and the price shows up in the schedule.

Multi-Site Turns 1 Gap into 4

Each location fills the gap its own way. One office calls two days out. Another calls the morning of, or not at all when the phones get busy. A third mails postcards for recalls because that is what the office manager set up in 2016.

A regional director cannot answer a basic question from that setup: how many patients did we reach this week? The data lives in four sets of habits and none of them write it down.

A Patient Communication Workflow That Runs Alongside Centricity

Reminders go out on a schedule you set, usually a week ahead, then two days out, then the morning of. The patient replies with a single character to confirm.

Anything else they type, a question about parking or a request to move to Thursday, lands in a shared inbox where staff answer by text.

Call volume drops as much as 50% once patients get a channel they actually use, based on our internal data. Staff productivity climbs about 30% alongside it.

The mechanic worth understanding is the reply path. A one-way reminder blast still forces the patient to phone you back. Two-way texting closes the loop inside the same thread, which is why the confirmation rate moves at all.

Intake, Payment, and Recall Without a Portal Login

Forms arrive as a text link. The patient fills them out on a phone in the parking lot, or the night before, and the front desk stops re-keying handwriting.

Balances go out the same way. A text-to-pay link on a $140 copay gets settled faster than a statement that takes nine days to arrive and another two weeks to get opened.

Recalls are the piece most legacy groups have quietly abandoned. Pulling a list of patients overdue past twelve months takes minutes. Calling all 400 of them takes weeks nobody has. A batch text goes out in one pass, and the replies come back to the same inbox.

Platform Independence is the Part that Matters at Renewal

The layer does not live inside Centricity. Your numbers, templates, saved replies, and full message history belong to the practice, not to the EHR vendor.

That matters at exactly one moment: the day leadership decides to migrate. Groups that built communication into the EHR rebuild it from zero. Groups that built it beside the EHR point the new system at the same layer and keep the patient threads intact.

Ask any vendor how their tool behaves the day you leave. The answer tells you what you are actually buying.

How Curogram Fits a Centricity Group

Curogram 2-Way Texting runs on a HIPAA-compliant number tied to each location. The north office and the south office keep separate identities. Staff still work from one queue.

Automated Appointment Reminders send on your cadence and post confirmations for the front desk to see. Patient Recalls handles the overdue list in batches. Online Forms sends intake by text link. Text-to-Pay collects balances in the same thread the patient already answers.

On integration scope, we would rather be plain than impressive. Curogram connects with a wide range of EHR and practice management systems. How deep that connection goes depends on your version, hosting setup, and available interface.

Ask us to confirm what is possible on your build before you plan around it. Sites that cannot get an interface still run the full communication layer next to the system, and that is how many legacy groups start.

A signed BAA covers the messaging. Patients text a real number instead of logging into a portal they gave up on years ago.

Conclusion: Start With the Layer You Can Change This Quarter

Centricity is not the problem. It charts, it bills, and it has done both for a decade at your practice. The part that aged out is the ring of manual work around it, and that ring was never really part of the EHR to begin with.

Groups on legacy platforms often wait for the migration decision before fixing anything. That wait costs real appointments. Atlas cut no-shows by roughly two thirds without touching a clinical system, and the same layer would have followed them anywhere.

Whatever your platform is called next year, patients will still confirm by text, fill out forms on a phone, and pay from a link. Build that layer where it can outlive the roadmap.

Book a demo and we will walk through what this looks like across your locations, including what is possible on your current Centricity version

Frequently Asked Questions