Custom healthcare app development
A healthcare app is a mobile application that lets care professionals record data at the bedside and clients view their own care records, integrated with the source system where the record lives. Appfront builds these apps to order: tailored to your care process, with data exchange via HL7 FHIR, and built to NEN 7510 and the GDPR so you can demonstrably stay in control of who accesses which record.
What is a healthcare app?
A healthcare app is the mobile layer around your care record. The record itself stays in the source system, usually an electronic health record (EHR). The app retrieves the data needed at that moment and writes the entry back. That distinction matters: an app that starts keeping its own shadow record creates exactly the double administration you wanted to avoid.
In practice there are two users with opposing needs. The care professional wants to sign off a procedure in a few taps, one-handed, standing next to a bed. The client or informal carer wants to read through the care plan calmly at home and reschedule an appointment. Cramming both into one interface produces an app in which neither feels at home. That is why we build them as separate entry points on the same secure foundation.
What sets an app in healthcare apart is the burden of proof. The Additional Provisions for Processing Personal Data in Healthcare Act (Wabvpz) refers to NEN 7510 via the Decree on electronic data processing by healthcare providers, and as a healthcare provider you must be able to demonstrate that you comply with that standard. Logging, authorisation and data minimisation are therefore not an afterthought, but shape what the app looks like from the very first sketch.
One record, no copy
The app reads and writes directly in the source system via an integration. No second version of the truth emerges, and the care professional doesn't have to retype anything from another screen.
Logging in line with NEN 7513
NEN 7513 describes how to record actions on an electronic record. Every view and change is logged, so it remains traceable who opened which record and why.
Keeps working with poor coverage
In a basement, a lift or a home without signal, recording carries on. As soon as a connection is back, the app syncs and any conflicts are presented explicitly to the care professional.
How we build your healthcare app
We don't start with screens but with the care process and the data flows. Care professionals, your data protection officer and the administrator of the source system are at the table early, because that's where the decisions are made that are expensive to change later.
We walk through the work process as it really happens: who records what, at what moment, and on what legal basis. For each data flow, we establish which data is needed and which is deliberately not retrieved.
We design the integration with your EHR, preferably via HL7 FHIR resources, plus the authorisation model and the logging. This is also where we decide what may be available offline and what the device must never retain.
We build in short iterations and let care professionals try working versions along the way. A step that seems logical in the office often turns out to be two taps too many at the bedside.
Controlled rollout through your mobile device management, with monitoring of integrations and synchronisation. After that, ongoing maintenance, including when Wegiz makes new exchanges mandatory.
If you show data to a patient, they are also entitled to see who has accessed their record. See Wabvpz software.
Two applications that start on the work floor: reporting an incident at the moment it happens and access with logging outside the organisation.
If you work in youth care, the difference often lies in what happens to the recorded hours: they have to match the allocation before you can submit a claim. This is described in the app for start, stop and hours in youth care.
What a healthcare app actually does
Which functionality matters most differs greatly between a home care organisation, a mental healthcare provider and a hospital ward. These are the components we build most often.
Bedside recording
Record procedures, measurements and reports at the moment they happen, rather than from memory at the end of the shift. Input fields follow the structure of your record, so the data comes back usable in the source system.
Medication overview and sign-off
View the current medication overview and sign off administration, with a check step for deviations. The app shows what has been prescribed, not a list maintained by hand.
Care plan and goals
The care plan with goals and agreements, visible to both care provider and client, so both work from the same plan and evaluations don't disappear into scattered notes.
Client portal and informal carers
Give clients and, with their consent, their family and friends access to appointments, reports and the care plan. See also our work on patient intake software.
Secure messaging
Messages between care providers and to the client, with the basis of trust that NEN 7512 describes for electronic communication in healthcare. For communication with other care providers, we build a ZorgMail integration.
Management information without personal data
Aggregated figures on lead times, procedures and usage, built from minimised data, so team leaders can steer without looking into records.
Which healthcare organisations we build for
The care process shapes the app, not the other way round. The focus differs for each type of organisation.
Residential care providers
Nursing homes and clinics where several care providers work on one client. The focus here is handover: what happened in the previous shift, and what is still open.
Home care and outreach teams
Teams that are on the road all day and record on location, often with patchy coverage. Routes, planning and offline working matter most here.
Mental healthcare and long-term support
Care pathways that run for months or years, where the care plan and evaluation take centre stage rather than individual procedures. See also our mental healthcare software.
Healthcare software vendors
Software vendors who want to give their existing package a mobile layer without rebuilding their core. We build the app on the API that already exists, or help get it in order first.
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 in healthcare
A healthcare app stands or falls with its integration. HL7 FHIR is the standard for structured exchange between healthcare systems and is well suited to mobile applications. For exchange with personal health environments, the MedMij framework applies. Where a source system has no modern API, we build an intermediate layer rather than having the app read directly from a database. You can read more about our broader approach at building healthcare software.
If your app needs to retrieve data from the source system or write it back using HL7 FHIR and the Dutch profiles, take a look at our HL7 FHIR integration.
For practices that use FysioManager alongside their own app, there is our page on a FysioManager integration.
If you measure insoles and want to keep scan, prescription and evaluation together, take a look at our app for the insole measurement record.
Why choose Appfront for your healthcare app?
We build custom software with smart technology and considered design, starting with the process rather than a screen design. In healthcare, that means first getting clear on which data comes from where and who may see it, and only then thinking about how it looks.
We work in design and development sprints, so you see working versions along the way. Healthcare professionals who get involved early help weed out the steps that don't work in practice. That matters even more in healthcare, because an app that costs time instead of saving it will be left unused at the bedside within two weeks.
The process runs from a no-obligation introduction through planning and development to maintenance. Work continues after go-live too: the Wegiz (Dutch Act on electronic data exchange in healthcare) is introducing mandatory data exchange step by step for each care process, and that means maintaining integrations.
Still exploring more broadly? Take a look at our app development, what we do in custom software, our overview of healthcare software companies or our sovereign cloud for healthcare.
- Custom apps for iOS, Android and web that fit your care process
- Built in line with NEN 7510 and the GDPR, so you can demonstrate compliance
- Logging set up in line with NEN 7513
- Experience with integrations on EHR systems
- HL7 FHIR as the starting point for structured data exchange
- Offline working where coverage is unreliable
- Healthcare professionals involved during the sprints, not just at delivery
- Clear documentation of data flows for your record of processing activities
- Ongoing maintenance when the Wegiz makes new data exchanges mandatory
Security and privacy in a healthcare app
A healthcare app processes health data, which is special category personal data under the GDPR. On top of that, NEN 7510 applies as the information security management standard for healthcare. Certification is not mandatory, but as a care provider you must be able to demonstrate that you meet the standard. We set up the app so that this evidence comes from the system itself rather than from a separate statement.
In practice, that means authorisation based on role and treatment relationship, so staff don't see all records by default, logging of access and changes in line with NEN 7513, and data minimisation in the integration. It also involves an explicit decision on what may be stored encrypted on the device, with remote wipe if a device is lost.
Our broader approach is set out in our information security policy and CVD policy. Would you like to discuss your situation? Get in touch.
- Processing of special category personal data in line with the GDPR
- Building in line with NEN 7510 as the management standard
- Trust framework for data exchange in line with NEN 7512
- Logging of actions on the record in line with NEN 7513
- Authorisation based on role and treatment relationship
- Encrypted offline storage and remote wipe
- Encryption in transit (TLS 1.2 or higher) and at rest
- Data minimisation in every integration
- Documented data flows for your processing register
Frequently asked questions about building a healthcare app
The questions healthcare organisations ask us most often before they build an app.
A healthcare app is a mobile application that lets healthcare professionals record data and clients view their care information, connected to the source system where the record is held. The record stays in the EHR; the app retrieves what is needed and writes the entry back. An app that keeps a second record of its own creates exactly the duplicate administration you wanted to avoid.
Via the Decree on electronic data processing by healthcare providers, the Additional Provisions for Processing Personal Data in Healthcare Act (Wabvpz) refers to NEN 7510. As a healthcare provider, you must be able to demonstrate that you comply with that standard. Certification is not mandatory, but demonstrating compliance is. We design authorisation, logging and data minimisation so that you can pull that evidence straight from the system.
NEN 7510 is the information security management standard for healthcare and describes how you organise security. NEN 7512 covers the basis of trust for electronic communication in healthcare. NEN 7513 describes the logging of actions on electronic records, so that it can be verified who viewed or changed which record.
Preferably via HL7 FHIR, the international standard for structured data exchange, which works well for mobile applications. If your source system has no modern API, we build an intermediate layer that handles the exchange. We never let an app read directly from another system's database, because that turns every upgrade of that system into a risk.
It can, and in home care it is usually a hard requirement. The app keeps an encrypted local working set and synchronises as soon as a connection is available. What matters is what happens when conflicts arise: we present these explicitly to the care professional rather than silently letting one version win.
MedMij is the Dutch framework of agreements for data exchange between healthcare providers and personal health environments. If you want clients to be able to retrieve their data into their own PHR, connecting to that framework is the way to go. It does come with requirements that only pay off if your clients actually use it, so we weigh that up together beforehand.
Yes. We regularly take over the maintenance of an existing application or build a mobile layer on top of a package that is already in place, even if another party built it. We start with a review of the architecture, the integrations, the authorisation model and the logging, and document what we find before changing anything.
The Electronic Data Exchange in Healthcare Act (Wegiz) introduces mandatory electronic exchange step by step, per care process. This means new requirements will periodically be added for flows that you currently handle differently. Build on standards such as HL7 FHIR, so that a new obligation becomes an extension rather than a rebuild.
Ready to build your healthcare app?
Tell us where your care process gets stuck: registration that only happens at the end of a shift, a client portal that nobody uses, or a source system that cannot be opened up to mobile. We are happy to think along with you on integrations, authorisation and what NEN 7510 and the GDPR require in your situation.
Is this topic relevant within your own organisation too? On applatenmaken.com you can read more about Software for healthcare.