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.