Sector · Healthcare

Electronic health record app. A mobile layer on top of your EHR.

We build custom apps for healthcare professionals that run alongside the EHR system. Record access on a tablet, nursing reports at the bedside, medication administration with BEM checks, photos for wound reporting, voice-to-text for quick notes. Secure via UZI card or ZorgID, integrated with HiX, Epic or another EHR via HL7 FHIR R4, assessed against NEN 7510. For hospitals, mental healthcare, long-term care, GPs and pharmacists.

SettingHospital / university medical centre
SettingMental healthcare
SettingNursing and care / disability care
SettingGPs / pharmacists

Dutch healthcare IT in numbers.

~70%
HiX (ChipSoft) market share in Dutch hospitals
100%
NEN 7510 mandatory for healthcare providers
2.300+
Healthcare providers connected to MedMij
FHIR R4
Standard for data exchange since Wegiz

Source: Nictiz information standards, MedMij register, Wegiz implementation plan.

The EHR was never built for the ward floor.

HiX, Epic, Cerner and CGM's GP systems do well what they were designed for: a reliable source record of the patient file, with the regulatory safeguards that come with it. But staff on the ward experience them every day as sluggish, click-heavy and tied to a desktop in a nurses' station. The nurse who has to record a check at 03:00 wants to do it on a device at the patient's side, not four rooms away on a workstation on wheels that someone is already using.

The consequences are familiar: duplicate administration on a paper worksheet that is typed up later, reporting delayed until after the shift, and frustrated nurses who lose working time to screen navigation. In long-term care the picture is even sharper: staff often work at locations without fixed workstations, and EHR use sometimes falls back entirely on a colleague who fills things in later.

An app on top of your EHR fills exactly those gaps that the EHR itself does not. Entering vital signs at the bedside, adding a wound photo plus observation to the record, dictating a SBAR handover with speech-to-text, signing off medication with a BEM scan, working through a discharge checklist: all at the bedside or in the community, all synced back to the EHR via FHIR.

We do not replace the EHR. It is deeply embedded in your organisation's work processes, regulations and financial flows. A rip-and-replace makes sense in almost no care setting. We build the mobile layer that works on top of it and spares the EHR the clicks that never belonged there, and that puts your care professionals back where they want to be: at the bedside, not in front of a screen.

An EHR app for every care setting.

The workflow on a surgical ward is fundamentally different from that in a mental health clinic or at the GP. For each setting we build the functionality that belongs there, with the right integrations and the right authorisation model.

Hospitals & university medical centres

On a nursing ward, doctors and nurses work at a high pace with patterns that fit poorly with a desktop EHR. The EHR app brings the record to the iPad, a shared tablet or the workstation on wheels: lab results, imaging thumbnails, the current medication overview, allergies, vital signs and the ability to report immediately, without the user having to log out and back in on a shared desktop every time.

Commonly requested in this setting: a SBAR handover module with voice input for warm handovers between shifts, a BEM medication scan workflow that links the barcode on the patient wristband to the medication with a double check, photo capture for pressure ulcer or wound reporting with automatic sizing and historical comparison, and an admission/discharge checklist that syncs with HiX or Epic. We connect via HL7 FHIR R4 or, where necessary, via the existing HL7v2 interfaces of your integration layer (Cloverleaf, Rhapsody, Mirth). In university medical centres we also often work with research infrastructure: an EHR app that supports opt-in research participation and can deliver data to the research environment via i2b2 or OMOP mapping does not need to be a separate build, but a module of the same app.

  • Record access at the bedsideLab values, medication, allergies and vital signs on a tablet.
  • BEM medication administrationBarcode scan on patient and medication, double-check flow.
  • Wound reporting with photoEncrypted upload, retention handled in the EHR.
  • Ambient AI scribeSpeech-to-text for clinical notes and SOAP reporting.

Built to healthcare's strictest standards.

An EHR app handles special category personal data and, with diagnostic features, may fall under the Medical Device Regulation. For us, compliance is not a document written after the fact, but part of the first sprint. Read how we build NEN 7510-compliant software.

NEN 7510-1 / 7510-2

Information security in healthcare

The standard healthcare providers must comply with, based on ISO 27001 but with healthcare-specific controls. From the first sprint, we build role-based authorisation, end-to-end encryption, audit logging and key management in line with the NEN controls. If your organisation goes through a certification process, we can supply the relevant app documentation for the external auditor.

GDPR / UAVG Art. 9

Special category personal data

Health data falls under Art. 9 GDPR and may only be processed under strict conditions: a treatment relationship, explicit consent, or a specific legal basis. On every project we deliver a DPIA, a data minimisation analysis, a retention period matrix and a data processing agreement in line with the Dutch UAVG implementation. Your organisation's data protection officer (DPO) receives the full file and is actively involved in the scoping phase.

WGBO & Wkkgz

Medical treatment contract

