Prior authorization automation for dermatology practices works by pulling the step-therapy history, severity scores, and lab results payers require for biologics and specialty drugs directly from the chart, packaging that evidence into a payer-specific request, submitting it, and tracking the case until a decision comes back. It doesn't replace your staff for peer-to-peer calls or appeals — it clears the paperwork so a person only gets involved when judgment actually matters.
Why Dermatology Generates So Much Prior Auth Work
Ask any office manager at a derm practice which payer task eats the most staff time, and prior authorization wins without a fight. Dermatology sits at an unusual intersection: it prescribes some of the most expensive drugs in medicine (biologics for psoriasis, eczema, and hidradenitis suppurativa), it bills procedures that payers love to second-guess (Mohs surgery, excisions, light therapy), and it constantly runs into "is this cosmetic or medical?" denials that other specialties rarely see.
Biologics are the biggest driver. A single systemic for moderate-to-severe plaque psoriasis can run tens of thousands of dollars a year, and payers gate nearly all of them behind prior auth. Coverage reviews have found that 87% of patients prescribed adalimumab for psoriasis needed a prior authorization before the prescription could be filled, and that share is similar across the other biologics dermatologists prescribe most (AJMC).
What does that volume actually cost a practice? One analysis of dermatology PA workflows put the annual cost of denied or delayed prior authorizations at roughly $83,200 per practice, once you count staff hours, delayed revenue, and the phototherapy and biologic starts that get pushed back weeks while paperwork sits in a queue (HCPLive). Why does the cost run that high? Because dermatology PA isn't a single form — it's a packet: chart notes, photos, lab values, and a step-therapy history, all formatted the way a specific payer wants to see it.
And the denial letters that come back often aren't much help. A review of dermatology prior authorization denials found that 75% didn't name an actual decision-maker, and 41% gave no explanation of what step therapy or alternative treatment the payer wanted documented instead. That's the core problem prior authorization automation for dermatology practices is built to solve: making sure the right documentation goes out the first time, instead of guessing what a vague denial letter meant.
What Payers Actually Want to See Before Approving a Biologic
Every biologic and most specialty topicals get evaluated against the same basic question: has this patient tried and failed the cheaper stuff first? That's step therapy, and it's the backbone of nearly every derm PA denial.
Payers typically want four things in the packet. First, step therapy history — documented trials (and failures, intolerances, or contraindications) of topical steroids, topical calcineurin inhibitors, and sometimes phototherapy, before they'll approve a systemic biologic. Second, a severity measurement — usually body surface area (BSA) percentage or a validated score like PASI for psoriasis, since "moderate to severe" is a defined threshold, not a feeling. Third, baseline labs — a lot of payers want a TB screen, hepatitis panel, or CBC on file before authorizing an immunosuppressive biologic, because they're checking for contraindications, not just medical necessity. Fourth, prior treatment history from other prescribers, which matters when a patient switches practices or insurance plans and the new payer has no record of what already failed.
Here's where it gets messy: what happens when BSA isn't sitting in a structured field anywhere in the chart? A lot of EHRs let dermatologists free-text severity into a visit note instead of a discrete field, which means the number a payer needs is technically documented but not in a form a claims system can read. That's a big reason so many derm PAs get denied on the first pass and have to be resubmitted — not because the patient doesn't qualify, but because the qualifying data was never extracted into the request.
How Prior Authorization Automation Actually Works, Step by Step
Strip away the marketing language and prior authorization automation for dermatology practices comes down to four jobs, done in sequence, for every request.
Clinical data extraction. The system reads the chart — visit notes, medication history, lab results, photos where relevant — and pulls out the specific data points a payer's policy requires: step therapy trials, BSA or PASI, lab dates and values, diagnosis codes. This is the part that has to handle unstructured text, because so much of this lives in free-text notes rather than dropdown fields.
Payer-specific rule matching. Every payer (and often every plan within a payer) has its own medical necessity criteria for the same drug. What Cigna wants documented for Dupixent isn't identical to what a regional Medicaid MCO wants. Automation maps the extracted clinical data against the specific payer's current policy, so the request goes out matched to what that reviewer is actually checking against — not a generic template.
Submission. Once the packet is assembled, it goes out through whatever channel that payer accepts — a payer portal, a fax, or an X12 278 electronic transaction where the payer supports one. As of the 2024 CAQH Index, only about 35% of medical prior authorizations nationally were being submitted fully electronically, with the rest going through portals, phone, or fax (CAQH) — which is exactly why an automation layer that can format for fax and portal submissions matters as much as one that handles electronic transactions.
Status tracking and follow-up. After submission, someone has to check whether the payer needs more information, whether a determination came back, and whether a deadline is approaching. Automation logs the request, watches for a response, and flags it for staff the moment a payer asks a question or issues a decision — instead of a biller having to call the payer to check.
Honey Health's Prior Authorization agent runs this exact workflow for dermatology practices: pulling step-therapy and severity documentation out of the EHR, generating the payer-specific request, submitting it, and tracking it through to a decision, so staff spend their time on the cases that actually need a phone call instead of the ones that just need a form filled out correctly.
Specialty Pharmacy Coordination and Where a Human Still Has to Step In
Biologics don't just need an approved PA — they need a specialty pharmacy to actually dispense them, and that pharmacy runs its own intake process in parallel with the payer's. Hub programs for drugs like Cosentyx or Skyrizi collect their own paperwork, verify benefits, and often run copay assistance enrollment at the same time the payer is reviewing the medical necessity request. If the PA status isn't synced with what the specialty pharmacy's hub is doing, patients get stuck in a gap where the payer approved the drug three days ago but nobody told the pharmacy, or the hub is waiting on a document the practice already sent to the payer.
Good automation keeps those two tracks connected — flagging when a PA decision lands so staff (or the patient) can move the specialty pharmacy step forward immediately, instead of losing another few days to a handoff nobody owned. This is one of the quieter but most practical benefits of prior authorization automation for dermatology practices: it isn't just about getting the payer to say yes, it's about making sure the drug actually reaches the patient once the answer comes back.
What automation doesn't do is argue your case on the phone. Peer-to-peer review — where the payer's medical director wants to discuss the clinical reasoning directly with the prescribing dermatologist — is a clinical judgment call, and it stays a human conversation. Same with formal appeals after a denial: a person has to build the argument, cite the specific policy language, and often get the physician to add clinical detail a form can't capture. Automation's job in both cases is upstream — getting a cleaner packet out the door in the first place so fewer cases end up needing a peer-to-peer at all, and handing appeals staff an organized file instead of a blank page when one is unavoidable.
What Changes Under the New CMS Prior Authorization Rule
Starting January 1, 2026, CMS's Interoperability and Prior Authorization final rule (CMS-0057-F) requires Medicare Advantage plans, state Medicaid and CHIP fee-for-service and managed care programs, and ACA marketplace plans to issue prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests (CMS). Those same payers also have to start publicly reporting PA metrics and, by January 2027, support electronic prior authorization through standardized APIs.
Does this fix dermatology's PA problem? Only partly. The rule doesn't cover commercial insurance the same way — and a large share of derm biologic prescriptions run through employer-sponsored commercial plans that aren't bound by these timelines. Faster decisions from Medicare Advantage and Medicaid plans will help some patients, but step-therapy documentation and payer-specific packaging still matter just as much for the commercial book of business the rule doesn't touch. If anything, tighter decision windows raise the cost of a sloppy first submission: a payer with 7 days to decide is more likely to deny for missing documentation than to chase you down for it, since asking for more information often resets their clock.
Frequently Asked Questions
How long does dermatology prior authorization usually take to get approved?
It depends heavily on the payer and the drug, but derm practices commonly see anywhere from a few days to several weeks for biologics, especially on the first submission if documentation is incomplete. Clinicians and staff spend an average of 39 prior authorizations per week and roughly 13 hours on the process across specialties, according to a 2024 physician survey, and incomplete packets are the single biggest reason cases drag past that.
Can prior authorization automation handle cosmetic-adjacent denials, like blepharoplasty or scar revision?
Yes, in the sense that it can assemble and submit the medical-necessity documentation payers ask for — visual field testing, functional impairment notes, photos — that separates a covered procedure from a cosmetic one. But whether the payer agrees the case is medical rather than cosmetic is still a clinical and often an appeals question, not something a submission tool decides.
Does prior authorization automation work for Mohs surgery authorizations?
It can extract and submit the pathology, lesion characteristics, and prior treatment documentation many payers require before authorizing Mohs. Since Mohs requirements vary a lot by payer and plan, the payer-specific rule matching step matters more here than almost anywhere else in dermatology.
What happens when a prior authorization automation system still gets a denial back?
It should flag the denial immediately, pull the payer's stated reason, and hand staff an organized file — the original documentation, the payer's policy criteria, and what's missing — so they can either resubmit with the gap filled or start an appeal. Automation shortens the time between a denial landing and someone acting on it; it doesn't file the appeal argument itself.
Does automating prior authorization mean a practice needs fewer PA staff?
Usually it means existing staff stop spending most of their week on data entry and status-checking and spend it instead on the harder cases — peer-to-peer prep, appeals, and patients stuck in a payer-specific edge case. Given that 92% of medical group practices report hiring or reassigning staff specifically to keep up with PA volume (MGMA), most practices redirect that capacity rather than cut it.
Is prior authorization automation secure enough to handle protected health information?
Any system pulling clinical data out of an EHR to build a PA request is handling PHI, so it needs to run under the same HIPAA safeguards — encryption, access controls, audit logs, a signed business associate agreement — as any other tool touching patient records. That's a baseline requirement to check before connecting anything to your EHR, not an optional add-on.
