EHR IntegrationHealthcare InteroperabilityPost-Acute Care

MatrixCare Integration Guide: Access, Routes, Cost (2026)

November 14, 202622 min readUpdated Nov 14, 2026
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

MatrixCare Integration Guide: Access, Routes, Cost (2026)

MatrixCare is an electronic health record (EHR) for post-acute care. Its partner form lists seven care settings: skilled nursing, senior living, life plan community, private duty, palliative care, hospice and home health.

This guide is for a buyer or product lead who has to connect a product to MatrixCare. It covers who to apply to, what opens up, what MatrixCare leaves unpublished, and what to ask before you commit.

MatrixCare integration at a glance

Question Short answer
Who grants access? MatrixCare, through its Partner Marketplace and its Certified Integrator Program.
Who signs for the customer? A duly authorized representative of each customer. The form names no job title.
Is there a public API reference or sandbox sign-up? No. We found neither on MatrixCare's site on Nov 14, 2026.
Which routes exist? They differ by product line. The sources show a census feed, HL7 messages, a FHIR API for home health and hospice, and national networks.
What does it cost? MatrixCare publishes no fee. Net Health documents a MatrixCare integration fee of $10 or $30 per site per month that it passes to its customers.
How long does it take? MatrixCare publishes no time. Named partners quote their own customers anything from 48 hours to 30 days, for integrations that already exist.
What is the biggest limit? MatrixCare activates most integrations one facility and one care setting at a time.

What can you build on a MatrixCare integration?

Nine use cases follow, from census sync to supply orders. Each use case below points to a row in the table of what you can read and write. MatrixCare publishes no build times, so this guide gives no build estimate. Build complexity is our own rating.

Nine use cases for a MatrixCare integration. Build complexity is our own rating. Open a use case below for the detail.

1. Keep a therapy app's resident list in step with the census

medium
  • Who it is for: therapy and rehab software companies.
  • The value: therapists see admissions, discharges and transfers without typing them twice.
  • Build complexity: medium.
  • How well it works: well for census data. ADT (admission, discharge and transfer messages) is the largest data group on MatrixCare's partner list, with 99 vendor rows. Net Health documents that its Optima integration receives ADT messages through the MatrixCare Census Subscriber Feed. See row P1.

2. Send admissions and food allergies to a dining system

medium
  • Who it is for: dining and nutrition software companies.
  • The value: the kitchen knows who arrived and what each resident cannot eat.
  • Build complexity: medium.
  • How well it works: well for facility products. The partner list has a Dietary group with 16 vendor rows. MealSuite documents that its MatrixCare interfaces carry ADT messages and food allergies. See rows P1 and P12.
  • For scale: MealSuite documents that it rates each of its own MatrixCare interfaces a three-week project. That figure covers an interface that already exists.

3. Tell a hospital or care-transition team when a resident moves

medium
  • Who it is for: care coordination and referral platforms.
  • The value: the discharging hospital sees where the patient went and gets a care summary.
  • Build complexity: medium.
  • How well it works: well for events and summary documents. WellSky's marketplace listing says ADT data and Continuity of Care Documents (CCDs, a standard care summary) flow from MatrixCare into its product. See rows P1 and P2.

4. Write therapy or wound notes back into the chart

high
  • Who it is for: therapy, wound care and other clinical point-solution vendors.
  • The value: the whole care team sees the note inside MatrixCare.
  • Build complexity: high.
  • How well it works: shown for named partners. MatrixCare publishes no write specification. Rehab-Connect's listing says its therapy notes render in the MatrixCare EHR through what it calls the Documentation API. WoundZoom's listing says it transfers wound assessments into MatrixCare over an HL7 interface. See row P5.

5. Upload signed documents to the resident's chart

medium
  • Who it is for: secure messaging, e-signature and intake vendors.
  • The value: staff stop printing, faxing and scanning.
  • Build complexity: medium.
  • How well it works: shown for one named partner. Mediprocity's listing says teams can upload PDF attachments to the patient chart. Aline documents that its own integration fails on any document over 15 MB. See row P5.

