Building a BgZ integration
Appfront builds integrations for the Basisgegevensset Zorg, the BgZ: the patient data needed for almost every handover. The BgZ is an information standard from Nictiz, built from health and care information models (zibs). We make sure your system can compile, send and receive the BgZ according to the standard, so a referral or handover doesn't start with retyping.
What is a BgZ integration?
The Basisgegevensset Zorg is a set of patient data that is almost always needed for continuity of care, such as problems, medication, allergies, results and the healthcare professionals involved. It is defined as an information standard by Nictiz and built from health and care information models, the zibs. The BgZ is recorded in a structured way and travels with a handover.
Under the Dutch Electronic Data Exchange in Healthcare Act (Wegiz), the exchange of the BgZ is being introduced in stages. You can follow which requirements apply to your organisation, and when, via the government and Nictiz, and coordinate with your adviser. In practice, handovers still often go by letter or PDF, and medication and allergies are re-entered by the recipient, with the risk of errors that brings.
We build custom because healthcare organisations and systems differ: how your system records the data, who you exchange it with, and which infrastructure is used in your chain. The standard is maintained by Nictiz; we make sure your system works with it. Which data may be shared is something you decide together with your data protection officer.
From your own system
The BgZ compiled from what your system already records, according to the zibs.
Sending and receiving
The BgZ included with a referral or handover, and a received BgZ processed into your record.
According to the standard
Data as Nictiz describes it, so every recipient can read it.
How we build your BgZ integration
We start with your system and your handovers: how the data is recorded, who you exchange with, which infrastructure they use, and where retyping currently happens. It often turns out that not every part of the BgZ is already recorded in a structured way. We map that out, so you know what needs to change at the source.
Your data, handovers, partners and infrastructure.
Your data mapped to the parts of the BgZ, according to the zibs.
Exchange via the chain, and process a received BgZ.
Go-live, monitoring, and maintenance when new versions arrive.
What a BgZ integration actually does
The parts below appear in almost every BgZ integration. Which ones you need depends on your role in the chain.
Compile
The BgZ from your own system.
Sending
Included with referral and handover.
Receiving
A received BgZ in your record.
Validation
Missing or incorrect data reported.
Legal basis
Consent and legal basis recorded.
Log
Every exchange logged.
Who we build a BgZ integration for
The integration is intended for anyone who exchanges patient data during handovers.
Hospitals
Many referrals and discharges. Sending is the core.
Rehabilitation
Patients coming from hospital. Receiving matters most.
Long-term care
Handovers on admission. Medication is what's needed.
Software suppliers
A product for healthcare. The standard is the core.
Technology and integrations
This page is about the Basisgegevensset Zorg (Basic Dataset for Healthcare). For medication, see our page on a medication transfer integration, for referrals our page on a ZorgDomein integration, and for healthcare in general our page on healthcare software. You can read about our approach at building software.
If you also want to be certain which healthcare provider or system is requesting the data, read more about our UZI pass integration.
For making the BgZ available to a PHR, see our page on MedMij integration.
If you want to know which exchanges fall under the Wegiz for you and how to build them to the standard, take a look at our integration for the Wegiz.
Why Appfront for your BgZ integration?
An allergy that is retyped during a handover can end up wrong at the recipient's end. We build on that: the BgZ from your own system, according to the standard, and included with every handover.
Safer
Data arrives as it was recorded.
Less retyping
No more letters or PDFs.
Prepared
In line with the Wegiz standard.
Security and privacy in a BgZ integration
The integration processes medical data, which is particularly sensitive. Only data for which there is a legal basis or consent is exchanged, 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 a BgZ integration
Questions healthcare organisations ask before getting started.
The Basisgegevensset Zorg (Basic Dataset for Care): a set of patient data that is almost always needed for continuity of care, such as problems, medication, allergies, test results and the healthcare professionals involved. It is defined by Nictiz and built from health information building blocks (zibs).
Zorginformatiebouwstenen (health information building blocks): small, fixed descriptions of a care concept, such as an allergy or a blood pressure measurement. The BgZ is built from zibs, so every recipient understands the data in the same way.
Under the Wegiz, exchange is being rolled out in stages. You can follow which requirements apply to your organisation, and when, through the government and Nictiz, and check with your adviser or trade association.
For a good BgZ, yes. Often part of the data sits in free text. In the first step we map what is structured and what is not, so you know what needs to change at the source.
The infrastructure used in your chain or region. We look at which route fits in the first step, together with you and your chain partners. Where your system is already connected to a network or platform, we build on that instead of creating a new connection.
Yes. A received BgZ is processed into your record, or first shown so that a healthcare professional can confirm what is adopted. How this works is something you decide together with the people who use the record. Medication or an allergy is often reviewed first before being adopted, so that no duplicate or conflicting data is created.
For software suppliers who need to support the BgZ in their product, and for care organisations with their own systems that do not connect through a standard package. If you use a package that already supports the BgZ, a custom integration is often not needed.
Handovers without retyping?
Tell us which system you have, who you exchange handovers with and how that works today. We will show you what the BgZ integration looks like.