Features Wmo tailor-made packages (from 01-01-2015)

Open data API in a single place

Provided by Centraal_Bureau_voor_de_Statistiek

Get early access to Features Wmo tailor-made packages (from 01-01-2015) API!

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

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Sociaal domein, Wmo, Data Governance Act, DGA, ODISSEI, Microdata
Quality scoring

Dataset description

This file contains data on tailor-made arrangements granted under the Social Support Act (Wmo). This data is collected for the municipal social domain monitor, where municipalities participate on a voluntary basis. The file contains only data from municipalities that have submitted and have given permission for publication. An overview of participating municipalities is available by looking at the total number of clients per municipality per half year in StatLine table ‘Wmo-clients; type of tailor-made arrangement, region’. http://opendata.cbs.nl/statline/#/CBS/nl/dataset/83262NED/table?dl=54404 If there is a point here for the municipality in question, it has not provided any data during that period (or it is a municipality that does not exist in that reporting year). More information on how to access the data: > https://www.cbs.nl/nl-nl/onze-diensten/maatwerk-en-microdata/microdata-zelf-onderzoek-doen ### Methodology The supplied files are checked by means of a technical test to determine whether the file meets the agreed specifications. In the data deliveries of municipalities to CBS, it often happens that several records are provided that are (presumably) about the same arrangement. For all deliveries delivered by a municipality within a calendar year with an allocation number, for counting the number of tailor-made arrangements, the data from all records of the same person with the same assignment number and type of arrangement shall be merged into one package. After this aggregation, records are reassembled into a single arrangement when: — the municipality, the person, the type of arrangement and the form of delivery are the same and — the start and end dates are either a record no more than 3 days after the end of a previous record or the care period of one record (fully) falls within the care period of the other record. The above method is valid from WMO2020BUSV2, for older versions: Data on customised arrangements of the same person (in the same municipality) are aggregated by CBS into one package based on the allocation number. If no allocation number is present in a municipality’s file, records are merged when — the type of arrangement, the form of financing and the reason for termination are the same and in addition — the start and end dates are the same or the start date of one record matches the end date of the other record, with a margin of 3 days. The data provided by municipalities will be included in the publication after they have been assessed by the submitting municipality for plausibility and, if necessary, have been agreed upon. Municipalities receive information from CBS about the quality and completeness of the data provided. Municipalities then decide whether the data may be published, partly on the basis of their own assessment of the accuracy and completeness of the data provided by them. The municipalities are asked twice a year to provide data to CBS over the past six months. In addition, in addition to the last six months, it is also possible for them to provide data for the six-month period (re-delivery). Due to this system in the delivery of source data and by the chosen publication strategy (2x a year), this file will always have multiple versions. The first version of this file always contains only the first half of the year t and will always consist of preliminary figures. After all, in the second half of the year under review, there may be re-deliveries for this first half of the year. In a subsequent version, normally the second version, this file contains the entire reporting year t. This version will consist of the first half of the year (whether or not with re-deliveries) and the second half together. The first six months in this stock can be regarded as further provisional, because any re-deliveries during this period are included. The first half of the year has also been adjusted to the second half of the year, if necessary (e.g. by failing to fill in the start date or end date). The second half of the year in this version can be regarded as preliminary figures. This is the first time this data has been provided. Only during the first half of the reporting year t + 1 will it be possible to re-delivery for the second half of the year under review t. This ensures the latest version of this file, normally the third version. This version incorporates the re-deliveries of the second half of the year. This is the six-month final. The first half of the year has also been adjusted (again) to the second half of the year. This also makes the first half of the year definitive. Due to the complexity of the versions, the type of reporting period is not unambiguous. In the end, the year under review is envisaged. ### Population Persons (in the participating municipalities) who have been supported during the reporting period under the Social Support Act (Wmo). In almost all cases, these are only persons who have been registered in the Basic Records Persons (BRP) at any time during the reporting period.
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