6. Bring remote monitoring readings into a home health record

high
  • Who it is for: remote patient monitoring and telehealth vendors.
  • The value: nurses see vitals in the record they already use.
  • Build complexity: high.
  • How well it works: partly documented. MatrixCare's home health and hospice FAQ, with a 2019 footer, describes a FHIR API that partners use to pull data. FHIR is a web standard for exchanging health records. Health Recovery Solutions documents that its interface records vitals in the Flow Sheets and Communication Note sections. MatrixCare's own pages do not describe a FHIR write. See row P4.

7. Post payroll and general ledger entries

medium
  • Who it is for: payroll, accounting and expense software companies.
  • The value: finance staff stop keying the same totals into two systems.
  • Build complexity: medium.
  • How well it works: shown for named partners. The partner list has Financial, Enterprise financials and Payroll groups. ProLiant's listing says it sends a client-specific general ledger to MatrixCare. See row P7.

8. Build an operator dashboard on the customer's own data

medium
  • Who it is for: analytics vendors and operators with their own data team.
  • The value: one view of census, clinical and financial numbers across facilities.
  • Build complexity: medium.
  • How well it works: well for reading. MatrixCare's MyData product gives a customer a replicated copy of its data for its own reporting tool or data warehouse. The sources show it as a copy to read from. See row P10.

9. Pre-fill a supply order with patient demographics

low to medium
  • Who it is for: medical supply and equipment companies.
  • The value: staff order supplies without retyping the patient's details.
  • Build complexity: low to medium.
  • How well it works: shown for named partners. Cardinal Health at-Home's listing says its integration imports patient demographics from MatrixCare. Medline documents that its home health interface takes demographics by file upload, or by HL7 ADT on request. See row P3.

The nine MatrixCare use cases compared

Use case Who it is for Build complexity (our rating) Row in the read and write table
1. Keep a therapy app's resident list in step with the census Therapy and rehab software companies Medium P1
2. Send admissions and food allergies to a dining system Dining and nutrition software companies Medium P1 and P12
3. Tell a hospital or care-transition team when a resident moves Care coordination and referral platforms Medium P1 and P2
4. Write therapy or wound notes back into the chart Therapy, wound care and other clinical point-solution vendors High P5
5. Upload signed documents to the resident's chart Secure messaging, e-signature and intake vendors Medium P5
6. Bring remote monitoring readings into a home health record Remote patient monitoring and telehealth vendors High P4
7. Post payroll and general ledger entries Payroll, accounting and expense software companies Medium P7
8. Build an operator dashboard on the customer's own data Analytics vendors and operators with their own data team Medium P10
9. Pre-fill a supply order with patient demographics Medical supply and equipment companies Low to medium P3

How do you get access to a MatrixCare integration?

MatrixCare has no self-service sign-up. Access has two layers. The vendor gets approved once. Each customer facility then gets authorized.

The steps

The vendor gets approved once, and each customer facility then gets authorized and activated.
Step Who acts What happens
1. Apply Vendor Apply to join the Partner Marketplace. MatrixCare then schedules a call.
2. Describe the integration Vendor The form asks for the care settings and a description of up to 150 words.
3. Certify Vendor and MatrixCare The program for approved vendors is the Certified Integrator Program.
4. Authorize each facility Vendor and customer The vendor collects the facility information and an authorized signature.
5. Submit Vendor or customer The form goes to authorization.form@matrixcare.com. A customer can also use an online form. The online form asks for the address of the customer's MatrixCare system.
6. Activate MatrixCare The Technical Services team acts for each care setting at each facility.
7. Confirm MatrixCare MatrixCare sends a confirmation email after it confirms the information.

After step 1, the only stated next step is that MatrixCare makes contact. A customer who wants a listed integration can also start from the "I want this integration" button on a marketplace listing.

In a 2018 press release MatrixCare described step 3 in one line. It defines the integration points with the vendor and then formally certifies the result. The current toolkit names one MatrixCare contact for technical certification and one for contracts. In April 2017 MatrixCare said it connects only fully validated parties to customer environments.