The right of access, the right of correction and the twenty-year retention period from the WGBO are built in at data model level. For Wkkgz incident reporting, we provide a separate audit trail that can be viewed independently of the client record.

MedMij & Nictiz

Personal health environment

For PHR features or patient portals, we work in line with the MedMij guidelines and Nictiz information standards, with FHIR zib mapping (healthcare information building blocks) on the exchanged fields.

MDR (EU 2017/745)

Medical Device Regulation

If a feature supports clinical decision-making or provides diagnostics, the app falls under the MDR, usually class IIa or higher. That brings a notified body process, technical documentation, a quality management system (often ISO 13485) and a post-market surveillance plan. During the scoping phase, we classify together with your notified body or clinical physicist, and only then decide which functionality falls inside or outside the MDR process. It is often wise to separate the MDR features from the non-MDR features in a separate module to keep the scope manageable.

EU AI Act

Responsible AI in a clinical context

Under the AI Act, AI features such as an ambient scribe, risk triage or image classification are classed as high-risk. We document the risk assessment, transparency requirements and human oversight according to the Annex III criteria.

SNOMED CT & ICF

Clinical coding

Wherever possible, we code diagnoses, findings and interventions in SNOMED CT, and functioning in ICF. That saves integration headaches later with quality registries and health insurers' DBCs.

Integrated with the EHR systems used in healthcare.

EHR systems are deeply embedded in healthcare organisations, so a rip-and-replace rarely makes sense. We build apps that work on top of your existing EHR, via a FHIR API, HL7v2 or HL7v3 interfaces, or via the native integration points of your EHR vendor.

HiX
ChipSoft: hospitals
Epic
University medical centres and large care groups
Cerner / Oracle Health
International
CGM
GP EHR
Topicus
Care & youth care
VIPLive
eHealth layer
Nedap Ons
Long-term care
UZI / ZorgID
Authentication

Our app is a layer, not a replacement.

The EHR remains the source system. Our app reads and writes via FHIR, with audit logging on every transaction and a data model anchored on the zibs (healthcare information building blocks). For fields that are not in FHIR R4 — there are still EHR-specific flows that fall outside the standard — we work through a vendor-specific interface. For HiX, for example, that is the Cure API or the IHE-compliant XDS interface; for Epic, the App Orchard canvas; for CGM, the GP API interface. We connect to your organisation's existing integration platform, so our app does not become an extra integration layer that has to be maintained separately later.

For authentication we support the UZI card (PKIoverheid), ZorgID and, in an office context, eHerkenning. Session management meets the NEN 7510-3 controls for healthcare logins: short sessions, automatic lock on inactivity, hardware-bound secrets. For offline use (poor Wi-Fi on wards or in community nursing), the app uses an encrypted local cache that syncs on reconnection with a conflict-resolution strategy we agree per workflow — last-write-wins is rarely safe enough in a healthcare context; a merge with clinical review is often the right choice. Our experience with offline-first field service apps comes in directly useful here, even though healthcare regulation is stricter.

For the patient side — a PGO (personal health environment) integration, an appointment portal, or access to their own record — we work in line with the MedMij framework requirements and the Nictiz guidelines. These come with their own authorisation flow (BSN-based via DigiD) and their own retention and withdrawal rights.

Ambient AI alongside the record.

The most interesting improvement we are currently building in healthcare is an ambient AI scribe: a microphone feature on the tablet or phone that records the conversation between doctor and patient, transcribes it locally or in a NEN 7510 environment, and prepares a draft report in SOEP structure for the doctor. The doctor edits, checks and files it in the EHR. Comparable to Nuance DAX or Abridge, but built within Dutch compliance frameworks.

For nursing reports we use Whisper-based speech-to-text (locally or in a European cloud environment), with a post-processing layer that understands healthcare terminology — abbreviations, medication names, anatomical terms. In an early test the time savings show up within a few shift rounds, provided the language model is well tuned to your field.

For every AI feature we document the risk classification under the EU AI Act, the human supervision role, and how the user is informed about the AI's involvement. A hallucination in a SOEP report is far more serious than in a marketing email; human review is therefore a standard part of the flow, not an option.

From scope to live on the ward.

A healthcare project has its own rhythm: medical ethics, IT security and the shop floor all sit at the table. Five phases that recur in every EHR app project.

01 · Discovery

Workflow shadowing

We follow along on the ward. One nurse, one doctor, one department manager as a guide. Result: current flows mapped, friction points identified.

02 · Design

Scope and classification

Which flows go in the app, which integrations take priority, does anything fall under the MDR? First version of the DPIA. AI features get an Annex III check.

03 · Build

Sprints with a clinical test group

One working flow delivered every sprint. Nurses test alongside us. FHIR integration live early in a test EHR environment.

04 · Cutover

Phased rollout per ward

First one ward, then a second, then a broad rollout. With every rollout: training, a super-user programme and a shadow-running period.

05 · Maintenance

Compliance maintenance

We adapt with every iOS or Android update, EHR release or change in legislation. First-line support through your IT department, escalation to us.

