Hospitalisations National Basic Registration Hospital Care (01-01-2018-01-01-2019)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Hospitalisations National Basic Registration Hospital Care (01-01-2018-01-01-2019) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
ODISSEI, DGA, Microdata, Ziekenhuis, Data Governance Act, Zorggebruik, Ziekenhuisopname, Diagnose
Quality scoring

Dataset description

This file contains data on hospitalisations in Dutch hospitals of persons registered in the Basic Registration Persons (BRP). The data comes from the National Basic Registration of Hospital Care (LBZ) of Dutch Hospital Data (DHD). More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology Hospitalisations are linked to the Basic Registration Persons (BRP) based on Citizen Service Number (BSN) pseudonyms and for a small part based on the combination of date of birth, gender and postcode. The final return (after verification and correction) of the BRP coupling of LBZ shots is 97.3 % in 2013, 99.1 % in 2014, 99.5 % in 2015 and 2016, 99.6 % in 2017 and 99.7 % in 2018. This file displays only the LBZ records associated with the BRP. As a Person ID, the variable RINPERSOON is added to the files, a meaningless and dimensionless number, which can be used to link to other CBS SSB files. A high weight has been included with which hospital admissions (linked to the BRP) can be increased to all hospital admissions. The variables involved in the weighting concern gender, type of care of hospitalisation, admission specialism and the patient’s municipal code. The LBZ files are there since 2013. For the registration years 1995 to 2012, there are files of hospitalisations based on the LMR, the predecessor of the LBZ. The LMR files (LMRbasisjjjjj) linked to the population register do not include the images missing in the LMR. From 2013, for the previously missing recordings, microrecords are usually delivered to the LBZ by the hospitals. These so-called 'incomplete records ' contain some data about the admission and the patient, but for example no diagnoses. These records can largely be linked to the BRP and are then recorded in LBZBASISJJJY. In 2013 and 2014, some hospitals had not or did not deliver these incomplete records to the LBZ. For these recordings, CBS requested some recording data from the hospitals, so that they could largely be linked to the BRP and could be added to LBZBASISJJJJ as incomplete records. In LBZBASISJJJJ, almost all recordings are present, with only part of the records missing the main diagnosis and main operation and some other variables in a small part of the records. This 'incomplete records ' in LBZBASIS, 23.3 % of hospital admissions linked to the BRP in 2013, 12.5 % in 2014, 6.2 % in 2015, 7.7 % in 2016, 10.6 % in 2017 and 10.5 % in 2018. In clinical shots, 14.9 % was incomplete in 2013, 3.0 % in 2014, 0.3 % in 2015 and 0 % in 2016 and later years. For daily admissions, 30.3 % was incomplete in 2013, 22.7 % in 2014, 13.6 % in 2015, 17.2 % in 2016, 23.3 % in 2017 and 22.8 % in 2018. At the 'long-term observations without overnight stay ' 0.4 % is incomplete in 2015 and 0 % in 2016 and later years. CBS has the missing information in these incomplete records & imputated &#039, i.e. the values of the variables in question have been taken from a fully recorded record that resembles the incomplete record as much as possible. In the imputation procedure, a complete record is sought with equal recording specialism, care type and gender, with a & distance function ' a most similar record is chosen, using the variables age, whether or not death in hospital, migration background from BRP, type of hospital, duration of admission and urgency of admission. The values imputed with the incomplete records are displayed in the file in the variables with the suffix &imp ' in the name and are thus distinguishable from the actual recorded variables. Please note that the imputated variables are not suitable for use in (longitudinal) examination of recordings of individuals; these are not real data. For cross-ectional research at a sufficiently aggregated level, these imputed variables can be used. ### Population Hospitalisations that have taken place in all general and academic Dutch hospitals. In addition, hospitalisations within three categorical hospitals (two kankerk clinic and an eye hospital) have been admitted. These data on hospital admissions are from the National Basic Registration of Hospital Care (LBZ). In the file are both day shots, clinical shots and from 2015 also & long-term observations without overnight stay ' registered. Outpatient contacts are not included in this file. Data on admission and dismissal are included in LBZBASISJYY, the main diagnosis and (if applicable) the main operation carried out. All diagnoses recorded during the recording (including side diagnoses) are included in the file LBZDIAGNOSENJJJ. Only hospitalisations linked to the BRP are included in LBZBASISJYYY (see 'Used methodology ' for more details).
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks