MicroHIS integration development
MicroHIS is the GP information system from iSOFT Nederland, also known in overviews of GP information systems as MicroHIS X. GP practices work in it every day, and through standards such as HL7, FHIR and the LSP (the national healthcare information exchange), MicroHIS exchanges data with pharmacies, laboratories, out-of-hours GP services and other care providers. If you want to use data from MicroHIS in your own application, an overview for the care group or a system that is not covered by the standard integrations, more is needed. Appfront builds the integration between MicroHIS and those systems, using only the data that is permitted and necessary.
What is a MicroHIS integration?
A MicroHIS integration connects iSOFT's GP information system with the systems around it. In MicroHIS, the practice manages patient records, the diary, prescribing and communication with chain partners. iSOFT offers MicroHIS as a Published App that runs in the browser, and with MaaS also as a fully managed workplace in Dutch data centres. As of version 17.0, you can dictate a consultation with Voice-Text-SOEP, and decision support comes via ExpertDoc. The integration takes over the data that another system needs and returns what belongs in MicroHIS.
According to iSOFT, MicroHIS already exchanges data with out-of-hours GP services, pharmacies, laboratories, physiotherapists, mental health care, community nursing, dietitians and midwives, using standards such as HL7, FHIR and the LSP (the national patient summary exchange). With the pharmacy, MicroHIS 17.0 communicates via Edifact, and the package is prepared for Medicatieproces 9 (the national medication process standard). For exchange with other systems, iSOFT is the exclusive partner in the Netherlands for Rhapsody, a healthcare integration platform supporting HL7 v2, FHIR and CDA. A custom integration covers whatever falls outside that: your own triage or waiting-room application, an overview for the care group, or data for your own portal.
We build custom because every practice and care group has different needs. Which data you need, on what legal basis, for which practices and in which system it has to end up, determines how the integration works. We did not find public MicroHIS API documentation on the iSOFT website. Which route fits best, via a standard, via Rhapsody or via another entry point, and how you get access, we establish in the first step together with you and iSOFT.
Your own overview
Data from MicroHIS, brought together.
Only what is permitted
With legal basis and permissions.
Alongside the HIS
Your applications connected.
How we build your MicroHIS integration
We start with your question: which data you want to retrieve from or send to MicroHIS, for which practices, on what legal basis, and which integrations you already use. Then we agree the route with iSOFT and build the first integration, usually the flow that currently costs the most manual steps. You work with it in the practice for a while. Other flows and practices follow if it goes well. After that, we maintain the integration when MicroHIS gets a new version or your other systems change.
Data, practices, legal basis.
The biggest time saving first.
More flows and practices.
Go-live, monitoring, and maintenance when things change.
What a MicroHIS integration actually does
The components below appear in almost every MicroHIS integration. Which ones you need depends on your question and on the systems you use alongside MicroHIS.
Standards
HL7, FHIR and Edifact.
Practices
Organised per practice.
Validation
Deviations flagged.
Selection
Only the data that is needed.
Access
Permissions per role.
Reporting
Overview for the care group.
Who we build a MicroHIS integration for
The integration is intended for GP practices and organisations that work with MicroHIS and also have systems that don't talk to it as standard. The more practices and patients, the more it delivers.
Practices
Adding your own applications.
Health centres
Multiple disciplines together.
Care groups
Overview across practices.
Out-of-hours GP services
Data across the chain.
Technology and integrations
This page is about integrations with iSOFT's MicroHIS. If you work with a different package, see our pages on the OmniHis Scipio integration and the Medicore integration. For medication data according to the national standard, see our page on the medication transfer integration, for referrals the ZorgDomein integration, and for message exchange our page on Edifact integrations. You can read about our approach on custom software development.
Why Appfront for your MicroHIS integration?
An overview for the care group that is compiled by hand from separate exports, an application that retypes data from the HIS, or patient data that is shared without it being clear why, costs a practice time and trust. That is what we build on: only data that is permitted and necessary, checked against MicroHIS, and an integration that shows when something went wrong.
Only what is permitted
Legal basis recorded up front.
Reviewed
Checked against MicroHIS.
Visible
Errors in the log.
Security and privacy in a MicroHIS integration
The integration processes patients' medical data, which falls under the strictest GDPR rules. It uses only data for which there is a legal basis and that is necessary for the purpose, aligns with the NEN 7510 requirements your practice works to, and records every exchange with time and result.
The integration runs in a European data centre, with encrypted connections and storage. Keys are kept secure and are not visible to staff. We agree with you in advance who in your practice or care group may see which data, and where possible we report without data that can be traced back to the patient.
Frequently asked questions about a MicroHIS integration
Questions that GPs, practice managers and care groups ask before they get started.
A connection between MicroHIS and another system you use, such as your own application, a portal or an overview for the care group. Data then flows back and forth automatically, without exports or retyping.
The GP information system from iSOFT Nederland. Practices use it to manage patient records, appointments and prescribing, and to exchange data with pharmacies, laboratories, out-of-hours GP services and other healthcare providers. iSOFT offers it as a Published App and as a managed workplace.
On the iSOFT website the package is called MicroHIS, with version numbers such as 17.0. In overviews of GP information systems you will also come across it as MicroHIS X. It is the same GP information system.
According to iSOFT, MicroHIS supports standards such as HL7, FHIR and the LSP (the national exchange point), and Edifact for pharmacies. We have not found any public API documentation. Which route suits your needs and how you get access, we establish in the first step together with you and iSOFT.
Rhapsody is a healthcare integration platform supporting HL7 v2, FHIR and CDA, among others. iSOFT is the exclusive partner in the Netherlands and cites integration with MicroHIS as an advantage. We will look at whether your integration runs via Rhapsody together with iSOFT.
The integration retries, and an exchange that keeps failing is placed in an error list together with the reason. You can see which message or practice is affected and have it resent after correcting it.
For care groups, health centres and practices with their own application, an overview across several practices or a system that is not covered by the standard integrations. If the integrations MicroHIS already has are enough, custom work is usually not needed.
Want MicroHIS to work with your own applications?
Tell us which data you need from MicroHIS and where it needs to go. We will show you how an integration handles that securely.