iStandaarden Wmo & Youth Act messaging GGK & VECOZO

Custom iWmo and iJw integration development

Appfront builds custom integrations with the iWmo and iJw standards, so that messaging between municipalities and care providers runs fully automatically through your own administration. Allocations, start and stop notifications and claims are validated, processed and confirmed, via the Municipal Data Hub (GGK) and VECOZO. Less manual work, fewer errors and a chain that demonstrably complies with the official iStandaarden.

What are iWmo and iJw?

iWmo and iJw are the iStandaarden for electronic messaging in the social domain. iWmo covers data exchange for support under the Social Support Act (Wmo), and iJw covers youth care under the Youth Act. They are maintained by Zorginstituut Nederland and ensure that municipalities and care providers exchange information in a standardised way, from allocation through to care delivery and claims.

Messaging runs on structured messages with fixed numbers: the municipality sends an assignment (301), the provider confirms (302), reports the start of care with a start message (305), the end with a stop message (307) and claims periodically with a claim message (323). Every message has a response message. On the municipality side, transport runs via the Municipal Data Hub (Gemeentelijk Gegevensknooppunt, GGK) of the Inlichtingenbureau, and on the provider side via VECOZO.

Appfront builds the integration according to the official iStandaarden specifications and the OWASP ASVS security standard. We tailor message validation, response processing and error handling to your actual workflows, so the integration keeps pace with the annual iWmo and iJw releases and message exchange stays reliable even at peak volumes.

301

Assignment and response

The municipality allocates care or support with a 301 assignment; the provider confirms with a 302 response message. Your system processes both automatically and keeps the assignment and client record in sync without manual re-entry.

Start and stop messages

With a start message (305), the provider reports the start of care; with a stop message (307), the end. The integration sends these automatically at the right moment and feeds the corresponding response messages (306 and 308) back into your scheduling.

Claims and invoicing

Care delivered is claimed periodically with a 323 claim message; the municipality returns approval or rejection per line with a 325 response message. The old 303 and 304 messages were discontinued with iWmo 3.1, so we build on the current standard.

This page covers the transport of the messages. What you need on the side where response messages and rejections are picked up and investigated is covered under software for iJw messaging and accountability.

Our development process for iWmo and iJw integrations

We work with a proven method that removes uncertainty early and delivers a stable integration. From an initial analysis of your role in the chain, the message flows you need and the connection to the GGK or VECOZO, through to go-live and ongoing maintenance — every step is aimed at an integration your team can understand and trust.

1
Analysis & scope

We map out whether you use iWmo, iJw or both, which messages you want to process (assignment, start, stop, claim), what role you play in the chain and which hub you connect to.

2
Architecture

We design the integration architecture, arrange the connection with PKIoverheid certificates and draw up a strategy for validation and error handling of return messages.

3
Development

Implementation with automated tests against the iStandaarden specification, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with message validation and a safety net, followed by ongoing maintenance and keeping pace with new iWmo and iJw releases.

What an iWmo and iJw integration delivers in practice

Every integration is set up specifically for your role in the chain, the message flows you need and your existing system. Below are the features we deliver most often for municipalities, care providers and software vendors in the social domain.

Assignment processing (301/302)

Incoming assignments (301) are read automatically into your care or municipal system and linked to the correct client record. The response message (302) is drafted and sent automatically, with validation against the current iWmo or iJw specification.

Request for assignment (315/316)

For implementation variants where the provider requests an assignment itself: the request for assignment (315) is drafted from your system and the municipality replies with a response message (316). The request for change (317/318) is also supported.

Start and stop of care (305/307)

Start messages (305) and end messages (307) are generated and sent automatically based on your scheduling, with processing of response messages 306 and 308. This keeps the care status in your system in sync with the municipality's.

Claim processing (323/325)

Claims (323) are compiled from the recorded care delivered and sent periodically. The claim response (325) is processed per line (approved, rejected or under investigation), so your financial administration knows the status of every claim line.

