Custom healthcare software development
Custom software for healthcare organisations: additions to your existing EHR, a completely new client record for a niche practice, or integrations with USER, Pluriform, Carenzorgt and Vecozo. Appfront builds it with NEN 7510 and the GDPR as its starting point, with a team that understands the healthcare context.
What is custom healthcare software?
Custom healthcare software is software built for a single healthcare organisation, alongside or instead of a standard EHR. We are not an EHR vendor. Packages such as USER, Praktijkdata, Incura, Nedap and Pluriform work well for most practices, and there is no point reinventing the wheel. What we build is everything around them: modules your EHR lacks, client portals the vendor doesn't offer, and integrations between your EHR, billing system, questionnaires and your own administration. This removes a lot of Excel, email and retyping work, without you having to give up the EHR your team is used to.
We also build fully custom solutions for organisations that don't fit any standard product: niche practices, multidisciplinary partnerships, or organisations whose way of working is hindered more than helped by a standard EHR. What we bring is an understanding of the healthcare context: how a DBC or ZPM claim is processed, how NEN 7510 relates to the GDPR and the Wgbo (Dutch Medical Treatment Contracts Act), and why a record is more than a database with free-text fields.
What a record must be able to do follows partly from the law. Your record system must support two rights: electronic access and access to the logs. What that means for your architecture is explained on our page about Wabvpz software, and there is a separate app for access and logging outside the institution. The reporting obligations under the Wkkgz and the record you provide to the inspectorate also tie in with your record. The investigation itself runs through the investigation app.
Alongside your EHR
Modules, portals and integrations that the package is missing.
Fully custom
For practices where no standard product fits.
Healthcare standards
HL7 FHIR, Vecozo, NEN 7510 and the Wgbo.
How we build your custom healthcare software
A project starts with a conversation about the processes you want to support, the EHR you use now and what it lacks, which rules apply and which parties are involved: practitioners, clients, chain partners and health insurers. This is followed by a discovery phase with workshops and interviews, resulting in a concrete scope, an overview of the data flows for your DPIA and an initial screen flow for you to respond to. We build in sprints, starting with the core process and expanding to reporting and integrations. Every sprint lands on an acceptance environment where your practitioners and application managers can give immediate feedback, and we schedule a pentest in the final sprints rather than leaving it as a surprise at the end. You can read what determines the price on our knowledge base page on custom software costs. For how we work in general: see our software approach.
Processes, your current EHR, compliance and the parties involved.
Scope, data flows and an initial screen flow.
Core process first, always testable on an acceptance environment.
Phased rollout, training key users and handover to application management.
What custom healthcare software does in practice
Which form suits you depends on your situation: are you hitting the limits of an existing EHR, or starting with a blank sheet? Below are the components we build most often. For integrations with Vecozo, ZorgMail, HL7/FHIR and DigiD, see our smart API integrations. For medication and the Basic Healthcare Data Set (BgZ), there are our medication transfer integration and our page on a BgZ integration.
EHR modules
Triage, ROM (routine outcome monitoring) assessments, multidisciplinary meetings or a management dashboard, integrated with your EHR via API or HL7 FHIR.
Client portal
View records, complete intake questionnaires, book appointments and send messages, with login via DigiD or iDIN.
Questionnaire tools
PROMs, PREMs, NPS and measurement instruments such as the OQ-45 or CBCL, or a custom instrument that isn't available as standard anywhere.
Claims validation
Checks on DBC, ZPM and NZa codes before a claim is sent to Vecozo.
Custom EHR
A record system built around your way of working, for a niche practice or department, with AGB codes for healthcare professionals and providers.
Exchange
HL7 v2 and FHIR R4 with EHRs, labs, imaging and regional platforms, following Nictiz profiles where they exist.
Who we build custom healthcare software for
The common thread: complex administration, strict requirements and a workflow that fits poorly into a standard product. We work for primary care, mental health care, youth care, Wmo (social support), home care, hospitals and social work. On applatenmaken.com you can read more about software for healthcare.
Physiotherapy, occupational therapy, speech therapy and exercise therapy
Practices that want a client portal, online intake or PROMs collection alongside Intramed, FysioRoadmap or Spotonmedics, or a single shared record across disciplines. For podiatrists and insole makers, there is our app for the insole measurement record.
Mental healthcare
ROM tools, billing modules based on ZPM and NZa codes, and client portals alongside the EHR. You'll find more detail on our mental health software page.
Social domain
Municipalities, youth care providers and Wmo providers with iJw and iWmo messages, support-request registration and collaboration between multiple parties around a single client, plus management and monitoring platforms for youth care procurement.
Outpatient care
Home care and district nursing: route planning, mobile access to records on the road and claims via Vecozo for Wlz and Zvw. If waiting lists are kept in separate lists per location, take a look at our waiting list management software with access times.
Hospitals and university medical centres
Modules alongside Epic, HiX or another EHR, such as theatre scheduling, ICU dashboards, research data platforms and outpatient clinic portals. For larger institutions, we also work on enterprise projects where architecture and governance take centre stage.
Long-term care and disability care
Care plans, informal carer portals and registration under the Wet zorg en dwang (Care and Compulsion Act). See also our app for the support plan in disability care and our software for Wlz production reporting.
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 →Standards and integrations
Healthcare has its own language for security, billing and data exchange. For youth care and Wmo, iJw and iWmo messages come on top of that, and in secondary care, DICOM for imaging and LOINC for laboratory results. If you work with an EHR that needs to be integrated, see the Puur by Ecare integration. If you want to keep track of notifications and admission licences under the Wtza, there is our software for the Wtza licence file.
Why Appfront for your custom healthcare software?
You get a working healthcare application plus the documentation and maintenance to keep using it for a long time, without depending on a single supplier for every small change. We build together with your own practitioners, application managers and, where needed, your chain partners and clients.
Code in your own repository
Source code, build and deployment instructions and an architecture overview with the data flows for your DPIA.
Documents for your ISMS
Data processing agreement, security plan based on NEN 7510 and a procedure for incidents and data breaches.
Maintenance with us or with you
Monitoring, security updates and further development, or a handover to your own IT team.
Security and privacy in custom healthcare software
Healthcare software processes health data, which counts as special category personal data under the GDPR. NEN 7510 is the information security standard for healthcare: we set up design, hosting and maintenance around it and provide the documents you need if you are working towards certification. Privacy by design and data minimisation are our starting point, and patient rights under the Wgbo and the Wabvpz, such as access and logging, are built into the design. We include DPIA documentation.
Login works at the level your process requires: DigiD for patients, iDIN for business clients and the UZI card for healthcare professionals where appropriate. Hosting is within the EU, on GCP, AWS or Azure, or with a Dutch healthcare cloud. For the Wet zorg en dwang (Care and Compulsion Act), we build the registration of involuntary care with an audit log and the reports the inspectorate expects. After the pentest you receive the report and the list of resolved findings.
Frequently asked questions about custom healthcare software
What healthcare organisations usually want to know before we start.
If you use Caress as your electronic client record, read more about our Caress integration.
If you want to measure outcomes consistently in physiotherapy or exercise therapy and show results per condition, read more about software for clinimetrics and outcome measurement.
Usually not. Packages such as USER, Praktijkdata, Incura, Nedap and Pluriform work well for most practices. We build what is missing around them: modules, client portals and integrations. We build a fully custom record for organisations where no standard product fits, such as niche practices and multidisciplinary centres.
Yes, via the EHR's API or via HL7 v2 or FHIR, depending on what your supplier supports. We look at which route is available in the first phase. Where Nictiz profiles exist, we build on them.
We set up design, hosting and maintenance with NEN 7510 as the framework, and deliver a security plan, a data processing agreement and a procedure for incidents and data breaches. You can adopt these documents into your own ISMS, including if you are working towards certification.
Yes. We build claims modules that align with the DBC and ZPM systems, with checks on NZa codes before a claim goes to Vecozo. In the social domain, this covers iJw and iWmo messages.
Patients via DigiD, business clients via iDIN, and healthcare professionals via the UZI card where appropriate. Which level is needed depends on the data a person gets to see.
Yes. The source code sits in your own Git repository, with build and deploy instructions and an architecture overview. Maintenance can stay with us or move to your own IT team, and in both cases we make it transferable.
Mainly the scope of the process, the number of integrations, the security and data exchange requirements, and the number of parties involved. After discovery, the scope is concrete enough for a well-founded estimate.
Talk to us about your healthcare software
A no-obligation introduction: we listen to your workflow, probe the points where it clashes with your current systems, and give you direction you can use, even if it turns out custom software is not the right choice. For large institutions, there are our enterprise software projects.
Want to start a project?
We'd love to hear from you.
Long story, or would you otherwise have emailed it? Choose Detailed briefing: headings and bullet lists, images in the text and attached files.
Your brief has reached us
We'll read it through and usually respond within one working day. Anything to add? Send it to fabian.vandijk@appfront.nl.
Your message has been sent
Thanks for your interest! We'll get back to you as soon as possible, usually within 1 working day.