FHIR Camp 2026

Day 3 · November 6

FHIR Hackathon

A day to make something that actually runs. Pick an idea and build a prototype with the experts you met in BoFs and panels.

How it works
  • 1 Create a project or join one Open the Hackathon tab in the Camp app — add your idea, or join one of the projects already there.
  • 2 Invite people to join your project Invite them in the app or just talk to them over coffee. Solo is fine too.
  • 3 Pitch at the kickoff If the project is yours, you get two minutes in the morning to explain it and find teammates.
  • 4 Build it together Two hacking sessions with lunch in between — about eight hours, enough for a prototype.
  • 5 Demo your prototype Ten minutes per team at the end of the day, live and running. Broken edges are fine, slides are not.
  • 6 Vote for the winner Everyone at the camp votes in the app right after the demos — no jury, results show up live on the screen. · You can't vote for your own project · +1 on each vote if the project uses FHIR · +1 on each vote if the team has more than one person
  • 9:30–10:00 Coffee & welcome
  • 10:00–11:00 Kickoff & idea pitches · 2 min per team
  • 11:00–13:00 Hacking session 1
  • 13:00–14:00 Lunch
  • 14:00–16:00 Hacking session 2
  • 16:00–17:00 Demos · 10 min per team
  • 17:00–17:30 Closing
How to choose a project

You can prototype or build anything related to healthcare or FHIR — an app, a clinical workflow, a research tool, or a purely technical project like a parser, a validator or a library.

  • Healthcare or FHIR related
  • Can be shown live, not on slides
  • Solo or team, any size
  • Yours — you pick the idea, no assigned themes
  • Any tools, any prior preparation

Nothing has to start from scratch. Prepare in advance, bring a repo you've already started, use AI for as much of the work as you want, build on your own product or stack. Any tools, any libraries. Have fun, learn something new, and get to the demo — that's the whole goal.

Ideas to start from

No idea yet? Six directions where this room is unusually well placed to build — chances are someone at your table has already solved half of it.

Agents and AI on FHIR

· An agent that answers clinical questions by querying FHIR instead of guessing

· Retrieval over clinical guidelines, grounded in real sources

· FHIR bundles into compact text for prompts, without leaking PII

Messy data into FHIR

· CDA or HL7 v2 to FHIR, with validation as the judge

· A terminology mapping helper across SNOMED, LOINC, ICD-10 and RxNorm

· A registry extract or a spreadsheet turned into clean resources

Validation and CI

· A validation pipeline you'd actually put in CI, with readable failures

· A test-data generator that produces plausible patients for an IG

· A cross-version diff (R4 to R5 to R6) run against real resources

Workflows that run

· A CDS Hooks service that fires inside a real workflow

· A guideline turned into something executable with PlanDefinition

· An SDC questionnaire that pre-fills from the record and writes back

Getting data out

· A SQL on FHIR view that answers a question your analysts keep asking

· A FHIR to OMOP slice with the terminology part left visible

· A dashboard a clinician would open twice

Tooling for FHIR developers

· One CLI that works across FHIR servers

· A FHIRPath debugger that explains why an expression returns empty

· IG tooling: preview, linting, anything that makes authoring hurt less

Tools you can use

Free for the hackathon. Bring your own stack too — the point is to have something running by demo time, not to learn a new tool in eight hours.

Aidbox

FHIR server to build against — storage, search, and the API your prototype talks to.

Get started

Hosted sandbox at aidbox.app, no setup. Or local Docker — about five minutes if you have Docker.

Terms

Free dev instance for the hackathon. Nothing to request in advance.

Contact

The Health Samurai team on site, or ask in the Camp app.

BMJ clinical intelligence

deadline

Peer-reviewed clinical guidelines as a computable knowledge graph — 30+ specialty areas, mapped to SNOMED CT, LOINC, RxNorm, ICD-10 and CPT.

Free for Camp participants, but access must be set up at least one week before November 6.

A GraphQL server in GitHub Codespaces with an interactive workbench, starter queries, synthetic patients and value sets. Slices cover COPD, acute COPD, type 2 diabetes in adults, ongoing atrial fibrillation and ischemic stroke.

Good for

· Grounded AI and RAG — answers backed by validated clinical evidence

· FHIR-native CDS with PlanDefinition and ClinicalReasoning

· Differential diagnosis and risk stratification

· Prior authorization logic

Get started

Request access by email, then open the Codespace.

Contact

Derrick Leung — dleung@bmj.com. Send your GitHub username and a one-line description of your project.

Add your own tool

Using something the rest of the room should know about — an API, a dataset, a library, a sandbox of your own product? Add it in the Camp app and it shows up here for everyone.

The form asks for

Name — required

What it is — required, one line

Details — optional, a paragraph

Good for — optional, a few use cases

Get started — how to get going

Terms — cost, access conditions, deadlines

Links — docs, repo, sandbox

Contact — who to ask

Add a tool