Healthcare-MSP integrations footprint
Healthcare-MSP integrations footprint.
Every provider in the Cavaridge Integrations Hub, organized by HIPAA access posture — what data flows through each, whether BAA coverage is on the platform or your side, and which credential your IT owns.
PHI-aware (EMR / EHR read)
EMR / EHR read access
Cavaridge does not currently expose EMR / EHR catalog entries in the Integrations Hub. Where a customer needs read access into an Epic, Cerner, athenahealth, or eClinicalWorks instance, we route through the API Gateway plus a separately signed custom DPA on a customer-by-customer basis — not the standard catalog.
No live EMR / EHR providers in the Hub today. Talk to us about a custom integration + DPA —
sales@cavaridge.io.
RMM & PSA telemetry
Inventory, alert, patch, and ticket telemetry flows into Cavaridge from each customer's existing RMM and PSA vendor. BAA coverage for these feeds is customer-side — your existing vendor BAA covers the data on its way to us; Cavaridge receives de-identified metadata (device ID, ticket ID, alert summary) rather than the originating clinical record.
PSA
ConnectWise PSA
Data flow: ticket metadata → Cavaridge
BAA: CustomerCred: Customer IT
PSA
Autotask PSA
Data flow: ticket metadata → Cavaridge
BAA: CustomerCred: Customer IT
PSA
HaloPSA
Data flow: tickets, clients, assets → Cavaridge
BAA: CustomerCred: Vendor admin
RMM
Datto RMM
Data flow: device inventory + alerts → Cavaridge (de-identified)
BAA: CustomerCred: Customer IT
RMM
NinjaRMM
Data flow: device health + patch status → Cavaridge
BAA: CustomerCred: Vendor admin
RMM
Kaseya VSA
Data flow: endpoints + scheduled tasks → Cavaridge
BAA: CustomerCred: Customer IT
RMM
Atera
Data flow: agents + alerts + patch reports → Cavaridge
BAA: CustomerCred: Customer IT
EDR / Endpoint detection
Endpoint detection & response
Threat, incident, and quarantine events from each customer's EDR vendor are pulled in for the Security Alerting app. Customer-side BAA coverage is unchanged by this integration — Cavaridge only stores incident summaries, file hashes, and agent status, never customer clinical content.
EDR
Huntress
Data flow: incident reports + agent status → Cavaridge
BAA: CustomerCred: Customer IT
EDR
SentinelOne
Data flow: threats + quarantined files → Cavaridge
BAA: CustomerCred: Customer IT
EDR
CrowdStrike Falcon
Data flow: detections + prevention events → Cavaridge
BAA: CustomerCred: Vendor admin
EDR
Microsoft Defender for Endpoint
Data flow: alerts + vulnerability data → Cavaridge (Graph API)
BAA: CustomerCred: Vendor admin
Identity / SSO
Identity, SSO & MFA
SSO and identity providers that anchor Cavaridge's single RBAC across all 21 apps. BAA coverage remains customer-side; Cavaridge only receives user identifiers, group membership, and MFA enrollment status — never SSO assertion contents.
Identity
Okta
Data flow: users + groups + MFA status → Cavaridge
BAA: CustomerCred: Customer IT
Identity
Duo Security
Data flow: auth logs + MFA enrollment → Cavaridge
BAA: CustomerCred: Customer IT
Identity
Microsoft Entra ID
Data flow: users + devices + conditional access → Cavaridge
BAA: CustomerCred: Vendor admin
Productivity, Communication & Backup
Productivity, alerting & backup
Productivity suites (mailbox, license, Drive usage), outbound alerting channels (Slack, Teams, PagerDuty), and backup / DR platforms. Productivity content (mail bodies, Drive contents) is never pulled into Cavaridge — only license, metadata, and admin-event data, scoped to what BAA posture requires.
Productivity
Productivity
Microsoft 365
Data flow: mailboxes + licenses + SharePoint activity → Cavaridge
BAA: CustomerCred: Vendor admin
Productivity
Google Workspace
Data flow: users + Drive usage + admin audit → Cavaridge
BAA: CustomerCred: Vendor admin
Communication
Communication
Slack
Data flow: Cavaridge → alerts/SLA warnings → Slack channels
BAA: CustomerCred: Vendor admin
Communication
Microsoft Teams
Data flow: Cavaridge → alert notifications → Teams
BAA: CustomerCred: Vendor admin
Communication
PagerDuty
Data flow: Cavaridge → incidents → PagerDuty
BAA: CustomerCred: Customer IT
Backup
Backup
Veeam Backup
Data flow: job status + restore points → Cavaridge
BAA: CustomerCred: Customer IT
Backup
Datto BCDR
Data flow: verification screenshots + recovery tests → Cavaridge
BAA: CustomerCred: Customer IT
Backup
Acronis Cyber Protect
Data flow: backup plans + alerts + compliance → Cavaridge
BAA: CustomerCred: Vendor admin
Backup
Backupify
Data flow: SaaS backup status (M365 / Google) → Cavaridge
BAA: CustomerCred: Customer IT
Backup
Axcient x360
Data flow: backup health + failover tests → Cavaridge
BAA: CustomerCred: Customer IT
Billing
Billing rail
Stripe is auto-created as a per-tenant integration at provisioning and records each billing / lifecycle event into the Integrations Hub activity log. Out of PHI scope — billing-only.
Billing
Stripe
Data flow: Cavaridge → invoices + subscription events → Stripe
BAA: Out of PHI scope — billing-onlyCred: Cavaridge-stored API key
Request a healthcare-MSP demo
See the integrations footprint on your own data.
Tell us a little about your MSP and we'll walk you through how each of these providers maps onto your stack — same BAA, same permission model, same bill.