HHAeXchange API
HHAeXchange provides EVV and homecare management solutions used by provider agencies, clinics, and state Medicaid programs to ensure in-home and community-based services are delivered and documented as required by the 21st Century Cures Act. This page is an independent design exercise that asks what a well-designed HHAeXchange API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed HHAeXchange API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing HHAeXchange product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is HHAeXchange?
HHAeXchange provides EVV and homecare management solutions used by provider agencies, clinics, and state Medicaid programs to ensure in-home and community-based services are delivered and documented as required by the 21st Century Cures Act. The platform spans caregiver mobile EVV, telephony, scheduling, visit documentation, authorization tracking, plan-of-care management, and billing/EDI connections to Medicaid and Managed Care Organizations (MCOs).
Many Medicaid programs and payer networks rely on HHAeXchange in whole or in part for EVV connectivity and billing workflows, with recent rollouts and expansions in states like Alabama, Illinois, Minnesota, New Jersey, Mississippi, and West Virginia.
Core product areas include:
- EVV (mobile app, telephony/IVR, aggregator connections)
- Scheduling and visit management
- Patient/client and caregiver/provider rosters
- Payer authorizations and service programs
- Plan of Care (tasks, required documentation)
- Exception handling, reason codes, and compliance reporting
- Export and billing support for Medicaid/MCO claims (EDI 837) and remittances (EDI 835)
An API for a platform like this would naturally organize around its core data entities:
- Clients/Members (patients)
- Caregivers/Employees (aides, nurses, staff)
- Visits (EVV check-in/out, service codes, tasks)
- Authorizations (payer/program, units, date ranges)
- Plan of Care and visit tasks
- Exceptions (late/missing calls, GPS mismatch, overlapping visits)
- Schedules/Assignments
- Claims (837P/I referencing verified visits)
- Remittances (835 payment/denial summaries)
The HHAeXchange Integration Challenge
Organizations rely on HHAeXchange daily, but turning portal-based EVV workflows into automated pipelines is hard:
- State- and payer-specific rules: Each Medicaid/MCO program may use distinct service codes, modifiers, reason codes, and EVV validation logic
- Strong enterprise security: MFA, rotating cookies, and network controls complicate headless automation
- Portal-first delivery: Visit maintenance, exceptions, and reporting often live in web apps or batch exports, not unified public APIs
- File interfaces and timing windows: SFTP/EDI feeds, batching constraints, and daily submission windows must be respected
- Compliance nuances: Visit edits require compliant reason codes and audit trails; evidence artifacts (GPS, signatures) must be preserved
What a HHAeXchange API Could Look Like
If HHAeXchange exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The sections below flesh out this hypothetical design.
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Use Cases
EHR-to-EVV Synchronization
- Push patient and caregiver rosters from your EHR into HHAeXchange - Create visits automatically from your scheduling system with correct service codes and modifiers - Maintain a single source of truth for demographics and eligibility
Authorization-Aware Scheduling and Eligibility
- Validate authorizations before scheduling or visit creation - Track remaining authorized units and prevent over-utilization - Surface program-specific rules to care coordinators
EVV Exception Resolution
- Pull exception queues and route issues (e.g., late arrival, missing check-out, GPS mismatch) to staff for resolution - Apply compliant reason codes on visit edits with audit trails - Escalate unresolved exceptions prior to claim submission
Claims Generation and Reimbursement Automation
- Bundle verified visits into 837P/I claims with payer-specific formatting - Submit via the configured channel (state portal, MCO gateway, or clearinghouse) - Track claim statuses and reconcile remittances alongside EVV evidence
Audit and Compliance
- Export complete visit packets with timestamps, locations, signatures, and reason codes - Maintain machine-readable audit trails aligned to state/MCO requirements - Prove EVV coverage and claim provenance during reviews
Technical Requirements
Authentication
Would require username/password with MFA (SMS, email, TOTP); supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination
Rate limits
Tuned for enterprise throughput while honoring licensing and usage controls
Session management
Would need automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of visits, authorizations, and claim artifacts
Security
Encrypted transport, scoped tokens, and audit logging; respects HHAeXchange entitlements and compliance requirements
Webhooks
Optional asynchronous delivery for exceptions, claim generation, and remittance updates
Latency
Design target: sub-second responses for list/detail queries
Throughput
Design target: designed for high-volume EVV and batch claims pipelines
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Versioning
Clear versioning and change management would matter as HHAeXchange evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual HHAeXchange product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.