Skip to main content

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.

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 / IntegratorRegionFunctionalityAuthDeveloper docs
acuity-schedulingAcuity Scheduling (Squarespace)US / GlobalAppointments (list/get/create/cancel), clients, appointment types, availability slotsHTTP Basic or OAuth2https://developers.acuityscheduling.com/reference
clinikoClinikoAU / UK / NZPatients (list/get/create), appointments, practitioners, businesses, treatment notes, invoicesAPI key (HTTP Basic)https://docs.api.cliniko.com
dentallyDentally (Henry Schein)UK / IEPatients (CRUD), appointments, practitioners, treatments, paymentsScoped Bearer tokenhttps://developer.dentally.co
easypracticeEasyPractice (Nordhealth)DK / EUClients (list/get/create), appointments, journals, services, invoicesOAuth2 Bearerhttps://system.easypractice.net/api
makeplansMakePlans ASNOBookings (list/get/create/cancel), services, resources, clients, availability slots; webhooksOAuth2 Bearer or API tokenhttps://developer.makeplans.com
muntraMuntraSEPatients (list/get/create), appointments, clinics, treatments, invoicesAPI key (sent as both Bearer and X-API-Key)https://api.muntra.com/api/documentation
kaddioKaddio (Leyr)SEPatients (list/get/create), visits, appointments, journal entries, caregiversBearer token (self-service)https://github.com/kaddio/documentation
sembleSemble TechnologyUKGraphQL: patients, bookings, practitioners, plus raw query passthroughAPI key (x-token header)https://docs.semble.io

Tier 2 — Documented public API, partner program required​

Connector (node id)Vendor / IntegratorRegionFunctionalityAuthDeveloper docs
epic-fhirEpic SystemsUS / GlobalFHIR 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 connectionhttps://fhir.epic.com · https://open.epic.com
cerner-fhirOracle Health (Cerner Millennium)US / GlobalFHIR R4: search, read, patient search, create, updateOAuth2 client credentialshttps://fhir.cerner.com · Oracle Health Developer Program
athenahealth-fhirathenaOne (athenahealth)USFHIR R4: search, read, patient searchOAuth2 client credentialshttps://developer.athenahealth.com
athenapractice-fhirathenaPractice / athenaFlex (ex-Centricity)USFHIR R4 against athenaFlex (V20/V22/V23): search, read, patient searchOAuth2 client credentialshttps://github.com/athenahealth/apiserver-athenaFlex · https://mydata.athenahealth.com
allscripts-fhirAllscripts / VeradigmUSFHIR R4: search, read, patient searchOAuth2https://developer.veradigm.com
dedalus-fhirDedalus HealthcareEUFHIR 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-fhirNextech SystemsUSFHIR 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-fhirDIPS ASNOFHIR 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-carasentWebDoc (Carasent)SEPatients, encounters, observations, medications, clinics (version-pinned, default v6.96)Bearer (Carasent-issued)https://docs.webdoc.com
sensei-dentalSensei (Carestream Dental)USPatients, appointments, procedures, charts, providersAPI key (X-Sensei-Api-Key)https://gosensei.com/pages/sensei-developer-program
exact-dentalEXACT (Software of Excellence / Henry Schein One)UK / GlobalPatients, appointments, treatments, referrals (read + create); V12.7 PF2+API key (X-API-Key), per-install base URLPartner-managed via Henry Schein One (no public portal)
avon-healthAvon Health Inc.USPatients (list/get/create), encounters, notes, module discovery; AI-first EMRBearer + module scopehttps://www.avonhealth.com (direct approach — small vendor)
emisEMIS Health (Optum) — EMIS-X Partner APIUK (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 Bearerhttps://www.emishealth.com/products/emis-x (partner program)
maxims-fhirIMS MAXIMS — CareConnect FHIR STU3UK (NHS) / IECareConnect 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 nodenone / Bearer / OAuth2 client-credentialshttps://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 ModuleFunctionality
sap-patient-managementIS-Hget/search patient, admit, discharge, get case, get encounters
sap-clinical-dataIS-H/MEDdiagnoses (get/add), procedures, orders (get/create), observations
sap-billingIS-Hinvoices (get/create), charges, DRG, insurance claims
sap-s4hana-healthS/4HANAbusiness partners, cost centers, service orders (get/create), GL accounts
sap-hcmSuccessFactors / HCMemployees, schedules, certifications (workforce management)
sap-materialsMMmaterials, stock checks, purchase orders (get/create)
sap-integration-suiteCPI / BTPsend 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)PurposeAuthReference
fhir-client / fhir-query / fhir-crudUniversal FHIR R4 client against any compliant serverBearer / client-credentials / nonehttps://hl7.org/fhir/R4
fhir-bulk-export-connectorFHIR Bulk Data Access ($export)Bearer / client-credentialshttps://hl7.org/fhir/uv/bulkdata
stu3-to-r4Vendor-neutral FHIR STU3 → R4 normalizer (healthcare/standards category)n/a (pure transform)https://hl7.org/fhir/R4/r3maps.html
s3-connectorAWS S3 read/writeAWS credentialshttps://docs.aws.amazon.com/s3
gcs-connectorGoogle Cloud Storage read/writeGCP service accounthttps://cloud.google.com/storage/docs

Authentication legend​

Auth styleWhat the integrator providesUsed by
API key (Basic)Vendor-issued key, sent as HTTP BasicCliniko, 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 tokenLong-lived token from the vendor portalDentally, EasyPractice, MakePlans, Kaddio, WebDoc, Avon
OAuth2 client credentialsClient 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.


  • 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.