Custom zibs integration development
Appfront builds integrations based on zibs, the healthcare information building blocks published by Nictiz. A zib describes a single healthcare concept unambiguously, such as an allergy, a diagnosis or a blood pressure measurement, along with the data and code systems that go with it. We make sure the data in your system aligns with those building blocks, so it can be exchanged and reused within the national standards built on them.
What is a zib-based integration?
Healthcare information building blocks, zibs, are national agreements on how a healthcare concept is recorded. A zib describes, for example, an allergy, a problem, medication use or a measurement: which data belong to it, what they mean and which codes are used. Nictiz manages the zibs, and they form the basis of information standards such as the Basisgegevensset Zorg.
The idea behind zibs is to record once and use many times: what a healthcare professional records properly once can be exchanged, used for a handover, for a registration or for research. In practice, each system records data in its own way. An allergy sits in free text, a measurement without a unit, a diagnosis with its own code. Then exchanging means translating every time, with loss.
We build custom solutions because systems differ: how your system records the data, which zibs you need, which release your partners use, and what you want the data for. The zibs are managed by Nictiz; we make sure your data aligns with them. Which data may be shared or reused is for you to decide with your data protection officer.
According to the building blocks
Your data translated into the zibs, with the correct code systems and meaning.
Record once
Data recorded properly once, usable for exchange, registration and research.
Foundation for standards
Alignment with standards built on zibs, such as the Basisgegevensset Zorg.
How we build your zib-based integration
We start with your data: how your system records it, which zibs you need, which release your partners use, and what you want the data for. The translation is often not one-to-one. Where your data is structured differently, we decide together with the people who work with it how to handle it, and what can be improved at the source.
Your system, data, required zibs and partners.
Your data mapped to the zibs, with code systems.
Within standards such as the BgZ, and for registration or analysis.
Go-live, monitoring, and management with new releases.
What a zib-based integration actually does
The components below feature in almost every zib-based integration. Which ones you need depends on your purpose.
Translation
Your data mapped to the building blocks.
Code systems
The right codes for each data element.
Releases
The version of the zibs your partners use.
Exchange
Within standards built on zibs.
Reuse
For registrations and analyses.
Validation
Missing or incorrect data flagged.
Who we build zib-based integrations for
The integration is for anyone who wants to record and exchange healthcare data unambiguously.
Software suppliers
A healthcare product. The building blocks are the core.
Healthcare organisations
Your own systems alongside packaged software. Translation matters most.
Registrations
Data from many sources. Reuse is what counts.
PHR providers
Data for the patient. The standard is the core.
Technology and integrations
This page is about zib-based integrations. For medication, see our page on a medication handover integration; for mental health, our page on mental health software; and for GP and pharmacy systems, our page on a Sanday integration. You can read about how we work under getting software built.
Why choose Appfront for your zib-based integration?
Every system records a piece of data slightly differently, and each exchange loses something. We build on that: data structured by the building blocks, recorded properly once, and usable in the standards built on them.
Unambiguous
Each data element means the same thing everywhere.
Reusable
For handover, registration and research.
Future-proof
The foundation under national standards.
Security and privacy in a zib-based integration
The integration processes medical data, which is particularly sensitive. Only data for which there is a legal basis or consent is exchanged or reused, connections are encrypted, and every exchange is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and strict role-based access.
Frequently asked questions about zib-based integrations
Questions care organisations ask before getting started.
Healthcare information building blocks: national agreements on how a care concept is recorded, such as an allergy, a diagnosis or a measurement. A zib defines which data belongs to it, what it means and which codes are used. Nictiz maintains them.
The Basic Dataset Healthcare (BgZ) is built from zibs. If you apply the zibs properly, you have the foundation for the BgZ and for other standards built on zibs.
That depends on what your partners and the standards you use require. There are several releases, and not everyone moves over at the same time. In the first step we map out which release you need.
Not everything. Much can be translated. But what is held in free text or without a code is difficult to translate. In the first step we look at what works well and what should be improved at the source.
Data structured according to the zibs is well suited to reuse for registrations and analyses. Whether and how that is permitted depends on the legal basis, consent and the policies in your organisation; you determine that with your data protection officer.
A new release may change or add building blocks. In management we track the releases, and we adjust the translation when you or your partners move over.
For software vendors who need to apply the zibs in their product, for healthcare organisations with their own systems or their own data platform, and for registries that want to receive data from many sources in a consistent way.
Healthcare data that means the same thing everywhere?
Tell us which system you have, which data you want to exchange or reuse, and with whom. We'll show you what the zib-based integration would look like.