Centralize PA across sites and specialties on Intergy without an EHR migration

Prior authorization automation for Greenway Intergy in multi-specialty groups and MSOs

TL;DR: Multi-specialty groups and MSOs on Greenway Intergy get the most from prior authorization automation when they centralize PA into one queue, apply payer rules the same way across every specialty and site, and let AI agents handle submission and follow-up so local staff only manage exceptions. The payoff is consistency: the same documentation standards, the same turnaround, and one view of every open auth across the organization, without forcing anyone onto a new EHR.

Why decentralized prior authorization breaks at scale

Prior authorization works tolerably at a single small practice because one or two experienced coordinators know every payer quirk by heart. Grow to five, ten, or twenty locations across several specialties, and that model falls apart.

In most MSOs and multi-specialty groups, PA still happens site by site. The orthopedic clinic has its own coordinator, the GI center has another, and the cardiology group inherited a third process from before the acquisition. Each one keeps its own notes, tracks status its own way, and handles the same payer differently.

The problems show up quickly:

  • Inconsistent documentation. One site sends a complete packet for a knee MRI, another sends a bare order and waits for the payer to ask for more.
  • Invisible backlogs. Leadership has no idea how many auths are open, how old they are, or which site is behind until procedures start getting cancelled.
  • Uneven denial rates. The same payer denies one location twice as often as another, and nobody can explain why.
  • Fragile staffing. When a site's only PA coordinator leaves, that site's auths stall for weeks.

The volume makes these gaps expensive. The AMA's 2024 physician survey found physicians average 39 prior authorizations per week. Multiply that across 100 or 200 providers and you're running thousands of auths a month, each one a chance for a delay or denial.

What a centralized PA model looks like on Intergy

Centralizing prior authorization doesn't mean moving everyone into one room. It means running one process with one set of rules and one queue, regardless of where the order originates.

A centralized model on Intergy usually has four parts:

One intake point. Every auth-sensitive order, from every site, lands in a single PA queue. In Intergy, that's typically a dedicated task type or work queue that all locations route to.

Shared payer rules. A single library defines which services need auth for which payers and what documentation each payer requires. Sites don't maintain their own versions.

A central team, organized by payer or specialty. Instead of one coordinator per site, a central team splits work by payer (one person owns the big commercial plans, another handles Medicaid managed care) or by specialty. Either way, expertise concentrates instead of scattering.

Standard status and write-back. Every auth records the same fields in Intergy: status, auth number, approved units, and date range. Schedulers at every site see the same information in the same place.

Groups that make this shift usually find they need fewer total PA staff, not more, because coordinators stop duplicating payer research and stop losing time to inconsistent handoffs. Centralization also makes automation much easier, since there's one workflow to automate instead of a dozen.

Keep a light local role at each site. Someone on-site still needs to answer patient questions, collect missing paperwork, and flag urgent cases, such as a same-week surgery added to the schedule. The central team owns the process; local staff own the patient relationship. Spelling out that split in writing avoids the most common failure, where sites assume the center has it and the center assumes the site does.

Which specialty prior authorizations are worth templating?

Multi-specialty groups deal with very different PA patterns, and that's exactly why templates matter. A standard packet for each high-volume auth type cuts pends and speeds up submission. These are the categories most groups template first.

Advanced imaging

MRI, CT, PET, and nuclear cardiology studies are some of the highest-volume auths in orthopedics, neurology, GI, and cardiology. Payers and radiology benefit managers usually want documentation of symptoms, duration, conservative treatment tried, and exam findings. A template that prompts for each item turns a frequent pend into a first-pass approval.

Biologics and infusions

Rheumatology, GI, dermatology, and oncology groups handle biologics and infusion drugs that often sit under the medical benefit. These auths typically need diagnosis confirmation, step-therapy history, lab results, and dosing. They also need re-authorization on a schedule, which makes tracking expiration dates critical.

Surgical procedures

Orthopedic, spine, GI endoscopy, and cardiology procedures need auths tied to a specific CPT code, site of service, and date. Changes in any of those can invalidate the approval. Templates should capture all three and flag when a scheduling change requires an update.

Specialty drugs under the pharmacy benefit

Some specialty medications run through medication ePA instead. Make sure your centralized process knows which path each drug takes so coordinators aren't duplicating work across channels.

How automation standardizes PA without an EHR migration

Many MSOs assume that standardizing operations means standardizing EHRs first. For prior authorization, that's rarely true. If your sites run Intergy, or a mix of Intergy and other systems after acquisitions, automation can sit on top and apply one process everywhere.

