Axxess API
Axxess is a cloud technology platform for healthcare at home, spanning home health, home care, hospice, and palliative care. This page is an independent design exercise that asks what a well-designed Axxess 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 Axxess 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 Axxess 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 Axxess?
Axxess is a cloud technology platform for healthcare at home, spanning home health, home care, hospice, and palliative care. The platform covers scheduling, clinical documentation, electronic visit verification, billing, and revenue cycle management, and serves more than 9,000 organizations worldwide managing care for millions of patients, with 200,000+ mobile app users in the field.
Core product areas include:
- Clinical solutions (Home Health, Home Care, Hospice, and Palliative Care software)
- Revenue Cycle Management (claims processing and billing)
- Axxess CAHPS and Axxess CARE (patient satisfaction tracking and staffing)
- Axxess Exchange and Business Intelligence (patient data exchange and analytics)
- Axxess Intelligence and Growth Hub (AI capabilities and self-service growth tools)
An API for a platform like this would naturally organize around its core data entities:
- Patients, Referrals, Intake records, Physician orders
- Visit schedules, EVV records with GPS verification, Clinical notes
- OASIS assessments, CAHPS data, Quality measures
- Medicare/Medicaid claims, Billing records, Payroll inputs
The Axxess Integration Challenge
Thousands of agencies run scheduling, EVV, clinical documentation, and billing on Axxess daily, but programmatic access to that data is tightly gated:
- Compliance-only public API: the only publicly documented API is the CEHRT-mandated patient-access endpoint (C-CDA/CCDS documents), a regulatory checkbox, not a business or operations API, with no self-serve signup, sandbox, or keys
- Negotiated premium access: Axxess's API Usage Policy routes expanded access through negotiated order forms with fees and email-granted call limits rather than a developer program
- A short partner list behind a contact form: roughly 15-18 hand-built Interoperability Partners across clinical, operational, and EVV categories, with a contact form as the only pathway in, leaving 9,000+ organizations without general programmatic access
- No developer surface: no developer portal, no SDKs, no webhooks, and no public technical documentation for business data
- Mobile and multi-product spread: operational data is split across web back-office products and 200,000+ mobile app users capturing EVV and point-of-care documentation in the field
- PHI and compliance constraints: OASIS assessments, EVV records, and Medicare/Medicaid claims demand HIPAA-aligned access controls and audit trails
What a Axxess API Could Look Like
If Axxess 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 endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Axxess: MCP servers for software without a public API →
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.
Potential API Endpoints
Authentication
/authenticateWould authenticate to an Axxess organization account and obtain a session token for downstream calls.
Patient Operations
/patientsWould list patients and referrals with filters for product line, branch, status, and payer.
Visits
/visitsWould retrieve completed and upcoming visits with clinician, EVV verification status, and date-range filters.
Scheduling
/schedulesWould pull visit schedules and caregiver assignments across branches and service lines.
Clinical
/oasis_assessmentsWould retrieve OASIS assessments, clinical notes, and physician orders tied to patient episodes.
Billing
/claimsWould pull Medicare/Medicaid claims, billing records, and remittance status by payer and date range.
Use Cases
Sync patient and visit data into your systems
- Pull patients, referrals, and physician orders from Axxess into a central warehouse - Stream visit completions and GPS-verified EVV records to downstream analytics tools - Keep census and intake pipelines in sync across home health, hospice, and home care lines
Automate scheduling and EVV compliance
- Pull visit schedules and caregiver assignments in near real time - Flag unverified or missed visits before they become EVV compliance problems - Feed schedule data to staffing, payroll, and capacity planning workflows
Reconcile claims and revenue cycle data
- Pull Medicare/Medicaid claims and billing records for financial reporting - Match visit activity against expected reimbursement to surface leakage - Route held or rejected claims to staff workflows without portal clicks
Power quality and compliance reporting
- Extract OASIS assessments and clinical documentation for QA review - Combine CAHPS and quality-measure data with operational metrics - Surface documentation gaps to clinical leadership dashboards automatically
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require agency credentials and MFA handled in a managed, encrypted session
Connectivity
Would build on authenticated Axxess web workflows surfaced as a normalized API across product lines
Response format
Normalized JSON across patient, visit, schedule, OASIS, and claim objects
Rate limits
Adaptive throttling tuned to your organization to avoid platform-side limits
Session management
Would need automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for census, visits, and claims with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned controls, and audit logging
Webhooks
Event-style callbacks for new referrals, visit completions, EVV events, and claim status changes
Latency
Design target: sub-second reads on cached entities; multi-second writes when posting through scheduling and billing workflows
Throughput
Design target: horizontally scaled workers sized to single-agency and multi-branch enterprise volume
Reliability
Retry, backoff, and idempotency keys for intake, scheduling, and claim operations
Versioning
Clear versioning and change management would matter as Axxess evolves
Frequently asked questions
Yes. PHI flows through an encrypted credential vault with scoped tokens, HIPAA-aligned access controls, and full audit logging so clinical and billing data stays protected.
Home health, home care, hospice, and palliative product lines are supported from one API surface, covering patients and referrals, visit schedules, EVV records, OASIS assessments, clinical notes, and Medicare/Medicaid claims, with write operations where your configuration permits them.
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 Axxess 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.