Open Source

Proxy Smart
Healthcare Auth,
Solved.

A stateless proxy that adds SMART on FHIR authorization to any FHIR server. Pair with BabelFHIR-TS for type-safe, profile-aware TypeScript — and go from zero to production-ready SMART app in minutes.

Get Started → View App Store
Scroll
At a Glance
Spec 2.2.0 SMART App Launch STU2.2
Data Stored Zero Stateless proxy, no PHI touches us
Apps Included 5+ Patient Portal, Consent, DTR, Imaging...
Deploy 1 cmd Docker Compose, mono or multi-container
Proxy Smart App Store

Register, manage, and launch SMART on FHIR apps through a single admin interface. Every app gets OAuth 2.0 + PKCE, scope-based access control, and FHIR server routing out of the box.

Browse the App Store →
01
Stateless FHIR Proxy
No clinical data touches the proxy. Requests pass through to your FHIR server with auth injected. Smaller attack surface, simpler HIPAA and GDPR compliance.
02
SMART 2.2.0, Inferno Tested
Passes the ONC Inferno SMART STU2.2 test suite. OAuth 2.0 + PKCE, JWT validation, scope-based access control, refresh token rotation, and enterprise SSO.
03
App Store
Built-in marketplace to publish, discover, and launch SMART on FHIR apps. Dynamic Client Registration (RFC 7591), one-click install, per-app scope control.
04
Patient Portal
Patient-facing dashboard with International Patient Summary, lab results, documents, medications, blood type, and a built-in DICOM imaging viewer.
05
Admin Dashboard
Manage SMART apps, users, roles, organizations, launch contexts, and runtime branding. User federation, identity brokering, and multi-tenant support built in.
06
Consent Engine
Granular patient consent with configurable IAL levels, scope-level approval, and webhook notifications. Dedicated consent app included.
07
AI-Native: MCP + Tools
Expose a Model Context Protocol server for AI agent integration. RAG-powered assistant, skills registry, and a CDS Hooks–ready architecture.
08
BabelFHIR-TS
Generate type-safe TypeScript from any FHIR Implementation Guide. Profile-aware interfaces, runtime validation, and a type-safe FHIR client.
09
Deploy Anywhere
One-command dev and prod deployments. Docker Compose (mono or multi-container), Caddy reverse proxy, and AWS CDK infrastructure included.
Register your own SMART apps via the Admin Dashboard or SMART Dynamic Client Registration.

The hardest part of building a healthcare app isn't the clinical logic — it's the authentication, authorization, and interoperability. We handle that.

How It Works
Your App
SMART App
→
Proxy
Proxy Smart
→
Server
FHIR Server

Keycloak handles OAuth · Your FHIR server keeps all clinical data

Powered by BabelFHIR-TS

Install any FHIR Implementation Guide as a node module. Get type-safe interfaces, runtime validation, and a generated FHIR client — all from a single command. 

// Install US Core profiles into your project
$ npx babelfhir-ts install hl7.fhir.us.core@8.0.0

// Use the generated type-safe FHIR client
import { FhirClient } from "./output/fhir-client";

const client = new FhirClient("https://proxy-smart.example.com/fhir");

// Profile-specific methods — fully typed
const patient = await client.read().usCorePatient().read("123");
const bundle  = await client.read().usCoreCondition().search({ patient: "123" });

// Validate against profile constraints at runtime
const { errors, warnings } = await patient.validate();