Skip to main content

Integration

Fanoni integrates with the rest of your healthcare ecosystem through three layers:

  • First-party connectors — direct integrations with common medical systems (DoseSpot, Health Gorilla, Stripe, Epic, etc.)
  • Standards-based — FHIR R4 REST/GraphQL, HL7 v2, SMART-on-FHIR, FHIRcast, SFTP, X12 EDI
  • Custom integrations — built with the Fanoni SDK and Bot framework

Standards-based integrations

StandardUse casesDocumentation
FHIR R4Read/write clinical data to/from any FHIR-compliant storeFHIR datastore
GraphQLStrongly-typed queries on top of FHIRGraphQL
HL7 v2Connect to legacy hospital systemsHL7 interfacing
SMART-on-FHIREmbed Fanoni inside other EHRs (Epic, Cerner, Athena)SMART app launch
FHIRcastReal-time context sync between Fanoni and other clinical appsFHIRcast
C-CDAPatient summary import/export for HIEC-CDA

First-party connectors

PartnerTypeDocumentation
DoseSpotE-prescribing (controlled and non-controlled)DoseSpot
Health GorillaLab orders + results, clinical document exchangeHealth Gorilla
Candid HealthMedical billing / RCMCDS Hooks
eFaxInbound + outbound clinical faxeFax
Log streamingAudit + observability via syslog / OpenTelemetryLog streaming

Custom integrations

Build your own with Fanoni Bots — TypeScript functions that run server-side, triggered by FHIR resource changes, schedules, or webhooks.

Common patterns:

  • Webhook → FHIR — receive a payload from an external system, parse, write a FHIR resource
  • FHIR → external API — react to a Patient.create, push to a third-party CRM
  • Scheduled jobs — nightly batch processes, e.g. claim submission to clearinghouses
  • Document parsing — convert PDFs / HL7 / CSV into structured FHIR resources

Authentication for integrations

Use caseDocumentation
Server-to-server API accessClient credentials
User-on-behalf-of flowsOn-behalf-of
Mutual TLSmTLS
External identity providers (OIDC)External IdPs