TL;DR: Prior authorization status tracking in a pulmonology practice is the work of monitoring every submitted PA, whether for a biologic, CPAP, a sleep study, or a PFT-dependent procedure, across payer portals, faxed determinations, and phone queues until it resolves to approved, denied, or pended for more information. Good tracking means one queue, an owner and next-action date on every open request, and same-day response when a payer asks for records. A pulmonology prior auth status tracking and follow-up tool automates the checking and alerting so staff only touch exceptions.
What is prior authorization status tracking?
Prior authorization status tracking is everything that happens after you hit "submit." Submission gets most of the attention because it's the visible, form-filling part of the job. Tracking is quieter, and it's where pulmonology PAs actually go to die.
A submitted request can land in one of five states: approved, denied, pended for additional information, partially approved (fewer units or a shorter duration than requested), or simply not received. That last one is more common than payers like to admit. A fax that never got indexed or a portal upload that timed out looks identical to a request still under review until someone checks.
Tracking is the discipline of knowing which of those five states every open request is in, today, and acting on it before the clock runs out. That clock matters more than it used to. Under the CMS Interoperability and Prior Authorization final rule, Medicare Advantage, Medicaid, and CHIP plans must return decisions within 72 hours for expedited requests and 7 calendar days for standard ones as of January 1, 2026. Commercial plans aren't bound by the same rule, so your queue now runs on two different speeds.
The scale is what turns tracking into a staffing problem. The AMA's physician survey found practices complete about 39 prior authorizations per physician per week, and physicians and staff spend roughly 13 hours a week on them. Every one of those requests needs to be watched until it closes.
What does a pulmonology PA go through after submission?
Pulmonology carries an unusually mixed PA load, and each category behaves differently once it's submitted.
- Biologics for severe asthma and COPD. Drugs like dupilumab, tezepelumab, mepolizumab, benralizumab, and omalizumab usually run through the pharmacy benefit, often with a specialty pharmacy or manufacturer hub in the loop. Status can live in three places at once.
- CPAP, BiPAP, and home oxygen. These are DME authorizations, frequently handled by a DME supplier rather than your office, which means your staff may be tracking someone else's submission.
- Sleep studies. Home sleep tests and in-lab polysomnography are routinely managed by radiology benefit managers or utilization management vendors, each with its own portal.
- Imaging and procedures. Chest CT, bronchoscopy, and EBUS often go through yet another benefit manager.
- Pulmonary rehab and PFT-dependent services. These tend to get pended for documentation, usually spirometry values or exacerbation history.
Recent data shows how long that tail can get. A retrospective review of 326 pediatric biologic prescriptions presented at the 2026 ACAAI meeting and reported by Healio found a mean of 32.7 days from prescription to PA approval, a median of 13 days, a 39.3% denial rate, and further steps after submission in 28.8% of prescriptions. That's a pediatric allergy population, not adult pulmonology, but the shape is familiar to anyone running a biologic clinic: a long, uneven tail that only shrinks if someone keeps pushing.
Where does PA status actually live?
There's no single place to look. That's the core problem.
On any given morning, a pulmonology PA coordinator might need to check:
- Payer portals, often four to eight of them, each with its own login, layout, and session timeout.
- The fax inbox, where determination letters, requests for additional information, and peer-to-peer offers arrive as unindexed PDFs.
- Specialty pharmacy and hub updates, which come by phone, fax, or a separate web portal.
- Benefit manager portals for sleep and imaging.
- Phone queues and IVR lines, for payers whose portals don't show real-time status or for requests that never appeared online.
- The EHR, which usually knows nothing about any of this until someone types it in.
Each source updates on its own schedule. A portal may show "in review" while a denial letter already sits in your fax queue. A hub may have approved a bridge supply while the payer is still reviewing the PA. If your tracking only watches one channel, you'll miss changes that show up in the others.
Why spreadsheet tracking breaks in pulmonology
Most pulmonology groups start with a spreadsheet, a shared Outlook folder, or a whiteboard. It works until it doesn't, and the break point comes earlier than people expect.
The math is simple. Take a five-physician pulmonology group at the AMA average of 39 PAs per physician per week. That's close to 200 new requests a week. If the average request stays open 10 business days, you're carrying something like 400 open PAs at any moment. Checking each one twice a week across multiple portals is hundreds of portal logins, fax reviews, and phone calls every week, before anyone submits a new request.
Spreadsheets fail in predictable ways at that volume:
- No owner. A row without a named person and a next-action date doesn't get followed up.
- Stale status. The sheet says "submitted" because nobody updated it after the denial fax came in.
- Lost pends. Requests for additional information carry short response windows. Miss one and the payer closes the case, and you start over.
- Expired approvals. An approval for a sleep study with a 60-day window quietly expires because scheduling didn't know about it.
- No reauth calendar. Biologic approvals typically run 6 or 12 months. Without a reminder, the reauth surfaces when the pharmacy rejects a refill.
It's also getting harder, not easier. In a September 2026 MGMA Stat poll, 44% of practice leaders said payer PA turnaround had gotten slower compared with 2025, 40% said it was about the same, and only 7% said it was faster.
What should a pulmonology prior auth status tracking and follow-up tool do?
A tracking tool earns its keep by doing the checking so your staff can do the deciding. When you evaluate one, these are the capabilities that matter in pulmonology.
A single queue across every channel
Every open PA, whether drug, DME, sleep, imaging, or procedure, should live in one list with its current status, payer, request type, owner, and next-action date. If the tool only covers pharmacy-benefit drugs, you'll still be running a spreadsheet for everything else.
Automated status checks
The tool should check payer portals on a schedule, read incoming fax determinations, and update status without a human logging in. For payers that only answer by phone, look for automated call handling or at least a structured call task.
Alerts on the things that expire
Requests for additional information, peer-to-peer offers, partial approvals, and approvals with service windows should trigger alerts with the deadline attached. These are the events that turn a solvable PA into a lost one.
Write-back to the EHR
Approval numbers, authorized units, and date ranges belong on the patient's chart and the scheduled appointment. If status lives only in the tracking tool, your front desk and billers are still guessing.
Reporting by payer and request type
You want to see which payers pend the most, which request types take longest, and where denials cluster. That's how a pulmonology group decides whether a payer's biologic criteria need a documentation template or a contract conversation.
How AI agents handle status tracking and follow-up
The newest category of tools uses AI agents to do the work a PA coordinator would do between submissions: log into portals, read faxes, interpret determination letters, and decide what happens next.
In practice, an agent-based approach looks like this. The agent checks every open request on a cadence tied to the payer's expected turnaround. When a determination arrives, it reads the letter, updates the status, and writes the approval details or denial reason back to the EHR. When a payer pends for information, the agent pulls the requested records, such as the latest spirometry, eosinophil count, or exacerbation history, assembles the response, and routes it to a human for sign-off when judgment is needed.
Honey Health's Prior Authorization agent follows this pattern, working alongside the EHR rather than replacing it and handling submission, status checks, and follow-up in one flow. The same platform's fax triage agent reads incoming determination letters so they don't sit unindexed.
Be honest with yourself about the limits. Peer-to-peer reviews still need a physician on the phone. Denials based on medical necessity still need a clinician to decide whether to appeal. Payers that change portal layouts without notice will occasionally break automated checks until they're fixed. The goal isn't zero human touches; it's making sure humans only touch the requests that need judgment.
Frequently Asked Questions
How often should a pulmonology practice check prior authorization status?
For Medicare Advantage, Medicaid, and CHIP plans, check at 72 hours for expedited and around day 7 for standard requests, since those are the federal decision windows. For commercial payers, check 2 to 3 business days after submission and then twice a week until resolved. Biologic and DME requests often need more frequent checks because pends are common.
What's the difference between submitting a PA and tracking it?
Submission is assembling and sending the request with supporting documentation. Tracking is monitoring that request until it resolves, responding to requests for more information, catching denials quickly enough to appeal, and recording approval details where scheduling and billing can see them. Most lost PAs fail during tracking, not submission.
Why do pulmonology PAs get pended so often?
Pulmonology criteria lean heavily on specific clinical data: FEV1 and other spirometry values, blood eosinophil counts, documented exacerbations, step therapy on inhaled corticosteroids and long-acting bronchodilators, and sleep study results. If any one is missing or outdated in the submission, payers commonly pend the request instead of approving it.
Do I need to track DME authorizations if a supplier submits them?
Yes, at least at the status level. If a CPAP or oxygen authorization stalls at the supplier, your patient experiences that as your practice's delay. A shared queue that shows supplier-submitted requests alongside your own gives staff a reason to call before the patient does.
Can EHRs track prior authorization status on their own?
Some EHRs offer PA work queues, and a few support electronic PA for pharmacy-benefit drugs. Few track status across medical-benefit portals, benefit managers, fax determinations, and phone-only payers. Most pulmonology groups need a tracking layer that pulls from those channels and writes results back into the EHR.
What happens to PA tracking when payer APIs arrive in 2027?
Covered federal-program payers are expected to offer FHIR-based prior authorization APIs starting in 2027, which should make status checks faster for those plans. Commercial plans, benefit managers, and specialty pharmacies will still use portals, fax, and phone for some time, so multi-channel tracking will stay necessary.

