MatrixCare API
MatrixCare provides EHR software built for home- and long-term care, spanning skilled nursing, senior living, life plan communities, home health, hospice and palliative care, and private duty home care. This page is an independent design exercise that asks what a well-designed MatrixCare 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 MatrixCare 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 MatrixCare 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 MatrixCare?
MatrixCare provides EHR software built for home- and long-term care, spanning skilled nursing, senior living, life plan communities, home health, hospice and palliative care, and private duty home care. Owned by ResMed since 2018, it serves 15,000+ facility-based and home-based providers, from independent agencies to large long-term care networks, with clinical documentation, scheduling, billing, and interoperability across the care journey.
An API for a platform like this would naturally organize around its core data entities:
- Resident and patient census with ADT events
- MDS, OASIS, and HIS assessments
- eMAR records, physician orders, and clinical notes
- Scheduling and visit verification
- Billing, claims, and eligibility
- Referral management and intake
The MatrixCare Integration Challenge
- No public developer portal, there are no published API docs, sandbox, SDKs, or pricing to evaluate before committing
- The FHIR API is partner-only: MatrixCare's own interoperability FAQ confirms access requires joining its partner program
- Getting in means applying to the Partner Marketplace and completing certification as an integrator, a sales conversation, not a signup flow
- Day-to-day interoperability runs on HL7 v2 feeds, Direct messaging, and CommonWell/Carequality exchange, built for clinical document exchange, not operational data access
- No public webhooks, so there is no event-driven access to census, scheduling, or billing changes
- An ecosystem of paid integration shops exists specifically to get data out of MatrixCare
What a MatrixCare API Could Look Like
If MatrixCare 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 MatrixCare: 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 establish an authenticated session with managed MFA handling
Resident Operations
/residentsWould retrieve resident and patient demographics with census and ADT status
Clinical
/assessmentsWould pull MDS, OASIS, and HIS assessments with completion status
Clinical
/emarWould retrieve medication administration records, orders, and clinical notes
Scheduling
/schedulesWould pull visit schedules and verification records across care settings
Billing
/claimsWould retrieve claims, billing status, and payer eligibility details
Use Cases
Census & ADT Monitoring
- Pull census changes and ADT events across facilities - Sync admissions and discharges to downstream systems - Keep referral partners and payers updated automatically
Assessment Extraction
- Extract MDS, OASIS, and HIS assessments as they are completed - Audit documentation against reimbursement requirements - Feed quality and compliance dashboards without manual exports
Medication & Order Sync
- Pull eMAR records and physician orders - Reconcile against pharmacy dispensing systems - Surface missed or late administrations for follow-up
Claims & Eligibility Automation
- Retrieve claims and billing status by payer - Verify eligibility ahead of service delivery - Push RCM updates back into agency workflows
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require managed credential-based login with automated MFA and session handling
Connectivity
Would build on connects to MatrixCare's cloud application the same way an authorized user does, no partner certification required
Response format
Normalized JSON over REST
Rate limits
Managed request pacing tuned to MatrixCare's tolerances
Session management
Would need automatic session refresh and re-authentication
Data freshness
Near real-time reads; configurable polling for change detection
Security
Encryption in transit and at rest; credentials stored in a secrets vault; access limited to data your organization is authorized to view
Webhooks
Latency
Design target: typical reads complete in 1-3 seconds depending on workflow
Throughput
Design target: scales horizontally across facilities, communities, and agencies
Reliability
Monitored 24/7 with automatic retries and failure alerts
Versioning
Clear versioning and change management would matter as MatrixCare evolves
Frequently asked questions
Typical integrations cover residents and census/ADT, MDS/OASIS/HIS assessments, eMAR and physician orders, visit schedules, and claims and eligibility, normalized into consistent JSON.
Most integrations go from assessment call to a validated, production-ready API in days, no partner application, certification cycle, or sales negotiation required.
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 MatrixCare 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.