Custom UZI pass integration
The UZI register of CIBG enables healthcare providers and care-assessment bodies to be uniquely identified in electronic communication. Healthcare professionals and their staff use the UZI card, a kind of electronic passport, and systems use a UZI server certificate. If you want healthcare professionals to log in to your own application with their card, or your system needs to identify itself with a server certificate, you need an integration that verifies the certificates. Appfront builds that integration.
What is a UZI card integration?
A UZI card integration ensures your software knows for certain who is logging in or which system is connecting. The UZI register is part of CIBG, an executive agency of the Dutch Ministry of Health, Welfare and Sport (VWS), and acts as a Trust Service Provider. There are three types of card: the healthcare professional card, the named employee card and the unnamed employee card. The cardholder's personal details are stored in the certificate on the card. According to the UZI register, a cardholder can use it to identify themselves, exchange data with other subscribers and verify patients' citizen service numbers (BSN). A new card must first be activated using the SafeSign software.
The server certificate is for systems. According to the UZI register, it lets you use the BSN services of SBV-Z, identify your organisation when exchanging medical data (which also requires a card), set up a secure connection with other systems and encrypt medical data. The certificates are issued under the Dutch government PKI, with the root certificate of the Dutch State as the highest trust anchor. Anyone who relies on a UZI certificate, for example to authenticate a healthcare professional or verify a signature, is a relying party and must comply with the obligations in the UZI register's Certification Practice Statement.
We build this as a custom integration because it needs to do more than accept a certificate. It verifies the entire chain up to the root certificate, checks that the certificate has not been revoked and reads the person's role from the certificate, so your application grants the right permissions. Alongside the current CA certificates, the UZI register also publishes a new generation (G4); the integration must be able to trust both. For testing, there are test cards and test server certificates with their own, lower trust hierarchy. According to the UZI register, the register will eventually be replaced by Dezi, De Zorgidentiteit (the Healthcare Identity); we build the integration so that the verification of the login method is a separate component that can be adapted later.
Certainty about who
Healthcare professionals with their card.
Certainty about which system
Server certificate verified.
The right permissions
Role taken from the certificate.
How we build your UZI card integration
We start with your use case: who needs to log in, with which cards, and which systems communicate with each other. Then we define which checks the integration performs, which data from the certificate you use and which permissions go with it. Using a test set from the UZI register, we first build and test logging in with the card or the connection with the server certificate, including a revoked and an expired test credential. Roles, the audit log and the production environment follow. If the UZI register publishes new CA certificates or a new hierarchy, we update the integration.
Users, cards, systems.
What gets verified.
With test cards and a test certificate.
Production, monitoring and management when new CAs are issued.
What a UZI card integration actually does
The components below appear in almost every UZI card integration. Which ones you need depends on whether it is about logging in with the card, connections between systems, or both.
Logging in
With the UZI card and PIN.
Chain
Verified up to the root certificate.
Revocation
Revoked cards rejected.
Rolls
Permissions from the certificate.
Server certificate
Secure connection between systems.
Log
Every login traceable.
Who we build a UZI card integration for
The integration is intended for organisations that have or are building their own healthcare software and want healthcare professionals to log in with their UZI card, or want their systems to communicate using a UZI server certificate.
Healthcare organisations
Your own applications behind the card.
Assessment bodies
Staff securely logged in.
Software builders
UZI in your healthcare software.
Chain partners
Systems with a server certificate.
Technology and integrations
This page is about identifying healthcare professionals and healthcare systems using UZI credentials. If patients or citizens need to log in, see the DigiD integration; for businesses logging in on behalf of their organisation there is the eHerkenning integration. If it is about exchanging data between healthcare professionals, read about the Wegiz integration, and for data that patients manage themselves, the MedMij integration. You can read about our approach on building software.
Why Appfront for your UZI card integration?
A login screen that accepts a card without checking the chain, a revoked card that still grants access, or an integration that stops working as soon as new CA certificates are issued are risks for every healthcare organisation. That is what we build against: checks defined up front, testing with the UZI register's test credentials, and an integration that is kept up to date as new certificates are issued.
Checked
Chain and revocation checked.
Tested
With the UZI test credentials.
Kept up to date
New CAs and hierarchies.
Security and privacy in a UZI card integration
A UZI integration determines who gets access to patient data, and therefore to health data. The integration only uses the data from the certificate that is needed to identify someone and assign permissions, and records every login with its time and result. When processing citizen service numbers (BSN), the rules of the Dutch act on supplementary provisions for the processing of personal data in healthcare also apply.
For the server certificate, the UZI register prescribes security measures, such as an encrypted private key and preferably an HSM or the operating system's certificate store. We set up the environment accordingly, in a European data centre or at your premises, with encrypted connections and storage. We agree with you in advance who manages the certificate and who may use it.
Frequently asked questions about a UZI card integration
Questions that healthcare institutions, information managers and healthcare software suppliers ask before getting started.
The Unique Healthcare Provider Identification (UZI) register enables the unique identification of healthcare providers and assessment bodies in electronic communication. It is part of CIBG and issues UZI cards and UZI server certificates.
There are three types: the healthcare professional card, the named employee card and the unnamed employee card. Which one someone needs depends on their role in the care process. A new card must be activated first.
For systems rather than people. With a server certificate, a system can use the BSN services of the SBV-Z, set up a secure connection with other systems and encrypt data. The certificate may only be installed in an environment that meets the security requirements.
Anyone relying on a UZI certificate must check that it was issued by the UZI register by verifying the chain up to the root certificate, and comply with the obligations in the Certification Practice Statement. An integration performs these checks on every login.
Yes. The UZI register issues test sets containing test cards or a test server certificate, including for the new G4 hierarchy. They are technically comparable to the real credentials, but sit in a lower trust hierarchy and are published in a test LDAP and a test CRL.
The UZI register says it will eventually be replaced by Dezi, De Zorgidentiteit (the Healthcare Identity), and that registered organisations will then be migrated automatically. We keep the verification of the login credential separate within the integration, so it can be adapted for the switch without touching the rest of your application.
For organisations with their own healthcare software, or suppliers who want to include UZI in their product. If you only use standard software that already supports the UZI card, a custom integration is usually not needed.
Want healthcare professionals to log in securely with their UZI card?
Tell us who needs to log in and which systems need to talk to each other. We'll show you how an integration handles that securely.