Monthly DIS submission requires more than pressing export. A reliable process connects registration close, technical validation, correction and documented approval.
What is required?
Providers of Dutch specialist medical care submit DBC data to the DBC Information System (DIS). The NZa uses this data for supervision and policy. Always verify current scope, specifications and deadlines through official NZa channels.
A controlled monthly workflow
Schedule extraction after the registration close. Validate counts, periods, mandatory fields and technical syntax before submission. Record which version was sent and who reviewed the outcome.
- Close registration and corrections to a set calendar.
- Compare volumes with prior months and production.
- Retain validation report, receipt and return message.
- Correct errors at source where possible.
Reconciliation and data quality
Technical acceptance does not prove content completeness. Reconcile DIS with the EHR and claims process. Unexplained differences in volume, profile or missing attributes should trigger investigation.
- Use trend controls by specialty and location.
- Make exceptions explicit and traceable.
- Feed recurring errors into training and system controls.
Governance
Name a process owner, deputy and content reviewer. Put DIS submission on the compliance calendar and discuss variances with registration, finance and quality teams.
Frequently asked questions
How often is DIS submitted?
The NZa describes data submission for specialist care as a monthly obligation.
Is technical acceptance enough?
No. It does not automatically confirm that content is complete or reconciles with source records.
What evidence should we retain?
Keep the submitted version, validation outcomes, receipt, return message and correction record.
Official sources
This guide provides general information, not legal or medical advice. Always verify current official requirements for your circumstances.