GGK and VECOZO connection

The integration connects to the right node: the Municipal Data Node (GGK) of the Inlichtingenbureau on the municipality side, or VECOZO on the provider side. We handle the technical connection, the certificates and the processing over Digikoppeling.

Validation, logging and monitoring

Every inbound and outbound message is validated against the iStandaarden specification and fully logged. A dashboard shows outstanding return messages, rejected claim lines and processing errors, so your administration team can spot and follow up on deviations straight away.

Typical use cases in practice

An iWmo and iJw integration works out differently for each organisation, depending on your role in the chain. We see a number of contexts come up often — and for each of them we have a suitable set-up, with attention to the right message flows, node connection and return processing.

Municipalities

Municipalities that want to link their Wmo and youth care administration to the GGK, so that allocations, start and stop messages and claim returns are handled automatically. We connect to your existing system or build a custom one — see also our software for municipalities and the Digikoppeling integration.

Care providers

Wmo and youth care providers who want to process message traffic directly in their own care administration instead of manually in the VECOZO portal. Allocations, start and stop messages and claims flow through automatically, with immediate feedback on return messages.

Social domain software vendors

Vendors of care or municipal software who want to support the iWmo and iJw standards in their product. We build a reusable messaging module that keeps pace with the annual releases, so your customers always run on the current standard — see also our custom software.

Regional partnerships

Partnerships that handle message traffic centrally for multiple municipalities. A single integration processes the iWmo and iJw flows for the whole region, with clear logging per municipality and provider. Also compare our Suwinet integration for work and income.

Technology we use

We build iWmo and iJw integrations on the official message specifications of the iStandaarden, combined with the backend stack that suits you. The exact choice depends on your existing administration and the connection to the GGK or VECOZO — so your own team can manage the integration and keep up with new releases.

If you manage your care administration in ZilliZ and want hours, invoices and care to work together with your accounting or planning, take a look at our ZilliZ integration.

If you are a youth care provider with your own case management system, take a look at our iJw messaging integration for youth care.

For the Long-term Care Act (Wlz), see our page on an iWlz integration.

iWmo message specifications iJw message specifications Messages 301 / 302 (allocation) Messages 305 / 307 (start & stop of care) Messages 315 / 317 (allocation request & change) Messages 323 / 325 (claims) Municipal Data Hub (GGK) VECOZO Switchboard Digikoppeling PKIoverheid certificates XML & XSD validation Node.js / Python / PHP / .NET / Java REST & SOAP interfaces Retry & dead-letter queues Audit logging & monitoring CI/CD with automated tests

Why Appfront for your iWmo and iJw integration?

Appfront has extensive experience building integrations with government and chain standards for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes — an integration must not only be technically correct, but also add practical value to the way your administration works.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

See also the Inlichtingenbureau integration (operator of the GGK) and Wmo and youth care software where this message traffic ends up. Take a look at our broader services around software for municipalities, municipal websites and custom software, or get in touch directly about your situation.

  • Experience with integrations based on government and chain standards in the social domain
  • Building exactly to the official iWmo and iJw message specifications
  • Familiar with connecting to the GGK (Inlichtingenbureau) and VECOZO
  • Secure by default — PKIoverheid, secrets in vaults, role-based access
  • Structured validation and error handling of return messages
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Keeping pace with the annual iStandaarden releases
  • Approach tailored to your existing software landscape

Security and privacy in iWmo and iJw integrations

Wmo and Youth Act message traffic contains special category personal data about care for vulnerable clients. Appfront builds to the OWASP ASVS security standard. Among other things, that means: connecting to the GGK and VECOZO with PKIoverheid certificates, secrets in secure vaults, role-based access and regular audits of the message flows — with data minimisation as the starting point.

We document the data flows, the message processing and the connection to the nodes so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Every processed message is logged with a traceable audit trail, so your organisation can show it is in control of data exchange in the social domain.

