Healthie is one of the best API-first EHRs on the market. Its GraphQL API covers the entire platform, the same one Healthie's own developers build the product on, which is why so many digital health companies run their whole stack on it. 

Prior authorization is one of the few workflows it leaves to you. Pharmacy-benefit PAs run through a separate e-prescribing add-on. Medical-benefit PAs are, by design, a phone call to the payer and a number typed into a field.

This guide covers what Healthie gives you natively, then it assesses four options for handling prior authorizations.

How Prior Authorization Works in Healthie

Healthie runs two completely separate PA paths that never touch each other. Most confusion about "prior authorization in Healthie" comes from not knowing which one you are in.

Pharmacy-Benefit PAs Run Through DoseSpot

Healthie offers e-prescribing as an add-on integration with DoseSpot and Surescripts, and ePA is a feature of that integration rather than of Healthie itself. Patient coverage details populate automatically from Surescripts where available, and formulary data flags whether a medication will require PA.

In the enhanced DoseSpot experience, a medication needing authorization carries a Prior Auth Required status. Selecting it prompts Initiate Prior Auth for Selected, you check the EPA box, and the request appears in a Prior Authorizations tab inside Tasks where you can review details, check status, and read the history log.

When the payer wants more information, the request flips to Action Required, and a clinician has to upload supporting documents or complete an e-form before the medication moves back to Pending Prescriptions. Partial denials get resolved by marking the request cancelled or denied.

Everything upstream is a few clicks; everything downstream is a person reading a chart for evidence of step therapy or documented comorbidities and typing it into a payer's question set.

Medical-Benefit PAs Are Manual by Design

If you are authorizing a service rather than a prescription, Healthie does have the capability to help you obtain it. The official instruction is to contact the insurance payer directly, then record the authorization number under Client Profile > Insurance > Edit Eligibility so it flows into Box 23 on the claim.

Healthie's Insurance Eligibility Tracker stores the useful surrounding detail: the authorization number, visits approved and used, and benefit start and end dates. It is connected to the calendar, so visits remaining update automatically as appointments are scheduled and occur.

For behavioral health and nutrition practices on Healthie, where authorizations are usually visit-count based and need periodic renewal, this is the kind of workflow that consumes an admin's week.

The 4 Ways to Handle Prior Authorizations on Healthie

Option 1: DoseSpot ePA Inside the E-Rx Add-On

If your prescribers are not on the E-Rx add-on, or ePA is not enabled on their DoseSpot clinician role, fixing that is a great first step. Electronic submission through the CoverMyMeds and Surescripts networks removes fax and phone from the front half of the process. Healthie passes through DoseSpot's cost at $40 per month per prescribing clinician, with no charge for proxy users.

Best for: Every Healthie organization that prescribes.

Where it is limited: It only transmits and does not complete. Staff answer every question set, monitor the Prior Authorizations tab manually, and own every denial. There is no appeal workflow, and ePA is only available for patients with pre-populated formulary information in DoseSpot. Delegation is also capped: proxy users can add and edit prescriptions but cannot send them, so a prescriber stays in the loop on every request.

Option 2: Manual PA With the Eligibility Tracker

For medical-benefit authorizations this is less an option than the only native path. Call the payer, obtain the number, log it against the client, let it populate Box 23, and set a reminder before it expires.

Best for: Low-volume practices, and any organization with visit-based authorizations that renew predictably. Also the correct baseline for medical-benefit volume regardless of what else you adopt.

Where it stops: Everything about it is linear with volume. But the industry has not solved this side either. The AMA's 2025 survey found phone is still the most commonly used method for completing medical-service PAs, and only about 40% of medical PA transactions are fully electronic nationally. This is the industry norm, not a Healthie-specific failure.

Option 3: Add People or Outsource Them

Many Healthie organizations hire a dedicated PA coordinator or contract a third-party authorization service, and see a real improvement, because specialization reduces denials. A staff member who has seen the same payer-drug combination fifty times fills the form correctly the first time.

Best for: Organizations with steady, predictable volume in a narrow set of drugs, and teams that want improvement without an integration project.

Where it is limited: Cost scales one-for-one with patient growth, which is the wrong shape for a virtual clinic trying to grow 3x a year. Outsourced services also sit outside Healthie, so you lose status visibility inside the chart and inherit someone else's queue times.

Option 4: API-Based Automation (Develop Health)

Because Healthie exposes the same GraphQL API its own developers use, covering EHR, prescribing, and billing workflows, it is a natural fit for automation platforms that connect over an API rather than requiring a native EHR install. 

