Service · Software for mental health care

Custom GGZ software built around your practice.

A client file, schedule, billing module or complete practice system that fits how your mental health organisation works. Not a standard package that almost fits, but custom development that aligns with your care process, ZPM coding and privacy requirements.

NEN 7510 & GDPRZPM & NZa codesVecozo & ZorgMailClient portalROM questionnaires

Arrange an introductory call View custom care software

Standard mental health software rarely fits your practice.

USER, Incura, Praktijkdata and the other major packages do a lot well. But every mental health practice sooner or later runs into the same wall: the package forces you into a way of working that doesn't match your care team, your lead clinicians or your multidisciplinary meetings. You build manual Excel steps around it, buy separate tools for ROM or intake, and export data between systems.

We build custom mental health care software for organisations that want to resolve this friction. Sometimes as a complete replacement for a standard package, more often as a smart addition: a client portal alongside your existing EHR, a custom claims export to Vecozo, or a questionnaire module that actually follows your treatment protocol. We are not an EHR vendor. We are the builders of what the package cannot do.

In recent years we have worked for care providers both within and beyond mental health on custom care software that does fit. The common thread: you know your care process, we know software architecture, and together we deliver something clinicians actually use rather than work around.

The important difference from large healthcare IT implementation projects: we start small, deliver visible results quickly and build from there. No two-year waterfall project with a big-bang go-live. A first working module, such as a client portal or a billing export, can run in a test environment within a few sprints, so your team can judge something working rather than a PowerPoint.

Three types of mental health software we build.

Most projects start small and grow, or begin as an integration and end up as a complete system. We scale with your ambition and your budget.

Compact project · fixed sprint budget

Client portal & ROM module

A secure web environment where clients complete questionnaires themselves, confirm appointments, view documents and communicate with their clinician. Questionnaires are configurable per treatment pathway: HoNOS, OQ-45, SQ-48, or your own clinical instruments. Results go straight into the client file and are available to the lead clinician.

DigiD / iDIN loginConfigurable PROMSecure messagingNEN 7510-compliant

Mid-sized project · fixed sprint budget

Administration & billing system

An administration module that handles ZPM coding, NZa tariffs, declaration export to Vecozo and billing to health insurers in one flow. It replaces the patchwork of separate Excel files and manual declaration batches. It integrates with your accounting and with ZorgMail for secure exchange with GPs and partner organisations.

ZPM & NZa codesVecozo exportZorgMail integrationAccounting export

Larger project · fixed sprint budget

Complete mental health practice system

A full-featured practice system that brings together the client record, treatment plans, scheduling, multidisciplinary consultation, claims and management reporting. Designed for organisations that have outgrown USER or Incura and want a system that reflects their clinical vision rather than constraining it. Roles for clinicians, lead clinicians, administrative staff and management are built in.

Client recordTreatment plansScheduling & MDTManagement reporting

What you get at the end.

Not just the software, but everything you need to carry on independently as a care organisation. No lock-in to a supplier who doubles the price of the package two years from now.

The production-ready mental health softwareIncludes acceptance and production environments, hosted in a Dutch healthcare cloud or in your own Azure/GCP tenant.
Full source code and architecture documentationYou own the codebase. Another developer can take over the work without you having to start again.
NEN 7510 compliance fileDPIA, data classification, technical measures, data processing agreement, audit log specifications — everything your Data Protection Officer needs.
Training for clinicians and administrative staffTwo live sessions per role plus a short video tutorial. No 200-page manual that nobody reads.
Migration from your current EHRClient records, ongoing care plans, outstanding claims and diary data from USER, Incura, Praktijkdata or another package, transferred and checked.
Ongoing maintenance (optional)Security patches, NZa tariff updates, further development. A fixed monthly fee with no surprises, and a notice period of no more than one quarter.

When custom mental healthcare software is the right choice.

Four patterns we often see among mental health organisations that get in touch with us. If you recognise one of these situations, a conversation is likely worth your time.