Do you also work in other areas of government? Take a look at our Suwinet integration for work and income or our AI for municipalities.

  • GDPR-compliant data processing and minimisation
  • PKIoverheid certificates for connecting to GGK and VECOZO
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable message flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for anomalies
  • Documentation for your record of processing activities

Frequently asked questions about iWmo and iJw integrations

Answers to the questions we get asked most often about iWmo and iJw integrations.

iWmo and iJw are the iStandaarden for electronic message exchange between municipalities and care providers under the Wmo (Social Support Act) and the Jeugdwet (Youth Act). An integration lets your own system process these standardised messages automatically: the allocation (301), the start-of-care message (305), the stop message (307) and the claim (323), including the associated return messages. On the municipality side, transport runs via the Inlichtingenbureau's Municipal Data Hub (Gemeentelijk Gegevensknooppunt, GGK), and on the provider side via VECOZO. Appfront builds the integration with your care or municipal administration so that messages no longer have to be imported or retyped by hand.

iWmo and iJw are closely related standards from the same iStandaarden suite, managed by Zorginstituut Nederland. They work on the same principles and use the same message numbers and message flow. The difference lies in the legislation and the product categories: iWmo handles support under the Wet maatschappelijke ondersteuning (such as guidance, sheltered housing and assistive devices), while iJw handles youth care under the Jeugdwet. Many municipalities and providers use both standards side by side; Appfront builds the integration so that a single integration handles both.

The integration supports the standard messages in Wmo and Jeugdwet message exchange: the allocation (301) and return message (302), the allocation request (315) with return (316), the change request (317) with return (318), the start-of-care message (305) with return (306), the end-of-care message (307) with return (308) and the claim (323) with the return claim (325). The old claim and invoice messages 303 and 304 were phased out with the move to iWmo 3.1. We set up exactly the message flows your organisation needs.

On the municipality side, message exchange is sent and received via the Municipal Data Hub (Gemeentelijk Gegevensknooppunt, GGK), which is managed by the Inlichtingenbureau. Care providers connect via VECOZO. The messages are structured XML following the iWmo and iJw message specifications; the underlying transport runs over Digikoppeling. Appfront builds the integration between your own administration and the right node, with validation of messages against the current specification and correct processing of return messages.

The cost depends on the number of message flows you want to automate, whether it involves iWmo, iJw or both, the connection to the right node (GGK or VECOZO) and the degree of customisation in your own administration. The handling of return messages, error handling, monitoring and ongoing maintenance also play a part. We always provide a clear quote after a no-obligation analysis of your situation and your existing software landscape.

Yes. Wmo and Youth Act message exchange involves special category personal data relating to care, so diligence is essential. The connection to the GGK and VECOZO runs over secured channels with PKIoverheid certificates. Appfront builds according to OWASP ASVS: secrets in secure vaults, encryption in transit and at rest, role-based access and full logging of all processed messages. We document the data flows so your processing register stays complete and you can demonstrably comply with the GDPR, with data minimisation as the starting point.

Yes. Appfront takes over the maintenance of existing integrations, even if they were originally set up by another party. We review the message processing, the validation against the specification, the error handling and the connection to the node, document the current set-up and draw up improvement proposals. Because the iStandaarden get a new release every year, we also keep your integration up to date with version updates.

An integration is relevant for municipalities that want to automate their Wmo and youth care administration, for care providers that want to process message exchange directly in their own care administration, for software suppliers in the social domain that want to support the standards in their product, and for regional partnerships that handle message exchange centrally for several municipalities. Whether you connect on the municipality side via the GGK or on the provider side via VECOZO, Appfront builds the integration to suit your role in the chain.

Ready to build your iWmo and iJw integration?

Tell us whether you want to integrate iWmo, iJw or both, which message flows you need and whether you connect via the GGK or VECOZO — we're happy to help you think through the connection, validation and return processing. A no-obligation first conversation gives you a clear picture of the possibilities within half an hour. Get in touch for an advisory session.

Edit content