Florida's Open Vendor EVV Model Explained: State Aggregator vs. Third-Party Systems

When states began complying with the federal 21st Century Cures Act mandate for Electronic Visit Verification (EVV), they chose different structural models. Some states implemented a "closed" or single-vendor model, forcing every healthcare provider to abandon their operational software and adopt one state-mandated platform.

Florida chose a different path. In its Medicaid Comprehensive Quality Strategy, the Agency for Health Care Administration (AHCA) formally established an Open Vendor Model for Florida Medicaid Fee-for-Service (FFS) home health providers.^[1]

This policy protects agency autonomy, allowing home health operators to keep or adopt software that best serves their caregivers, patients, and dispatchers, while still transmitting standardized visit data to the state.

Here is a comprehensive guide to how Florida's Open Vendor EVV model functions, how third-party interoperability works, and what agency leaders must evaluate when choosing their technology stack.

1. What Is an "Open Vendor" Model?

In healthcare informatics, an open vendor EVV model separates the operational software layer (used by caregivers, nurses, and schedulers) from the state data aggregator layer (used by the Medicaid agency to validate claims and prevent fraud).^[1][2]

Under AHCA's open vendor policy, Florida home health providers delivering Fee-for-Service services—including Private Duty Nursing (PDN), Skilled Nursing visits, physical/occupational/speech therapy, and Personal Care Services—have two distinct options:^[1][3]

┌────────────────────────────────────────────────────────────────────────┐
│                   AHCA Florida Open Vendor Policy                      │
└───────────────────────────────────┬────────────────────────────────────┘
                                    │
            ┌───────────────────────┴───────────────────────┐
            ▼                                               ▼
   Option 1: State Portal                         Option 2: Third-Party EVV
• Free HHAeXchange portal                      • Agency selects preferred software
• Basic scheduling & IVR                       • Direct point-of-care mobile app
• Data lives in state system                   • Structured voice documentation
            │                                  • Pre-submission validation
            │                                               │
            │                                               ▼
            │                                     [ Electronic Interface ]
            │                                               │
            └───────────────────────┬───────────────────────┘
                                    │
                                    ▼
                    [ HHAeXchange Data Aggregator ]
                                    │
                                    ▼
                 [ Florida Medicaid Claims Adjudication ]

2. Option 1: The State-Provided EVV System (HHAeXchange)

Under Option 1, providers use the state-contracted portal provided through AHCA's vendor contract with HHAeXchange (which went live for Fee-for-Service on October 1, 2024).^[3]

• Cost: The basic web portal and mobile app are made available at no software licensing charge to Medicaid providers.^[1][3]
• Functionality: Provides basic scheduling, clock-in/out telephony (IVR), mobile punch tracking, and direct claim generation within the portal.
• Limitations: The state portal is built primarily as an audit aggregator rather than a comprehensive agency operating system. Agencies running diverse lines of business (e.g., commercial insurance, private pay, VA Community Care, or multi-branch operations) often find running day-to-day operations out of a compliance portal cumbersome for field clinicians.

3. Option 2: Approved Third-Party EVV Systems

Under Option 2, an agency operates its daily workflow—including patient intake, dynamic scheduling, caregiver dispatch, clinical notes, and EVV timekeeping—on an independent, third-party platform of its choice.^[1][3]

According to AHCA and HHAeXchange documentation, agencies selecting Option 2 must ensure their system meets two legal criteria:^[1][3]

1. Federal Cures Act Compliance: The system must electronically capture and verify all six mandatory data elements under 42 U.S.C. § 1396b(l) (service type, recipient, date, location, caregiver, and start/end timestamps).^[2]
2. Aggregator Interoperability: The system must connect to the HHAeXchange portal through an established electronic data interface (EDI), transmitting verified visit files in the standardized schema required for Florida Medicaid claim matching.^[3]

4. Fee-for-Service vs. Statewide Medicaid Managed Care (SMMC)

A frequent point of confusion for Florida agencies is how the Open Vendor model applies across different payer contracts:

Florida Medicaid Fee-for-Service (FFS)

For patients enrolled in traditional Fee-for-Service Medicaid, AHCA is the direct payer. HHAeXchange acts as the official state aggregator under AHCA’s contract.^[1][3] All FFS visits—whether captured via Option 1 or Option 2—must flow through HHAeXchange before claims are paid.

Statewide Medicaid Managed Care (SMMC)

Under Florida's managed care program (effective since January 1, 2020), managed care plans (such as Sunshine Health, Humana, Simply Healthcare, etc.) manage Medicaid member care.^[1] Many Florida MCOs also contract with HHAeXchange to aggregate visit data, while others maintain alternative clearinghouse arrangements. Under Florida regulations, health plans must accept compliant encounter data from third-party EVV systems that adhere to state standards.^[1]

5. Technical Interoperability: How Third-Party EVV Data Flows

When using an independent operating platform alongside HHAeXchange under Option 2, the data transmission follows a four-stage lifecycle:

1. Point-of-Care Capture: The field nurse or aide clocks in using GPS geofencing on their mobile device and records clinical shift observations.
2. Internal Validation: The agency's software verifies that the caregiver is within the patient's geofence, confirms authorization units, and flags any schedule variances.
3. Aggregator Transmission: The confirmed visit record is packaged and transmitted electronically to the HHAeXchange aggregator via API or batch file.
4. Pre-Claim Matching: When the agency submits its 837P electronic claim, the state's claims adjudication engine validates that the claim line matches an accepted visit in the aggregator.

6. What to Evaluate When Choosing an Operational System Under the Open Vendor Model

Before selecting or migrating to a third-party software layer, agency leadership should verify four critical capabilities:

7. How Bickle Fits the Florida Open Vendor Ecosystem

Bickle is designed specifically to empower Florida agency operators under the Open Vendor Model:

• Voice-to-Ledger Clinical Capture: Caregivers speak their clinical shift summaries directly into the app, turning bedside voice notes into structured, audit-ready clinical records linked to exact EVV punches.
• Pre-Submission Quality Gate: Real-time geofencing and shift validation catch missing elements before data leaves the agency, eliminating downstream claim denials.
• Caregiver-First Workflow: Field staff spend less time tapping complex menus and more time delivering direct patient care, while agency dispatchers maintain complete visibility over active shifts.

Related Resources

• Florida EVV Requirements for Home Health Agencies
• The 6 EVV Data Elements Explained
• HHAeXchange EVV for Florida Home Health Agencies
• How Florida Agencies Can Reduce EVV-Related Claim Problems

This article provides general informational guidance on healthcare regulations and technology models. It does not constitute formal legal or billing advice. Always confirm current state requirements directly with AHCA and contracted Medicaid health plans.