Custom MedMij integration development
MedMij is the framework of agreements that allows patients to retrieve their health data in a personal health environment, or PGO. Healthcare providers make that data available through a qualified service provider. Appfront builds the technology in between: the data services in FHIR, authorisation with OAuth 2.0, and the integration with the healthcare system the data comes from.
What is a MedMij integration?
MedMij is the framework of agreements from the MedMij Foundation (Stichting MedMij) for the secure exchange of health data between healthcare providers and patients. A patient uses a personal health environment, a PGO, from a person-side service provider. The healthcare provider is represented by a provider-side service provider, which makes the data from the care system available. Logging in is done with DigiD.
Which data can be exchanged is set out in the data services, such as the Basic Dataset for Healthcare (BgZ), GP data, medication data, laboratory results and questionnaires. Together with Nictiz, they are based on HL7 FHIR. Authorisation runs via OAuth 2.0, with the provider-side service provider acting as the authorisation server. The Wegiz (Dutch Electronic Data Exchange in Healthcare Act) makes exchange with a PGO mandatory for a number of data types, such as the medication agreement at the GP since 1 July 2024.
We build the technology, not the participation. Anyone who joins MedMij as a service provider signs a participation agreement, holds an NEN 7510 certificate and has an audit carried out every year. We make sure your software correctly delivers or retrieves the data services, connects to your care system, and passes the tests.
Data to the patient
In the PGO of their choice.
According to the agreements
Data services in FHIR.
Securely authorised
OAuth 2.0 and DigiD.
How we build your MedMij integration
We start with your role: are you a supplier of a care system, of a PGO, or a healthcare provider with your own systems? Which data services do you want to support, and where do you stand on participation and certification? Then we look at your care system and the specifications of the data services. We often start with a single data service, such as the Basic Dataset for Healthcare or medication, because that is where the demand or the obligation lies. Other services follow once the first one works well. After that, we keep the integration up to date whenever the framework of agreements or the information standards get a new version.
Supplier, PGO or healthcare provider.
Data services and versions.
FHIR, OAuth and care system.
Testing, go-live, new versions.
What a MedMij integration actually does
The components below feature in almost every MedMij integration. Which ones you need depends on your role and the data services.
Data services
BgZ, medication and more.
FHIR resources
According to the standards.
OAuth 2.0
Authorisation per request.
Care system
Where the data is held.
Availability
Monitored and measured.
Logging
According to the standards framework.
Who we build a MedMij integration for
The integration is intended for organisations that want to bring health data to or from a PGO in line with MedMij. The more data services and healthcare providers, the more it delivers.
Care system vendors
Making data available.
PGO suppliers
Retrieving and displaying data.
Care providers
Own systems. Wegiz applies.
Existing participants
Adding new data services.
Technology and integrations
This page is about exchange with the patient via a PGO. For exchange between healthcare providers under the Wegiz, see our page on the Wegiz integration, for the Basic Dataset for Healthcare our page on the BgZ integration, and for referrals to other healthcare providers our page on the ZorgDomein integration. You can read about our approach on custom software development.
Why Appfront for your MedMij integration?
A care system that cannot deliver data to a PGO, a Wegiz obligation that is getting closer, and specifications that change with every version all cost a supplier or healthcare provider customers and time. That is what we build on: data to the patient, according to the agreements, and securely authorised.
Ready for the Wegiz
Where exchange is mandatory.
Passes the tests
According to the specifications.
Kept up to date
With new versions.
Security and privacy in a MedMij integration
The integration processes medical data. This is special-category personal data, and the requirements are strict. We work within the MedMij information security framework, with logging in line with NEN 7513, access only after authorisation by the patient, and encryption of all connections.
The integration runs in a European data centre that meets the requirements of your certification, with encrypted storage and backups. We record the processing in a data processing agreement and support the annual audit.
Frequently asked questions about a MedMij integration
Questions that suppliers and healthcare providers ask before getting started.
MedMij is a framework of agreements maintained by the MedMij Foundation. It sets out how health data is passed securely from a healthcare provider to a patient's personal health environment, and which roles, standards and security requirements apply. A PHR (PGO) with the MedMij label complies with those agreements.
No. Participants are the service providers, such as the supplier of the healthcare system or the PHR. They sign the participation agreement, hold an NEN 7510 certificate and have the annual audit carried out. We build the technology into their software or into the healthcare provider's systems.
MedMij has a range of data services, including the Basic Healthcare Dataset (Basisgegevensset Zorg), GP data, medication data, laboratory results, vaccinations, questionnaires and documents such as PDF/A. Which ones you need depends on your type of care and on what the Wegiz (Dutch Act on electronic data exchange in healthcare) makes mandatory for you.
Data is exchanged as HL7 FHIR resources, following the information standards of Nictiz and MedMij. The patient logs in with DigiD and gives consent, after which the PHR uses a token to request the data from the data-providing service provider. The framework also sets requirements for availability and response time.
The Wegiz makes electronic exchange mandatory for a number of data types. Since 1 July 2024, GPs have been required to make the medication agreement available to a PHR with the MedMij label, and according to the ministry's schedule the Basic Healthcare Dataset will follow, also towards the PHR. We look at which obligation applies to you in the first step.
Then we adapt the integration. MedMij and Nictiz publish new versions of the framework and the information standards, and for each version we look at what changes in the data services or the technology. That way your software stays compliant without you having to keep track of it yourself.
For suppliers of healthcare systems that want to make data available, PHR suppliers, healthcare providers with their own systems, and existing participants that want to add a data service. If your healthcare system already supplies the data via a qualified service provider, your own integration is often not needed.
Health data to the PHR?
Tell us which role you have and which data services you want to support. We'll show you what the integration looks like.