MatrixCare integration · United States

MatrixCare API Integration for Long-Term and Post-Acute Care

We build MatrixCare integrations for vendors serving skilled nursing, senior living, home health and hospice. MatrixCare does not publish a public developer portal: integrations run through its Certified Integrator Program, with a signed authorization for each customer facility. We map each workflow to the access point MatrixCare documents and prepare the evidence its certification asks for.

  • Certified Integrator Program
  • Customer Authorization Form
  • Public APIs
  • FHIR
  • NCPDP
  • MyData
  • DIRECT

Certified first, then facility by facility.
  1. 01Join the program

    Apply to MatrixCare's Partner Marketplace and Certified Integrator Program.

  2. 02Authorize each facility

    The customer signs a Customer Authorization Form per facility; MatrixCare confirms it.

  3. 03Build to the access point

    Public APIs or FHIR through MatrixCare's integration engine, DIRECT or IHE for summaries, MyData for reporting.

Evidence you can check

The problem

Sound Familiar?

Vendors selling into skilled nursing and senior living run into these four problems first.

No public developer portal

You searched for MatrixCare API docs and found report cards, not a sandbox.

A signed customer is not a live facility

The contract is signed, but data cannot flow until each facility is authorized and MatrixCare confirms it.

Census changes found a day late

Admissions, transfers and discharges reach your product through a spreadsheet, so your team works from yesterday's census.

Pharmacy orders on the phone

Medication changes go back and forth with the long-term care pharmacy by fax and call, and the eMAR lags behind.

Use cases

What It Looks Like When It Works

Four use cases, each shown as the screen your team works in. Facilities and residents are fictional; the access steps follow MatrixCare's published program.

Facilities Activated the Way MatrixCare Expects

Today

Go-live dates slip because nobody tracked which facility had signed what.

With the integration

Each customer facility has a signed Customer Authorization Form with its MatrixCare ID, MatrixCare confirms it, and only then does data flow for that facility.

What we build
  • A tracker for authorization forms and MatrixCare confirmations
  • Facility details checked before the form is sent
  • No data flow for a facility until its confirmation arrives
Facility activation tracker with MatrixCare IDs, signed customer authorizations, confirmation status and one incomplete form
Illustrative screen with fictional facilities and residents: facility activation tracker with MatrixCare IDs, signed customer authorizations, confirmation status and one incomplete form. Tap to open full size.

Census Changes the Same Day

Today

Care coordinators learn about an admission or a hospital transfer from a phone call.

With the integration

Admissions, room changes, hospital transfers and discharges reach your product through the interface MatrixCare approves, and a transfer alerts the care team.

What we build
  • The admission, transfer and discharge events your workflow needs
  • Mapping through MatrixCare's integration engine and Public APIs as certified
  • Alerts for transfers and bed holds
Census changes from MatrixCare: admission, room change, hospital transfer with alert and discharge, all synced
Illustrative screen with fictional facilities and residents: census changes from MatrixCare: admission, room change, hospital transfer with alert and discharge, all synced. Tap to open full size.

Medication Orders That Reach the Pharmacy

Today

Nurses call the pharmacy to confirm a dose change and update the eMAR later.

With the integration

New orders, dose changes and discharges move between MatrixCare and the long-term care pharmacy over NCPDP messaging, and anything that needs a prescriber's signature is held for one.

What we build
  • NCPDP order and status messages with the pharmacy partner
  • Order status shown next to the eMAR
  • Controlled substances held for signature
Medication orders between MatrixCare and the pharmacy: new order filled, dose change confirmed, controlled substance held
Illustrative screen with fictional facilities and residents: medication orders between MatrixCare and the pharmacy: new order filled, dose change confirmed, controlled substance held. Tap to open full size.

The Right Access Point for Each Workflow

Today

Teams try to build everything on one route and stall on access.

With the integration

Discovery maps each workflow to the access point MatrixCare documents: Public APIs or FHIR as a certified partner, DIRECT or IHE for care summaries, MyData for reporting.

What we build
  • A workflow to access point map per customer
  • The certification steps that route needs
  • A written fallback where no route fits
Discovery table mapping workflows to MatrixCare access points: Public APIs, FHIR, DIRECT and IHE, MyData, and who grants each
Illustrative screen with fictional facilities and residents: discovery table mapping workflows to MatrixCare access points: Public APIs, FHIR, DIRECT and IHE, MyData, and who grants each. Tap to open full size.

First call

Questions We Will Ask You on the First Call

The answers decide whether you need certification, which access point fits and how long activation takes.

Are you already in MatrixCare's Certified Integrator Program or Partner Marketplace?

If not, applying is usually the first step, and it sets the timeline.

Which care settings do your customers run on MatrixCare?

Skilled nursing, senior living, home health and hospice use different MatrixCare products.

Which workflow comes first?

Census, assessments, orders, billing or reporting each use different access points.

Do you need to write to MatrixCare, or only read?

Writes go through the routes MatrixCare certifies; reporting can often use MyData.

How many facilities will you activate, and who signs the authorization at each?

