TL;DR: The fastest way to cut prior authorization turnaround in Greenway Intergy without adding staff is to start every auth at the moment the order is placed, not when the patient gets scheduled, standardize a documentation packet for each payer and service, and automate status checks so your team only touches exceptions. Process fixes come first and cost nothing. Prior authorization automation for Greenway Intergy then removes the manual submission and follow-up work that eats most of your coordinators' week.
Why prior auth turnaround is really a workflow problem
Most PA backlogs don't come from slow payers. They come from slow starts, incomplete packets, and nobody checking status until a patient calls.
Look at where the days actually go in a typical Intergy practice. The order sits for a day or two before anyone notices it needs an auth. A coordinator starts the request, realizes the last office note doesn't document failed conservative therapy, and sends a message to the provider. Two days later the note is addended. The auth goes out by portal. Then nobody checks again until the scheduler asks, four days later, whether the MRI is cleared.
That's eight days of turnaround, and the payer was responsible for maybe two of them.
The national numbers show how much is at stake. In the AMA's 2024 prior authorization survey, 93% of physicians said prior auth delays care, and practices reported spending about 13 hours a week per physician on PA work. The 2024 CAQH Index estimated that moving to electronic prior authorization would save medical providers and staff about 14 minutes per request.
The good news is that most of your delay is inside your own walls, which means you can fix it.
Step 1: Trigger the auth at the order, not at scheduling
The single biggest turnaround win is starting earlier. If your team only learns that a service needs an auth when the scheduler tries to book it, you've already lost days.
Set up a rule that every order for an auth-sensitive service creates a PA task the same day. In Intergy, that usually means:
- Defining your auth-sensitive list. Pull your top 30 to 50 CPT and HCPCS codes by volume and mark which ones commonly require auth for your main payers. Advanced imaging, surgical procedures, injections, infusions, and DME usually top the list.
- Creating a dedicated task type or queue for prior auth work, so PA requests don't get lost among general messages.
- Routing orders to that queue automatically or, at minimum, training providers and MAs to flag auth-sensitive orders before the patient leaves the room.
Practices that make this one change often take two to three days off average turnaround on their own. The work isn't faster. It just starts sooner.
Pair the trigger with an eligibility check. A surprising number of auths stall because the coverage on file is outdated, and the payer bounces the request after days in review. Verifying active coverage and the correct plan when the order is placed means the auth goes to the right payer the first time.
Step 2: Build payer-specific documentation packets
Incomplete documentation is the second-biggest source of delay. Every time a payer pends a request for more information, you add days and rework.
Fix it by building a short "packet checklist" for each common payer and service combination. For a lumbar MRI with a major commercial plan, the checklist might include:
- Duration and type of conservative therapy tried
- Neurological exam findings
- Red-flag symptoms, if any
- Prior imaging results
Keep these as one-page references your coordinators can open alongside the chart. Better yet, share them with providers so the office note documents what payers need the first time. A note that says "six weeks of PT without improvement, positive straight-leg raise" gets approved faster than one that says "back pain, ordering MRI."
Update the checklists whenever a payer changes its policy. Assign one person to own this. It's a small job that pays for itself in fewer pends.
Step 3: Use Intergy tasks and flags to route work cleanly
Even with good triggers and packets, PA work slows down when nobody can see the queue. Intergy's task and messaging tools can carry more of this load than many practices use them for.
A few routing practices that help:
- One queue, clear ownership. Every open auth should sit in a single queue with an assigned owner, not scattered across individual inboxes.
- Status categories. Use consistent labels like "needs documentation," "submitted," "pended," "approved," and "denied" so anyone can see where the backlog is.
- Due dates tied to service dates. If a procedure is in five days, the auth task should show that urgency.
- Scheduling holds. Train schedulers to check auth status before confirming a service. A visible flag on the patient account prevents unauthorized bookings.
This won't make individual auths faster, but it stops them from stalling. Most "lost" auths aren't lost. They're sitting in someone's inbox while that person is out.
Step 4: Add automation for submission and status checks
Once your process is clean, automation removes the parts of the job that are pure keystrokes. This is where you reclaim staff time instead of just reorganizing it.
The two highest-value steps to automate are submission and status follow-up. Submission is repetitive: log into a payer portal, re-key demographics and codes, attach notes, click through screens. The CAQH Index found providers spend about 16 minutes per auth on portals and 24 minutes by phone, fax, or email. Status follow-up is worse, because it repeats every few days until a decision arrives.
AI agents can do both. They read the order and documentation from Intergy, fill out the payer's portal or fax form, submit, and then check status daily. When a decision comes back, the agent records it and routes denials or pends to your team with the reason attached.
This is the job Honey Health's Prior Authorization agent handles for Intergy practices. It runs submissions and daily status checks across portals and fax so your coordinators spend their time on peer-to-peers, appeals, and urgent cases instead of portal logins. Some practices also add fax triage, because payer requests for more information often arrive by fax and sit unread.
The result is that turnaround drops for two reasons: requests go out the same day they're ready, and decisions get picked up the day they're issued instead of whenever someone remembers to check.
Roll automation out in stages. Start with your two or three highest-volume payers and one or two high-volume services, such as advanced imaging, and run it alongside your coordinators for a few weeks. Have staff spot-check submissions, compare turnaround against your baseline, and fix any gaps in the payer checklists before expanding. Most practices find that once the first payers are running cleanly, adding the next ones goes much faster because the documentation rules are already written down.
What does the CMS prior authorization rule change for Intergy practices?
The CMS Interoperability and Prior Authorization Final Rule will help, but it won't solve internal delays for you.
Starting in 2026, impacted payers (Medicare Advantage, Medicaid, CHIP, and ACA Marketplace plans) must return decisions within 72 hours for expedited requests and seven calendar days for standard ones. By January 2027, those payers need to support prior authorization APIs that let EHRs and other systems check requirements and submit electronically.
Three caveats matter for planning:
- Commercial employer plans aren't covered by these requirements, and they make up a big share of most practices' auth volume.
- API rollout will be uneven. Payers will meet deadlines at different speeds, and EHR and vendor support will follow.
- Payer speed doesn't fix your speed. A seven-day payer clock doesn't help if the request leaves your office on day five.
Fix your internal workflow now. When payer APIs mature, you'll be positioned to use them rather than scrambling.
Which metrics show whether turnaround is improving?
You can't improve what you don't measure, and most practices don't measure PA at all. Start with four numbers you can pull from Intergy tasks and auth records.
- Days from order to submission. This is your internal speed. Target same day or next day for routine auths.
- Days from submission to decision. This is mostly the payer's speed. Track it by payer to spot the slow ones.
- Auths completed per coordinator per day. Your productivity measure. It should rise as automation takes over submission and status checks.
- Denials and reschedules tied to missing or expired auths. This is your quality measure, and it connects PA directly to revenue.
Review these monthly. When order-to-submission time drops but submission-to-decision time doesn't, you know the remaining delay is on the payer side and you can escalate with specific data. When denials tied to auths drop, you have a clean revenue story for your partners.
A realistic goal for a practice that adopts all four steps: order-to-submission under one business day for most auths, and a coordinator team that handles growing volume without new hires.
Frequently Asked Questions
What is a good prior authorization turnaround time?
For routine requests, aim to submit within one business day of the order. Total turnaround then depends on the payer: CMS now requires impacted payers to decide standard requests within seven calendar days and expedited ones within 72 hours. Commercial plans vary, so track turnaround by payer.
How can I reduce prior authorization delays without hiring?
Start auths at the order instead of at scheduling, build payer-specific documentation checklists, route all PA work through one visible queue, and automate submission and status checks. These changes remove most internal delay and free coordinators for exceptions rather than routine keystrokes.
Does Greenway Intergy track prior authorization status?
Intergy can store auth numbers, approved units, and date ranges on the patient account, and staff can track work through tasks. Checking status with payers usually still happens in payer portals or by phone, which is the step most practices automate first.
What causes most prior authorization delays?
Late starts, incomplete documentation that triggers payer pends, and infrequent status checks cause most of the delay practices control. Payer review time matters too, but it's usually a smaller share of total turnaround than the time a request spends waiting inside the practice.
How much staff time does prior authorization automation save?
It depends on volume and payer mix. The 2024 CAQH Index estimated about 14 minutes saved per request by moving to electronic transactions, and automating status follow-up removes repeated portal logins and calls on top of that. Measure your own baseline before and after a pilot.