Develop Health automates the full pharmacy-benefit cycle: real-time benefit verification, payer form identification, clinical evidence extraction from chart notes with citations, submission, determination follow-up, denial analysis, and AI-generated appeals. It connects through REST endpoints for running benefit verifications and submitting prior authorizations, with webhooks pushing status changes back as they happen.

Your team wires prescription events from Healthie into the API, and statuses flow back into whatever surface your staff already watches, whether that is a Healthie task, a Slack channel, or your own admin tool. Clinicians keep prescribing exactly as they do today.

The obvious question for a Healthie-native engineering team is why not build against DoseSpot's ePA API directly. Because ePA rails only handle transmission. They do not read a chart to find documented six-month lifestyle therapy, call a PBM when the rails fall short, or write appeal letters. Those are the steps that consume staff hours.

The capability that matters most for virtual-first prescribers is multi-channel submission. Rather than relying on ePA alone, using Develop Health requests route through ePA, AI-driven phone calls, fax, or direct PBM portals depending on the payer, reaching 99%+ of plans against a rough industry standard of 80% for ePA-only coverage.

Develop Health customers report an 83% reduction in PA handling time, a 14% lift in approval rates, and prescription-to-approval cycle times cut from roughly 1.5 weeks to about 20 hours. Arches Primary Care processed roughly 800 prior authorizations in six weeks, cutting turnaround from weeks to two days.

Best for: 

• Practices with high pharmacy-benefit PA volumes, especially those managing specialty medications like GLP-1s, biologics, or ADHD drugs.
  
  

• Also a strong fit for digital health companies, specialty pharmacies and any practice that wants to eliminate PA-related staff overhead without replacing tools or changing how providers prescribe.

Where it is limited:

• Develop Health focuses primarily on pharmacy-benefit PAs, it is not the right solution if your primary volume is medical-benefit authorization (procedures, imaging, referrals).

Side-by-Side: PA Options on Healthie

Automate the PAs That Healthie Was Never Built to Handle

Healthie gives you a solid electronic submission path and a clean place to record authorizations, and every organization should max both out first. But the work that actually consumes staff hours, finding clinical evidence, chasing determinations, and appealing denials, is outside anything Healthie or DoseSpot automates.

If that is where your team's time goes, Develop Health automates the complete pharmacy-benefit cycle through an API that fits alongside your Healthie environment, with no change to how clinicians prescribe. Book a demo to see how it would work for your stack.

Frequently Asked Questions

Does Healthie have built-in prior authorization?

Partly, and only for prescriptions. Pharmacy-benefit ePA is available through the DoseSpot E-Rx add-on, where requests appear in a Prior Authorizations tab within Tasks. Medical-benefit PAs have no submission workflow at all; Healthie stores the authorization number for claims but you obtain it from the payer yourself.

How do I submit an electronic prior authorization in Healthie?

Save the prescription as a pending medication in the DoseSpot E-Rx interface. If the medication shows a Prior Auth Required status, choose Initiate Prior Auth for Selected and check the EPA box. The request then appears under the Prior Authorizations tab in Tasks, where you monitor status and respond to any Action Required prompts from the payer.

Why can't I see the ePA option in my Healthie account?

The most common reasons are that E-Rx is not enabled on your plan, that your user has not been approved by DoseSpot, or that the ePA clinician role is not checked. Support staff also cannot access prescribing functions unless they are designated as Proxy users.

Can third-party prior authorization tools integrate with Healthie?

Yes, through Healthie's GraphQL API, which is available as an add-on on Enterprise and Group plans and covers the full platform. Partners can also distribute integrations through Healthie's Harbor marketplace. API-native platforms such as Develop Health expose REST endpoints and webhooks that your team connects to prescription events, with statuses flowing back into your existing surfaces.

How long does a prior authorization take on Healthie?

It depends entirely on the path. ePA requests to participating payers can return determinations within minutes to a couple of days, while manually worked PAs for non-connected payers historically run one to two weeks. End-to-end automation platforms report cutting the full prescription-to-approval cycle to roughly 20 hours.

Is Healthie's ePA enough for a GLP-1 or specialty practice?

Usually not on its own. ePA handles transmission well, but GLP-1 and biologic authorizations turn on documented step therapy, BMI and comorbidity history, and payer criteria that change frequently, all of which someone has to locate in the chart and enter by hand. High-volume specialty prescribers typically need evidence extraction and appeal automation on top of the ePA rail.