Danish Hackathon 2026
1.0.2 - release
Danish Hackathon 2026
1.0.2 - release
Danish Hackathon 2026, published by HL7 Denmark. This guide is not an authorized publication; it is the continuous build for version 1.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7dk/dk-hackathons/ and changes regularly. See the Directory of published versions
Track lead: Jacob Andersen
Imagine a health system where the citizen is at the centre — where data follows the person, and where every individual has real control over what is shared, with whom, and for how long.
That future is now encoded in law. The European Health Data Space (EHDS), in force since March 2025, grants every EU citizen the right to access, download, and share their personal electronic health data. It also creates a legal framework for citizens to contribute their data — including patient-generated data (PGHD) from wearables and apps — to research under transparent, revocable consent. The standards are converging. The regulation is in force. What does that actually look like, built in FHIR, running today?
This track invites participants to explore that question by building components of a personal health dataspace: an ecosystem where a citizen's health data — whether sourced from a hospital EHR, a fitness tracker, a blood glucose monitor, or an environmental sensor — can be stored, shared, and optionally donated to research, all under the citizen's own control.
There is no single prescribed task. Participants are free to build whatever component they find most interesting or meaningful. We do, however, encourage participants to communicate their intentions ahead of the hackathon so that components built on the day can potentially be demonstrated together.
This track hopes to demonstrate — at least in prototype form — some of the following propositions:
As a common scenario, we will be using the case of Anne Sørensen moving from Denmark to Germany:
Anne Sørensen is a 41-year-old woman (fictional test persona) who grew up and has lived her whole life in Denmark, but recently moved to Flensburg, Germany, while continuing to work in Sønderborg. Her healthcare ties are therefore split — and shifting — between two countries: she holds a Danish pension scheme with private health insurance, keeps her dentist and physiotherapist in Denmark near her workplace, but is in the process of switching her general practitioner from her long-standing Danish GP to a new German GP in Flensburg. She is under active treatment for hypertension and type 2 diabetes, and self-reports a penicillin allergy that is not recorded in any of her electronic records.
To give participants something to build towards and against, the track will provide a number of pre-deployed shared FHIR (R4) servers running HAPI FHIR. Details about the configuration of each server and its intended use will be published on this platform overview page. This page is work in progress, so please monitor it for changes.
Participants are not required to use these servers. Anyone who prefers to run their own FHIR backend (Medplum, another HAPI FHIR instance, Aidbox, etc.) are welcome to do so. The shared servers exist to lower the barrier of entry and to enable inter-component demos.
A common GitHub repository is set up here. The intention is that all participants/teams can clone this repo, create a folder named after their component, and add contents in a shared code space. Initially, this repository is public, to allow all participants to started. As participants join the hackathon track, they will get write permissions to this repo, and we may choose to close it down to private visibility when the hackathon starts and all relevant participants have been invited in.
The Anne Sørensen character has been added to MitID, NemLogin and FUT test environments, if anyone would like to play with any of these.
All participants are asked to join and monitor the conversation on the FHIR Zulip #denmark channel "hackathon 2026 track 3 coordination" in order to coordinate as much as possible before the hackathon begins.
The following is an illustrative — not exhaustive — list of components participants could choose to build. They are organized into four groups. Participants are welcome to address problems in any group – or across. Bring-Your-Own-Idea!
Consent resource, profiled according to IHE Privacy Consent on FHIR (PCF). The consent should distinguish between clinical use (primary) and research use (secondary).Consent resource recording the donation decision. Data For Good Foundation is an example of a platform that could be a recipient.Consent resource.This track deliberately leaves participants free to choose their own focus. There are no required tasks, and there is no expectation that every participant's work will integrate with everyone else's.
That said, there is real value in knowing what others are building — both to avoid duplication and to enable a more interesting closing demo. Before the hackathon, participants are asked to briefly describe their intended component on the FHIR Zulip #denmark channel "hackathon 2026 track 3 coordination". The track lead will compile a simple overview and share it at the preparatory webinar.
During the closing session, participants who wish to attempt a live integration demo are encouraged to identify potential "connection points" with other components — but this is entirely optional and should not drive scope decisions on the day.
Participants should arrive prepared. Before the hackathon:
Participants are not expected to deliver a production-ready system. A successful outcome for any participant is one or more of the following:
The track lead will collect links to all repositories and write-ups after the hackathon and compile a summary for the Results page and for the HL7 Denmark pitch session at eSundhedsobservatoriet on October 7.
| Resource | Description |
|---|---|
| HL7 Personal Health Records IG | Core IG for structuring a FHIR-based PHR. |
| HL7 Personal Health Device IG | Core IG for collecting measurements from personal health devices. |
| IPA — International Patient Access | Minimum FHIR API a clinical system must expose for patient access. |
| IPS — International Patient Summary | Cross-border patient summary; one of the six EHDS EEHRxF priority categories. |
| SMART Health Cards & Links IG | Citizen-controlled, cryptographically verifiable data sharing via QR codes and links. |
| IHE Privacy Consent on FHIR (PCF) | FHIR Consent profiling with OAuth integration; the most complete consent-enforcement profile available. |
| EU Health Data API IG (EURIDICE) | Joint HL7 Europe / IHE specification for EHDS Article 15 EHR interoperability component. |
| HL7 Europe Base/Core IG | Common EU FHIR foundation. |
| DK-Core IG | Danish base profiles: Patient (CPR), Practitioner, Organisation, etc. |
| DK SMART IG | Danish SMART App Launch Specification. |
| MedCom FHIR | Danish healthcare messaging profiles. |
| Nordic FHIR Terminology Server | Shared terminology server for the Nordic countries. |
| Tool | Language | Description |
|---|---|---|
| Medplum | TypeScript | Open source FHIR-native platform with SMART on FHIR built in. |
| HAPI FHIR JPA Server | Java | The canonical open source FHIR server. Stable and well-documented. |
| gICS — generic Informed Consent Service | Java | Open source (AGPL v3) consent management with FHIR gateway. Used in production in German research networks. Docker-ready. |
| HealthKitOnFHIR | Swift | Stanford library for mapping Apple HealthKit samples to FHIR Observations. |
| EUDI Wallet reference implementations | Various | EU Digital Identity Wallet — Android, iOS, and issuer libraries. All open source. |
| SMART Health Links reference | TypeScript | Reference implementation of the SMART Health Links specification. |
| openFHIR | TypeScript | Bidirectional openEHR ↔ FHIR mapping engine. Useful if working with openEHR-based systems. |
| eHealth Reference Clients | Java | Reference client implementations for the DK eHealth infrastructure (FUT). |
| Source | Description |
|---|---|
| DMI's Open Data API | Danish Meteorological Institute: weather, pollen, climate. Free API key required. |
| Google Health Connect | Android aggregation layer for wearable and fitness data. |
| Apple HealthKit | iOS health data platform. |
| Withings Developer API | REST API for Withings scales, blood pressure monitors, etc. |
| Garmin Health API | REST API for Garmin wearables. |
| Resource | Description |
|---|---|
| EHDS Regulation (EU) 2025/327 | The regulation itself and the EU Commission's summary page. |
| HL7 Data Access Policies IG | R6-direction for FHIR Permission resource as complement to Consent. |
| Data For Good Foundation | Danish-based consent-driven data sharing platform; a potential recipient for donated PGHD. |
| Kanta PHR (Finland) | A national PHR for citizens in Finland; useful as a reference architecture. |
| FHIR Validator | Online FHIR resource validator. |
| FHIR Shorthand (FSH) | If you want to define profiles as part of your work. |
See the Results page after the hackathon.