Causes of death of persons who at the time of death were residents of the Netherlands (from 01-01-2013)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Causes of death of persons who at the time of death were residents of the Netherlands (from 01-01-2013) API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
ODISSEI, Sterfte, DGA, Data Governance Act, Microdata, Overledene, Doodsoorzaakverklaring, Doodsoorzaak
Quality scoring

Dataset description

Contains all underlying causes of death of persons registered in the BRP who have died since statistical year 2013. In addition, the most important injury and location of the accident has also been recorded for those who died of a non-natural death. For all deceased, the location of death and the statistical year, i.e. the year in which the deceased is included in the statistics, is present in this component. More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology For each deceased person, a certificate of death (B-declaration) is completed by a doctor. This cause of death is either sent in a closed envelope via the municipality where the death occurred or via a secure electronic connection directly to the medical officer of CBS. At CBS, the forms are processed. This happens completely anonymously, the name of the deceased is not known to CBS. Causes of death are assigned from the internationally applied code list, the so-called International Statistical Classification of Diseases and Related Health Problems (ICD) of the World Health Organisation (WHO). Since 1996, the 10th revision of the ICD (ICD-10, WHO). Up to and including statistical year 2012 has been completely manually encoded by the medical encoders of CBS. As of statistical year 2013, the causes of death are (partly) automatically encrypted using the computer program IRIS (version 4.2.0; release February 2013). Iris is based on the international standard for automatic coding of causes of death (MMDS) and is able to provide an underlying cause of death to approximately 93 % of the natural deaths in the annual stock. The remaining part of the stock, as well as the non-natural causes of death and maternal or perinatal deaths, are still processed manually as before. Automatic coding of causes of death entails better international comparability and reproducibility of the data. Also, all causes of death on the cause of death certificate are now coded, increasing the availability of data for research. The introduction of automatic coding involves (one-time) shifts in statistics. In particular, the sharp increase in dementia (including Alzheimer’s) and late effects of the CVA, as well as the sharp decrease in pneumonia and COPD as the underlying cause of death, stand out. ### Population Deceased persons who were registered in the GBA at the time of death. The component relates to a particular reporting year or part of a reporting year. The reporting period shall indicate which period is available. Annual files have release designation definitive, part of a year has as release designation for the time being.
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