Skip to content

How to Connect Your Systems to HHAeXchange

The routes in and out of HHAeXchange, the questions to ask before you start, and what to build around the connection so it keeps working.

Key takeaways
  • HHAeXchange stays the record for scheduling, visits and billing. An integration makes your other tools agree with it.
  • There are two documented routes: an EVV API for sending caregivers and visits in, and EDI files exchanged over SFTP. Which ones you can use depends on your state, payers and contract.
  • The agency requests access, not the developer. Start that request first, because it is the part nobody can speed up.
  • The connection itself is the small part. Matching records, handling rejections and retrying is what keeps it working.
  • Start with one flow that staff re-type every day.

To connect your systems to HHAeXchange, your agency first asks HHAeXchange which integration options are enabled for your account, then a developer builds a small service that moves data between HHAeXchange and your other tools on a schedule, matches each record to the right patient or caregiver, and reports anything that fails. Scheduling, visit verification and billing stay in HHAeXchange.

Most home care offices run HHAeXchange next to a task manager, a phone system, text messaging, a nursing system and a pile of spreadsheets. The same patient name, Medicaid ID and coordinator get typed into each one. This guide explains how that stops. It is based on the integration work in our home care case study and on HHAeXchange's own published documentation.

What agencies usually want connected

  • The task system, so a referral, a timesheet problem or a missed call becomes a task with the patient or caregiver already attached and the right coordinator assigned.
  • Phones and text, so a caller can be recognised and a phone agent can look up a caregiver or a visit before it answers.
  • The nursing or clinical record, so contracts and visit schedules appear in the patient profile without a nurse copying them.
  • The caregiver app or portal, so compliance items such as the annual physical or TB test show the same dates everywhere.
  • Reports, so the owner sees one set of numbers.

The ways data gets in and out

HHAeXchange publishes documentation for the following. What is switched on for a given agency varies, so treat this as a map to take into the conversation with them.

RouteWhat it is forDirection
EVV APIA third-party visit verification system sends caregiver and visit records to HHAeXchange. It uses secure web requests with short-lived access tokens.Into HHAeXchange
EDI files over SFTPStructured files exchanged on a schedule. Import files load into the portal; export files are placed for you to collect. The layouts and timing are set per state and payer programme.Both ways
Reports and exports from the portalStaff download a report and another system reads it. Useful as a stopgap, fragile as a long-term answer.Out of HHAeXchange

Two details from the documentation are worth knowing early. For the EVV API, a caregiver must exist before a visit for that caregiver can load, and records with missing required fields are rejected. And the screen where an agency manages its API credentials only appears for providers that have been set up for a third-party connection, so if you cannot find it, that is the first thing to ask about.

What to ask HHAeXchange before any code is written

  1. Which integration options are enabled for our account, for our state and each of our payers?
  2. Which data can we read, and which can we write? Patients, caregivers, schedules, visits, contracts, compliance items?
  3. What is the onboarding process? Is there a form, a test environment, or a sign-off before going live?
  4. How do we get and rotate credentials, and who at the agency holds them?
  5. How are rejected records reported, and how often can we send or collect data?

The agency makes this request, because access belongs to the provider account. Your developer can draft it. Send it before you plan anything else: it is the one step that depends on someone else's queue.

What to build around the connection

Moving a file or calling an endpoint is a few days of work. What makes an integration last is the part around it.

  • One owner for each fact. Decide which system is right when two disagree. Visits and schedules belong to HHAeXchange. A task's status belongs to the task system.
  • A reliable way to match records. Names are not enough. Use the HHAeXchange ID, and the Medicaid ID for patients, and store them on the other side.
  • No duplicates. If the same timesheet arrives twice, it should update one task, not create a second.
  • Retries and a visible failure list. Connections drop. A failed item should try again on its own and, if it still fails, appear somewhere a person looks every day.
  • A log of what changed and when, so a question about a record can be answered.
  • Least access. Each tool should see only the fields it needs. Talk through how patient information is protected with your developer and your compliance lead before going live.
Do not move scheduling or EVV out of HHAeXchange to make an integration easier. Your payers expect visits to be verified there. Connect to it and leave it in charge.

What this looked like for one agency

For the New York agency in our case study, HHAeXchange is connected to the task system, the phones, text messaging, the nursing platform and the caregiver app:

  • Timesheets, referrals, calls and texts become de-duplicated tasks with retries, so nothing is lost when a connection hiccups.
  • The coordinator on a patient stays in sync between HHAeXchange and the task system.
  • Contracts and visit schedules flow into the patient profile in the nursing platform.
  • An employment-verification phone line checks the caregiver in HHAeXchange before it sends a letter.
  • Compliance items such as TB, flu and the annual physical are shown in one view.

The full account is in the case study.

Where to start

Pick the one flow where staff re-type the most, usually referrals or timesheets into the task system. Get access sorted, connect that flow, and run it for a few weeks before adding the next. If you are also changing clinical systems, read our checklist for moving patient records first. If you would like us to look at your setup, book a free 30-minute review, or see what we build for home care agencies.

Frequently asked questions

Does HHAeXchange have an API?

HHAeXchange documents an EVV API for sending caregiver and visit records in from a third-party system, and file-based EDI exchanges over SFTP. What your agency can use depends on your state, your payers and your contract, so the first step is to ask HHAeXchange which options are enabled for you.

Who has to request integration access, the agency or the developer?

The agency. Access belongs to the provider account, so the request goes from the agency to HHAeXchange's integration support team. Your developer can prepare the request and handle the technical testing, but the agency should own the credentials.

Does an integration replace EVV or scheduling in HHAeXchange?

No. Visits stay scheduled and verified in HHAeXchange. An integration reads from it and writes to it so your other tools show the same facts without anyone typing them again.

How long does an HHAeXchange integration take?

It depends on what access you already have and how many systems you are connecting. Getting access and passing any required testing is usually the slow part and is outside the developer's control, so start that request early.

What should we connect first?

The place where staff re-type the most. For many agencies that is the task system: referrals, timesheets and calls should become assigned tasks with the patient or caregiver already attached.

What does it cost?

We work on a monthly plan, not a fixed project price: $1,200 a month for 40 hours, $2,100 for 80, or $3,600 for 160, and you can change plan or cancel at any time. Most agencies start with one connection and add the next when the first is running.