Who signs on the customer side

The signer must be a "duly authorized representative" of the customer. The form names no job title. The form states a policy of written customer consent before data is shared.

The form asks for a different identifier for each facility environment.

Environment Identifier the form asks for
MatrixCare360 (skilled nursing) MatrixCare Billing Client ID
SigmaCare (a second skilled nursing environment) SigmaCare Account ID
Life Plan Community (LPC) LPC Company Code

Plan for two snags. The Billing Client ID is hidden from some customer users. MatrixCare sometimes contacts the customer to confirm the facility before it activates.

A vendor is allowed to write its own version of the form. MatrixCare must approve that version first.

Why there are no public API documents

This point explains most of what follows.

All 27 MatrixCare listings on the federal record are retired, and none was ever certified to an API criterion.

A US vendor with a federally certified API must publish its API documentation at a public link. It must also publish its terms, including fees, restrictions and limitations. These rules apply to developers of products certified to the API criteria. The certifying body is ONC, the federal health IT office. Its public register is the Certified Health IT Product List (CHPL).

MatrixCare has no such product. CHPL holds 27 MatrixCare listings. All 27 have the status Retired, and none is 2015 Edition. The newest was certified on Apr 30, 2020 and retired on Jun 30, 2020. The 2014 Edition listings covered five criteria: access control, automatic log-off, emergency access, integrity and quality management. No listing was ever certified to an API criterion.

So the usual paper trail is missing. The federal record holds no API documentation link and no list of API addresses. It holds no real world testing plan or results. The disclosures link on the record leads to a general privacy policy. ONC's Lantern directory of FHIR endpoints lists none from MatrixCare.

Read this finding with care. It says MatrixCare is not certified. It does not say MatrixCare has no API. MatrixCare's own pages name APIs and FHIR, as the table of routes shows. The practical effect is that MatrixCare decides what to publish, and access runs through its partner program.

What MatrixCare does not publish about access

MatrixCare does not publish the certification steps, the pass criteria or the test cases. It does not publish whether a partner gets a sandbox. Ask MatrixCare:

MatrixCare publishes the access steps and its partner list, and leaves fees, limits, times and specifications unpublished.
  • What are the certification steps, and who signs off?
  • Is there a contract, a security review or an insurance requirement?
  • Which job titles at the customer do you accept as signers?
  • Does one authorization cover every facility in an enterprise account?

What does MatrixCare access give you?

Access gives you a live connection that MatrixCare activates facility by facility. The authorization covers the customer's database or a static copy of it. MatrixCare does not publish whether a partner gets a test environment.

Environments

MatrixCare does not publish whether a partner gets a sandbox or test environment. A host named sandbox.matrixcare.com exists and shows a login page only.

Production is not one system. The facility products run as three environments with separate identifiers. Home Health and Hospice has its own sign-in page, and so does SigmaCare. Confirm early which environment your customers use.

What the authorization covers

The authorization covers the customer's database or a static copy of it. It covers all facilities in an enterprise account, and it can be two-way. That is the legal scope. Activation still happens facility by facility.

What data partners exchange today

MatrixCare publishes no field list or message specification. The best public view is its consolidated partner list. For each vendor, the list shows the receiving MatrixCare system and the data group exchanged.

ADT is the largest data group on MatrixCare's partner list, with 99 vendor rows on Nov 14, 2026.

On Nov 14, 2026 the list held 349 vendor rows. One row can carry several data groups.

Data group on the partner list Vendor rows, Nov 14, 2026
ADT (admission, discharge, transfer) 99
Clinical (SigmaCare) 91
Census 77
Clinical 68
HIE/RHIO (state and regional exchanges) 29
Financial 20
Dietary 16
Resident Profile 11
MDS (the federal nursing home assessment) 11
Billing 8
Medication Management 8
Payroll 6
User Access 5
Therapy 3

These counts change as MatrixCare edits the page. They show which data groups most partners exchange. They are not a list of fields.

