unlock.eir.space Unlock by Eir
Sweden is live. Finland is in pilot. Europe is next.

Help unlock healthcare data for every patient, in every country.

Citizens already have a right to see their health data. Unlock turns that right into an open, practical integration effort. One person logs into their official patient portal. One contribution helps map a country. Enough good contributions turn a portal into a working Eir adapter.

Download the extension Collaborate on Discord See the contribution flow
You log in yourself. No passwords are collected. Capture is reviewed before sharing.
Mission

Healthcare data should not stay locked behind country borders, vendor walls, or institutional inertia.

Unlock is the public side of Eir's integration work. The mission is simple: make it possible for people to access and carry their own healthcare data in the same way they already do through official patient portals. Not by waiting for every institution to modernize. By showing the path, mapping the flow, and turning real patient access into reusable integrations.

The tone matters. This is not data extraction theater. It is careful, review-first infrastructure work. Citizens contribute from the portals they already trust. Eir helps structure what is needed to unlock that country's electronic health record flow for everyone who comes next.

Patient-led

The patient performs the real login. Unlock never asks for a password and never turns access into a black box.

Protocol-aware

We learn from the actual transport layer: pages, API calls, response schemas, and document downloads.

Country by country

Each unlocked country becomes a documented public asset: portal flow, data mapping, and adapter confidence.

Built to ship

This is not a petition site. The output is working product infrastructure inside Eir.

How it works

One guided mission. One reviewed contribution. One step closer to a country adapter.

The contribution flow is designed to be autonomous where it should be and human where it must be. The user does the official login. Unlock guides the rest: which pages to visit, what evidence to capture, and what to review before anything is shared.

01

Choose your country and portal

Select the official patient portal you already use. Sweden is live. Finland is in capture pilot. More national missions follow the same template.

02

Log in yourself

Open the portal, authenticate as usual, and stay in control. Unlock records the flow around the session, not your password, OTP, or cookies.

03

Follow the mission path

Go to records, prescriptions, labs, vaccinations, visits, and any export screens. The extension captures page structure, network traffic, and document behavior.

04

Review and contribute

You inspect the capture bundle first. Shared contributions help Eir identify endpoints, map schemas, and promote a country from observed to unlocked.

Country missions

Sweden proves the route. Finland is the pilot. The next wave is already visible.

Not every market has the same shape. Some countries have one clean national portal. Others route citizens through regions, insurers, or personal health environments. Unlock makes that visible and turns it into an execution queue.

Live now

Sweden

1177 Journalen is the production path today. Citizens can download the Chrome plugin, export their healthcare data from 1177 into `.eir` files, and open it inside the Eir apps.

Portal: 1177 Mode: plugin download Status: usable now
Pilot mission

Finland

MyKanta is the first Unlock mission. The same extension now includes a Finland trial mode with capture bundles and page-level `.eir` exports from logged-in MyKanta pages.

Portal: MyKanta Mode: guided capture Status: active pilot
Research queue

Clean national portal candidates

Denmark, Estonia, Poland, Austria, Hungary, Slovenia, and Luxembourg look like the strongest follow-on countries for the current browser-first model.

Best fit for Eir National patient flow
Structured backlog

Messier but important

Belgium, France, Portugal, Germany, Italy, Spain, and the Netherlands need deeper analysis because the patient flow is distributed, app-heavy, or institution-fragmented.

Needs endpoint clustering Higher maintenance risk
Unlock missions

The system should feel clear, serious, and motivating enough that people want to help.

Each mission is small enough to complete in one sitting and structured enough to produce usable technical evidence. The user never has to improvise what to click next.

Mission type

Unlock a country

High leverage

Best for countries where no working Eir adapter exists yet. One good mission can surface the routes, schemas, and product constraints that define the whole country build.

  1. Open the official patient portal for your country.
  2. Visit records, prescriptions, labs, vaccinations, and documents.
  3. Stop recording and review the capture bundle locally.
  4. Contribute the structured mission output.
Mission type

Strengthen an existing adapter

Quality pass

Useful when a country is already observed or partially mapped. New sessions help validate endpoint stability across users, clinics, regions, and time.

  1. Run the guided flow with the current capture mission.
  2. Confirm whether the same core routes still appear.
  3. Highlight missing data categories or broken navigation paths.
  4. Help move the country from draft to validated.
Sweden

The working example already exists.

Sweden is not just a concept page. The 1177 Chrome plugin already lets people download their healthcare data and bring it into EIR. That matters because it shows the entire thesis can move from patient portal to usable health data product without waiting for centralized permission structures.

Live workflow