Every facility needs its own signed form and confirmation.

Which pharmacy do your customers use?

Pharmacy integration runs over NCPDP with pharmacy partners MatrixCare supports.

Do your customers also run PointClickCare?

Many post-acute vendors need both, and the patterns differ.

Who on your side owns MatrixCare's technical certification?

Certification needs test evidence and a named owner.

The short answer

Does MatrixCare Have an API? Yes, for Certified Partners

MatrixCare does not publish a public developer portal or sandbox. Its interoperability white paper describes the access points: an integration engine built on Orion Health's Rhapsody that calls MatrixCare Public APIs for inbound transactions, FHIR access, DIRECT messaging and IHE document sharing, and a MyData operational data store that customers and their authorized agents can license for reporting. Vendors reach these through MatrixCare's Certified Integrator Program, and each customer facility is activated with a signed Customer Authorization Form that MatrixCare confirms. Pharmacy integration runs over NCPDP with pharmacy partners.

Who it is for
Care coordination, census, clinical, pharmacy, billing and analytics vendors serving long-term and post-acute care on MatrixCare.
What we build
Certification preparation, facility activation tracking, census and clinical data flows, pharmacy order status and reporting from MyData.
The outcome we design for
Facilities activated in the order MatrixCare expects and data flowing through the access point it certifies. These are intended outcomes, not a promise about MatrixCare's decisions.

MatrixCare access points

MatrixCare Access Points and Who Grants Them

From MatrixCare's Certified Integrator Program page and its interoperability white paper (dated April 2017, so we confirm current details with MatrixCare).

Access pointWhat it is forWho grants itWhat to plan for
MatrixCare Public APIs through the integration engineTransactional reads and writes; inbound messages are mapped and passed to Public API callsMatrixCare, for certified partnersCertification, message maps and a named technical owner
FHIRStandards-based clinical accessMatrixCare, for certified partnersConfirm resources and versions during certification
DIRECT messaging and IHE XDSCare summaries with hospitals and HIEsLicensed options for the customerThe customer's license and the hospital's preferred method
MyData operational data storeReporting and analytics on replicated production tablesCustomer license; authorized agents can use itRefresh several times a day, not real time
NCPDP pharmacy messagingMedication orders and status with long-term care pharmaciesMatrixCare and the pharmacy partnerPharmacy partner agreements
Customer Authorization FormActivates your integration for each customer facilityThe customer signs; MatrixCare confirmsOne form per facility, with its MatrixCare ID

MatrixCare publishes no public API reference, so this page names access points, not endpoints. Endpoint detail comes through certification.

What we build

What Our MatrixCare Integration Builds

Pick the workstreams your product needs. Each one ships with a specification, test evidence and an owner.

01

Certification Preparation

The technical and security evidence MatrixCare's certification asks for, with test runs and a named owner on your side.

Certified Integrator Program · test evidence

02

Facility Activation Tracking

A tracker for Customer Authorization Forms, MatrixCare IDs and confirmations, so no facility goes live before MatrixCare confirms it.

Customer Authorization Form · facility IDs

03

Census and Resident Data

Admissions, transfers, discharges and resident details flowing to your product through the certified access point.

Public APIs · FHIR · message maps

HL7 integration services →
05

Reporting From MyData

Analytics and dashboards built on the customer's MyData license, with refresh timing stated on every report.

MyData · operational data store

Buyer decisions

MatrixCare Integration Options Compared

Most vendors need certification. Reporting is the main exception.

OptionBest fitStrengthsWhat to plan for
Certified integration (Public APIs or FHIR)Products that read and write resident dataSupported by MatrixCare once certifiedCertification time and evidence
MyData licenseReporting and analyticsBroad data, no transactional buildRefresh delay; the customer licenses it
DIRECT or IHECare summaries with hospitalsStandard exchangeCustomer license; documents, not transactions
ExportsMigrations and one-off analysisNo build on MatrixCare's sideManual steps, no ongoing sync
Login-based automationWorkflows no certified route coversWorks where routes stopMatrixCare's terms, written authorization and strict controls

We say so when the certified routes cannot do what you need.

Integration boundaries

MatrixCare Integration Boundaries: Who Owns What

We write the split down before the build starts.

The customer

Signs the authorization for each facility and licenses options such as MyData or DIRECT.

MatrixCare

Owns certification, access decisions, its APIs and terms. We build to what MatrixCare certifies.

Your product team

Owns what your product does with MatrixCare data and how it appears to users.

The integration layer (ours)

Message maps, connectors, activation tracking, redacted operational logs and alerts. Defects in this layer are ours to fix.

Security and PHI

A BAA is available for agreed work involving PHI. We encrypt in transit and at rest and keep raw payloads out of operational logs.

Deliverables

MatrixCare Integration Deliverables

Everything lands in your repository and your runbook.

01

Access point map

Which MatrixCare access point serves each workflow, with field maps.

02

Certification pack

Test evidence and documentation for MatrixCare's technical certification.

03

Integration code in your repository

