Delivered care matches claims Production versus agreements per care office Ready for retrospective calculation and the auditor

Custom Wlz production reporting software

Appfront builds software for care providers who deliver Wlz care and need to account for their production to the care office. The care delivered from the EHR and the scheduling, the claims, and the production agreements per care office come together. Differences between delivered and claimed care stand out during the year, utilisation of agreements can be tracked, and at year-end the data is ready for the retrospective calculation and the auditor.

What is software for Wlz production accountability?

Care providers delivering care under the Wlz (Long-term Care Act) agree production volumes with care offices, claim for the care they deliver, and account at the end of the year for what was delivered. That accountability is the basis for the retrospective settlement with the care office, and is checked by the auditor in line with the applicable regulations.

In practice, the care delivered sits in the EHR and the scheduling system, the claims in the billing system, and the agreements in the controller's spreadsheet. During the year it is hard to see whether production is on track or whether under- or overproduction is looming. A difference between care delivered and care claimed only comes to light at the end of the year. And preparing the retrospective settlement and the audit takes weeks.

We build custom software because care providers differ: which care offices and forms of care delivery, which EHR and billing system, how production agreements were made, and how your controller reports. Which rules and regulations apply to your accountability is something you determine with your controller and auditor; the software brings the data together and shows where it does not match up.

Delivered and claimed

The care delivered alongside the claims per client, with differences flagged during the year.

Production against agreements

How much of the production agreements is used, per care office and service, so that under- or overproduction is spotted early.

Ready for the retrospective settlement

Data and specifications for the retrospective settlement and the auditor, from the same source.

How we build your Wlz production accountability software

We start with your accountability process: which care offices, which systems, how the agreements were made, and where things currently go wrong.

1
Mapping your accountability process

Your care offices, forms of care delivery, EHR, billing system and agreements.

2
Bringing the data together

Care delivered, claims and agreements per client and care office.

3
Reconciliation and alerts

Differences between delivered, claimed and agreed, flagged during the year.

4
Retrospective settlement and maintenance

Preparation for the retrospective settlement and the auditor, reporting, and maintenance afterwards.

What Wlz production accountability software actually does

The components below appear at almost every Wlz provider. Which ones you need depends on your care.

Care delivered

Care per client from the EHR, scheduling and registration.

Claims

Claims and feedback messages per care office.

Agreements

Production agreements per care office and service.

Reconciliation

Delivered, claimed and agreed, side by side.

Alerts

Under- or overproduction and differences during the year.

Post-calculation

Data and specifications for the retrospective settlement and the auditor.

Who we build Wlz production accountability software for

The software is intended for Wlz providers who currently put their accountability together by hand.

Elderly care

Many clients and locations. Reconciliation is the core.

Disability care

Different forms of care delivery. The agreements per service matter most.

Mental health residential care

Wlz alongside other funding. What you need is a separation per funder.

Providers with multiple care offices

Agreements across several regions. Utilisation per care office is the core.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page is about Wlz production accountability. For healthcare software in general, see our page on healthcare software, for claims our page on a VECOZO integration, and for mental health care our page on an integration for the care performance model. You can read about our approach at building software.

If you also want to build the annual quality report from the same source systems, take a look at our quality report generator for long-term care providers.

For providers' annual accountability in DigiMV, see our software for annual accountability in DigiMV.

For message exchange with care offices under the iWlz, see our page on an iWlz integration.

Care delivered EHR integration Claims and feedback Production agreements Reconciliation per client Under- and overproduction Final settlement Breakdowns for the auditor Reporting for the board Log

Why Appfront for your Wlz production accountability software?

A gap between care delivered and care claimed that only surfaces at final settlement costs money and time. That is what we build around: reconciliation during the year, production measured against agreements, and data that is ready when you need it.

Adjust early

Under- or overproduction shows up during the year.

Weeks less work

The final settlement follows from the same data.

Auditor finished sooner

Breakdowns are ready per component.

Security and privacy in Wlz production accountability software

The software processes data about clients and their care, which is special category personal data. For accountability, totals are often enough; personal data is only used where reconciliation per client requires it. Access is set up per role, and every change is logged.

The software runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about Wlz production accountability software

Questions that controllers in healthcare ask before they get started.

It brings together care delivered, claims and production agreements, shows per client and care office where they do not reconcile, flags under- or overproduction during the year, and prepares the final settlement and the audit.

That depends on your agreements with the care offices and the regulations for the Wlz and the audit, which can differ from year to year. What applies to you is something you determine with your controller and auditor; the software calculates with what you set.

The care delivered comes from your EHR, scheduling or registration system, the claims from your claims system and the feedback from the care office, and the agreements from the contracts. The software integrates with those systems where possible.

The software sets production to date against the agreements and the expectation for the rest of the year. That shows where you are on track and where a conversation with the care office is needed.

The data for the final settlement comes from the same source as the reconciliation during the year. Differences have already been investigated, so the final settlement is no longer a reconstruction.

Yes. Agreements, claims and utilisation are tracked per care office, so a provider with care in several regions can account for each care office separately.

Check that first. Some EHRs and claims systems have production reports, and those are enough if everything sits in one system. Custom software makes sense when data is spread across several systems, or when you want to see reconciliation and utilisation per care office during the year.

Wlz production that reconciles, during the year?

Tell us which care offices you work with, which systems you use and how you currently account for production. We will show you what the reconciliation, utilisation and final settlement look like.

Edit content