Custom ChipSoft integration development
Appfront builds custom integrations with the ChipSoft HiX hospital EHR. Using healthcare standards such as HL7v2, HL7 FHIR and IHE profiles, we connect HiX securely to your own care application, patient portal or medical app. Patient, appointment, order and result data flows in a structured, bidirectional way, within a secure environment that complies with the GDPR and NEN 7510.
What is a ChipSoft integration?
ChipSoft is the Dutch market leader in hospital information systems with its product HiX (Healthcare Information eXchange). HiX is the electronic patient record that most Dutch hospitals, and many mental health and care institutions, use to manage the care process: patient records, care administration, scheduling and billing all come together in one system.
A custom integration means that your own application, patient portal or medical app exchanges structured data with HiX. Through HL7v2 messages, HL7 FHIR resources and IHE profiles, patient details, appointments, orders and results move between HiX and your system, either one-way or bidirectionally, depending on the care process you support.
Appfront builds on the official FHIR specifications published by ChipSoft and OWASP best practices. We align interfaces, message flows and error handling with your actual care process, so the integration stays reliable and demonstrably compliant within the secure environment, even at peak volumes.
Structured care data
Patient, appointment, and order or result data from HiX as structured HL7 and FHIR resources, not loose documents. Fields are cleanly mapped to your data model, so information flows reliably and unambiguously between systems.
Real-time synchronisation
Changes to appointments, admissions and results are passed on immediately through message flows, so your application and HiX stay in step. No manual re-typing or overnight batches falling out of sync.
Secure and compliant
Authentication via certificates, encryption, and logging of access to patient data within a secure environment. We build to NEN 7510 and GDPR, so the exchange of medical data demonstrably takes place with due care.
Our development process for ChipSoft integrations
We follow a proven method that removes uncertainty early and delivers a stable care integration. From an initial analysis of your care process, the required message flows and the right HiX interface, through to go-live and ongoing management, every step is designed to give your team an integration they can understand and trust.
We map out which patient, appointment or result data you want to exchange with HiX, which healthcare standards (HL7v2, FHIR, IHE) and interfaces are needed, and which legal basis and secure environment apply.
We design the integration architecture, choose the appropriate certificate-based authentication, and establish an error handling and logging strategy compliant with NEN 7510.
Implementation with automated tests, structured logging and monitoring. We test the message flows in an acceptance environment, and you see working builds along the way.
Controlled go-live with data validation and a safety net, followed by ongoing management, certificate rotation and further development.
What a ChipSoft integration delivers in practice
Every HiX integration is tailored to your care process, the healthcare standards involved and the adjacent systems. Below are the features we most often deliver for organisations that need to integrate with the ChipSoft HiX hospital EHR.
Exchanging patient data via HL7/FHIR
Demographic details, identification (BSN) and record data from HiX made available in a structured way via HL7v2 (ADT) and HL7 FHIR resources. Fields are carefully mapped to your data model, with data minimisation as the starting point.
Synchronising appointments and scheduling
Synchronise appointments, admissions and scheduling bidirectionally between HiX and your application or patient portal. Changes are passed on via message streams, so that agendas and waiting lists are accurate on both sides.
Connecting orders and results
Connect laboratory and diagnostic orders and their results via HL7 order messages (ORM/ORU). Requests and results flow reliably between HiX, laboratory and diagnostic systems and your own application, with status monitoring.
Patient portal integration
Feed a patient portal or care app with record, appointment and results data from HiX. Patients see their own information only after valid authentication, with access logged, so that access is demonstrably handled with care.
Medical apps & devices
Connect medical apps and devices to HiX so that measurements and generated data reach the record via FHIR or HL7. We configure the integration around the correct resources and monitor the integrity and provenance of the data supplied.
Regional exchange & BI
Make HiX data available to regional exchange and to a BI or data warehouse environment. Anonymised or pseudonymised data flows in a structured way for management information, with legal basis and data minimisation as the starting point.
Typical use cases in practice
A ChipSoft integration looks very different from one organisation to the next. We regularly see a number of recurring patterns, and for each we have a proven setup that accounts for the right healthcare standards, interfaces and secure environment.
Hospitals
Hospitals that want to connect HiX to their own applications, a patient portal or a data warehouse. Patient details, appointments, orders and results flow reliably between HiX and adjacent systems via HL7 and FHIR. See also our API integrations.
Mental health institutions
Mental health and care institutions using HiX that want to connect it with treatment, care coordination or client applications. Record, appointment and treatment data flows in a structured way, with logging of access and a clear legal basis for every data flow involving special category personal data.
Patient portal & app vendors
Healthcare software vendors, patient portals and care apps that need to integrate with the hospital EHR. We build a reusable interface on HL7 and FHIR, so your product connects to multiple HiX environments without starting custom work each time.
Medical device integrations
Vendors of medical devices and measuring equipment that want their data to land in HiX. Measurements and signals are translated via FHIR or HL7 into the correct resources, with attention to provenance, integrity and NEN 7513 logging of access.
Technology we use
We build ChipSoft integrations using the prevailing healthcare standards and HiX interfaces, combined with the backend stack that suits you. The precise choice depends on the care process, the systems involved and the secure environment, so that your own team can manage or further develop the integration.
Why choose Appfront for your ChipSoft integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always begin with a thorough analysis of the existing systems and processes. A healthcare integration must not only work technically, but also add practical value to the care process.
With every integration, we write clear documentation so that your own team, or a future supplier, can understand and manage the integration. No black box, just transparent code and clear agreements on monitoring, alerting and certificate management.
You work with a dedicated point of contact who understands both the technical and the functional side. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.
You may also be interested in our wider services around API integrations, middleware, custom software and web app development. Working in healthcare? Take a look at our integrations with Nedap, ZorgMail and VECOZO.
- Experience with HL7v2, HL7 FHIR and IHE profiles
- Experienced with ChipSoft interfaces and HiX message flows
- Experienced with patient data, appointments, orders and results
- Secure by default: certificate authentication and scoped permissions
- Compliant with NEN 7510, NEN 7512 and NEN 7513
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing management, certificate rotation and further development
Security and privacy in ChipSoft integrations
A HiX integration processes special category personal data: patients' medical data. This calls for the highest level of care. Appfront builds in line with the NEN 7510, NEN 7512 and NEN 7513 healthcare standards, as well as the OWASP ASVS. This includes, among other things: authentication via certificates in a secure environment, encryption in transit and at rest, data minimisation, and logging of every access to patient data.
We only process medical data on a valid legal basis and with the appropriate consent, and we do not exchange more data than the care process requires. We document the data flows, interfaces and NEN 7513 logging so that your record of processing activities is complete and you can demonstrably comply with the GDPR. This keeps every exchange with HiX traceable and accountable.
More on our security approach: information security policy and CVD policy.
- NEN 7510 / 7512 / 7513-compliant healthcare integration
- GDPR-compliant processing and data minimisation
- Certificate authentication in a secure environment
- Encryption in transit (TLS 1.2+) and at rest
- Logging of access to patient information
- Role-based access and least-privilege principles
- Automatic retries and dead-letter queues
- Monitoring and alerting for anomalies
- Documentation for your record of processing activities
Frequently asked questions about ChipSoft integrations
Answers to the questions we most often receive about HiX implementations.
A ChipSoft integration is a technical link between the HiX hospital EHR from ChipSoft and another system, such as your own care application, patient portal, medical app or data warehouse. Using healthcare standards such as HL7v2, HL7 FHIR and IHE profiles, patient, appointment, order and result data is exchanged in a structured way. An integration can be simple (a single message flow carrying patient data) or complex (bidirectional synchronisation of appointments, orders and results with real-time status updates), always within a secure environment.
A HiX integration makes sense when your organisation or application needs to exchange data with the hospital EHR used by most hospitals in the Netherlands. HiX is the standard for hospital EHRs. For care and elderly care EHRs, Nedap ONS is often used, ZorgMail is used for secure care communication, and VECOZO for claims traffic. Appfront connects to HiX rather than replacing it. Together with you, we will assess which standard and which interface best suit your situation.
The lead time depends on the type of interface, the healthcare standards involved and the secure environment the integration runs in. A well-defined message flow can be delivered faster than a bidirectional integration with appointments, orders and results plus regional exchange. Because this involves medical data, we allow time for a security review, testing in an acceptance environment and validation. After an intake conversation, we give you a realistic estimate.
We work with the established healthcare standards for HiX: HL7v2, HL7 FHIR, IHE profiles and the ChipSoft interfaces, with authentication via certificates and credentials in a secure environment. We build the backend in the stack that suits you, whether Node.js, .NET, Java or Python. We align with the official FHIR specifications as published by ChipSoft, and we set up logging, monitoring and error handling in line with NEN 7510 (Dutch information security standard for healthcare) and OWASP best practices.
The cost is determined by the complexity of the data flows, the number of systems to integrate, the healthcare standards chosen, the requirements for the secure environment, and the amount of custom business logic. Ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote following a no-obligation analysis of your situation.
Yes. A HiX integration processes special category personal data (medical data), so security and privacy are central. Appfront builds to NEN 7510, NEN 7512 and NEN 7513 (Dutch healthcare information security standards) and OWASP best practices: certificate-based authentication, encryption in transit and at rest, data minimisation, and logging of access to patient data. We only work with a valid legal basis and consent, and we document the data flows so that your record of processing activities remains complete and you can demonstrate GDPR compliance.
Yes. Appfront regularly takes over existing healthcare integrations, even if they were originally set up by another party. We review the HL7 and FHIR message flows, the interfaces, the certificate authentication and the error handling, document the current setup and propose improvements. From then on, we can handle adjustments, extensions and monitoring, including timely certificate management.
A ChipSoft integration suits hospitals and mental health institutions that want to connect HiX to their own applications, and healthcare software, patient portal and medical app providers that need to integrate with the hospital EHR. Typical use cases include exchanging patient data via HL7/FHIR, synchronising appointments and scheduling, linking orders and results, feeding a patient portal, and making data available to a BI or data warehouse environment. For care ECD, care communication or claims traffic, we will work with you to determine whether Nedap, ZorgMail or VECOZO is a better fit.
Ready to build your ChipSoft integration?
Tell us which patient, appointment or results data you want to exchange with HiX, and which application, patient portal or device ChipSoft should connect to. We are happy to help you choose the right healthcare standards, interfaces and secure environment. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.