The Partner Marketplace is the public catalog of these partners. On Nov 14, 2026 its site map held 118 listings. Skilled nursing was the most common tag, on 97 listings.

The customer's own data copy

MyData is a separate MatrixCare product. It gives a customer a replicated copy of its MatrixCare data for its own reporting tool or data warehouse. In April 2017 MatrixCare said a certified third party can connect to that copy with the customer's explicit authorization. We found no current page that repeats this policy.

What are the ways to integrate with MatrixCare?

MatrixCare names APIs as the general mechanism behind marketplace integrations. It gives no detail. The table lists every route the sources show. Rows marked "partner statement" describe one partner's own integration. They are not MatrixCare specifications.

The route depends on the customer's MatrixCare product, and several routes rest on one partner's own statement.
Route What the source says Product line Fits when
Partner program integration MatrixCare defines integration points with the vendor on its API layer and certifies the result (2018 press release). Facility products You sell a product to many MatrixCare customers.
Census feed (partner statement) Net Health documents that its Optima integration receives ADT messages through the MatrixCare Census Subscriber Feed, pushed every five minutes. MealSuite documents the same feed for MatrixCare 360 and Senior Living. MatrixCare 360, Senior Living You need admissions, discharges and transfers.
HL7 over a file connection (partner statement) MealSuite documents that its Life Plan Community interface uses an SFTP connection that carries HL7 messages. Life Plan Community Your customer runs LPC.
SOAP API (partner statement) MealSuite documents that its SigmaCare interface uses a SOAP API that carries HL7 messages. SigmaCare Your customer runs SigmaCare.
FHIR API Partners pull data through a FHIR API (FAQ with a 2019 footer). Current pages name FHIR-enabled integrations. Home health and hospice You need to read home health or hospice data.
HL7 v2 and CCD push Agencies push HL7 V2 and CCD messages on admission, discharge and transfer events (FAQ with a 2019 footer). Home health and hospice You need event notices from an agency.
File upload (partner statement) Medline documents that its home health interface takes demographics by SFTP upload, or by HL7 ADT on request. Home health A daily file is enough.
National networks Facility products exchange records through QHINs, by way of Health Gorilla. Home health and hospice use CommonWell and Carequality. All You need hospital records only.
Direct Secure Messaging Messages and documents travel on the DirectTrust network. Skilled nursing You exchange referrals with outside providers.
Pharmacy Two-way NCPDP e-prescribing, plus pharmacy-centric order entry (2019 press release). Facility products You are a pharmacy or pharmacy system.
State and regional exchanges Exchanges such as CRISP appear on the partner list as live partners. Facility products A state exchange already holds the data you need.
Third-party connector A connector company appears on the partner list as a live vendor. Skilled nursing A connector already covers your data.
MyData The customer gets a replicated copy of its own data. Facility products You report on data and do not write back.

Three terms in the table need a line each. HL7 v2 is the older message standard that most hospital and nursing systems use for events. SFTP is a secure way to move files. A QHIN is a network approved under TEFCA, the federal framework for nationwide record exchange.

Check two things before you pick a route. First, MatrixCare's own documents do not name a transport for any product. The words "SFTP" and "SOAP" appear in none of twelve MatrixCare documents we searched. Second, the oldest technical source is a white paper dated April 2017. It says integration runs through an integration engine and "Public APIs". It says the engine supports file transfer, sockets, web services and REST. Treat it as history until MatrixCare confirms it.

Want a team to scope the route with you? See our MatrixCare integration service.

What can you read and write in MatrixCare?

MatrixCare publishes no list of readable and writable fields. This table is built from MatrixCare's product pages, its partner list and named partner listings. "Read" means data leaves MatrixCare. "Write" means data enters it.

