Data & Integrations — Areti Health
Product · Data & Integrations

Plugs into the stack you already run.

Pre-built connectors for the CTMS, EMR, CRM, calendar, ad, and identity systems clinical research teams actually use. TEFCA-ready, HIPAA-compliant, audit-logged on every interaction. Custom connectors via API on request.

50+ integrations HIPAA TEFCA ready FHIR R4
CTMS
REALTIME
CTMS
CRIO
CTMS
CLINICAL CONDUCTOR
CTMS
Areti Coordinator
ARETI AI COORDINATOR
Real-time patient engagement layer
Outbound channels
SMS
EMAIL
VOICE
WEB
Native connectors
REALTIME
CRIO
CLINICAL CONDUCTOR
CLINSPARK
NYLAS
SALESFORCE
HUBSPOT
Categories

Six integration categories — covering 50+ systems.

Pre-built connectors for the categories clinical research teams already operate in. Custom connectors built on request for proprietary systems.

CTMS

Clinical Trial Management

Patient records, visit scheduling, eligibility data flow into your CTMS as qualified candidates.

REALTIMECRIOCLINICAL CONDUCTORCLINSPARK
CRM

Customer Relationship Management

Patient leads sync as records, conversations sync as activities. Multi-tenant for PRC agencies.

SALESFORCEHUBSPOT
Calendar & comms

Scheduling & calendar sync

Real-time calendar availability, automated booking, reschedules, and reminders.

NYLASGOOGLEOUTLOOKO365
Advertising

Ad platforms

Qualification events flow back into ad optimization. Landing pages tracked end-to-end.

METAGOOGLELOCALIQ
TEFCA / HIE

Health information exchange

QHIN-aligned interoperability. Trusted exchange for cross-network patient identification with consent.

QHINHIECARIN
Partner API

Custom & partner integrations

REST API, webhooks, OAuth 2.0. Build into our platform or have us build a connector to yours.

RESTWEBHOOKSOAUTHSDK
How data flows

Where the data goes, who sees it, what's logged.

The Coordinator runs as a layer between your patient channels and your existing systems of record. Inbound patient signals (ad clicks, EMR matches, site referrals) flow into Areti for qualification. Outbound interactions (SMS, email, voice) happen through Areti's compliant infrastructure.

Once qualified, the patient lands in your CTMS or CRM as a fully prepared record — eligibility checked, consent captured, visit scheduled, conversation history attached. Your coordinator's first action is opening the chart, not creating it.

Every step is logged with patient-level audit trail: what was asked, what was answered, what eligibility rule fired, what was sent to which system. Exportable for IRB and sponsor audit.

  • Inbound: patient signals arrive from ads, EMR mining, site referrals, partner CRMs.
  • Process: Coordinator runs eligibility logic, consent capture, channel-of-choice conversation.
  • Outbound: qualified records land in your CTMS, CRM, or EHR with full context attached.
  • Audit: immutable patient-level log retained 7+ years per FDA 21 CFR Part 11.
Security principles

Six controls baked into every integration.

Built for the questions IT, security, and DPO teams ask before any connector goes live.

Encryption

Encrypted in transit & at rest

TLS 1.3 in transit. AES-256 at rest. Customer-managed KMS keys available for enterprise tier.

Access control

SSO + MFA + RBAC

SAML/OIDC SSO, MFA required for admin access, role-based access on every endpoint.

Audit trail

Immutable, exportable

Every read/write logged. Tamper-evident, retained 7+ years, exportable to your SIEM.

Data minimization

Read what's needed

EMR reads scoped to eligibility-relevant fields. De-identified data used where full identifiers aren't required.

Consent

Captured + honored

Patient consent tracked per protocol and per HIE participation. Right-to-revoke supported on demand.

Vendor management

SOC 2 sub-processors only

Public sub-processor list maintained. Annual review. 30-day notice on changes.

Talk to solutions engineering

Bring your stack diagram.

A 20-minute call is enough to map your CTMS, EMR, CRM, and ad stack into Areti's architecture. We'll flag what's pre-built and what would need a custom connector.

Build with us

REST API. Webhooks. OAuth 2.0. SDKs in Python and TypeScript.

Need a connector we don't have? Build it on the partner API or have our solutions team build it for you. Sandbox accounts available for any sponsor or PRC running a paid pilot.

Documentation, OpenAPI spec, and Postman collection available under NDA.

api.aretihealth.com/v1
# Push a qualified patient to your CTMS
POST /v1/patients/qualified
Authorization: Bearer $TOKEN

{
  "protocol_id": "DIA-218",
  "patient": {
    "external_id": "4821",
    "language": "es",
    "eligibility_passed": true,
    "consent_captured": true
  },
  "visit": {
    "site_id": "218",
    "scheduled_at": "2026-05-12T15:00Z"
  }
}

# Returns 201 + record url in your CTMS

Plugs into the stack you already run.

Bring your stack diagram. We'll show you what's pre-built, what's a custom connector, and how fast each path is.