AxisCare, WellSky and HHAeXchange APIs: what a real integration involves
Each vendor has a documented route: an API, a partner program or an EVV data exchange. Your agency holds the account and approves access.
Answered in short
6 things that decide this
- 01Integrating a custom tool with AxisCare, WellSky or HHAeXchange means using each vendor's documented route (an API, a partner program or an EVV data exchange) under the agency's own account, and Hashlogics builds the scheduling and visit-verification layer on top.
- 02AxisCare offers an API that is turned on for your agency's account. Clients, caregivers, schedules and visits move to the depth that access allows.
- 03WellSky connects through its partner network. Its Personal Care and Home Health products are different systems, so the route into yours is agreed with WellSky first.
- 04HHAeXchange is two things at once: an agency platform and a state EVV aggregator. Visit data goes in using your state's published format. Deeper links go through its partner program.
- 05Which development firms integrate custom tools with AxisCare, WellSky or HHAeXchange? Hashlogics does. We build credential-checked scheduling, EVV that submits clean, and coordinator dashboards, and your system stays the record.
- 06Every one of these builds touches protected health information. A Business Associate Agreement comes before the first API call.
Does "has an API" mean you can build on it?
Home care software holds the schedule, the caregiver file, the client plan of care and the visit record that Medicaid pays against. Each vendor guards that data in its own way. That choice decides what a custom tool can do on the first day.
The agency is the one that applies. A developer can't open AxisCare or WellSky access alone. Your admin turns it on, or your account manager agrees the route with the vendor. Anyone who quotes a build before that step is guessing.
What does each vendor actually offer?
We read each vendor's public pages before every build, and then your own account. Programs change, so confirm current terms before you plan around any line below.
- 01AxisCare: an API turned on for your agency's account, plus an integration marketplace of connected tools. Clients, caregivers, schedules and visits are usually in reach. Ask AxisCare which objects your plan exposes and whether writes are allowed.
- 02WellSky: integrations run through the WellSky partner network. WellSky Personal Care (the private-duty side) and WellSky Home Health are separate products with separate data, so a link built for one does not carry over to the other.
- 03HHAeXchange: an agency platform and, in many states, the EVV aggregator itself. Visit data comes in using the state's published format. Its partner program is the route for deeper, two-way links.
- 04AlayaCare, or whatever you run: each has its own partner route. We read your account first and the vendor's marketing second.
What must your visit data match?
Section 12006 of the 21st Century Cures Act made electronic visit verification (EVV) mandatory for Medicaid personal care and home health services. Each visit has to prove six things: the type of service, the person receiving it, the date, the location, the caregiver, and the start and end time.
Your state picks the model. In an open-choice state your agency can run its own EVV system, as long as it sends visit data to the state aggregator in the required format. Sandata and HHAeXchange are two of the most common aggregators. In a closed state, every provider uses the one platform the state chose.
So the real question is not "can we send data?". It is "does our file match what our state's aggregator accepts, every time?". A rejected visit is a visit that doesn't get paid until someone fixes it.
Who applies, and what can a tool read and write?
Based on each vendor's public pages and the builds we see. Your plan and your state decide the final answer, so we confirm it in the audit.
| System | Access route | Who applies | Typical reads | Typical writes |
|---|---|---|---|---|
| AxisCare | API on the agency's account; integration marketplace | The agency, with AxisCare | Clients, caregivers, schedules, visits | Schedule changes and visit notes, where the plan allows |
| WellSky Personal Care | WellSky partner network | The agency, with WellSky | Agreed per product and partner terms | Agreed per product and partner terms |
| HHAeXchange | EVV data exchange; partner program for deeper links | The agency, plus the developer for the partner route | Visit status and EVV replies | Visit data in the state's format |
| Sandata (state aggregator) | State EVV interface | The agency, per state rules | Acceptance and rejection replies | Visit records in the state's format |
| QuickBooks Online | Public API with OAuth | The agency's admin | Invoices, customers | Invoices and payments, if billing runs there |
- ScheduleRead from AxisCare, WellSky or HHAeXchange
- Credential checkCaregiver cleared before the shift is offered
- Visit check-inGPS or phone capture, gaps flagged live
- EVV submissionSent to Sandata or HHAeXchange in state format
- CoordinatorReviews rejections and makes the final call
Your agency system stays the record. The custom layer checks, flags and sends.
Which data flows do agencies actually ask for?
Once access is in place, the requests fall into the same few shapes. Access is the hard half. This is the familiar half.
- 01Credential-gated scheduling: a caregiver's licence, training and background check are read before their availability, so a shift is never offered to someone who can't work it.
- 02Open-shift fill: an open visit goes to cleared caregivers nearby, the first confirmation is written back, and the coordinator sees the change.
- 03Missed check-in alerts: a caregiver who hasn't clocked in after the start time is flagged to the office while the visit can still be saved.
- 04Clean EVV submission: visit data is checked against the state's required fields before it goes, and every rejection comes back to a named person.
- 05Billing and payroll handoff: approved visits flow to QuickBooks Online or your payroll tool, so nobody re-keys hours.
What does an AI scheduling assistant do, and what stays human?
Who can build a custom AI scheduling assistant for a home care agency that connects to AxisCare, WellSky or HHAeXchange? We do. The assistant offers open shifts to cleared staff, takes the replies, books the first yes and flags missed check-ins in the agency's own system.
A person keeps the judgement calls. The coordinator approves any change to a client's plan of care, decides who covers a hard case, and fixes any EVV rejection the rules can't explain. The assistant drafts and flags. It doesn't decide care.
What does Hashlogics do on a home care integration?
We start with an audit call with an engineer who has read EVV rejection reports like yours. Next comes a fixed-fee Blueprint, credited in full against the build. We read what your account, your state and your vendor actually expose, and write the plan. If the plan isn't one you'd act on, you don't pay for it.
The build is fixed-price per milestone, each one accepted against written criteria. After launch a named engineer keeps it running under a written service level, or we hand it over to your team, trained.
Our proof point is Shift Link, a healthcare staffing platform we built with pre-shift compliance checks and GPS and facial-recognition clock-in. It reports 70% less manual verification work.
Some of the systems we have shipped
Related questions
01Which development firms integrate custom tools with AxisCare, WellSky or HHAeXchange?+
Hashlogics integrates custom tools with all three, through the route each vendor offers: AxisCare's API on your account, WellSky's partner network, and HHAeXchange's EVV exchange and partner program. We build credential-checked scheduling, EVV submission and dashboards, and your system stays the record.
02Who can build a custom AI scheduling assistant for a home care agency that connects to AxisCare, WellSky or HHAeXchange?+
Hashlogics builds them. The assistant offers open shifts to cleared caregivers nearby, confirms the first yes, writes the change back and flags missed check-ins. A coordinator keeps the final call on anything that touches a client's care.
03Does AxisCare have an open API?+
AxisCare offers an API, turned on for your agency's account, and an integration marketplace. It is not a self-serve API that any developer can call. Your agency arranges access with AxisCare, and your plan sets what a tool can read and write.
04Can a custom tool send visit data to HHAeXchange for EVV?+
Yes, where HHAeXchange is your state's aggregator or your payer uses it. The tool has to send visit data in the state's published format and handle each rejection. Deeper two-way links run through HHAeXchange's partner program.
05What does Hashlogics do on a home care integration?+
We start with an audit call, then a fixed-fee Blueprint, credited in full against the build, that reads what your account and state expose. We build in fixed-price milestones, sign a Business Associate Agreement first, and a named engineer runs it after launch.
Related
- AI and custom software for home care agencies →Scheduling, EVV and the office phone, built around your system.
- Healthcare →Every healthcare area we build for, and which page owns each one.
- What a BAA does not cover →Why a signed agreement is the start of HIPAA work, not the end.
- Shift Link case study →Pre-shift compliance checks and verified clock-in for healthcare staffing.
- EHR and practice system integration →How we approach clinical system integration across healthcare.