Row Function Read Write Evidence
P1 Admission, discharge and transfer events Yes Not shown ADT is on 99 partner rows and Census on 77. WellSky's listing says ADT data flows into its product.
P2 Care summary documents (CCD, C-CDA) Yes Yes, through networks WellSky's listing says CCDs flow into its product. The network link shares the facility's documents outward.
P3 Patient demographics Yes Not shown Cardinal Health at-Home's listing says it imports patient demographics, using HL7 messaging. The Optima by Net Health listing says resident demographics flow to Optima.
P4 FHIR read (home health and hospice) Yes Partner statement only Partners pull data through a FHIR API (FAQ with a 2019 footer). Health Recovery Solutions documents that its interface records vitals in MatrixCare.
P5 Clinical notes and documents Not shown Yes, for named partners Rehab-Connect's listing says its therapy notes render in the EHR. WoundZoom's listing says it sends wound assessments over HL7. Mediprocity's listing says teams upload PDFs to the chart.
P6 Referral data from outside providers Not shown Yes Direct Secure Messaging imports demographics, medications, allergies and diagnoses.
P7 Financial and payroll data Not shown Yes, for named partners ProLiant's listing says it sends a general ledger to MatrixCare. Private duty interfaces with payroll, general ledger and payment systems.
P8 Pharmacy orders Yes Yes NCPDP two-way e-prescribing (2019 press release).
P9 Hospice medication and equipment Yes Yes FHIR-enabled pharmacy benefit manager integrations pull demographics and medications. Hospice has a two-way equipment ordering interface with Brightree.
P10 The customer's own data copy (MyData) Yes Not shown MyData provides a replicated copy of the customer's data.
P11 User accounts and single sign-on Yes Not shown Mediprocity's listing says it integrates through single sign-on. User Access is on 5 partner rows.
P12 Dietary data Yes Not shown Dietary is on 16 partner rows. MealSuite documents that its interfaces carry ADT and food allergies.
P13 Visit verification (private duty) Yes Not shown Private duty has integrations with electronic visit verification vendors.
P14 State and regional exchanges Yes Yes Exchanges appear on the partner list as live partners.

"Not shown" means no source we read shows it. It does not mean MatrixCare forbids it. Ask MatrixCare for the field list behind each row you depend on.

What is not possible with a MatrixCare integration?

MatrixCare does not publish a current list of data or functions that are closed to partners. The limits below come from what the sources show.

  • No self-service access. You cannot sign up, get keys and start testing.
  • No enterprise-wide switch. Each care setting at each facility needs its own action by MatrixCare.
  • No public endpoint list. The federal FHIR endpoint directory lists none from MatrixCare.
  • No confirmed partner FHIR API for facility products. In April 2017 MatrixCare planned FHIR support for 2018. No current page we read confirms it for skilled nursing.
  • No use of the badge before certification. Only certified vendors are allowed to display the Certified Integrator badge.

MatrixCare stated three policies in its April 2017 white paper. No current page repeats or withdraws them. Ask whether each still holds.

  • MatrixCare can refuse an integration at its sole discretion on grounds of patient safety, customer harm or unpaid use of its intellectual property.
  • Directly competing products get basic integration. MatrixCare reserves deeper integration for its own modules.
  • A customer is not allowed to sell to others a tool built on its own data access.

The usual workarounds

  • Use a partner that is already live. A connector company is on the partner list for skilled nursing.
  • Use the customer's data copy for reporting. MyData gives the customer a copy of its data for reporting.
  • Use the networks for hospital records. Facility products reach national networks through QHINs.

What are the MatrixCare integration limits?

MatrixCare does not publish rate limits, payload limits, paging rules, history depth or sandbox limits. The words "rate limit" and "throttle" appear in none of twelve MatrixCare documents we searched.

Here is what the sources do state.

  • Scope. Activation is per facility and per care setting.
  • Refresh of the data copy. The April 2017 white paper gives the MyData refresh as every 15 minutes. The same paper also says several times per day. We found no current figure.
  • Network coverage. Carequality warns that a listed connection can be one-way or inactive.

Named partners document limits in their own integrations. These are partner statements. None is a MatrixCare specification.

Partner What the partner documents about its own integration
Aline Its integration fails on any document over 15 MB. It sends documents once, with the resident push. A second push can create duplicates.
AR Proactive Its integration is for the MatrixCare 360 product only. It imports the AR Aging report every hour.
Net Health Its Optima integration receives ADT messages every five minutes.

