Make it concrete.
Working examples, synthetic environments, and step-by-step guides turn specifications into something you can run and understand.
Meet our first product: SMART Flint FHIR.
Healthcare interoperability, made approachable
FHIR.
Without the
friction.
Great ideas shouldn’t get lost in integration work. We build practical, source-available tools that make complex healthcare standards easier to use.
Self-hosted. Source available. Built for your stack.
FEWER MOVING PARTS. MORE BUILDING.
Keep credentials at the bridge
Your applicationSMART FlintFHIR server
Your app reads and searches through SMART Flint. The bridge holds upstream credentials, manages renewal, and applies its gateway policies.
const connection = await session.getFHIRConnection({
route: 'gateway'
});Ordinary FHIR HTTP clients work. Gateway access uses a SMART Flint session credential.
Keep your existing FHIR client
Your applicationOriginal FHIR server
Your app talks to the original FHIR endpoint with its upstream access token. SMART Flint continues to own credential renewal.
const connection = await session.getFHIRConnection({
route: 'direct'
});Token export must be allowed by the installation. Gateway-specific controls apply only to gateway traffic.
Take ownership explicitly
Understand credentials & ownership Your applicationOriginal FHIR server
Your app explicitly takes ownership of the upstream credentials. The bridge stops owning refresh-token rotation for that grant.
POST /api/activations/:id/credentials/handoffIndependent refresh may also require confidential client authentication on your backend. Handoff is a separate API action.
One integration service. Three ways to connect.
Illustrated architecture · explore each mode above
Illustrated architecture · explore each mode above
01 / The toolkit starts hereMeet SMART Flint.
Meet SMART Flint.
Your integration head start.
Our first product takes care of the connection lifecycle, so you can focus on the application you came to build.
SMART on FHIR
integration, simplified.
A self-hosted service for launch orchestration, EHR connections, OAuth grants, clinical context, and optional FHIR access mediation.
Your FHIR client. Your infrastructure. Your choice.01
Launch with context
EHR and standalone launch orchestration, patient and encounter context, PKCE, and single-use activation codes.
02
Connect across organizations
Reusable application registrations, EHR platform profiles, organization connections, and installation-specific policies.
03
Choose your access path
Use the read/search gateway, connect directly with managed renewal, or explicitly take credential ownership.
04
Go beyond browser launches
SMART Backend Services, authenticated CDS Hooks forwarding, and optional TypeScript and Python SDKs.
02 / The guiding principleKeep the standards.
Keep the standards.
Lose the guesswork.
FHIR makes health data interoperable. The surrounding setup can still be complicated. Our tools make that work understandable, repeatable, and yours to control.
Fit your application.
Use familiar HTTP and FHIR clients. Adopt an SDK when it helps. Choose the integration boundary that works for your architecture.
Keep control.
Inspect the source, self-host the service, and understand its boundaries. Clear community terms make it accessible to more builders.
03 / From reading to runningStart local.
Start local.
Learn by doing.
Clone the source and use the guided Docker installer. Explore synthetic EHR launches before connecting a real organization.
- 1Choose your setup
Docker guided setup or a Node.js source checkout.
- 2Run your first SMART launch
Open the workspace and follow the Developer lab.
- 3Build your integration
Register your app, choose an access mode, and connect.
macOS / Linux · guided Docker setup
git clone https://github.com/davidvaccaro/smart-flint.git
cd smart-flint
bash ./install.shChoose “Try SMART Flint”
Then open http://127.0.0.1:3010. The guided Windows installer is available too. No host Node.js installation is needed for Docker setup.
Synthetic protocol simulators are included. Real EHR onboarding and deployment-specific validation are separate steps.