What the healthcare IT literature points to.

Nictiz · MedMij framework

"FHIR R4 and healthcare information building blocks form the basis for data exchange between EHRs, PHRs and healthcare apps in the Netherlands."

Wegiz — Electronic Data Exchange in Healthcare Act

Since Wegiz, data exchange between healthcare providers must be electronic. Apps that connect to the EHR must therefore be FHIR-compliant as standard.

NEN 7510-3 — Logging in healthcare

"Every access to a patient record is traceable to an individual user, with an immutable audit trail." Our apps meet this from the first release.

Answers for IT directors and business managers.

The questions we hear most from CMIOs, IT managers and medical directors.

What exactly is an EHR app?
An EHR app is a mobile or tablet application that runs alongside your existing electronic health record (EHR). The app does not replace the EHR — that remains the source system — but adds mobile functionality: bedside access to patient records, nursing reports, medication administration with barcode scanning, photo capture for wound care, or voice-to-text for quick reporting. The EHR remains the source of truth; the app writes and reads via FHIR or a vendor integration. For the care provider, this means the work comes back to the bedside or consulting room, away from the shared desktop in a corner of the ward.
How does your app integrate with HiX or Epic?
HiX offers the ChipSoft Cure API for read and write access from certain versions onwards; we also often work with HL7v2 messages via your organisation's integration layer (for example Cloverleaf or Rhapsody). For Epic, we use the App Orchard programme and the associated FHIR endpoints. Both vendors require a formal integration process with certification — we guide the application and build against the test environment before going into production.
Does the app comply with NEN 7510?
Yes. From the first sprint, we build within the NEN 7510-1 and 7510-2 control framework: role-based authorisation, end-to-end encryption of data at rest and in transit, key management in a KMS, audit logging in line with NEN 7510-3 and periodic pen tests. For large projects, we involve an external NEN 7510 auditor for formal assessment. The NEN 7510-3 logging requirements are a standard part of the architecture.
What is FHIR and do we really need it?
FHIR (Fast Healthcare Interoperability Resources) is the international standard for exchanging healthcare data, defined in resources such as Patient, Observation, MedicationRequest and Encounter. In the Netherlands, FHIR R4 is the de facto standard for PHR and MedMij integrations, and Wegiz is making it mandatory more and more often. Yes, for a new EHR app FHIR is our default — only if your EHR does not yet support it do we build a bridging integration via HL7v2 or a vendor-specific API.
Does our EHR app fall under the Medical Device Regulation?
That depends on the functionality. A record-viewing app or a reporting tool generally does not fall under the MDR. As soon as a feature supports clinical decision-making — for example a triage algorithm, a risk score or diagnostic image analysis — MDR classification comes into play (often class IIa or higher). During the design phase, we carry out a classification check together with your clinical physicist or a notified body. Only then do we determine which features fall inside or outside an MDR process.
Does the app also work offline?
Yes, that is a common requirement. On nursing wards, in community care or in the basements of older care buildings, WiFi coverage is not always reliable. Our apps use a local encrypted cache: you can view record data, type reports, take photos and sign off medication without a connection. On reconnecting, the app syncs with the EHR via FHIR, using a conflict-resolution strategy we agree per workflow (last-write-wins is usually not safe enough in a healthcare context).
What determines the cost of an EHR app?
For a single department and one specific workflow (for example wound reporting only, or medication administration only), this is a compact project. A broad mobile layer spanning multiple departments, with an FHIR integration, offline mode, ambient AI scribe and a patient portal component, is a larger project. The biggest cost drivers are usually the complexity of your EHR integration (in particular whether an FHIR endpoint is available), MDR classification where applicable, the number of distinct role flows in the app, and the degree of offline functionality. We work with a fixed sprint budget and give you a concrete price indication for the complete build after the scoping phase.
Who can be the client within a healthcare organisation?
In practice, we work most with IT directors, CMIOs (Chief Medical Information Officers) and business managers of a department or service. For larger projects, the Board of Directors or the medical director joins the table for scoping. For input from the shop floor, which is crucial to the success of an EHR app, we work with super-users from nursing, physicians and allied health professionals. The DPO (data protection officer) is involved from the DPIA phase and stays involved until go-live.
How does this fit within Wegiz and MedMij?
The Wegiz (Electronic Data Exchange in Healthcare Act) requires healthcare providers to exchange data electronically and in a standardised way, in most cases via FHIR with zib mapping. MedMij is the framework of agreements that governs how personal health environments (PGOs) communicate with EHRs. If your EHR app gives patients access or exchanges data with other healthcare providers, it must be built in compliance with Wegiz and MedMij. We build to these standards from day one, not as a mandatory retrofit but as the natural architecture.

Talk to us about your EHR app.

An initial introduction with a CMIO, IT director or business manager. We listen to the workflow, look at your existing EHR, and give you an initial direction. No obligation, from our office on Westerdoksdijk or at your location.

Edit content