It is not known whether Aline's 15 MB limit belongs to MatrixCare or to Aline.

Ask MatrixCare:

  • What are the rate and size limits on each interface?
  • How far back does each feed go on first load?
  • How much notice do you give before an interface changes?

How much does a MatrixCare integration cost?

MatrixCare does not publish any fee for partner access, certification or facility activation. The current program documents contain no fee amount. Because MatrixCare has no certified API, the federal rule on publishing API fees does not apply to it.

The only MatrixCare statements about money are from its April 2017 white paper. A partner agreement defines commercial terms, including any startup or ongoing fees. MatrixCare expects to be compensated for use of its intellectual property. Partner products are generally sold separately by the partner. MyData was a licensed item. None of these gives an amount, and none is confirmed on a current page.

Named partners document what they bill or were billed. These are partner statements about their own products.

  • Net Health documents that it passes a MatrixCare integration fee through to its customers. The fee is $10 per site per month for sites enabled before Jan 1, 2026. It is $30 for sites enabled on or after that date. Net Health documents a start date of Jan 1, 2026 for MatrixCare 360 sites and Apr 1, 2026 for LPC and SigmaCare sites.
  • Aline documents that some functions of its integration can carry a monthly fee.
  • How's Mom documents that activating its integration needed a one-time fee per facility payable to MatrixCare. The page was last edited in 2022.

We found no MatrixCare fee schedule that confirms any of these figures. Do not budget from them. Use them as questions.

Ask MatrixCare:

  • Is there a fee to join the program or to certify?
  • Is there a monthly fee per facility, and who is billed, the vendor or the customer?
  • Is there a one-time activation fee?
  • Does MyData carry a separate license today?

How long does a MatrixCare integration take?

MatrixCare does not publish a time for partner approval, certification or facility activation. The current program documents state no number of days or weeks. After a vendor applies, the stated next step is that MatrixCare makes contact. The one dated rule is for the exit. A cancellation takes effect on the date MatrixCare receives the request.

Named partners tell their own customers what to expect. These are partner statements about existing integrations. They do not cover the time to get approved or to build something new.

Partner What the partner tells its customers
AR Proactive With MyData already in place, allow 2 weeks on the MatrixCare side. Without MyData, allow 4 weeks. Add 1 week on the AR Proactive side.
VitalCare Connect MatrixCare's processing of the authorization form can take up to 30 days.
MealSuite A standard project finishes within three weeks, depending on activation on the EHR side.
Medline Its home health interface takes up to 4 weeks.
How's Mom Setup took 1 to 2 weeks (page last edited in 2022).
Cliniconex Live within 48 hours of MatrixCare API activation.
Net Health It moved its MatrixCare 360 customers to the new census feed between June and September 2025.

The partner figures differ from each other. Plan each facility as its own activation, because that is how MatrixCare processes them.

Ask MatrixCare:

  • How long does approval take after the first call?
  • How long does certification take, and what holds it up?
  • What is the turnaround on an authorization form?
  • Do you activate facilities in batches for an enterprise customer?

How do you build a MatrixCare integration, step by step?

MatrixCare does not publish a build guide, an authentication method or an API version. The order below follows the access process that MatrixCare does publish.

  1. Name the product line and the environment. The facility products have three environments. Home Health and Hospice has a separate sign-in.
  2. Check the partner list. See whether a live partner already exchanges the data group you need.
  3. Apply and take the first call. Use the Partner Marketplace form.
  4. Agree the integration points. MatrixCare defines them with the vendor (2018 press release). Ask for the specification, the sign-in method and a test environment at this stage.
  5. Build and map. In April 2017 MatrixCare said each interface uses a message map defined for that interface.
  6. Certify. The toolkit names a MatrixCare contact for technical certification and support.
  7. Authorize each facility. Collect the facility information, the identifier and an authorized signature.
  8. Activate. MatrixCare's Technical Services team acts per care setting and per facility. MatrixCare then sends a confirmation email.
  9. Keep the OID. At onboarding, a MatrixCare technician gives the partner an identifier called an OID. A partner's cancellation email must include it.
  10. Run support. After go-live, either the customer or the partner raises issues with MatrixCare support.

