The complete backend
Fire Arrow Server
Self-contained FHIR backend with auth, RBAC, GraphQL, CarePlan engine, subscriptions, and admin UI.
Open Server docsChoose your edition
Fire Arrow ships in two editions. Pick the one that matches where you start.
The lightweight facade
Fire Arrow Core
GraphQL facade in front of an existing FHIR server. Adds auth and RBAC to Azure Health Data Services and others.
Open Core docsNot sure which one fits? Compare editions →
What you can build with Fire Arrow Server
Step-by-step guides for the patterns digital health teams build most often.
Multi-tenancy
Tenant isolation that lives in the data, not the infrastructure
One server, many clinics. The tenant boundary lives in the FHIR data model itself, enforced at query time.
Open the implementation guideSurveillance
Schedule, track, and alert on patient questionnaires
Define a PHQ-9 schedule once. Fire Arrow creates the Tasks, fires notifications, and triggers alerts on threshold crossings.
Open the implementation guideAI agents
Agentic AI without handing out the keys
An LLM agent queries FHIR data using the clinician’s own token. The model never holds credentials.
Open the implementation guideAnonymization
Same server, two audiences, zero data leakage
Investigators see full PHI; sponsors see anonymized data. Property and identity filters do the work at query time.
Open the implementation guideCarePlans
Medication reminders that write themselves
Model a medication plan as a FHIR CarePlan. Fire Arrow materializes timed Tasks and fires webhooks on state changes.
Open the implementation guideAnalytics
Tabular analytics with full authorization
SQL-like HFQL queries over FHIR data, with the same RBAC and identity filters that protect every other request.
Open the implementation guideAPI reference:Server RESTServer GraphQLCore GraphQLRelease notes