Building a BgZ integration
Appfront builds integrations for the Basic Care Dataset (BgZ), the data about a patient that is needed in almost every handover. The BgZ is an information standard from Nictiz, built from care information building blocks. We make sure your system can compile, send and receive the BgZ according to the standard, so that a referral or handover doesn't start with retyping.
What is a BgZ integration?
The Basic Care Dataset is a set of information about a patient that is almost always needed for continuity of care, such as problems, medication, allergies, results and the care providers involved. It is defined as an information standard by Nictiz and built from healthcare information building blocks, the zibs. The BgZ is recorded in a structured way and travels with a handover.
Under the Electronic Data Exchange in Healthcare Act (Wegiz), the exchange of the BgZ is being regulated in stages. Which requirements apply to your organisation, and when, is set out by the government and Nictiz, and you should align this with your adviser. In practice, handovers still often take place as a letter or PDF, and medication and allergies are re-entered by the recipient, with the risk of errors that brings.
We build custom solutions because care organisations and systems differ: how your system records 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 for you to determine 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 sent along with a referral or handover, and a received BgZ processed into your record.
According to the standard
Data as Nictiz describes it, so that every recipient can read it.
How we build your BgZ integration
We start with your system and your handovers: how data is recorded, who you exchange with, which infrastructure they use, and where information is currently re-typed. It often turns out that not all parts of the BgZ are yet recorded in a structured way. We map this out, so you know what needs to change at the source.
Your data, handovers, partners and infrastructure.
Your data mapped to the components of the BgZ, according to the zibs.
Exchanging via the chain, and processing a received BgZ.
Go-live, monitoring, and maintenance when new versions are released.
What a BgZ integration actually does
The components below come up in almost every BgZ integration. Which ones you need depends on your role in the chain.
Compiling
The BgZ from your own system.
Sending
Sent along with referrals and handovers.
Receiving
A received BgZ in your record.
Validation
Missing or incorrect data flagged.
Legal basis
Consent and legal basis recorded.
Audit log
Every exchange logged.
Who we build BgZ integrations for
The integration is intended for anyone who exchanges patient data during handovers.
Hospitals
Many referrals and discharges. Sending is the core.
Rehabilitation
Patients discharged 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 at its 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 want to know which exchanges apply to you under the Wegiz and how to build them to the standard, see our integration for the Wegiz.
Why Appfront for your BgZ integration?
An allergy that is re-typed during a handover can end up wrong at the recipient. That's what we build on: the BgZ from your own system, according to the standard, and sent along with every handover.
Safer
Data arrives as it was recorded.
Less retyping
No more letters or PDFs.
Prepared
Follows 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 care organisations ask before they start.
The Basisgegevensset Zorg (Basic Care Dataset): a set of data about a patient that is almost always needed for continuity of care, such as problems, medication, allergies, results and the healthcare providers involved. It is defined by Nictiz and built up from zorginformatiebouwstenen (healthcare information building blocks).
Care information building blocks: small, fixed descriptions of a healthcare concept, such as an allergy or a blood pressure measurement. The BgZ is built up from zibs, so every recipient interprets the data in the same way.
Exchange under the Wegiz is being arranged in stages. You can follow which requirements apply to your organisation when via the government and Nictiz, and align with your adviser or industry body.
For a proper BgZ, yes. Often part of the data sits in free text. In the first stage we map what is structured and what is not, so you know what needs to change at the source.
Via the infrastructure used in your chain or region. Which route fits is looked at 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 rather than creating a new connection.
Yes. A received BgZ is processed into your record, or first shown so that a care provider can confirm what is taken over. You decide how this works together with the people who work with the record. Often medication or an allergy is reviewed before it is taken over, so that no duplicate or conflicting data arises.
For software vendors 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 unnecessary.
Handovers without retyping?
Tell us which system you have, who you exchange handovers with and how that works now. We'll show you what the BgZ integration looks like.