Axxess API
Axxess is a leading global technology platform for healthcare at home, powering home health, home care, hospice, and palliative care operations—EVV, scheduling, clinical documentation, and revenue cycle—for 9,000+ organizations caring for millions of patients. An unofficial API lets you programmatically pull patients, visits, schedules, OASIS assessments, and claims—and push updates like new referrals and visit changes back into Axxess without negotiating a fee-bearing partner agreement.
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)
Common 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
How Supergood Creates Axxess APIs
Supergood reverse-engineers Axxess's authenticated workflows to deliver a resilient, normalized API layer for your agency—covering patients, scheduling, EVV, clinical documentation, and claims without negotiating a fee-bearing order form or waiting on the interoperability partner queue.
- Handles agency credentials, MFA, and session continuity securely in a managed session
- Works across Axxess's home health, home care, hospice, and palliative product lines from one API surface
- Normalizes responses across patients, visits, OASIS assessments, and claims so you integrate once and rely on consistent objects
- Aligns with HIPAA-conscious access controls, scoped tokens, and audit logging for PHI
Use Axxess with AI agents: Axxess MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Axxess product lines, data entities, and authentication model. - Supergood Generates and Validates Your API
We deliver a hardened, production-ready Axxess adapter tailored to your agency configuration. - Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Axxess evolves.
Potential API Endpoints
Authentication
/authenticateAuthenticate to an Axxess organization account and obtain a session token for downstream calls.
Patient Operations
/patientsList patients and referrals with filters for product line, branch, status, and payer.
Visits
/visitsRetrieve completed and upcoming visits with clinician, EVV verification status, and date-range filters.
Scheduling
/schedulesPull visit schedules and caregiver assignments across branches and service lines.
Clinical
/oasis_assessmentsRetrieve OASIS assessments, clinical notes, and physician orders tied to patient episodes.
Billing
/claimsPull 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
Technical Requirements
Authentication
Agency credentials and MFA handled in a managed, encrypted session
Connectivity
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
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
Sub-second reads on cached entities; multi-second writes when posting through scheduling and billing workflows
Throughput
Horizontally scaled workers sized to single-agency and multi-branch enterprise volume
Reliability
Retry, backoff, and idempotency keys for intake, scheduling, and claim operations
Adaptation
Continuous monitoring of Axxess releases and per-organization configuration drift
Frequently asked questions
No. Supergood works with your existing organization credentials and authenticated sessions, so you can access your own data without negotiating a fee-bearing order form or joining the hand-built partner list.
The only publicly documented API is the CEHRT compliance-mandated patient-access endpoint serving C-CDA documents. It is a regulatory requirement, not a business API—it does not expose scheduling, EVV, claims, or operational data. Supergood provides a normalized API over those business workflows.
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.
Supergood continuously monitors Axxess releases and your organization's configuration, adapting the adapter automatically so your integration keeps running through platform updates.