How Sweden works today

Download the Chrome plugin, sign in to 1177 as usual, click the floating downloader, and download your healthcare data into `.eir` files that work with Eir. No cloud storage. No tracking. The records stay on your device unless you choose to move them.

Download extension zip Open 1177 View source

Install in Chrome

Unzip the file, open Chrome or another Chromium browser, then load the extension locally.

  • Download eir-chrome-extension.zip.
  • Unzip it so you have a local ChromeExtension folder.
  • Open chrome://extensions/ and turn on Developer mode.
  • Click Load unpacked and select the unzipped ChromeExtension folder.

Sweden live, Finland trial

The current build has two country modes inside one extension.

  • Sweden: production export from 1177 Journalen into `.eir` journal-note files.
  • Finland: trial integration on MyKanta with capture bundles and per-page `.eir` downloads for mapping the portal.
  • Other countries: tracked in the atlas with portal access instructions and claimable integration missions.
Privacy and trust

Unlock has to be ambitious without ever becoming reckless.

The project only works if contributors understand the boundaries clearly. The model is not “give us your login.” It is “perform your normal login, let the extension observe the patient-visible flow, and review the bundle before anything leaves your device.”

What the capture can include

  • Visited page routes and navigation steps
  • Sanitized HTML snapshots and visible text
  • Fetch and XHR request URLs, methods, statuses, and response bodies
  • Document download behavior and page classifications
  • Structured evidence that helps identify endpoint families and schemas

What the capture should never keep

  • Passwords or OTP values
  • Cookie values, bearer tokens, or authorization secrets
  • Hidden credential material copied from the browser state
  • Any upload that the contributor has not reviewed locally first
Open atlas

See what is unlocked, how to access your data, and who has claimed the next country.

The atlas is useful even before a country is integrated. Every country points to the official patient access route. Every country mission links to a GitHub issue where someone can claim the work in public.

Mission map

Europe first, with Nordic countries outside the EU included.

The map shows where Eir is already live, where pilots are active, and where contribution is still needed.

EU patient EHR map

A country-by-country view of the official patient-facing portals used across the EU, plus the likely integration shape for each market.

Read the map

Execution roadmap

A build-oriented roadmap that turns the country analysis into rollout priorities, adapter strategy, and practical sequencing for Eir.

Read the roadmap
When it works

Every unlocked country should end in the same simple outcome for the patient.

The integration work is not finished when a portal is mapped. It is finished when a person can open the official portal for their country, use the Chrome plugin, and download their healthcare data into a local format that is structured, readable, and portable.

The product outcome

Download your healthcare data in .eir.

When an integration is live, the patient does not need to understand endpoints, page states, or internal healthcare systems. They log in through the same official path they already use, click the Eir plugin, and download their records in a format designed to be easy to read and usable across Eir products.

Download the extension Collaborate on Discord See the live Swedish portal

How the live integration works

Sweden is the working reference. A patient installs the Chrome plugin, signs in to 1177 as usual, opens Journalen, and downloads their healthcare data locally. The plugin turns the patient-visible records into a consistent .eir export instead of leaving the information trapped inside one portal view.

  • The patient uses the normal national login flow.
  • The plugin runs on the logged-in healthcare pages.
  • The export is saved locally in a clear, structured format.

The same model should work country by country

Finland is the current trial path, and the same approach extends to every country once the portal flow is understood well enough. Unlock exists to make that reusable: official patient login, browser-side extraction, local download, and one common Eir format instead of one-off country silos.

  • Map the official patient portal and data routes.
  • Build the country adapter into the extension.
  • Let patients in that country download their own records the same way.

Why this matters

The goal is not just to inspect healthcare portals. It is to give people a dependable way to take their data with them in every market where electronic access already exists. Once a country is unlocked, the result should feel ordinary: log in, download your data, read it easily, and keep it under your own control.

Questions

What people need to understand before they help.

Is this only for Europe?

No. The current strategy starts with Sweden, Finland, and the wider EU because the patient portal landscape is already visible there. The model can expand to other countries once the mission system is mature.

Why not just wait for official APIs?

Because the patient-visible route already exists. Unlock starts from what citizens can already access electronically, then builds the product path from there. Official APIs are still valuable later, but they should not be the only route to progress.

Why does the language sound so direct?

Because this project is meant to feel operational, not ornamental. The aim is to unlock real healthcare data access, not to surround the problem with abstract policy language.

What is the actual output of a mission?

A reviewed capture bundle that helps Eir identify routes, endpoints, payload shapes, data categories, and adapter confidence. The contribution feeds real integration work.