Connector Directory
Integrator-facing reference for every third-party connector node shipped with the Tietai platform. For each connector: the vendor, region, what it does, how it authenticates, and a link to the vendor's developer documentation.
- Engineering pattern: Connector Pattern Guide
- Node catalog (per-node docs): EHR Connector Node Index
- Live catalog API:
GET /api/node-catalog(categoryehr)
Access tiers
- Tier 1 — open public API, self-service signup. You can integrate today with a key from the vendor's portal.
- Tier 2 — documented public API, but a partner program or approval is required for production access. Sandbox is usually open.
Tier 1 — Open public API, self-service signup
| Connector (node id) | Vendor / Integrator | Region | Functionality | Auth | Developer docs |
|---|---|---|---|---|---|
acuity-scheduling | Acuity Scheduling (Squarespace) | US / Global | Appointments (list/get/create/cancel), clients, appointment types, availability slots | HTTP Basic or OAuth2 | https://developers.acuityscheduling.com/reference |
cliniko | Cliniko | AU / UK / NZ | Patients (list/get/create), appointments, practitioners, businesses, treatment notes, invoices | API key (HTTP Basic) | https://docs.api.cliniko.com |
dentally | Dentally (Henry Schein) | UK / IE | Patients (CRUD), appointments, practitioners, treatments, payments | Scoped Bearer token | https://developer.dentally.co |
easypractice | EasyPractice (Nordhealth) | DK / EU | Clients (list/get/create), appointments, journals, services, invoices | OAuth2 Bearer | https://system.easypractice.net/api |
makeplans | MakePlans AS | NO | Bookings (list/get/create/cancel), services, resources, clients, availability slots; webhooks | OAuth2 Bearer or API token | https://developer.makeplans.com |
muntra | Muntra | SE | Patients (list/get/create), appointments, clinics, treatments, invoices | API key (sent as both Bearer and X-API-Key) | https://api.muntra.com/api/documentation |
kaddio | Kaddio (Leyr) | SE | Patients (list/get/create), visits, appointments, journal entries, caregivers | Bearer token (self-service) | https://github.com/kaddio/documentation |
semble | Semble Technology | UK | GraphQL: patients, bookings, practitioners, plus raw query passthrough | API key (x-token header) | https://docs.semble.io |
Tier 2 — Documented public API, partner program required
| Connector (node id) | Vendor / Integrator | Region | Functionality | Auth | Developer docs |
|---|---|---|---|---|---|
epic-fhir | Epic Systems | US / Global | FHIR R4: search, read, patient search, $everything (full patient record) | Client secret (OAuth2 client credentials) by default. For the interact operation auth_mode also offers Backend Services JWT (RS384/ES384), an injected bearer token, or a stored External Auth connection | https://fhir.epic.com · https://open.epic.com |
cerner-fhir | Oracle Health (Cerner Millennium) | US / Global | FHIR R4: search, read, patient search, create, update | OAuth2 client credentials | https://fhir.cerner.com · Oracle Health Developer Program |
athenahealth-fhir | athenaOne (athenahealth) | US | FHIR R4: search, read, patient search | OAuth2 client credentials | https://developer.athenahealth.com |
athenapractice-fhir | athenaPractice / athenaFlex (ex-Centricity) | US | FHIR R4 against athenaFlex (V20/V22/V23): search, read, patient search | OAuth2 client credentials | https://github.com/athenahealth/apiserver-athenaFlex · https://mydata.athenahealth.com |
allscripts-fhir | Allscripts / Veradigm | US | FHIR R4: search, read, patient search | OAuth2 | https://developer.veradigm.com |
dedalus-fhir | Dedalus Healthcare | EU | FHIR R4: search, read, create, update, batch (Keycloak OpenID Connect) | Keycloak OpenID Connect, client credentials against a configurable realm (default dedalus) | Dedalus partner program (no public self-service portal) |
nextech-fhir | Nextech Systems | US | FHIR R4: search, read, patient search (the node does not implement the vendor's app gallery or MyPatientVisit consent flow) | SMART on FHIR (OAuth2 client credentials) | https://developers.nextech.com |
dips-fhir | DIPS AS | NO | FHIR R4: search, read, patient search (by fødselsnummer), encounter history; catalog description: dominant Norwegian hospital EHR (~73% share) | OAuth2 (OpenDIPS) | https://open.dips.no |
webdoc-carasent | WebDoc (Carasent) | SE | Patients, encounters, observations, medications, clinics (version-pinned, default v6.96) | Bearer (Carasent-issued) | https://docs.webdoc.com |
sensei-dental | Sensei (Carestream Dental) | US | Patients, appointments, procedures, charts, providers | API key (X-Sensei-Api-Key) | https://gosensei.com/pages/sensei-developer-program |
exact-dental | EXACT (Software of Excellence / Henry Schein One) | UK / Global | Patients, appointments, treatments, referrals (read + create); V12.7 PF2+ | API key (X-API-Key), per-install base URL | Partner-managed via Henry Schein One (no public portal) |
avon-health | Avon Health Inc. | US | Patients (list/get/create), encounters, notes, module discovery; AI-first EMR | Bearer + module scope | https://www.avonhealth.com (direct approach — small vendor) |
emis | EMIS Health (Optum) — EMIS-X Partner API | UK (GP primary care) | Patient clinical record, demographics, patient-matching/sync, appointments; writes coded data back via FileRecord (raw EMIS JSON, Bronze) | OAuth2 client-credentials or injected Bearer | https://www.emishealth.com/products/emis-x (partner program) |
maxims-fhir | IMS MAXIMS — CareConnect FHIR STU3 | UK (NHS) / IE | CareConnect FHIR STU3 (3.0.x): search, read, patient search; optionally normalizes STU3→canonical R4 in-line (lossy; losses surfaced) or via the stu3-to-r4 node | none / Bearer / OAuth2 client-credentials | https://www.imsmaxims.com (partner program) |
SAP Healthcare (Hospital Information Systems)
SAP IS-H / S/4HANA Health / SuccessFactors connectors. Each node sends the auth_token field as a Bearer token and/or the api_key field as an APIKey header, plus an sap-client header (sap_client field), to the customer's SAP gateway (sap_url). The exception is sap-integration-suite, which can obtain a token by OAuth2 client credentials (client_id, client_secret, token_url). There is no open self-service portal. Integration is per-customer.
| Connector (node id) | SAP Module | Functionality |
|---|---|---|
sap-patient-management | IS-H | get/search patient, admit, discharge, get case, get encounters |
sap-clinical-data | IS-H/MED | diagnoses (get/add), procedures, orders (get/create), observations |
sap-billing | IS-H | invoices (get/create), charges, DRG, insurance claims |
sap-s4hana-health | S/4HANA | business partners, cost centers, service orders (get/create), GL accounts |
sap-hcm | SuccessFactors / HCM | employees, schedules, certifications (workforce management) |
sap-materials | MM | materials, stock checks, purchase orders (get/create) |
sap-integration-suite | CPI / BTP | send message, iFlow status, message logs |
SAP developer reference: https://api.sap.com (SAP Business Accelerator Hub).
Standards & storage connectors (vendor-neutral)
Not tied to a single EHR vendor. These live in the healthcare and cloud-storage categories.
| Connector (node id) | Purpose | Auth | Reference |
|---|---|---|---|
fhir-client / fhir-query / fhir-crud | Universal FHIR R4 client against any compliant server | Bearer / client-credentials / none | https://hl7.org/fhir/R4 |
fhir-bulk-export-connector | FHIR Bulk Data Access ($export) | Bearer / client-credentials | https://hl7.org/fhir/uv/bulkdata |
stu3-to-r4 | Vendor-neutral FHIR STU3 → R4 normalizer (healthcare/standards category) | n/a (pure transform) | https://hl7.org/fhir/R4/r3maps.html |
s3-connector | AWS S3 read/write | AWS credentials | https://docs.aws.amazon.com/s3 |
gcs-connector | Google Cloud Storage read/write | GCP service account | https://cloud.google.com/storage/docs |
Authentication legend
| Auth style | What the integrator provides | Used by |
|---|---|---|
| API key (Basic) | Vendor-issued key, sent as HTTP Basic | Cliniko, Acuity (basic mode) |
| API key (header) | Vendor key in a custom header (Muntra sends it as both Bearer and X-API-Key) | Muntra, Semble (x-token), Sensei (X-Sensei-Api-Key), EXACT (X-API-Key) |
| Bearer token | Long-lived token from the vendor portal | Dentally, EasyPractice, MakePlans, Kaddio, WebDoc, Avon |
| OAuth2 client credentials | Client ID + secret (server-to-server) | Epic, Cerner, athenahealth, athenaPractice, Nextech, DIPS, Allscripts, Dedalus, EMIS, MAXIMS |
| Bearer token / API key (enterprise) | Per-customer SAP gateway token and/or API key (auth_token, api_key) | SAP modules (sap-integration-suite can also use OAuth2 client credentials) |
All secret-typed fields (api_key, client_secret, access_token, api_token) are secret-typed fields: the node configuration form renders them as secret inputs, and run configuration snapshots store them masked.
Notes on link accuracy
- Links marked with a full
https://URL are the vendor's documented developer/API portal. - Where a vendor has no public self-service portal (Dedalus, EXACT) or gates access through sales/partner channels (Avon), that is stated explicitly instead of linking a guessed deep link.
- Epic, Cerner, athenahealth, and Veradigm portals require a developer account to view full API references and sandboxes.
Last updated: 2026-05-29. Source of truth: pkg/node/handlers/*_node.go Schema() + this directory. When you add a connector, update this table and the EHR Connector Node Index.
Something unclear? Send documentation feedback by email.