Home Health Auth Re-Verification: 8-Step Guide 2026

Key Takeaways

• Authorization re-verification failures are one of the top three revenue leakage points for home health agencies, and most still run this process manually.

• A structured 8-step automation workflow can reduce prior-auth-related denials by catching expiring authorizations before the visit — not after the claim.

• The average home health agency verifying authorizations manually spends 3–5 staff hours per day on tasks that can be handled by a trigger-based workflow.

• Platforms like WellSky and Axxess have native auth tracking, but neither eliminates the cross-payer re-verification gap that causes mid-episode denials.

• US Tech Automations connects your existing EHR and payer portals so your team is alerted — and the payer is contacted — before the authorization expires.

Authorization re-verification is the administrative equivalent of a ticking clock: if someone doesn't catch the expiring auth, the visit happens, the claim gets filed, and the denial lands 30–60 days later when the revenue has already been counted. Most home health agencies know this. Very few have a reliable process that doesn't depend on a single coordinator checking a spreadsheet every morning.

This guide walks through an 8-step automation workflow for home health authorization re-verification — what to trigger, what to check, and where each of the leading platforms fits (and doesn't fit).

Administrative costs represent a substantial share of US healthcare spending, according to KFF 2024 Health Spending Analysis — and prior authorization management sits near the top of the administrative burden for home health specifically.

What Authorization Re-Verification Actually Means

Authorization re-verification is the process of confirming — before a scheduled visit — that the patient's current insurance authorization is still active, covers the planned service, and has remaining units. It's distinct from the initial auth request: re-verification is ongoing throughout an episode of care.

For home health agencies, this matters because Medicare Advantage and commercial payers frequently issue authorizations in 30- or 60-day episodes that don't align with the full plan of care. A patient on a 90-day therapy protocol may require two or three re-verifications during that episode.

Home health coordinators who rely on manual spreadsheets to track auth expiration dates are running a reactive process — the error is discovered after the visit, not before it.

Who This Is for

This guide is designed for home health agency directors, revenue cycle managers, and clinical operations leads at agencies that:

• Serve 50+ active patients across Medicare Advantage or commercial payer lines

• Currently manage auth tracking in a spreadsheet, EHR task queue, or through manual payer portal checks

• Experience recurring mid-episode denials that take 45+ days to appeal

• Have integrated (or plan to integrate) a platform like WellSky, Axxess, or Forcura

Red flags: Skip this guide if your agency is entirely fee-for-service Medicare traditional with no managed care contracts, if you have fewer than 25 active patients, or if your authorization volume is too low to justify workflow investment (under 20 auths/month).

Why Manual Re-Verification Fails at Scale

Most agencies start with a shared spreadsheet or a field in their EHR's task module. For a 20-patient caseload, that's manageable. At 100+ patients across multiple payers, it collapses.

Here's what breaks:

1. No proactive alerts — Someone has to remember to check. No system pings the coordinator 7 days before expiration.

2. Payer portals don't sync — Auth status in the portal and auth status in the EHR are often out of sync by days.

3. Coordinators manage multiple payers — Each payer has a different portal, a different re-auth form, and different timelines. Tracking this manually across 8+ payers is untenable.

4. Denials arrive after the fact — By the time the EOB shows the denial, 30+ days of visits may be uncovered.

Typical payer re-auth processing windows by plan type:

Many physicians report prior authorization burdens contribute significantly to burnout, according to the AMA 2024 Physician Burnout Survey — a finding that extends equally to home health clinical coordinators managing auth paperwork.

The 8-Step Authorization Re-Verification Workflow

This workflow assumes you have an EHR or scheduling system that holds auth end dates. The automation layer sits on top of that system to trigger checks and escalations.

1. Ingest auth expiration dates daily. Pull all active authorizations from your EHR (WellSky, Axxess, Forcura, or your scheduling system) into a central tracker. This should run automatically at 6 AM each day.

2. Flag auths expiring within 14 days. Any authorization with an end date within the next 14 days moves to a "pending re-verification" queue. Fourteen days gives enough runway for most payers' re-auth processing windows.

3. Route by payer and service type. Medicare Advantage, commercial, and Medicaid managed care each have different re-auth forms and timelines. Route each flagged auth to the appropriate staff member or queue based on payer.

4. Auto-generate the re-auth request. Using data already in the patient record — diagnosis codes, plan of care, treating clinician — pre-populate the re-auth form. Staff review and submit; they don't start from scratch.

5. Log submission with timestamp. Record the date, method (portal, phone, fax), and the staff member who submitted. This creates an audit trail and starts the payer response clock.

6. Set a 5-day follow-up trigger. If no auth confirmation is received within 5 business days of submission, trigger a follow-up alert to the coordinator and an escalation to the billing manager.

7. Update the EHR upon confirmation. When the payer confirms the new auth number and dates, automatically update the EHR record. This prevents visits from scheduling against an expired auth.

8. Flag for clinical review if denied. If the re-auth is denied, immediately route to the clinical director for appeal and pause scheduling for the affected visit codes until resolved.

Agencies that run this workflow with automated triggers — rather than manual calendar reminders — typically see a measurable reduction in mid-episode denials within the first billing cycle.

Platform Comparison: WellSky vs. Axxess vs. Forcura

Each platform handles auth tracking differently. The right choice depends on how much of the workflow you need to own versus delegate to the software.

WellSky wins on EHR breadth and compliance reporting. If you are a large Medicare-certified agency with a full clinical team and your pain is primarily clinical documentation, WellSky's native tools are comprehensive. Axxess is stronger for mid-market agencies that want a single-platform approach to scheduling and billing. Forcura is purpose-built for document exchange and is excellent if your core problem is getting physician orders and clinical notes in on time — but it does not solve the re-verification gap.

When NOT to use US Tech Automations: If your agency operates entirely within WellSky or Axxess and all your payers are accessible through their built-in auth modules, the incremental lift from adding an orchestration layer may not justify the integration effort. The platform adds the most value when you have 3+ payers with separate portals, a high volume of managed care auths, or a gap between your EHR's auth tracking and your billing system.

Common Mistakes in Home Health Auth Workflows

Home health agencies that have tried to automate re-verification — and failed — tend to make one of these mistakes:

Tracking auth end dates only, not unit balances. An authorization can still be "active" (not expired) but have zero remaining units. If your workflow only flags by date, you will miss unit exhaustion denials.

Setting alerts too late. A 3-day warning is not enough for most payers. Many Medicare Advantage plans require 7–10 business days to process a re-auth. Build your trigger window around your payer mix's actual turnaround times.

Not separating auth tracking from auth requesting. These are two different tasks with different urgency. Tracking (checking status) can be automated; requesting (clinical justification) requires human review. Conflating them in one workflow creates bottlenecks.

Auth Re-Verification Benchmarks

Use this table to gauge where your agency stands relative to industry norms.

Most office-based practices and home health agencies have adopted EHR platforms, according to the HIMSS 2024 Health IT Adoption Report — but EHR adoption does not automatically translate to automated workflow management of authorization re-verification.

Integration Architecture: How the Pieces Connect

For agencies running WellSky or Axxess as their system of record, the automation layer connects at three points:

Data ingestion: A nightly or twice-daily pull from the EHR's auth module exports auth records — patient ID, auth number, payer, service type, units authorized, units used, end date — into the workflow engine.

Trigger logic: The workflow engine evaluates each record against your configured rules (14-day window, unit threshold, payer-specific SLAs) and generates tasks or alerts.

Write-back on confirmation: When a coordinator logs the new auth number and dates, that data writes back to the EHR record, keeping the system of record accurate.

US Tech Automations handles all three connection points through pre-built integrations with major home health platforms and payer portal APIs where available. For payers without API access, the workflow uses structured web automation to check portal status.

For a broader look at how eligibility checks fit into scheduling, see the related guide on how to integrate eligibility checks into your scheduling workflow.

Auth Workflow Glossary

Authorization (auth): A payer's pre-approval for a specific service, quantity, and time period. Required for most skilled nursing, therapy, and home health aide services under managed care contracts.

Re-verification: The process of confirming an existing authorization is still valid before a scheduled visit — as distinct from requesting a new or extended authorization.

Episode of care: The period covered by a single authorization or plan of care. Medicare home health episodes are traditionally 60 days; Medicare Advantage episodes vary by plan.

Prior authorization (PA): Used interchangeably with auth in home health, though PA more commonly refers to the initial request; re-verification is the ongoing check.

Units remaining: The authorized quantity still available for billing. A plan may authorize 12 therapy visits; tracking units prevents visits 13+ from being denied retroactively.

Payer portal: The payer's web-based system for checking auth status, submitting re-auth requests, and viewing explanation of benefits.

Denial management: The process of reviewing, appealing, and correcting denied claims. Auth-related denials are among the highest-volume and most preventable denial categories.

Building the Business Case Internally

For revenue cycle managers who need to justify the investment in automated re-verification, the math is straightforward:

Calculate your current mid-episode denial rate on managed care claims. For a typical home health agency with 150 active managed care patients and a 10% mid-episode denial rate, that is roughly 15 denied claims per month. If the average claim value is $1,200 and 60% of appeals succeed, that is 9 recovered claims per month — but only after 60–90 days of appeal work. Automation shifts most of those denials to prevented denials, recovering the revenue faster and without appeal labor.

Home health prior authorization denial rate: 14–18% of managed care home health claims are denied on first submission, according to Definitive Healthcare 2024 benchmarks — the highest denial rate in post-acute care and the primary revenue leakage driver for agencies managing 5+ payer contracts.

Average home health claim value: $1,100–$1,800 per episode, according to CMS 2024 Home Health Prospective Payment System data — meaning each prevented auth denial recovers meaningful revenue per episode rather than marginal amounts.

Revenue cycle automation in home health reduces billing cycle time by 30–40%, according to the American Association for Home Care 2024 Operational Benchmarks — a finding driven largely by proactive auth tracking that prevents back-end denial work.

Getting Started with US Tech Automations

US Tech Automations integrates with your existing EHR and payer portals to deploy the 8-step re-verification workflow described above. The setup process starts with a workflow audit of your current auth volume, payer mix, and EHR configuration — then maps that to the automation triggers that will have the most immediate impact on denial prevention.

For agencies with complex managed care contracts and multiple payers, this is typically a 2–4 week implementation, with most agencies seeing a measurable reduction in auth-related denials within the first full billing cycle.

See the full pricing page to understand the investment relative to your current denial volume. You can also review how this connects to broader healthcare automation approaches for intake and scheduling.

For related reading on referral tracking workflows that complement auth management, see 8 steps to automate referral tracking between specialists.

FAQs

What is the difference between authorization verification and re-verification?

Authorization verification confirms that a new auth has been issued before starting services. Re-verification is the ongoing process of confirming that an existing auth remains active, has not expired, and still has available units — a check that must happen repeatedly throughout an episode of care.

How often should home health agencies run re-verification checks?

Most agencies should run a daily automated check, with a 14-day alert window for upcoming expirations and a secondary alert at 7 days. High-volume managed care agencies may benefit from twice-daily checks to catch same-day payer updates.

Does WellSky or Axxess handle re-verification automatically?

Both platforms provide native auth tracking and can surface expiring authorizations. However, neither automatically contacts the payer, pre-populates re-auth forms, or routes denied re-auths to an appeal workflow. Those steps still require a coordinator or a separate automation layer.

What causes most mid-episode authorization denials?

The most common causes are missed re-verification before an authorization expires, visits scheduled against an auth with zero remaining units, and service codes that drift outside the authorized scope. All three are preventable with a properly configured workflow.

Can automation handle payers that require phone re-verification?

Some payers — particularly smaller regional plans — require phone calls for re-auth requests. Automation can handle the scheduling and escalation for these calls, ensure the coordinator has the patient information ready, and log the outcome — even if the actual phone call cannot be fully automated.

How do I calculate the ROI of auth re-verification automation?

Calculate your monthly denied claim volume that is auth-related, multiply by your average claim value and your appeal success rate, then factor in the staff hours currently spent on manual tracking and re-auth submission. For most agencies, the prevented denials alone justify the investment within 2–3 billing cycles.

What data does the automation need from my EHR?

Minimum data required: patient ID, payer ID, auth number, authorized service codes, authorized units, units used, and auth end date. Most major home health EHRs can export this via API or scheduled report.