Skip to main content

Adapters

Adapters are prebuilt Linkiir nodes that connect a workflow to an external system. Each one arrives as a node template plus the code library behind it, so you add it from the palette and fill in fields rather than writing a client from scratch.

You configure credentials, endpoints, and what to fetch or send. The connection work — authentication, token refresh, request signing, retries, error reporting — is already done.

Getting the adapters​

Adapters are published as catalogs — public git repositories your grid subscribes to. Subscribing adds a catalog's adapters to the node palette and keeps them updatable in place afterwards, with no product upgrade and no support request.

Start here

Adapter Catalogs lists every catalog with the public GitHub URL to paste into Settings → Catalogs. All the repositories are public and cloned anonymously, so no SSH key is needed.

CatalogCoversRepository
FHIR AdaptersEpic, Cerner, eCW, ModMed, Athena, FHIR toolshttps://github.com/Linkiir/linkiir-fhir-adapters
EHR AdaptersPointClickCare and other non-FHIR EHR APIshttps://github.com/Linkiir/linkiir-ehr-adapters
Diagnostics AdaptersDexcom CGM, labs, imaging, deviceshttps://github.com/Linkiir/linkiir-diagnostics-adapters
Business AdaptersSalesforce, Dynamics 365, ERP, identityhttps://github.com/Linkiir/linkiir-business-adapters
Transport AdaptersAWS S3, object storage, brokershttps://github.com/Linkiir/linkiir-transport-adapters
Notification AdaptersSlack, chat, SMS, email, paginghttps://github.com/Linkiir/linkiir-notification-adapters
AI AdaptersAzure OpenAI and other model serviceshttps://github.com/Linkiir/linkiir-ai-adapters
Developer ToolsData Simulator for HL7 v2, C-CDA, FHIR and X12 test datahttps://github.com/Linkiir/linkiir-devtools

If your grid has no outbound route to GitHub, a catalog can be delivered on a mounted share or removable drive instead — see Offline Delivery. Adapters can also arrive as a project to import, with templates and libraries already attached to the nodes that use them; see Project Import and Export.

Available adapters​

EpicPoll an Epic FHIR endpoint and push each matching resource downstream.CernerPoll a Cerner FHIR endpoint using a registered System Account.eClinicalWorksPoll an eCW FHIR endpoint, with its separate authorization server.ModMedPoll a ModMed FHIR endpoint with an API key and account credentials.Athena HealthPoll the Athena Health platform for a practice and push each patient found.Dexcom CGMAuthorize a Dexcom account and read continuous glucose values on a timer.PointClickCareAuthenticate with two-legged OAuth and call any PointClickCare endpoint.SalesforceQuery and update Salesforce records over the REST API from a script node.Dynamics 365Poll Microsoft Dynamics 365 CRM on a schedule with a FetchXML query.AWS S3Poll a bucket for new objects, upload messages as objects, and browse a bucket.SlackPost workflow messages and alerts into a Slack channel.Azure OpenAISend message content to a model deployment and route the response downstream.FHIR Resource CreatorTurn inbound patient data into a clean FHIR R4 Patient resource.FHIR ValidatorValidate a FHIR resource against a server and forward it only on a clean pass.FHIR Profiling ToolsBrowse FHIR resources and get a JSON template for any of them.FHIR ValidatorValidate a resource against a FHIR server and forward it only when it validates.

By catalog​

Which catalog publishes each adapter, and the library it uses. Subscribe to the catalog to get the adapter.

AdapterCatalogConnects toLibrary
HAPI FHIR / OmniVeraFHIR AdaptersHAPI FHIR or Smile OmniVera endpointhapi_fhir
EpicFHIR AdaptersEpic FHIR endpointepic_fhir
CernerFHIR AdaptersCerner FHIR endpointcerner_fhir
eClinicalWorksFHIR AdapterseCW FHIR endpointecw_fhir
ModMedFHIR AdaptersModMed FHIR endpointmodmed_fhir
Athena HealthFHIR AdaptersAthena Health platformathena_health
HAPI FHIR / OmniVeraFHIR AdaptersHAPI FHIR or Smile OmniVera endpointhapi_fhir
FHIR Resource CreatorFHIR AdaptersNothing — local transformationfhir_creator
FHIR ValidatorFHIR AdaptersA FHIR server's $validate operationfhir_validate
FHIR Profiling ToolsFHIR AdaptersNothing — local HTTP servicefhir_profiling
PointClickCareEHR AdaptersPointClickCare organizationpcc_api
Dexcom CGMDiagnostics AdaptersDexcom CGM accountdexcom_cgm
SalesforceBusiness AdaptersSalesforce REST APIsalesforce
Dynamics 365Business AdaptersMicrosoft Dynamics 365 CRMdynamics_crm
AWS S3Transport AdaptersS3 and S3-compatible storageaws_s3
SlackNotification AdaptersSlack workspaceslack
Azure OpenAIAI AdaptersAzure OpenAI deploymentazure_openai

Start here​

If you want toRead
Understand how an adapter is delivered and configuredHow Adapters Work
Pull patient data from an EHREpic, Cerner, eClinicalWorks, ModMed, Athena Health
Read glucose data from a CGM deviceDexcom CGM
Read or write records in long-term carePointClickCare
Read or write records in a CRMSalesforce, Dynamics 365
Move messages through object storageAWS S3
Send an alert to a channelSlack
Send message content to a modelAzure OpenAI
Build or inspect FHIR resources locallyFHIR Resource Creator, FHIR Profiling Tools

What every adapter has in common​

  • Fields, not code. Endpoints, credentials, and what to fetch are node configuration. See How Adapters Work.
  • Live Mode. A switch that lets the node authenticate and log what it would send, without sending it. Use it for the first run of every adapter.
  • Verify TLS on by default. Certificate verification stays on unless you deliberately turn it off for a local test proxy.
  • Secrets stored as masked fields. Passwords, API keys, and secret keys are encrypted in the project and never written to logs. Private keys stay on disk and are referenced by path.
  • Errors in the node log. Each adapter reports a stable error code and a readable message, listed on its page.
Build against a sandbox first

Point a new adapter at the vendor's sandbox or test environment, with synthetic data, before connecting it to production. See Sample Code for the practices the demo interfaces follow.

Next​