Prior authorization automation and eligibility checks for clinics
In US clinics, payer paperwork decides whether a visit gets paid. We build a workflow that collects insurance details before the appointment, flags visits whose payer and service need a prior authorization, tracks every pending request to a decision, and logs denial reasons for billing staff to work. It prepares and chases; billing staff and clinicians submit and decide. A typical build costs $1,000 to $2,500 per workflow and takes four to five weeks.
The problem
Why prior authorizations slip through
Prior authorization lives in payer portals, fax lines and phone queues. A request goes in, then someone has to remember to check it. Missing authorizations are often found after the patient has been seen, when the claim is already at risk.
Rules are changing. Under the CMS Interoperability and Prior Authorization final rule, impacted payers such as Medicare Advantage and Medicaid managed care plans must decide urgent requests within 72 hours and standard ones within seven calendar days from 2026, give specific denial reasons, and offer a Prior Authorization API from 2027. Clinics that track requests well will benefit most.
What we build
What our prior authorization automation includes
Insurance details before the visit
Subscriber, plan and group details collected with intake and placed where staff run the eligibility check.
Prior auth flags
Your own rules by payer and service mark which booked visits need an authorization.
Request tracker
Every pending authorization with payer, submitted date, expected decision date and owner.
Chase reminders
Reminders to billing staff when a decision is overdue against the payer's timeframe.
Denial log
Denial reasons recorded in one place so staff can appeal or fix patterns.
Day-before list
Tomorrow's visits with unverified coverage or pending authorizations.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Visit booked
A new appointment triggers the payer and service check.
-
02
Automated
Details gathered
Insurance details are collected and missing items flagged.
-
03
Automated
Auth flagged
Visits that need a prior authorization are listed with supporting documents attached.
-
04
Coordinator review
Billing staff submit and chase
Staff verify eligibility, submit requests through the payer route and work denials.
-
05
Clinician or medical director decides
Clinical justification
Medical necessity documentation comes from the clinician, never from the automation.
How it behaves
How eligibility and auth tracking behave
What the patient sees
- A request for insurance details with intake
- Fewer surprise calls about coverage on the day
- A call from billing staff if something needs their input
What staff see
- A tracker of pending authorizations with due dates
- A day-before list of unverified coverage
- A denial log by payer and reason
What the automation does
- Applies payer and service rules to booked visits
- Reminds staff when decisions are overdue
- Never submits clinical justification itself
Edge cases and fallbacks
- Payer rule is unclear
- Flagged as needs review rather than guessed.
- Authorization denied
- Reason logged and assigned to billing staff and the clinician.
- Visit moved after auth approval
- Flagged to check the authorization window still covers the new date.
- Clearinghouse or portal outage
- Tracker keeps statuses and staff work by phone; nothing is marked verified without a response.
Architecture
Eligibility and prior authorization prep at a glance.
- Input
- Logic and services
- Data
- People
How it flows
- 1 A booked visit starts the workflow, which applies the clinic's payer and service rules.
- 2 Insurance details are lined up for the eligibility check and authorizations needed are added to the tracker.
- 3 Billing staff verify coverage, submit requests through the payer route and get reminders when decisions are overdue.
- 4 Clinicians supply medical necessity documentation; denial reasons are logged for appeal.
Project planner
How the project runs, phase by phase.
Eligibility checks & prior authorization prep project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Payer mix, services that need authorization, current tracking and clearinghouse.
-
02
Design
2 to 3 days
Payer rules, tracker fields, reminder timing and the day-before list.
-
03
Build
About 2 weeks
Schedule reads, rules, tracker, reminders and denial log.
-
04
Shadow run
About 1 week
The tracker runs beside the current process while billing staff check every flag.
-
05
Launch
1 to 2 days
Go live for the highest-volume payers first.
-
06
Support
Ongoing
Payer rule changes and new services.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Workflow mapping with the clinic team, wording, data flows and a written specification.
$200 – $400
-
Build
The n8n workflow, rules, AI step where useful, logging and error handling.
$500 – $1,300
-
Integrations
EHR or practice management access, messaging and staff alert channels.
$150 – $400
-
Testing and shadow run
Acceptance tests and a side-by-side run while staff keep the old process.
$100 – $250
-
Launch and training
Go-live, front-desk walkthrough and a short run book.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Clearinghouse and payer portal access stay under your contracts. Electronic submission through a payer API is scoped per payer.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Clearinghouse: Your existing clearinghouse plan for eligibility transactions.
- n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: CMS prior authorization rule
Impacted payers must send prior authorization decisions within 72 hours for expedited and seven calendar days for standard requests and give specific denial reasons from 2026, with a Prior Authorization API from January 1, 2027. Drugs are excluded.
Source: www.cms.govUS: eligibility transaction standard
The X12 270/271 inquiry and response is the HIPAA standard for asking a health plan about coverage.
Source: cms.govUS: billing texts are outside the exemption
The FCC healthcare text exemption excludes billing and financial content, so patient balance or coverage messages need their own consent design.
Source: www.law.cornell.eduFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Eligibility checks & prior authorization prep questions, answered.
The tracking and chasing: flagging which visits need an auth, gathering documents, recording submissions and reminding staff when decisions are overdue. Billing staff still submit and clinicians still write the justification.
Not at first. Payer routes differ, and the CMS Prior Authorization API only becomes required for impacted payers from 2027. Where a payer offers an electronic route your contract allows, we can scope it.
It covers the front end of billing: eligibility and authorization. Claims, coding and denials management stay with your billing team or service, and we can feed them the denial log.
Per CMS, Medicare Advantage organisations, Medicaid and CHIP fee-for-service programmes and managed care plans; the decision timeframes do not apply to Exchange QHP issuers. General information, not legal advice.
Mostly not. UK and EU clinics usually deal with private medical insurers' pre-authorisation or self-pay, and we adapt the tracker to those routes.
Visits seen without a required auth, days from submission to decision by payer, denials by reason and visits with verified coverage the day before.
Free 20-minute call
Want this for your healthcare clinic?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for healthcare clinics
All servicesHealthcare CRM & new-patient pipeline
Every enquiry from web forms, calls, chat, directories and physician referrals lands in one healthcare CRM pipeline with owners, follow-ups and a weekly report by source and service line.
From $1,000 · About 4 weeks Details
Referral management & patient intake
Log incoming referrals the day they arrive, send and chase intake and consent forms, track what is missing before the first visit and close the loop with the referring provider.
From $1,000 · About 4 to 5 weeks Details
Patient reminders & no-show follow-up
Appointment reminders by each patient's preferred channel, easy confirm or reschedule replies, a waitlist offer when a slot opens and a person following up every missed visit.
From $1,000 · About 4 weeks Details