Prior authorization automation for Greenway Intergy works by reading orders and clinical documentation from each site's Intergy environment, checking them against your shared payer rules, assembling the payer-specific packet, and submitting through the payer's portal, ePA network, or fax. It then checks status daily and records the outcome back to the patient's account so local schedulers can see it.

For a multi-site organization, three benefits stand out:

  • Same rules everywhere. Every site's auths are checked against the same payer library and documentation templates, so quality no longer depends on which coordinator picked up the order.
  • One queue for leadership. Every open auth, across every location and specialty, is visible in one place with its status and age.
  • Exceptions routed centrally. Denials, pends, and peer-to-peer requests go to the right person on the central team with context attached.

The time savings are significant. The 2024 CAQH Index found providers spend about 24 minutes per prior auth by phone, fax, or email and 16 minutes through portals. Across thousands of auths a month, removing most of that time is the difference between hiring more coordinators and absorbing growth with the team you have.

Honey Health's Prior Authorization agent is built for this multi-site pattern. It applies one set of payer rules across every location, handles submission and follow-up across portals and fax, and routes exceptions to your central team, all without asking any site to switch EHRs. MSOs often roll it out alongside fax triage and referral intake, since those workflows feed the same central operations team.

How should an MSO roll out PA automation across sites?

Don't flip every location at once. A staged rollout proves the model and builds trust with site leaders who may be protective of their current process.

  1. Baseline first. Measure current auth volume, turnaround, and auth-related denials by site and specialty for at least a month. You'll need these numbers to prove the change worked.
  2. Build the payer library. Document requirements for your top payers and top 30 to 50 auth-sensitive services. This becomes the rulebook for both people and automation.
  3. Pilot one specialty at one or two sites. Advanced imaging in orthopedics or GI is a common starting point because volume is high and rules are well defined.
  4. Run supervised. Have the central team review automated submissions for the first few weeks and fix gaps in the templates.
  5. Expand by specialty, then by site. Add specialties one at a time with their templates approved before go-live.

Expect some pushback from sites that have run PA their own way for years. Involve each site's office manager early, show them the baseline data, and make the central team responsive. Sites accept centralization quickly once they see auths clearing faster than before.

What reporting should MSO leadership demand?

Centralized, automated PA should give leadership a level of visibility most groups have never had. Insist on these reports from day one:

  • PA volume by site, specialty, and payer, so you can staff and negotiate with real data.
  • Turnaround split into internal and payer time. Days from order to submission show your team's speed; days from submission to decision show the payer's.
  • Auth-related denials by site and payer. Differences between sites usually point to documentation gaps.
  • Open auths by age, highlighting anything close to its service date without a decision.
  • Expiring auths, especially for biologics and infusions that need re-authorization.

Review these monthly with site leaders, not just in the executive meeting. When an office manager sees their site's denial rate next to the group average, the conversation about documentation changes quickly.

The regulatory backdrop also makes this data more useful. Under the CMS Interoperability and Prior Authorization Final Rule, impacted payers must meet decision timeframes starting in 2026 (72 hours for expedited and seven calendar days for standard requests) and publish prior authorization metrics. With your own turnaround data by payer, you can hold payers to those timelines and spot the ones that miss them.

Frequently Asked Questions

Should an MSO centralize prior authorization?

For most MSOs with several sites or specialties, yes. Centralizing PA into one queue with shared payer rules improves consistency, gives leadership visibility, and reduces dependence on individual site coordinators. Local staff still handle patient communication and exceptions that need on-site context.

Can prior authorization be automated across multiple Intergy sites?

Yes. Automation can read orders and documentation from each site's Intergy environment, apply one set of payer rules, submit and track auths, and record outcomes back to each patient's account. Sites keep their EHR, while the PA process becomes consistent across the organization.

Which prior authorizations should a multi-specialty group automate first?

Start with high-volume, rules-driven categories such as advanced imaging in orthopedics, neurology, or GI. Biologics and infusions are a strong second phase because they also need tracking for re-authorization dates.

How many PA staff does a centralized model need?

It depends on volume, payer mix, and how much is automated. Most groups find centralization plus automation lets them handle more volume with the same or fewer coordinators, who shift from routine submission to exceptions, appeals, and peer-to-peer coordination.

What if our sites use different EHRs after acquisitions?

Prior authorization automation can run across mixed environments, reading from and recording to each site's EHR. That lets MSOs standardize PA operations now instead of waiting for an EHR consolidation that may be years away.

More of our Article
CLINIC TYPE
LOCATION
INTEGRATIONS
More of our Article and Stories