What Intergy covers, what it doesn't, and the five steps of an automated auth

How does prior authorization automation work for practices on Greenway Intergy?

TL;DR: Prior authorization automation for Greenway Intergy works by having software read the order and supporting chart data from Intergy, check whether the payer requires an auth, assemble the clinical packet, submit it through the payer's portal, ePA network, or fax, and then track status until a decision comes back and gets recorded on the patient's account. Intergy's e-prescribing workflow can cover many medication authorizations, but procedure, imaging, and DME auths still run through portals, phones, and fax. That's the gap automation fills, with staff handling only the exceptions.

Why prior authorization is still so manual for Intergy practices

Prior authorization is the process of getting a payer's approval before a service, drug, or device is delivered. For most Intergy practices, it's also one of the most stubborn manual workflows left in the building.

The volume is hard to overstate. In the AMA's 2024 prior authorization physician survey, physicians reported completing an average of 39 prior authorizations per week, and physicians and their staff spent about 13 hours a week on them. Ninety-three percent said prior auth delays patient care.

The reason it stays manual is that the work lives in many places at once. The order is in Intergy. The clinical justification is spread across notes, imaging reports, and outside records. The payer's requirements live on a portal, a PDF policy, or a phone tree. And the submission might go through any of those channels depending on the payer and the service.

The 2024 CAQH Index found that only 35% of medical prior authorizations were fully electronic. Providers reported spending about 24 minutes per request by phone, fax, or email, and 16 minutes using a payer portal. Multiply that by a few hundred auths a month and you've found where your front office's week goes.

What Intergy handles natively, and what it doesn't

Intergy gives you a solid foundation, but it doesn't run prior authorization end to end on its own. Knowing where the line sits helps you decide what to automate.

What Intergy typically covers:

  • Medication ePA through e-prescribing. For many prescription drugs, the e-prescribing connection can surface PA requirements and support electronic submission, depending on your configuration and the payer.
  • Recording the authorization. Auth numbers, approved units, and date ranges can be stored against the patient and visit so billing can attach them to claims.
  • Tasks and routing. Staff can use Intergy's task and messaging tools to assign PA work and follow up.

What usually falls outside Intergy:

  • Procedure and surgical auths, which most payers handle through their own portals or utilization management vendors.
  • Advanced imaging (MRI, CT, PET), often managed by radiology benefit managers with separate portals and clinical criteria.
  • DME and specialty drugs under the medical benefit, such as infusions and injectables, which frequently need fax packets or portal forms.
  • Status follow-up, which still means logging into portals or calling payers every few days.

That second list is where staff hours disappear. It's also where automation does the most good.

How does prior authorization automation work, step by step?

Most prior authorization automation for Greenway Intergy follows the same five-step pattern. The tools differ in how much they handle on their own, but the workflow underneath is consistent.

1. Requirement check

When a provider places an order or a service gets scheduled, the system reads the CPT or HCPCS code, the diagnosis, the patient's plan, and the site of service. It then checks the payer's rules to determine whether an auth is required. This step alone saves time, because staff often submit auths that weren't needed or miss ones that were.

2. Clinical data pull

If an auth is needed, the system gathers the supporting documentation from Intergy: recent progress notes, prior treatments tried, imaging results, labs, and relevant history. Good automation pulls only what the payer's criteria ask for, rather than dumping the whole chart.

3. Packet assembly

The clinical data gets mapped to the payer's specific form or questionnaire. For a lumbar MRI, that might mean documenting six weeks of conservative therapy and neurological findings. For a biologic, it might mean step-therapy history.

4. Submission

The packet goes out through whatever channel the payer accepts: portal, ePA network, or fax. This is where older tools stop working. An AI agent can log into payer portals, complete forms, and upload attachments the way a person would.

5. Status tracking and write-back

The system checks status on a schedule, captures the decision, and writes the auth number, approved units, and dates back to the patient's record in Intergy. Denials and pend requests get routed to staff with the reason attached.

Where humans stay in the loop

Automation doesn't remove people from prior authorization. It changes what they spend their time on.

Some cases need human judgment, and any honest vendor will tell you so:

  • Peer-to-peer reviews. When a payer wants a physician-to-physician conversation, that stays with your provider. Automation can schedule it and prep the case summary.
  • Medical necessity gray areas. If the chart doesn't clearly meet the payer's criteria, a clinician needs to decide whether to add documentation, change the order, or appeal.
  • Urgent and same-day cases. Expedited requests often need a phone call to move fast enough.
  • Unusual payers. Small regional plans or out-of-network payers with idiosyncratic processes may not be worth automating at first.

