Valer (Voluware)

Prior auth submission and tracking automation across payer portals

Our take

Valer, the company formerly known as Voluware, has sold prior authorization and referral automation since 2012 from Huntington Beach, California. Its platform submits PAs across 75+ payer web portals and more than 1,000 payer fax forms, checks statuses automatically, and syncs results bi-directionally with the EHR using the same 278/275 transactions and auth shells staff already use. It handles procedures, referrals, and services across care settings, which distinguishes it from drug-only PA tools, and it is listed on the Epic marketplace. Hospitals, health systems, and larger physician groups are the core buyers; OHSU is a publicly documented customer.

The company took its first institutional investment from healthcare-focused private equity firm Hughes & Company in 2021, rebranded from Voluware to Valer in January 2024, and earned HITRUST r2 certification in October 2024. It was named a top prior authorization company in AVIA Marketplace's 2024 report. Valer is a focused specialist: much smaller than Optum or McKesson properties, but built specifically for the portal-and-fax reality of medical prior auth that persists while payer APIs mature.

What it does

Automated PA submission to 75+ payer portals
Auto-completion of 1,000+ payer fax forms
Automated status checking and verification
Bi-directional EHR sync using standard 278/275 transactions
Covers procedures, referrals, and services, not just drugs
Reporting on turnaround times and staff productivity

Where it's strong

Covers the messy middle of PA: portal and fax submissions that pure API-based tools cannot reach.
Bi-directional Epic integration writes auth numbers and statuses back automatically.
Workflow is configured per client rather than one-size-fits-all, which suits complex health system setups.

What buyers should weigh

Small company with modest disclosed funding, so evaluate roadmap and support depth against bigger rivals.
Portal and fax automation depends on payer sites staying stable; expect some maintenance lag when payers change portals.
Per-client configuration means implementations take real effort compared with plug-and-play point tools.