HHAeXchange EVV for Florida Home Health Agencies: How It Works & What Agencies Must Know

Electronic Visit Verification (EVV) in Florida is not a single software application—it is a statewide compliance and claims validation pipeline. For Florida home health agencies delivering Medicaid-funded services, understanding how HHAeXchange fits into this ecosystem is essential to avoid delayed payments, claim rejections, and state audit citations.

This guide outlines AHCA's contract with HHAeXchange, the transition for Fee-for-Service (FFS) providers, how the data matching engine functions, and how agencies can connect existing software under Florida's Open Vendor policy.

1. The Regulatory Background: AHCA & the 21st Century Cures Act

Federal law under Section 12006(a) of the 21st Century Cures Act mandates that all state Medicaid programs require Electronic Visit Verification for Personal Care Services (PCS) and Home Health Care Services (HHCS).^[1] Under the statute, states that failed to implement EVV faced graduated reductions in their Federal Medical Assistance Percentage (FMAP).^[2]

In Florida, the Agency for Health Care Administration (AHCA) implemented EVV across two primary branches:

1. Statewide Medicaid Managed Care (SMMC): AHCA mandated EVV compliance across all participating Medicaid Managed Care Plans effective January 1, 2020, requiring monthly monitoring, validation, and complaint reporting from managed care plans.^[3]
2. Medicaid Fee-for-Service (FFS): For traditional Medicaid FFS providers—specifically covering Private Duty Nursing (PDN), Home Health Visits (physical therapy, occupational therapy, speech therapy, and skilled nursing), and Personal Care Services—AHCA contracted with HHAeXchange as the state EVV data aggregator.^[3][4]

The official go-live date for Florida Medicaid Fee-for-Service providers using HHAeXchange took effect on October 1, 2024.^[4]

2. Florida's "Open Vendor" Model

One of the most frequent misconceptions among Florida agency owners is that they are legally forced to abandon their existing operational software and run daily agency operations exclusively through HHAeXchange's basic interface.

According to AHCA's Medicaid Comprehensive Quality Strategy, Florida operates under an Open Vendor Model:^[3]

• Option 1: The Free State-Provided System. Providers may choose to use the state's contracted HHAeXchange portal directly at no software licensing cost to log visits, maintain caregiver rosters, and confirm visit data.^[3][4]
• Option 2: Third-Party EVV Interface. Providers may maintain an independent, third-party EVV and agency management system of their choice, provided that system captures all federally required EVV elements and transmits compliant visit data to HHAeXchange through an approved electronic interface.^[3][4]

Under Option 2, HHAeXchange acts as the state data aggregator, validating that visit data complies with federal and state standards before allowing claims to adjudicate.^[4]

3. The 6 Statutory Data Elements Required for Every Visit

Whether an agency records visits through the HHAeXchange mobile app, telephony (IVR), or a third-party clinical software layer, federal statute (Social Security Act §1903(l)(5)(A)) requires electronic verification of exactly six core data elements:^[1][2]

1. Type of service performed (matching the authorized Medicaid procedure code, such as T1000, T1002, T1003, or G0151–G0156).
2. Individual receiving the service (verified Medicaid recipient identity and recipient ID).
3. Date of service.
4. Location of service delivery (electronically captured GPS geofence coordinates or verified landline telephony at the patient's registered service address).
5. Individual providing the service (unique clinician identifier, AHCA Level 2 background screening Clearinghouse record, and NPI where applicable).
6. Time the service begins and ends (exact electronic timestamp at clock-in and clock-out).

4. How the Florida EVV & Claims Matching Pipeline Works

The primary function of HHAeXchange in Florida is pre-claim validation. The workflow follows a strict sequential gate:

[ Caregiver Clock-In / Out ]
           │
           ▼
[ Verification of 6 Core Elements ] (GPS geofence + real-time timestamp)
           │
           ▼
[ Exception Resolution ] (Any mismatch flagged: overtime, unauthorized location, missed clock-out)
           │
           ▼
[ Aggregator Acceptance ] (Visit marked verified in HHAeXchange)
           │
           ▼
[ EDI 837P Claim Submission ] (Visit ID and auth code matched against Medicaid claim line)
           │
           ▼
[ Payment Adjudication / 835 Remittance ]

When a claim is submitted to Florida Medicaid (or a Medicaid Managed Care Plan using HHAeXchange for claim gating), the state's claims engine matches the claim line against the confirmed EVV record in the aggregator.

If the dates, units of service, procedure code, recipient Medicaid ID, or provider NPI do not match the verified EVV visit, the claim will result in a denial or pre-payment rejection (frequently tagged with CARC 272 or specific state EVV mismatch codes).^[6]

5. Common EVV Exception Codes & Denial Triggers

In Florida, an EVV record that contains unaddressed "Exceptions" cannot be matched to a clean claim. Agency operations staff must monitor their exception queue daily:

6. Questions Every Florida Agency Owner Should Ask

If your agency operates under the Florida Open Vendor Model using third-party software alongside HHAeXchange, review these operational questions:

1. Does our software automatically format visit data to HHAeXchange specifications? Submitting incomplete payloads without exact GPS coordinates or compliant procedure codes creates a manual data-entry bottleneck.
2. How are mid-shift exceptions handled? If a caregiver arrives late or leaves the geofence perimeter for a medical transport, does your field software notify agency dispatch immediately, or do you only find out when billing runs weeks later?
3. Are clinical notes linked directly to the EVV punch? During an AHCA survey or Medicaid Program Integrity audit, surveyors cross-examine clinical shift notes against the electronic EVV timestamp to verify proof of service.^[8]
4. Is patient PHI protected during transmission? All electronic transmissions between field devices, agency servers, and state aggregators must comply with HIPAA administrative simplification standards.^[9]

7. How Bickle Fits into Your Florida Agency Workflow

Bickle is not an aggregator and does not replace HHAeXchange. Instead, Bickle serves as the operational and clinical frontline layer for Florida home health agencies:

• Voice-to-Ledger Documentation: Caregivers dictate their clinical visit notes naturally at the bedside. Bickle converts spoken shift updates into structured, audit-ready documentation linked directly to the shift record.
• Pre-Submission EVV Integrity: GPS geofencing and real-time punch validation verify that all six mandatory Cures Act data elements are captured accurately at the point of care, eliminating unverified punches before data reaches the state aggregator.
• Audit-Proof Operational Ledger: Every edit, exception override, and supervisor review is permanently logged with an immutable audit trail matching Florida Administrative Code Chapter 59A-8 requirements.^[10]

Keep Reading

• Florida EVV Requirements for Home Health Agencies
• Florida's Open Vendor EVV Model Explained
• Florida AHCA Home Health Survey Preparation Checklist
• How Florida Agencies Can Reduce EVV-Related Claim Problems

This page provides general educational and operational information for agency owners and administrators. It does not constitute legal counsel or formal billing advisory. Rules and payer requirements change; always verify current guidelines with AHCA and your contracted Medicaid Managed Care Plans.