Norwegian FHIR Hackathon 2026
1.5.0 - ci-build
Norwegian FHIR Hackathon 2026 - Local Development build (v1.5.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
FHIR is the data. SMART is what makes an app safe to plug into someone else's journal system. In this track you build the plug.
Track lead: Leo-Andreas Ervik, Nav.
Co-host: Jørn-Are Klubben Flaten, Nav.
public/README.md.Syntpop test clinicians
Each group shares its six test clinicians. Use a clinician from your group's rows below. Enter all 11 digits of the fødselsnummer, including any leading zero. These are synthetic test identities.
| Group | Fødselsnummer | Name |
|---|---|---|
| 1 | 28677509882 |
LØSNINGSORIENTERT DIAMETER |
| 1 | 22728131350 |
BESTEMT FOTNOTE |
| 1 | 21687739091 |
GØYAL FATTET DUE |
| 1 | 27717523763 |
RETT BYTTE |
| 1 | 12775015754 |
FORSKJELLIG JOURNAL |
| 1 | 25725696917 |
PASSIV RAVGUL OPPVASKMASKIN |
| 2 | 04685611959 |
KOMPATIBEL MÅNE |
| 2 | 05687536179 |
INKONSEKVENT KORTSTOKK |
| 2 | 06676340007 |
RETT DEKLARASJON |
| 2 | 08695717505 |
UKJENT LITEN AGG |
| 2 | 04667408313 |
ÄNDLÖS VOTT |
| 2 | 06705502321 |
OPPFARENDE FABRIKKPIPE |
| 3 | 13747390929 |
COMÚN LIGGESTOL |
| 3 | 03726112907 |
VÅKEN EVALUERING |
| 3 | 08775501708 |
FINTFØLENDE SLAPP FARESKILT |
| 3 | 25687490072 |
PÅLITELIG TREGRENSE |
| 3 | 17707948426 |
UROLIG HUSBÅT |
| 3 | 22667416691 |
RASTLØS BIOGRAF |
| 4 | 20716600700 |
TREIG HEST |
| 4 | 10697019362 |
VARSOM TUNFISK |
| 4 | 15765612710 |
KUNSTIG ONSDAG |
| 4 | 12675904675 |
ARITMETISK NØYTRAL FJELLKJEDE |
| 4 | 23736428482 |
HANDLENDE AKADEMISK BOOM |
| 4 | 06745732826 |
PRODUKTIV SVALE |
| 5 | 31666735709 |
JUSTERBAR FASE |
| 5 | 28695936569 |
TRIST TROMMIS |
| 5 | 30745547741 |
UGJENNOMSIKTIG BIOLOGI |
| 5 | 08685422981 |
UMAKE FUNKSJONÆR |
| 5 | 25727599404 |
VARSOM SERVITUTT |
| 5 | 20665046924 |
OPPSTEMT FLØYTE |
Most of us know FHIR as "resources and a REST API". Far fewer have worked with the SMART half of SMART on FHIR and how an application is launched from inside an EPJ, how it learns which patient, which clinician and which consultation without anyone typing anything. And how the EPJ stays in control of what that application is allowed to see.
By the end of the day you will have built a working SMART application and launched it from an EPJ provided by the track, against synthetic Norwegian patients.
No prior SMART or FHIR experience is needed. Teams mix developers and low-code or no-code builders, see Team roles.
The track mixes Norwegian and international terminology, because the specifications are written in English while the systems and identifiers we work with are Norwegian. This is the vocabulary we use.
Systems and standards
| Term | Means |
|---|---|
| EPJ | Elektronisk pasientjournal. The clinical system that holds the record and launches your app. This page uses EPJ throughout. |
| EHR | Electronic Health Record. The international term for the same thing. The SMART specification calls the flow we use EHR launch, so you will meet "EHR" in the spec where we say "EPJ". |
| FHIR | HL7's standard for exchanging health data. The data model and the REST API. |
| SMART | The standard that lets an EPJ launch a third-party app, authenticate the user, and hand the app a limited, short-lived access token. |
| SMART on FHIR | The two combined. SMART handles who you are and what you may see, FHIR handles the data itself. |
| HelseID | The national identity provider for Norwegian health personnel. |
| IG | Implementation Guide. A published specification such as this page's parent document. |
SMART and OAuth vocabulary
| Term | Means |
|---|---|
| Launch | The EPJ opening your app, passing along a one-time launch identifier. |
| Launch context | What the app is told about the situation: which patient, which encounter, which user. |
| Scope | The permissions the app asks for, for example patient/Condition.read. A contract between app and EPJ. |
| Access token | The short-lived credential the app uses when calling the FHIR API. |
| ID-token | Tells the app who the logged-in user is. |
| PKCE | Proof Key for Code Exchange. Stops someone else from stealing and using your authorization code. |
| Discovery | Reading .well-known/smart-configuration to learn where the EPJ's endpoints are. |
| JWKS | The public keys used to verify that a token really came from who it claims. |
Norwegian identifiers and code systems
| Term | Means |
|---|---|
| Fødselsnummer | The 11-digit Norwegian national identity number. |
| D-nummer | Identity number for people without a fødselsnummer, such as short-term residents. |
| HPR-nummer | The identifier for registered health personnel. Identifies the clinician. |
| Organisasjonsnummer | The identifier for a legal entity, such as a fastlegekontor. |
| ICPC-2 | Diagnosis coding used in Norwegian primary care. |
| ICD-10 | Diagnosis coding used in specialist care. |
| LOINC | International coding for measurements and lab results. |
public/ exercise containing numbered TODOs and finished
templates in client-secret/, private-key-jwt/ and backend-services/.client_id (hackathon-public), a set of test
clinicians per group, and a list of patients. Mentors register secret or key clients on request.The public/ skeleton implements the SMART launch from scratch, server-side. It does not use an
off-the-shelf SMART client library, for two reasons:
authorize().A reference implementation is provided for when you get stuck.
No prior SMART or FHIR knowledge is required, and there is no required pre-work. Turn up and we will get you running. If FHIR itself is new to you, consider dropping into the FHIR 101 track in the morning.
What you need on the day:
| Requirement | Detail |
|---|---|
| A laptop | Any operating system. You will be writing and running code on it. |
| A code editor | Visual Studio Code, IntelliJ IDEA or whichever you already use. Either is fine. |
| A GitHub account | You will clone the starter repository and push your team's work. |
| Node 22 | For running the starter locally. |
| A charger | ⚡️ |
Optional, only if SMART is entirely new to you, and you want a head start:
By the end of the day you should be able to:
iss, launch, state, code_verifier,
aud and code is protecting against;.well-known/smart-configuration document and know which endpoints matter;After the shared intro there is no presenter and no scheduled checkpoint. Learn SMART, then build, using the browser checklist (why, hints and rescue for each TODO), the discussion prompts in the starter README and the pacing rule below. Mentors help when you get stuck.
Assignments come in three tiers. Pick the one that matches your team and move up during the day. This is a learning track, not a competition. There are no prizes, and helping the team next to you is encouraged.
Your team chooses the clinical workflow it builds for. You can take one of the optional problem cards, which are starting hypotheses rather than confirmed clinical needs, or bring your own idea.
It launched. Target: every team, before lunch.
Launch the skeleton from the EPJ, complete the authorization code exchange on the server, and display the patient's name and age together with the active consultation. The skeleton has 10 numbered TODOs and the checklist tracks them.
When all 10 are done, the checklist shows a "Before you build" box with discussion prompts. Answer
them out loud to each other: open your browser's network tab and explain each redirect, and say what
iss, launch, state, code_verifier, aud and code protect against. The prompts help you
explain the flow. They do not make your app certified or secure.
If you are stuck, follow the Stuck section of the starter README. Start with the hint and the why on the checklist, then compare your code with the solved step on GitHub, or run the full solved app in a separate folder.
It is useful, and it is honest. Pick one.
It writes back, or it does something nobody expected.
Write-back is the default goal for the build phase; authentication options are optional extensions.
private_key_jwt end to end. Ask a mentor to
register a client.state. Replay a code. Send a token with
the wrong aud. Use an expired token. Ask for a resource outside your scopes. Document what the
server correctly rejected, and what it did not.Roles are for people who build in different ways, whether they write code or use low-code and no-code tools. Every team member can contribute without writing the OAuth flow by hand. Swap roles during the day. Several people can share a role.
curl and the browser, as described under
Break it in Gold, and keeps notes on what was rejected..well-known/smart-configurationContact the track lead, Leo-Andreas Ervik (Nav), or ask in the track channel.