The package no longer fits

You have outgrown USER or Incura

The standard package worked perfectly when you started with three clinicians. With a growing team, multiple sites and specialist programmes, you increasingly run into the limits of the package. Workarounds become the norm rather than the exception.

Workarounds

Excel does the real work

Your secretariat keeps waiting lists in Excel. Claims are checked on a second sheet. ROM results sit in a separate tool. The EHR is no longer the source of truth; it has become a formal filing cabinet.

Specialisation

Your clinical offering is specific

You provide specialist clinical mental health care, forensic care, a dedicated autism programme, trauma treatment or your own mentalisation-based therapy. Standard packages are designed around general mainstream mental health care and offer little support for protocols, roles, questionnaires and outcome reporting for your particular client group.

Ownership & data

You want control over your data and tariffs

Per-user licences for off-the-shelf packages quickly become unattractive as you grow. On top of that, your client data sits in a database you cannot access yourself for analysis, dashboards or a planned migration. Custom software gives you ownership of both the software and the underlying data, including the ability to build your own reports on your own warehouse.

Integrations we support as standard.

The Dutch mental healthcare chain is well standardised. We build on these standards so that your new software fits within the wider care landscape rather than standing outside it.

Billing & messaging

Vecozo, ZorgMail, OZIS and FHIR

Vecozo for claims (AGB checks, COV, GZ321/JW321 return messages) and authorisations, ZorgMail for encrypted messages with GPs and care partners, OZIS where it is still used regionally, and FHIR integrations for more modern exchange with EHRs, diagnostic platforms or a regional care network. We document every integration so that a later change by another party can be taken over.

Vecozo claimsZorgMailOZISHL7 FHIR

Identity & access

DigiD, iDIN, Azure AD and magic link

For clients we use DigiD or iDIN for reliable authentication without managing passwords ourselves. For clinicians and administrative staff we connect to your Azure AD or Google Workspace, with multi-factor authentication and automatic role provisioning. For external partners without SSO, we can set up temporary magic-link access per case.

DigiDiDINAzure AD / Entra IDMFA as standard

Security & compliance

NEN 7510, GDPR and penetration testing as standard

For healthcare organisations, NEN 7510 is not optional but mandatory. We deliver not only compliant software but also the accompanying documentation: DPIA, data classification, technical measures, data processing agreement, retention policy and audit log specifications. An independent penetration test concludes every delivery. For hosting we choose a Dutch healthcare cloud that is itself ISO 27001 and NEN 7510 certified.

NEN 7510GDPR / AVGDPIA as standardIndependent penetration test

How a mental healthcare software project runs.

Introduction & care process analysis

A first conversation with you, a clinical lead and someone from the administrative team. We want to understand how your care process really works: from referral to final invoice. Which roles look at which data, which compliance requirements apply, and where people get stuck today.

Scope, architecture & DPIA

We define the scope, deliver an architecture diagram, and start the DPIA in parallel. This is also where we decide which integrations are needed (Vecozo, ZorgMail, accounting, possibly a diagnostics platform) and how migration from your current package is handled.

Iterative build in sprints

Every two weeks the team delivers a working build. A fixed group of end users, usually a few clinicians and someone from the administrative team, test along. Adjusting is inexpensive at this stage, and it ensures the software truly fits daily practice.

Migration, audit & rollout

Client data is transferred from your existing EHR, an independent penetration test verifies security, and we roll out in phases per team or location. The old package keeps running for a while so you can fall back if something unexpected happens.

Maintenance & further development

After go-live the software moves into maintenance: NZa tariffs are updated on time, security patches are applied automatically, and new needs, such as a new treatment programme or an extra report for the Board, are added in small sprints.

Frequently asked questions.

The questions that mental healthcare executives and practice managers ask us before we begin.

What is the difference between custom software and USER, Incura or Praktijkdata?

USER, Incura and Praktijkdata are standard packages: they are built for a broad market and you pay per user. Custom mental healthcare software is written for your specific care process, your treatment programmes and your role structure. We do not always build a replacement; sometimes we are an addition that shores up the weak points of your current package. Which route fits is something we decide together with you in the introductory conversation.

What about NEN 7510, GDPR and client data privacy?

For us, NEN 7510 is the starting point, not the ceiling. All traffic is encrypted, data at rest is encrypted, access is role-based down to field level, there is a full audit log, and hosting stays within the EU (preferably in the Netherlands, in a healthcare cloud that is itself NEN 7510 certified). For every project we carry out a DPIA together with your data protection officer. An independent penetration test is standard at handover.

Can you integrate with Vecozo, ZorgMail and OZIS?

Yes. Vecozo for claims to health insurers (AGB check, COV, GZ321/JW321 claim standards), ZorgMail for secure messaging with GPs and partner organisations, and OZIS for regional record exchange where it is still used. For more modern exchange we also build FHIR integrations, for example with a GP's EHR or a diagnostic laboratory.

How do ZPM, NZa codes and claims work?

The ZPM (care performance model) and the NZa tariff structure are built into the claims module. We process the tariff updates the NZa publishes each year through a maintenance contract. The claims export produces valid files for Vecozo (GZ321 for mental health care, JW321 for youth mental health care) and keeps returned messages in a list of rejected claims for the administrative team to work through.

How do we arrange roles for the lead clinician, treating clinician and administrative staff?

Role-based access control is built into the system as standard, both at role level and at individual level. A lead clinician can view the records where they are the main clinician, a treating clinician only their own caseload, administrative staff see administrative data without clinical content, and management sees aggregated reports. For multidisciplinary team meetings we can build temporary access flows. Everything anyone views or changes is recorded in the audit log.

What determines the cost of a mental health care software project?

Three main factors: the scope (a ROM module alone is smaller than a complete practice system), the number and complexity of integrations (Vecozo, ZorgMail, accounting, a diagnostics platform), and migration from your current package. We work in fixed sprint budgets so you know where you stand at each phase. Exact figures only come after an initial analysis, because an estimate without context almost always turns out wrong. See also our explanation of what custom software costs.

Do you sell a mental health care product, or do you build custom solutions?

We build custom solutions. We are not an EHR vendor like USER or Incura; we do not have a standard package to sell you. That also means we are honest: if a standard package suits your situation, we will say so. Custom development is an investment, not an obvious choice. It pays off most when you have outgrown a package or offer a specific type of care for which the market has no solution.

How does migration from our current EHR work?

For every mental health care project, migration is a separate workstream. We export client records, ongoing treatment plans, the schedule, claims history and documents from your current package, usually through a database export or an API, and sometimes through a PDF archive if that is all the old system provides. Your administrative team validates a sample before we run the full migration. The old package remains available in read-only mode in parallel during the transition, in case anything ever needs to be looked up.

Does this also work for a small mental health care practice, or only for organisations?

Scalability works both ways. We work with smaller practices that need a focused module, for example just a client portal or a ROM tool alongside their existing package, as well as with larger organisations that want a complete system. For smaller practices we more often recommend an add-on to an existing package rather than a full replacement, because the business case is then easier to make.

Talk to us about your mental health care software.

A no-obligation introductory call of half an hour. We listen to your care process, ask questions about where it gets stuck today, and give you an honest answer, including if custom development is not the best route. Sometimes a well-chosen integration between your current package and a separate tool is enough. Sometimes it is time for a completely new system. Also worth discussing in that conversation: smart API integrations with your existing EHR, or a broader web development roadmap for your organisation. For administration, planning and financial matters that fall outside the core care process, we often also look at a custom ERP system that runs alongside the client record.

Book an introductory call Or email Fabian directly

Current context (May 2026)

According to Google Web Vitals data, progressive web apps show on average a 36% higher conversion rate than classic mobile websites and cost around 50% less than a native app to roll out initially.

Source: web.dev — Progressive Web Apps (web.dev)