Custom iWlz integration development
Appfront builds integrations according to the iWlz, the information standard for the Long-Term Care Act (Wlz). Care providers, care offices, the CIZ and the CAK exchange client data through it: assessments, allocations, and the start and end of care. We connect your own system to the message traffic, process allocations immediately, and prepare you for the move to the network model.
What is an iWlz integration?
Under the Long-Term Care Act, the CIZ, care purchasers, care providers and the CAK exchange client data: who has an assessment, which care provider is allocated the care, and when care starts and ends. This takes place under the iWlz, the information standard managed by the Zorginstituut. For years this relied on a relay of messages; through the iWlz action programme, the sector is moving step by step towards a network model, including the Indicatieregister (assessment register).
For a care provider, this means receiving and sending messages in line with the applicable release, and processing them in your own client system. In practice, an allocation is viewed in a portal and copied over by hand, the start of care is reported late, and error responses come back that nobody understands. With each new release, everything must be tested again.
We build custom software because care providers differ: which client system you use, which care offices you work with, and which parts of the network model apply to you. The standard is managed by the Zorginstituut (National Health Care Institute); we make sure your system works with it. What you need to report and when follows the agreements with your care offices.
According to the standard
Messages according to the iWlz release currently in force, to and from your own system.
Assignment processed immediately
An assignment or change goes straight into your client system, without manual transfer.
Ready for the network model
Connection to the Indication Register and other parts of the network model where this applies to you.
How we build your iWlz integration
We start with your message traffic: which client system, which care offices, which messages, and where things currently go wrong. Problems often lie in return messages and in processing changes. We look at those first, so the integration solves what currently costs the most effort. The rest of the message traffic follows, tested message by message.
Your system, care offices, messages and pain points.
Receiving and sending according to the release in force.
Processing assignments, reporting start and end of care, handling returns.
Connection to the network model, and maintenance with new releases.
What an iWlz integration actually does
The components below come up in nearly every iWlz integration. Which ones you need depends on your role.
Receiving
Assignments and changes from the care office.
Processing
Straight into your client system.
Reporting
Start and end of care.
Returns
Errors explained and handled.
Network model
The Indication Register, where it applies.
Audit log
Every message recorded.
Who we build iWlz integrations for
The integration is intended for organisations that exchange messages under the Wlz.
Nursing homes
Many clients and changes. Processing is the core.
Care for people with disabilities
Many types of care per client. Assignments matter most.
Your own client system
No off-the-shelf package. The standard is what is needed.
Software suppliers
A product for care. The releases are the core.
Technology and integrations
This page covers integrations according to the iWlz. For production accountability, see our page on Wlz production accountability; for claiming, our page on a VECOZO integration; and for the Wmo and Jeugdwet, our page on an iWmo and iJw integration. You can read about our way of working at custom software development.
Why Appfront for your iWlz integration?
An assignment entered by hand, or a start of care reported late, costs time and money. That is what we build around: messages according to the standard, assignments processed immediately, and ready for the network model.
No manual transfer
Assignments arrive automatically.
Reported on time
Start and end without delay.
Future-proof
Ready for the network model.
Security and privacy in an iWlz integration
The integration processes data about clients and their care, which is particularly sensitive. Only the data the standard requires is exchanged, connections are encrypted, and every message is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and strict access controls by role.
Frequently asked questions about an iWlz integration
Questions care providers ask before they get started.
The information standard for the Long-term Care Act (Wlz), managed by the Zorginstituut (Health Care Institute). CIZ, care offices, care providers and the CAK use it to exchange data on eligibility, assignments and the care provided.
The sector is moving step by step from a relay of messages to a network model, in which parties consult data at the source, such as in the Indication Register. Which parts already apply and which messages still travel via the relay depends on the releases.
The release currently in force for your messages. Releases can coexist, for example one for message traffic and one for the Indication Register. In the first step we map out what applies to you.
An assignment or change from the care office comes in and is entered into your client system, or set aside for review if something doesn't add up. That way, nobody has to re-enter it from a portal.
The integration reads the return message, explains in plain language what went wrong, and makes it available to whoever can fix it. Once corrected, it is sent again. Returns that keep recurring are made visible, so the root cause can be addressed in your client system.
Yes, provided it has an interface. Clients and care details come from the client system, and allocations flow back into it. Planning and claiming can also be connected, so that an allocation leads directly to a place in the schedule and a correct claim.
For care providers with their own client system that does not support the iWlz out of the box, and for software suppliers who want to build the standard into their product. If you use a package with iWlz support, you usually don't need a custom integration, unless you have your own systems alongside that package.
Wlz messages without manual work?
Tell us which client system you use, which care offices you work with, and where the message traffic currently gets stuck. We'll show you what the integration would look like.