Custom iJw message integration for youth care providers
Youth care providers exchange messages with municipalities under the iJw standard: a request for authorisation, the authorisation itself, the start and end of care, and the invoice. Those messages belong to what happens in the client record. Appfront builds the integration between your own record system and the message exchange, so messages originate from the record itself and are not copied by hand into a portal.
What is an iJw messaging integration for youth care?
Under the Youth Act, administration between municipalities and youth care providers runs through messages under the iJw standard. If a young person comes through a referrer other than the municipality, the provider requests authorisation with a request for authorisation (JW315). The municipality sends the authorisation (JW301), the provider reports the start and end of care (JW305 and JW307) and invoices (JW323), and the municipality replies (JW325). The messages run through the Inlichtingenbureau node (GGK) and VECOZO.
Those messages belong to what happens in the client's record: the intake, the start of support, the hours delivered and the closure. Many providers keep that record in their own system, which is not connected to the message exchange. Messages are then created by hand in a portal, authorisations are tracked separately, and a stop message gets forgotten when a case ends.
We build custom because providers and systems differ: one municipality or many, which record system, and which products and agreements. The integration creates messages from what happens in the record, and places municipalities' replies back with the client. Which version of the standard applies and which agreements your municipalities make, we cover in the first step.
From the record
Messages originate from what happens in the record.
Authorisation with the client
No separate list of authorisations.
Replies sent back
Return messages with the right client.
How we build your iJw messaging integration for youth care
We start with your record and your municipalities: which record system you use, how many municipalities you work with, how messages are currently created, and where it goes wrong. Then we define which moments in the record produce which message, and how your connection to GGK and VECOZO works. We often start with authorisations and start and stop messages, because a missed authorisation or a forgotten stop message causes the invoice to get stuck later. Invoices from delivered care and the processing of return messages follow. After that we maintain the integration when the standard or your system changes.
System, municipalities and current messages.
Which moment produces which message.
Authorisation, start, stop and invoice.
Go-live, deadlines and maintenance.
What an iJw messaging integration for youth care actually does
The components below appear in almost every iJw messaging integration for youth care. Which ones you need depends on your record system and municipalities.
Request for authorisation
From the intake.
Authorisations
With the right client.
Start and stop
From the record.
Claims
From delivered care.
Return messages
Back with the client.
Deadlines
Monitored per message.
Who we build an iJw messaging integration for youth care for
The integration is intended for youth care providers with their own record system that is not connected to the message exchange. The more clients and municipalities, the more time it saves.
Youth care providers
Own record. Messages from the record matter.
Youth mental health providers
Many cases. Start and stop matter.
Certified institutions
Compulsory framework. The right authorisation matters.
Software suppliers
One record for youth care. Connecting matters.
Technology and integrations
This page covers the integration from the youth care provider's record system. For the transport of messages for the Wmo (Social Support Act) and the Youth Act, see our page on the iWmo and iJw integration; for return information and accountability, see our page on iJw software; and for the combined administration of Wmo and youth care, see our page on Wmo and youth care software. You can read about our approach on building software.
Why choose Appfront for your iJw messaging integration for youth care?
Messages created by hand in a portal, and a record system that doesn't know which allocation applies, cost a youth care provider time and money when claims are rejected. That is what we build on: messages generated from the record, allocations linked to the client, and replies that arrive where they belong.
No duplicate work
Messages from the record.
Fewer rejections
Allocation checked upfront.
Overview
Returns linked to the client.
Security and privacy in an iJw messaging integration for youth care
The integration processes data about young people and their care, including the BSN (citizen service number) and details of the youth care provided. This is sensitive data. We use only what the message requires, access is set up per role, and every message is logged with what was sent and what came back.
The integration runs in a European data centre, with encrypted storage and daily backups. The connection to GGK and VECOZO runs via the secure route that applies to them. We document the processing in a data processing agreement.
Frequently asked questions about an iJw messaging integration for youth care
Questions youth care providers ask before getting started.
The standard that municipalities and youth care providers use to exchange the administration surrounding the Youth Act: requests for allocation, allocations, start and stop of care, and claims with their replies. The messages are routed via the Inlichtingenbureau's hub (GGK) and VECOZO.
That page is about the transport of messages for the Wmo and the Youth Act, for municipalities and providers. This page is about the youth care provider's side: generating the messages from what happens in your own record system, and putting replies back with the client.
Your own system, as long as it can exchange data. We look at which data is available and via which route in the first step. If your record system supplier already has a well-working integration with the messaging, custom work isn't needed.
By checking beforehand. A claim without a valid allocation, outside the allocation period, or for a different product than allocated is flagged in the integration before it goes to the municipality. That way fewer come back.
Replies from municipalities come back to the right client and the right care pathway. A rejected claim, or an allocation that differs from what was requested, goes into a work queue so that someone acts on it.
Yes. Municipalities can have their own products, rates and agreements. The integration keeps track of what applies per municipality, so that messages comply with that municipality's agreements.
The iJw standard gets new releases. We keep the integration up to date when the standard changes, and test the messages before a new version goes live. We follow which version applies and when via the publications of the standard's maintainers.
iJw messages from your own record system?
Tell us which record system you use, how many municipalities you work with, and how messages are currently created. We'll show you what the integration would look like.