In practice, a well-run automated workflow means staff touch maybe a fifth to a third of auths instead of all of them. Your PA coordinators become exception handlers and appeal writers, which is a better use of their experience than retyping chart notes into portals.

It's also worth setting expectations with providers. Automation won't make payers approve things they would otherwise deny. It makes sure the right documentation goes out the first time, which reduces avoidable denials and pends, but the payer's criteria still decide the outcome.

Why write-back into Intergy matters more than submission

Most practices evaluate prior authorization tools on how they submit. The bigger operational win is often what happens after the decision comes back.

When auth data lives in a separate system or a spreadsheet, three things go wrong. Schedulers book procedures before the auth is approved. Billers send claims without the auth number attached. And when a patient's visit slides past the approved date range, nobody notices until the denial arrives.

Writing the decision back to Intergy fixes all three. With approved status, auth numbers, units, and date ranges recorded on the patient's account, your schedulers can see at a glance whether a service is cleared. Your billing team can attach auth details to the claim without hunting. And reports can flag auths nearing expiration before they become a problem.

This is also how you measure whether automation is working. If decisions write back consistently, you can track days from order to approval, auth-related denials, and cancelled procedures directly from Intergy data.

What to look for in a prior auth automation tool for Intergy

Not every tool fits an Intergy environment equally well. A few questions sort the options quickly.

  • Does it cover more than medications? If it only does drug ePA, it duplicates what you may already have through e-prescribing. Procedure and imaging coverage is where the value is.
  • Which submission channels does it handle? Portal, fax, and ePA together. Most practices have payers across all three.
  • How does it connect to Intergy? Ask specifically how it reads orders and clinical documents, and how it writes decisions back.
  • What happens on exceptions? You want denials and pends routed to a named queue with the reason, not buried in a log.
  • Is it HIPAA-compliant and BAA-ready? Any vendor touching PHI should sign a business associate agreement and explain its security controls plainly.

Before you sign, agree on how you'll judge a pilot. Pick your three or four highest-volume payers and your most common auth types, record a baseline for days from order to decision and staff minutes per auth, and compare after 60 days. A vendor that's confident in its workflow will welcome that test. One that wants to skip it is telling you something.

This is the category Honey Health's Prior Authorization agent is built for. It works alongside Intergy rather than replacing it: reading orders and clinical documents, checking payer requirements, submitting through portals and fax, following up on status, and recording outcomes so your staff only handle the cases that need a person. Practices often pair it with fax triage, since many payer decisions and requests for more information still arrive by fax.

How the regulatory picture is changing

The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) is pushing payers toward faster, more electronic prior auth. Beginning in 2026, impacted payers (Medicare Advantage, Medicaid, CHIP, and Marketplace plans) must send decisions within 72 hours for expedited requests and seven calendar days for standard ones. By January 2027, they must stand up prior authorization APIs.

That's good news, but it won't fix your workflow on its own. Commercial plans outside the rule's scope still run on portals and fax. API adoption will roll out unevenly. And faster payer decisions don't help if your team takes days to submit in the first place.

Automation that works across today's channels gives you the benefit now and positions you to use payer APIs as they come online.

Frequently Asked Questions

Does Greenway Intergy have built-in prior authorization?

Intergy supports parts of the workflow, including medication ePA through e-prescribing in many cases, storing auth details on the patient account, and routing work through tasks. Procedure, imaging, and DME auths typically still require payer portals, phone calls, or fax, which is where most practices add automation or outsourced support.

Can prior authorization be fully automated?

Most of the routine work can be automated: checking requirements, gathering documentation, submitting, and tracking status. Peer-to-peer reviews, medical necessity judgment calls, and some urgent cases still need people. Most practices aim to have staff handle exceptions rather than every request.

How long does it take to set up prior auth automation with Intergy?

Timelines vary by vendor and scope, but many practices start with a pilot covering their highest-volume payers and services within a few weeks. Expanding to more payers, specialties, and locations usually happens over the following months.

Will automation reduce prior authorization denials?

It reduces avoidable denials caused by missing documentation, wrong forms, or expired auths, because the right information goes out the first time and approvals are tracked. It won't change a payer's clinical criteria, so denials based on medical necessity still need clinical review and appeals.

Is prior authorization automation HIPAA-compliant?

It should be. Any vendor that accesses patient data on your behalf must sign a business associate agreement and maintain HIPAA safeguards. Ask vendors to explain their security controls, audit logging, and data retention policies before you sign.

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