Leaderboard
| # | Company | Score | Status | Also | Sections | Resources | Errors (best) | Last submission |
|---|
How scoring works
Fix conformance first, because any error or fatal validation issue scores your submission 0. A valid bundle earns 50, plus +10 per distinct Composition section that actually has entries (capped at +160), and +2 for every clinical resource outside the Composition and Patient (capped at +60). Sections only count once - repeating a section or padding the bundle will not make it richer. Your company score is your best patient summary, plus a one-time +20 "first pass" bonus for the first company to submit a valid one, plus +15 for each other EHDS document type you also get passing. Interop testing is not scored.
Other EHDS documents we also validate3
This is the patient summary track, and the summary is what the leaderboard ranks. But EHDS (Regulation (EU) 2025/327, Article 14) names six priority categories of health data that EHR systems have to exchange, so if you bring one of the others it is detected from the bundle and validated properly against its own HL7 Europe guide. Each one you pass is worth a flat +15.
| EHDS category | Guide | Maturity |
|---|
Register your company
One registration per company - share the token with your colleagues.
Save this token, share it with company colleagues, and use it with every submission to identify your team.
Submit your EPS
Bringing one of the other EHDS document types instead? Send it here too - it is recognised from the bundle and checked against its own guide.
Embedded view
Or use the API
Every endpoint is described in the OpenAPI spec, which you can also browse and call from the interactive docs.
Register your company:
Submit a bundle (response headers carry X-Pass / X-Score / X-Errors, body is the FHIR OperationOutcome):
Leaderboard:
Clinical view of submitted documents
Interop testing
Compliance proves you can produce a valid patient summary, while interoperability testing proves another system can consume it. Every company's best valid submission is published below as its exchange document - take one, load one into your own system and see how well it renders.
After you've loaded the document, add a screenshot below showing how it renders in your system with an optional note. This will enable everyone in the hackathon, including the clinicians, to appreciate how well your system renders the patient summary data.
Published documents
Or use the API
Every endpoint is described in the OpenAPI spec, which you can also browse and call from the interactive docs.
Fetch a company's exchange document: