Service · Software development

Custom healthcare software development.

Custom software for healthcare organisations: add-ons to your existing EHR, a completely new client record for a niche practice, or integrations with USER, Pluriform, Carenzorgt and Vecozo. NEN 7510 and GDPR-proof, developed by a team that understands the healthcare context.

NEN 7510GDPR & WgboHL7 / FHIREHR integrations

Not an EHR product, but custom software that works alongside your EHR.

If you're looking for a standard EHR supplier, such as USER, Praktijkdata, Incura, Nedap or Pluriform, that isn't what we do. Those products already exist, they work well for most practices, and there's no point reinventing the wheel. What we do build is everything around them: the modules missing from your existing EHR, client portals the supplier doesn't offer, and integrations between your EHR, billing system, questionnaires and your own administration. Often, most of your spreadsheet, email and manual retyping work disappears in one go, without you having to say goodbye to an EHR your team has only just got used to.

We also build complete custom solutions for healthcare organisations that don't fit any off-the-shelf product. These are often niche practices, multidisciplinary partnerships or organisations with a way of working so specific that a standard EHR gets in the way more than it helps. We work across primary care, mental health, youth care, Wmo, home care, hospitals and social work, wherever the care need and the administrative reality don't line up neatly. The core expertise we bring is an understanding of the healthcare context: how a DBC or ZPM claim works, how NEN 7510 relates to GDPR and Wgbo, and why a patient file is far more than a database with free-text fields.

Our role is concrete: we design, build and test software that fits your working process and meets the demands care places on information security, data minimisation and data exchange. We work in sprints with your own practitioners, functional management and, where relevant, your chain partners and clients. Not from an ivory tower, but with software that can go live on a test environment every sprint, where you can respond straight away.

Three types of care software we build.

The right approach depends on your current situation: do you already have an EHR that you're running up against the limits of, or are you starting from a blank page? In the first conversation, we'll look at which direction will deliver the most value.

Compact project · fixed sprint budget

EHR add-ons & modules

Your EHR does most of the work well, but a specific process, such as triage, outcome measurement (ROM), multidisciplinary consultation, claims checking, a manager dashboard or research exports, doesn't fit the standard product. We build an additional module that integrates seamlessly with your EHR via API or HL7/FHIR and fits into your existing workflow. Commonly built add-ons include intake flows, NPS and client experience questionnaires, claims checks before submission to Vecozo, and management dashboards that go beyond the standard EHR reporting.

USERIncuraPraktijkdataNedap OnsPluriformCarenzorgt
Mid-sized project · fixed sprint budget

Client portal & questionnaire tools

A secure portal where clients can view their record, complete intake questionnaires, carry out ROM measurements, schedule appointments and communicate with their practitioners. Sign-in with DigiD for patient care or iDIN for business clients, with record access linked to your existing EHR. We also build standalone questionnaire tools for PROMs, PREMs, NPS, customer satisfaction and discipline-specific measurement instruments, such as the OMPSQ for physiotherapy, the OQ-45 for mental health, the CBCL for youth care, or your own instrument that isn't available as a standard tool anywhere.

DigiD / iDINPROMs & ROMMessagesFile accessAppointments
Larger project · fixed sprint budget

Fully custom EHR for niche practices

For healthcare organisations where no standard product fits, such as multidisciplinary centres, specialist mental health institutions, umbrella organisations with divergent chain requirements, or hospital departments with a specific workflow like theatre scheduling, intensive care monitoring or a research cohort. A record built precisely around your way of working, with billing via Vecozo (DBC, ZPM, NZa codes), data exchange with other care systems via HL7/FHIR, and integration with UPN and AGB for healthcare professionals and providers.

Two rights your records system must be able to support: electronic access to records and access to the audit log. What that means for your architecture is covered under Wabvpz software.

Three obligations that your records system must meet: access and logging outside the institution, the reporting duties under the Wkkgz, and the file for the inspectorate. The research itself runs through the research app.

Complete recordVecozo / DBC / ZPMHL7 / FHIRZorgMailUPN / AGB

What you get at the end.

A working care application plus the documentation and management to keep it running for years, without becoming dependent on a single supplier for every small change. We build for independence, not lock-in.

  • The application itselfProduction and acceptance environments, hosted in an NEN 7510-compliant cloud (GCP, AWS or Azure within the EU) or with a Dutch healthcare cloud provider.
  • Codebase + technical documentationFull source code in your own Git repository, build and deployment instructions, and an architecture overview including data flows for your DPIA.
  • Processor and SLA documentationData processing agreement, security plan based on NEN 7510, and a process description for incidents and data breaches that you can take over directly into your own ISMS.
  • Training for key users and administratorsTwo sessions for the functional management team plus a short instructional video for end users (practitioners and clients).
  • Management and ongoing development contract (optional)Monitoring, security patches, backup verification and ongoing development for a fixed monthly fee. You can also choose a handover only to your own IT team. In both cases, we make the management work transferable.
  • Penetration test & security audit reportAn external penetration test runs alongside the final sprints. You receive the report, a list of resolved findings and, if you wish, the documents you need for an NEN 7510 certification audit.

The care sectors we build for.

The common thread: complex administration, strict compliance, and a workflow that is hard to squeeze into a standard product. If you recognise your sector below, we know the context.

Primary care

Physiotherapy, occupational therapy, speech therapy, exercise therapy

Paramedical practices that want their own client portal, online intake or specific PROMs collection alongside their existing EHR (often Intramed, FysioRoadmap or Spotonmedics). Multidisciplinary centres that need one shared record across different disciplines. Or larger paramedical chains that want to automate operations around scheduling, no-show reduction and claims control.

Mental health

Mental health care

For mental health care institutions we build ROM tools, claims modules based on ZPM and NZa codes, and client portals that run alongside existing EHRs. We support treatment plans in line with the quality statute and integrations with DBC maintenance and NZa. For specific mental health solutions, see also our mental health software page for more detail.

Youth care & Wmo

Social domain

Municipalities, youth care organisations and Wmo providers that want to support messaging via iJw and iWmo standards, care request registration and multidisciplinary collaboration, often with several parties around a single client. We also build steering and monitoring platforms for municipalities that want to direct the procurement and quality of their youth care provision using data.

Home and community nursing

Community care

For home care and community nursing organisations we build route planning, mobile record access for care workers on the move, assessment registration in line with AZR standards and integrations with Vecozo for Wlz and Zvw claims. We also build informal care portals in which family and the wider informal network can securely follow along at the client's invitation.

Hospitals

Secondary & university hospitals

Specific modules alongside Epic, HiX or another EHR: theatre scheduling tools, ICU monitoring dashboards, research data platforms for academic hospitals, patient portals for specialist outpatient clinics, or integrations between the EHR and laboratory and imaging systems. For larger care institutions with multiple departments, we also work on enterprise programmes where architecture and governance are central.

Care & welfare

Nursing homes and social work

For long-term care and welfare organisations: care life plans in line with Wzd requirements, client participation modules, informal care portals, and integrations between several disciplines within one institution. With growing attention to involuntary care and restraint, we help with the registration and reporting obligations imposed by the Care and Coercion Act (Wet zorg en dwang).

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

Compliance & standards we work with.

The healthcare sector has its own language when it comes to information security, billing and data exchange. Below are the standards that almost always come up in our projects. We bring the expertise with us, so you don't first have to train an internal specialist.

Specific sectors bring additional domain codes and standards, which we incorporate per project. For youth care and Wmo these are the iJw and iWmo messaging standards; for primary care the UPS and CSI standards; and for secondary care DICOM for imaging and LOINC for laboratory results.

  • NEN 7510 — information security in healthcareOur projects are set up in accordance with NEN 7510. We deliver a security plan and the documentation needed to work towards certification if required.
  • GDPR, Wgbo & WabvpzPrivacy by design, data minimisation, patient rights under the Wgbo, and portability of patient data in line with the Wabvpz. We provide DPIA documentation as standard.
  • HL7 v2 & FHIR R4For exchange with other care systems: EHRs, laboratory systems, imaging, regional data exchange platforms. We implement in line with Nictiz profiles where these exist.
  • DBC, ZPM & NZa codesBilling modules aligned with the current DBC and ZPM system, with automatic checks on NZa codes before a claim is sent to Vecozo.
  • Vecozo, ZorgMail & LSPEDI with health insurers via Vecozo, secure messaging between healthcare providers via ZorgMail, and, where relevant, exchange via the National Switch Point (Landelijk Schakelpunt).
  • DigiD, iDIN & UZILogin for patients via DigiD, for business clients via iDIN, and for healthcare professionals via UZI pass where appropriate, depending on the level of security your process requires.
  • Wzd – Care and Coercion ActFor long-term care, we support the Wzd registration obligations around involuntary care, including audit logging and the reporting the Inspectorate expects.

How a care software project works.

1

Introduction and scope

A first conversation in which we understand which processes you want to support, which EHR you currently use (and what it lacks), which compliance requirements apply, and which parties are involved: practitioners, clients, chain partners, health insurers.

2

Discovery and DPIA preparation

A workshop with your team, plus interviews with practitioners and clients about the current way of working. At the end: a concrete scope, a data flow overview for your DPIA, and a first screen flow for your feedback.

3

Building in sprints

A working build you can test every two weeks. We build iteratively, starting with the core process, and expand to peripheral matters such as reporting and integrations. The penetration test runs alongside the final sprints, not as a closing surprise.

4

Rollout, training and maintenance

A phased rollout to your teams, training for key users and end users, and handover to your functional management. Afterwards, ongoing support for security updates and further development, either by us or by your own IT team.

Frequently asked questions.

What care organisations usually want to know before we start.

Are you an EHR supplier such as USER or Praktijkdata?
No. We don't sell a standard EHR product. We build custom software that runs alongside an existing EHR (additional modules, client portals, integrations) or fully bespoke solutions for niche practices where no off-the-shelf product fits. For most organisations, a combination of an existing EHR plus our additional modules is the smartest route.
How do you handle NEN 7510 and GDPR?
NEN 7510 governs every project: we work to the information security requirements for healthcare, deliver a security plan, and carry out a penetration test in the final sprint of every major project. For GDPR, we provide a data flow overview for your DPIA, arrange the data processing agreement, and, where relevant, apply the Wgbo and Wabvpz to the exchange of patient data.
Can this integrate with USER, Pluriform, Incura or Nedap Ons?
Yes, provided the supplier offers an API or HL7/FHIR integration. Such integrations usually exist for USER, Praktijkdata, Incura and Nedap Ons. We also have experience with Pluriform, Carenzorgt and exchange via ZorgMail and Vecozo. For specific API integrations, we have a separate smart API integrations page.
Do you support HL7 and FHIR for data exchange?
Yes. HL7 v2 and FHIR R4 are standard parts of our work whenever data exchange with other healthcare systems is required. For billing, we support DBC, ZPM and NZa codes via Vecozo, and for secure messaging we work with ZorgMail.
What determines the cost of a custom project?
The main cost drivers are: the scope (a single module or a full record), the number of roles and integrations, the compliance requirements (NEN 7510 audit, possibly ISO 27001), and the degree of data exchange with other systems. We work in sprints with a fixed price per sprint so you can scale up step by step. More context is available on our knowledge base page on custom software costs.
When should I choose custom software and when a standard product?
If your workflow is close to what a standard product offers, choose a standard product and, if needed, have us build an additional module. If your workflow is so specific that you click through more than you use in any standard product, custom development becomes worthwhile. We are candid about this in the first conversation: sometimes our advice is that you do not need custom software at all.
Do you also build specifically for mental health care (GGZ)?
Yes. For mental health organisations we have experience with ROM tooling, ZPM billing, client portals and treatment plan modules. We have a dedicated mental health software page with more detail on what we build there. The same approach works for other healthcare sectors.
Do you work with our IT department or care group?
Almost always. We handle knowledge transfer in the final sprint, deliver a runbook for incidents and data breaches, and agree clear responsibilities for functional and technical management. For larger care groups or enterprise software projects, we also work alongside your architecture team.

Talk to us about your healthcare software.

A thirty-minute introductory call, with no obligation. We listen to your workflow, ask questions where your current systems cause friction, and point you in a useful direction, even if it turns out that custom development is not the right choice.

Is this topic also relevant within your own organisation? You can read more about Software for healthcare on applatenmaken.com. If you work with an EHR that needs to be integrated, see Puur by Ecare integration.

For disability care, with the plan written in the client's own words and reporting per goal, there is our app for the support plan in disability care.

If your organisation has waiting lists currently kept in separate lists per location, take a look at our waiting list management software with access times.

For podiatrists and orthotic specialists who want measurement, scan and production order in one file, there is our app for the custom insole fitting file.

For care providers who need to keep track of notification and licensing under the Wtza, there is our software for the Wtza licence file.

For Wlz providers who need to account for production per care office, there is our software for Wlz production accountability.

If you want to exchange medication data digitally with chain partners, take a look at our medication handover integration.

If you want to send and receive the Basisgegevensset Zorg (BgZ, basic healthcare dataset) from your own system, take a look at our page on a BgZ integration.

Want to start a project?

We'd love to hear from you.

Got a lot to say, or did you send it another way by email? Choose Detailed brief: headings and bullet points, images in the text and files attached.

Mies

Get in touch with Mies

Business Developer

Get in touch with Martijn

Founder of Appfront

Martijn

Your message has been sent

Thank you for your interest! We'll get back to you as soon as possible, usually within 1 working day.

Edit content