Connectors and message maps, with facility configuration kept out of the code.

04

Facility activation checklist

Authorization form steps, IDs and confirmation checks for each facility.

05

Monitoring and runbook

Feed alerts, redacted operational logs and a support runbook.

Delivery phases

MatrixCare Integration Timeline

Initial planning estimate: 8 to 14 weeks to a first live facility, subject to MatrixCare certification, facility authorization and validation. Certification timing is set by MatrixCare, so discovery starts the application in week one.

  1. 01

    Discovery and application

    Weeks 1 to 3

    Workflows mapped to access points, program application and authorization forms started

  2. 02

    Build

    Weeks 3 to 8

    Connectors and maps built and tested

  3. 03

    Certification

    Weeks 6 to 12

    Evidence submitted and MatrixCare's review completed

  4. 04

    Go-live and hypercare

    Weeks 10 to 14

    First facility confirmed and live, monitoring on

Cost drivers

What Drives MatrixCare Integration Cost

Use the scoping call to pin down the workflow, the access you need and what goes into a scoped proposal. These are the factors that move cost.

Certification

Evidence and review cycles depend on the workflows you certify.

Access points

Public APIs, FHIR, MyData and pharmacy messaging each add work.

Workflows

Census, assessments, orders and billing each add mapping and tests.

Facilities per year

A repeatable activation checklist matters most when you add many facilities.

Fallback routes

Exports or login-based automation add their own controls and tests.

Support level

Monitoring and on-call support are priced per connection.

Book a call ↗

Proof

Post-Acute and Interface Work You Can Check

Client names are withheld. These are services we deliver and guides we publish; they do not prove MatrixCare certification or a live facility integration.

Service we deliver

PointClickCare Integration

Our integration work for skilled nursing and senior living on PointClickCare, the other platform most post-acute vendors meet.

See PointClickCare integration →

Service we deliver

Pharmacy and NCPDP Integration

E-prescribing and NCPDP messaging for digital health and care products.

See pharmacy integration →

Published engineering guide

EHR Automation Without API Access

How we decide between APIs, RPA and computer-use agents when a route stops short, and the controls each needs.

Read the guide →

Security

ISO 27001:2022 Certified, BAAs Signed

We are ISO 27001:2022 certified and sign Business Associate Agreements for work that touches patient data.

FAQ

MatrixCare Integration: Questions Buyers Ask

Does MatrixCare have an API?

Yes, for certified partners. MatrixCare does not publish a public developer portal or sandbox. Its documentation describes Public APIs reached through its integration engine, FHIR access, DIRECT and IHE exchange, and the MyData data store, made available through its Certified Integrator Program.

How do you become a MatrixCare certified integrator?

Apply to MatrixCare's Partner Marketplace and Certified Integrator Program. MatrixCare reviews the application and runs technical certification with a named technical contact.

What is the MatrixCare Customer Authorization Form?

It is the form a customer signs to activate your integration for each facility. It lists the facility and its MatrixCare ID; the partner sends it to MatrixCare, and MatrixCare confirms by email before the facility goes live.

Does MatrixCare support FHIR?

MatrixCare's interoperability documentation describes transactional access through FHIR for partners. We confirm the resources and versions available to your product during certification.

What is MatrixCare MyData?

MyData is a licensed operational data store that replicates MatrixCare production tables several times a day for customers and their authorized agents. It suits reporting and analytics, not real-time workflows.

How does MatrixCare connect to pharmacies?

Through NCPDP messaging with long-term care pharmacy partners. MatrixCare has announced, for example, NCPDP bidirectional e-prescribing and pharmacy-centric order entry with PharMerica.

Can we write data to MatrixCare?

Writes go through the routes MatrixCare certifies, such as its Public APIs via the integration engine. MyData is for reading and reporting.

What if MatrixCare has no route for our workflow?

We check MyData, DIRECT and exports first. Login-based automation is a last resort, used only where MatrixCare's terms and the customer's written authorization allow it.

Do you also integrate with PointClickCare?

Yes. Many post-acute vendors need both MatrixCare and PointClickCare, and we design one internal model so the product serves both.

How long does a MatrixCare integration take?

Our initial planning estimate is 8 to 14 weeks to a first live facility, subject to MatrixCare certification and facility authorization. MatrixCare sets the certification timing.

How much does a MatrixCare integration cost?

Cost depends on certification scope, the access points, workflows, facilities per year, any fallback routes and the support level. A BAA is available under our ISO 27001:2022 certified management system. After a scoping call we send a scoped proposal with the access dependencies listed.

Next step

Plan Your MatrixCare Integration

Tell us the care settings you serve, the workflows your product needs and whether you have applied to MatrixCare's program. An engineer replies with the access point per workflow and the certification steps.

Start with your workflow

Tell Us About Your MatrixCare Integration

Share the care settings, the workflows and your target date. Use de-identified examples only. Read by an engineer, answered within one business day.

Please exclude patient data and credentials. We use these details to respond to your inquiry. Privacy policy

Thank you. Your inquiry has been received. Our team will review your requirements.