SuwiML integration development
SuwiML is the messaging standard of the Suwi chain, in which UWV, SVB, municipalities and other parties exchange data on work and income. BKWI manages the standard. Appfront builds integrations that create, read and validate messages in line with SuwiML against the schemas, so your system connects correctly and doesn't grind to a halt when a new version of the standard is released.
What is a SuwiML integration?
SuwiML is the language the Suwi chain uses to exchange data. It consists of a data model, a base schema in XML held in the chain's data register, a message standard with the rules for how messages are built, and a transaction standard for each interface. BKWI maintains the standard and the agreements around it, together with working groups from the chain partners.
Anyone connecting to the chain has to produce messages that comply exactly with the standard, and be able to read other parties' messages correctly. It goes wrong on details: a field that has a different name in the new version, a code that is no longer valid, or a message that is technically correct but rejected on content. An integration built by hand for a single version stops working as soon as the standard changes.
We build custom solutions because connections differ: which messages, which interfaces and which transport route. In the first step, together with you, we look at which messages and versions apply to your connection, and which agreements with BKWI or the chain partner are needed. For consulting data via Suwinet, there is a separate integration.
Messages that follow the standard
Created and read according to SuwiML.
Validated in advance
Against the schemas, before a message is sent.
Ready for new versions
Updated when the standard changes.
How we build your SuwiML integration
We start with your connection: which messages need to go back and forth, with which chain partner, according to which version of the standard, and how the transport works. We often begin by validating messages against the schemas, because that immediately shows what is currently going wrong. Then we build the creation and reading of messages, the error handling and the transport. We test in the chain partner's test environment before the integration goes live, and keep it up to date when a new version of SuwiML is released.
Messages, versions and chain partners.
Against the SuwiML schemas.
Creating, reading and transport.
Testing, and updating for new versions.
What a SuwiML integration actually does
The components below appear in almost every SuwiML integration. Which ones you need depends on your connection.
Creating messages
According to the base schema.
Reading messages
In your own system.
Validation
Against the XML schemas.
Error handling
Rejections followed up.
Versions
New versions supported.
Log
Every message recorded.
Who we build a SuwiML integration for
The integration is intended for parties that exchange messages in the Suwi chain. The more messages and interfaces, the more a good integration delivers.
Municipalities
Work and income. Getting the data right matters most.
Software suppliers
Products for the chain. The standard is the core.
Regions
Multiple municipalities. One connection counts.
Reintegration
Programmes within the chain. Messages count.
Technology and integrations
This page is about messages according to SuwiML. For consulting data via Suwinet, see our page on the Suwinet integration, for transport between government bodies our page on Digikoppeling, and for UWV data our page on the WBS-UWV integration. You can read about our approach on custom software development.
Why Appfront for your SuwiML integration?
A message rejected over a detail, or an integration that stops working with a new version, brings a work and income process to a halt, with people waiting for a decision. That is what we build against: messages that follow the standard, validation in advance, and an integration that keeps pace with new versions.
Correct
According to the standard.
Checked in advance
No rejection after the fact.
Up to date
Keeps pace with new versions.
Security and privacy in a SuwiML integration
The integration processes citizens' data on work, income and benefits, and strict requirements apply to it. Access is set up per role, messages are sent encrypted, and every message is logged so it can be traced who exchanged what.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups. We record the processing in a data processing agreement and align with the security arrangements of the chain.
Frequently asked questions about a SuwiML integration
Questions that municipalities and suppliers ask before they start.
SuwiML is the message standard of the Suwi chain, in which parties such as UWV, SVB and municipalities exchange data on work and income. It consists of a data model, a base schema in XML, a message standard and a transaction standard for each interface. BKWI manages the standard.
Suwinet is the facility that municipalities and chain partners use to consult data, for example via Suwinet-Inkijk or Suwinet-Services. SuwiML is the standard for the messages themselves. An integration with Suwinet-Services uses messages that follow SuwiML.
Every message is checked against the XML schemas of the current version before it is sent. If it is not valid, it is not sent and you can see what is wrong. Incoming messages are checked in the same way before they enter your system.
We update the integration. We look at what changes in the new version, adjust the messages and test using the chain partner's test environment. Where necessary, the integration supports both versions for a period, so the transition does not have to happen in a single day.
The integration records the rejection along with the reason, and prepares the message for review and resending. That way, no message is left sitting unnoticed.
Connecting to the chain is subject to agreements and conditions, which differ per facility. We look at which apply to your situation in the first step. We build the integration; you arrange the connection itself with the chain partner.
For municipalities and partnerships that exchange messages in the Suwi chain, for software suppliers who want to connect their product to the chain, and for reintegration companies handling messages about support programmes. The more messages you handle, the more a good integration delivers.
Messages in the Suwi chain that are correct?
Tell us which messages you exchange, with which chain partner and what currently goes wrong. We will show you what the SuwiML integration looks like.