To cancel, the customer or partner emails Integration.cancel.req@matrixcare.com with the date and the customer information.

The access path in one view

Vendor applies. MatrixCare calls. Both agree the integration points. MatrixCare certifies. The customer signs. The vendor submits the form. MatrixCare activates the facility and confirms.

The data path, as far as it is published

For the facility products, the only description is from April 2017. Once a party is authorized, MatrixCare defines an encrypted route between that party and the customer's instance. For home health and hospice, the FAQ with a 2019 footer describes two paths. Partners pull data through a FHIR API. Agencies push HL7 V2 and CCD messages on events.

Which MatrixCare quirks should you know?

The public record on MatrixCare has old names, two live versions of one FAQ and directory entries that disagree. Each point below can change a design or a plan. Open the ones that match your product line.

Names changed, and old names survive

Two versions of the authorization FAQ are live. The older one calls the skilled nursing environment "MatrixCare SNF". Version 3 calls it "MatrixCare360". Older documents call the partner program MatrixCare Connections. MatrixCare's FAQ writes "MatrixCare360" as one word. Net Health and MealSuite write "MatrixCare 360".

Use version 3 of the FAQ

Only version 3 covers cancellation. The toolkit page still links the older version.

SigmaCare is tracked apart

The partner list keeps SigmaCare clinical data as its own group, with 91 rows. No source shows that an integration activated for one environment covers another.

The partner list covers facility products only

On Nov 14, 2026 its "Receiving System" column held no home health, hospice or private duty value. The list is also unfinished. One column is labeled as not yet added.

The networks differ by product line

Facility pages lead with QHINs. Home health and hospice pages lead with CommonWell and Carequality. CommonWell shows MatrixCare among its Service Adopters. It lists "MatrixCare Home Health & Hospice" as a Connected product. Its post-acute list does not include the skilled nursing product.

MatrixCare reaches the networks through other parties

MatrixCare is not one of the designated QHINs. Health Gorilla is. Carequality's directory lists "ResMed - MatrixCare" as a connection under Health Gorilla. On Nov 14, 2026 it held 556 entries below that name, across 44 state codes. An entry is not proof of a live facility.

Two Carequality records disagree

The directory places MatrixCare under Health Gorilla. A second Carequality page names "Matrix Care" as a candidate under Kno2. That page has no date. MatrixCare's 2018 press release named Kno2 as its Carequality partner. Ask MatrixCare which route your customer's facility uses.

Old names in the directories

The Carequality entry still carries the ResMed name. The sale closed on Sep 1, 2026.

The sale left links to check

The sale excluded Brightree, which stayed with ResMed. The hospice product has a two-way equipment ordering interface with Brightree. ResMed also provides certain services to MatrixCare for a limited period after the sale. The filing does not name the systems. Ask MatrixCare whether any interface you depend on runs on a shared system.

The transport differs by product, per one partner

MealSuite documents three transports across its four MatrixCare interfaces. It uses the Census Subscriber Feed API for MatrixCare 360 and Senior Living. It uses SFTP for Life Plan Community and a SOAP API for SigmaCare. MatrixCare publishes no transport per product.

The census feed name appears once on matrixcare.com

The Optima by Net Health listing names the Census Subscriber Feed (CSF). Net Health documents that the feed replaced its own retrieval of ADT messages.

One partner uses the word webhook

Wellzesta documents that its integration creates, updates and deactivates users. It says these actions are triggered by what it calls webhook events from MatrixCare. The word appears in none of twelve MatrixCare documents we searched.

One partner sends a placeholder address

Aline documents that its integration sends a generic address for a contact that has none. Check required fields before you design a contact sync.

The white paper marks itself confidential

Each page of the April 2017 paper carries a confidentiality footer, although the file is public. Its application address returned "404 not found" on Nov 14, 2026.

