HHAeXchange is Florida's dominant home health scheduling and EVV platform. Most Florida agencies running Medicaid waiver and community care services use it — but many are still manually re-entering visit data into their billing system, creating errors, delays, and compliance gaps.
How HHAeXchange Data Flows Into Billing
HHAeXchange captures EVV data at the point of care: caregiver check-in and check-out, GPS coordinates, service code, and patient identifier. This data exports as a visit file that your billing platform should ingest directly — no manual re-entry required.
Florida Medicaid requires EVV data to be transmitted to the state's EVV aggregator (currently Sandata) before the claim can be processed. Agencies that bill before EVV data is confirmed in the aggregator face systematic rejections that look like payer issues but are actually EVV compliance gaps.
Common HHAeXchange Billing Integration Errors in Florida
- ✓Visit export timing mismatch — billing team exports visits before EVV data is confirmed in Sandata, causing claim rejections
- ✓Service code mapping errors — HHAeXchange uses internal service codes that must be mapped to the correct HCPCS/procedure codes for each payer
- ✓Authorization mismatch — visit logged in HHAeXchange references an authorization that has expired or was not loaded correctly
- ✓Caregiver credential gap — EVV visit accepted in HHAeXchange but the caregiver NPI is not on file with the payer
- ✓Duplicate visit detection — same patient, same date, overlapping hours — HHAeXchange may not catch these; your billing platform should
Setting Up the Integration — What Your Billing Platform Needs
A proper HHAeXchange billing integration requires: API or SFTP connection to your HHAeXchange account, service code mapping table maintained per payer, authorization cross-reference to catch expired or mismatched auths before claim submission, and EVV confirmation check before releasing claims to the clearinghouse.
Florida MMC payers (Sunshine, Humana, Molina, Simply Healthcare) each have their own visit data requirements. A visit valid in HHAeXchange for Medicaid FFS may require additional fields for MMC billing. Confirm with each payer's EDI specifications.
What to Audit Before Going Live
- ✓Confirm EVV data is transmitting to Sandata before first claim run
- ✓Map all HHAeXchange service codes to the correct HCPCS for each payer in your billing system
- ✓Load all active authorizations into your billing platform — not just the current month
- ✓Run a test export of 10 visits and trace each one through to claim generation before going live
Leymax integrates directly with HHAeXchange for Florida home health billing. Our platform handles EVV validation, authorization cross-reference, and MMC payer rules automatically.
See our HHAeXchange billing integration →