Integrations
Specific status, before a sales conversation. “Available,” “private pilot,” and “planned” are not synonyms. Each connection below uses the reviewed maturity recorded in the product registry.
Paubox email Transactional delivery for approved messages and patient links.
PHI boundary: Only approved message templates and necessary recipient/context fields; no marketing analytics tags.
Authorization: Service-specific credential held server-side
Scope: Only the fields required for the named workflow email · reviewed 2026-08-28
Available Stedi 270/271 eligibility Account-scoped eligibility request and response workflow.
PHI boundary: Eligibility minimum necessary; practice activation and vendor eligibility are required.
Authorization: Service-specific credential held server-side
Scope: Only the fields required for the named workflow eligibility · reviewed 2026-08-28
Available athenahealth SMART on FHIR Practice-specific SMART launch and controlled payer-case prefill evaluation.
PHI boundary: Production PHI requires tenant validation, registered scopes, contract review, vault-backed tokens, and explicit activation.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Private pilot Epic SMART on FHIR Architecture and registration work only; no production connection is offered.
PHI boundary: No PHI permitted.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Planned Oracle Health (Cerner) SMART on FHIR Architecture and registration work only; no production connection is offered.
PHI boundary: No PHI permitted.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Planned eClinicalWorks SMART on FHIR Architecture and registration work only; no production connection is offered.
PHI boundary: No PHI permitted.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Planned MEDITECH SMART on FHIR Architecture and registration work only; no production connection is offered.
PHI boundary: No PHI permitted.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Planned DrChrono Synthetic developer evaluation only; no production connection is offered.
PHI boundary: No production PHI permitted.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Minimum registered patient-context read scopes; write scope separately gated ehr · reviewed 2026-08-28
Planned Da Vinci PAS FHIR R4 request model and capability probing validated against non-production endpoints.
PHI boundary: Synthetic sandbox data only until a payer endpoint, contract, certificate, and production test are approved.
Authorization: OAuth 2.0 / registered client; PKCE or confidential-client controls as applicable
Scope: Only the fields required for the named workflow payer api · reviewed 2026-08-28
Sandbox-validated Electronic fax Adapter candidates are documented; no production electronic-fax service is asserted.
PHI boundary: No PHI permitted until an approved service and executed agreement are recorded.
Authorization: Service-specific credential held server-side
Scope: Only the fields required for the named workflow fax · reviewed 2026-08-28
Planned Need a connection not listed here? We first confirm the workflow, data class, authorization model, vendor contract, region, rate limits, retry behavior, and production validation path. A logo is not an integration.
Discuss the workflow →