No public change log

We found no release notes or deprecation notices in MatrixCare's public site map.

What should you check before you sign with MatrixCare?

Check four things before you sign: consent and agreements, security, testing and support. Then put the ten questions at the end of this section to MatrixCare in writing.

Consent and agreements

Each facility's authorization is the consent record. The form states a policy of written consent before data is shared. On the online form, consent is a required tick box.

The form also states that the vendor and MatrixCare each hold a Business Associate Agreement with the customer. A Business Associate Agreement is the HIPAA contract that covers patient data. The form shows the statement. It does not prove the agreement exists for your customer. Check yours before you send the form.

Security

MatrixCare's security statement lists encryption, VPN and multi-factor authentication among its data-layer controls. It does not say which controls apply to partner connections. MatrixCare advises customers to look for integrations with user-access controls, encryption and audit trails. Expect customers to ask you for all three.

Testing

MatrixCare describes marketplace solutions as tested. It publishes no test plan or test cases. It does not say whether a partner gets a test environment. Ask for both in writing before you set a go-live date.

Support

After go-live, the customer or the partner contacts MatrixCare support by email or phone. In April 2017 MatrixCare said a partnership assigns operational responsibilities and service-level expectations. No figures are published.

Questions to ask MatrixCare before you sign

  1. Which product lines and environments does the certification cover?
  2. What data can we read and write, field by field?
  3. What is the sign-in method, and is there a test environment?
  4. What are the fees, and who is billed?
  5. How long do approval, certification and each facility activation take?
  6. What are the rate, size and history limits?
  7. How much notice do we get before an interface changes?
  8. Who supports a fault at 2 am, and what is the response target?
  9. Does any interface depend on a system that ResMed still runs?
  10. Do the 2017 policies on competing products and refusal still apply?

Next step

If you are planning a MatrixCare integration and want a team to scope the route, the access steps and the build, talk to us. Start at our MatrixCare integration service.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does MatrixCare have a public API?

We found no public developer portal, API reference or sandbox sign-up on Nov 14, 2026. MatrixCare's pages do name APIs as the mechanism behind partner integrations. Access runs through its partner program.

What is the MatrixCare Certified Integrator Program?

It is MatrixCare's program for approved vendors. A certified vendor uses an authorization form to get permission to activate a customer facility.

How do I join the MatrixCare partner program?

Apply to join the Partner Marketplace on MatrixCare's site. MatrixCare then schedules a call. The form asks for your care settings and a short description.

Is MatrixCare ONC certified?

Not today. The federal product list holds 27 MatrixCare listings, and all are retired. The newest was retired on Jun 30, 2020. None was certified to an API criterion. That is a statement about certification. It is not a statement about whether an API exists.

Does MatrixCare support FHIR?

For home health and hospice, yes. MatrixCare's FAQ, with a 2019 footer, describes a FHIR API that partners use to pull data. Current pages name FHIR-enabled integrations. The resource list and version are not published. For facility products, no current page we read confirms a partner FHIR API.

How much does a MatrixCare integration cost?

MatrixCare publishes no fee. Net Health documents that it passes a MatrixCare integration fee of $10 or $30 per site per month to its own customers. No MatrixCare fee schedule confirms that figure.

How long does a MatrixCare integration take?

MatrixCare publishes no time. Partners tell their customers different figures. AR Proactive tells its customers to allow 2 or 4 weeks on the MatrixCare side. VitalCare Connect tells its customers the form can take up to 30 days.

Who has to sign the MatrixCare authorization form?

A duly authorized representative of the customer. The form names no job title. The vendor then sends the form to MatrixCare.

Is one authorization enough for a multi-facility operator?

The authorization can cover all facilities in an enterprise account. Activation still happens for each care setting at each facility.

Who owns MatrixCare?

ResMed completed the sale of MatrixCare on Sep 1, 2026. The buyer is Frazier Healthcare Partners. MatrixCare announced the same day that it is an independent company. The sale included the home health and hospice products.
Share