Custom DBC-DIS integration
Providers of medical specialist care submit their DBC data to the Dutch Healthcare Authority (NZa) through the DBC information system, the DIS. What belongs in that minimum dataset is set out in an NZa regulation, and what the file looks like is defined in the data submission standard. If the data comes from more than one system, or your software package does not fit the way you work, you need an integration that assembles, checks and sends the file. Appfront builds that integration.
What is a DBC-DIS integration?
A DBC-DIS integration makes sure the minimum dataset you have to submit to the NZa comes directly from your own systems. According to the NZa, all providers of medical specialist care submit their DBC data via the DIS, so that the NZa can see what care is being delivered in the Netherlands. The Regulation on mandatory submission of the minimum dataset for medical specialist care (NR/REG-2511) has applied since 1 July 2025. It applies to hospitals, university medical centres and independent treatment centres, but also to rehabilitation institutions, thrombosis services, dialysis centres, radiotherapy centres and laboratories for primary care diagnostics, among others, as well as to care for people with sensory disabilities and geriatric rehabilitation care.
The regulation requires you to submit the minimum dataset every month for all declared DBC care products and other care products, and any changes to the production of a closed year must be received no later than 1 October of the following year. Submission is only permitted in line with the GA DBC-SZG data submission standard. The DIS carries out a technical check, and the NZa then assesses the content. Where care is provided under a subcontracting arrangement, the commissioning care provider submits the entire care product, including what the contractor has done. You send the file using the privacy and submission module (PVM). It pseudonymises the data, ZorgTTP pseudonymises it once more, and only then does the file go to the NZa. If the PVM is built into your software, you send directly from your own system.
We build custom integrations because the data for the dataset often comes from more than one source: the EHR, the billing system, a system for an outpatient clinic or a laboratory. For each data item, the integration records where it comes from according to the standard, assembles the file each month and checks it before it goes out. If a validation report comes back with errors, you can see per record what is wrong, and after correction it can be resubmitted. For mental health care and forensic care, DIS submission was discontinued in 2022 with the introduction of the care performance model; according to the NZa, that data now comes from Vektis and the DJI. This page is therefore about medical specialist care.
From the source
The dataset from your own systems.
According to the standard
Files as the DIS requires.
Errors returned
Validation report per record.
How we build your DBC-DIS integration
We start with your current submission process: which systems the data comes from, who assembles the file now, how often the validation report contains errors and where you fix them by hand. Then, using the GA DBC-SZG, we create a mapping from the data items in the standard to the fields in your systems, which your care administration can review. We first build the assembly and checking of a monthly file and compare it with what you submit now. Sending via the PVM, processing validation reports and submitting changes follow. If the NZa releases a new version of the standard, we update the integration.
Sources, process, error patterns.
The standard mapped to your fields.
Assembled and checked in advance.
Submitting, reports, and managing new versions.
What a DBC-DIS integration actually does
The components below appear in almost every DBC-DIS integration. Which ones you need depends on your systems and on what your EHR supplier already provides.
Mapping
Data traceable to the standard.
Compile
Monthly file from multiple sources.
Validation
Errors caught before submission.
Sending
Via the PVM, with confirmation.
Validation report
Errors returned per record.
Log
Every submission traceable.
Who we build a DBC-DIS integration for
The integration is intended for healthcare providers that fall under the scheme and pull their dataset from more than one system, or that currently spend a lot of time fixing errors from the validation report.
Hospitals
Data from EHR and billing.
Treatment centres
Submission without manual work.
Laboratories
Primary care diagnostics in the dataset.
Software builders
The PVM in your package.
Technology and integrations
This page is about submitting the minimum dataset for medical specialist care to the DIS. For mental health care and forensic care, see our page on care performance model integration, and for billing health insurers, the VECOZO integration. The dataset also requires the correct codes for healthcare providers; read more about that under AGB code integration. If your hospital uses HiX, also take a look at the ChipSoft integration. You can read about our approach at custom software development.
Why Appfront for your DBC-DIS integration?
A monthly file assembled by hand from exports, a validation report with the same errors every time, or changes that are only discovered late in the year cost your healthcare administration time and give the NZa (Dutch Healthcare Authority) an incomplete picture. That is what we build around: a mapping you can review, checks before submission, and errors you can see per record.
Traceable
Every data item mapped to its source.
Checked in advance
Fewer errors in the report.
Kept up to date
New versions of the standard.
Security and privacy in a DBC-DIS integration
The integration works with data about patients and their treatment, and that is health data. According to the NZa, patient consent is not required for submission, because you are legally obliged to supply the data; it is good practice to inform patients, though. The integration uses only the data the standard asks for, and pseudonymisation takes place in the PVM and then at ZorgTTP, so the NZa receives no data that can be directly traced to individuals.
The integration runs in a European data centre or in your own environment, with encrypted connections and storage. Certificates and activation codes for the PVM are kept secured and are not visible to staff. Every submission is logged with time and result, and we agree with you in advance who may compile and send a file.
Frequently asked questions about a DBC-DIS integration
Questions that healthcare administrations, information managers and healthcare software suppliers ask before they get started.
The DBC information system is the NZa's database that receives and manages data on DBC care products and other care products. Providers of medical specialist care submit their minimum dataset to it, so the NZa can see what care is being delivered.
Providers of medical specialist care, such as hospitals, university medical centres and independent treatment centres, but also rehabilitation institutions, dialysis centres, thrombosis services and laboratories for primary care diagnostics. This is set out in the Regulation on mandatory submission of the minimum dataset for medical specialist care (NR/REG-2511).
Not any more. According to the NZa (Dutch Healthcare Authority), DIS reporting for mental healthcare and forensic care was discontinued in 2022 with the introduction of the care performance model. The NZa receives that data from Vektis and the DJI (Custodial Institutions Agency), and mental healthcare providers do not need to do anything extra for it.
Monthly: for all declared care products belonging to the revenue of two months earlier, you submit the dataset before the first day of the month. Changes to the production of a closed year must be received by 1 October of the following year at the latest.
The PVM is the programme you use to send the file. It pseudonymises the data, after which ZorgTTP pseudonymises it a second time and forwards it to the NZa. If the PVM is built into your software, you send the data directly from your system.
You receive a notification that the processing was unsuccessful, and the errors are listed in the validation report. An integration reads that report, shows per record what needs to be done and resubmits the file after correction.
For healthcare providers who compile their dataset from multiple systems or spend a lot of time on errors, and for software vendors who want to include reporting in their package. If your EHR already produces a correct file that you only need to send, a custom integration is usually not necessary.
Your DIS submission straight from your own systems?
Tell us which systems your data comes from and how you currently compile the submission. We will show you how an integration takes that over.