ChipSoft ransomware attack: Dutch EHR vendor's patient portals offline, data stolen
A 7 April 2026 ransomware attack on Dutch EHR vendor ChipSoft took Zorgportaal, HiX Mobile and Zorgplatform offline and exposed patient data, Z-CERT says.

ChipSoft is the Dutch vendor behind the HiX electronic health record used by many hospitals in the Netherlands. It was hit by ransomware on 7 April 2026. To limit the damage, it cut off its patient and provider portals, and forensic work later confirmed that patient data from several customers had been stolen. For developers, this is a lesson in what happens when one hosted vendor becomes a single point of failure for a whole sector.
What happened
Z-CERT, the Dutch healthcare sector's cybersecurity centre, published several updates:
- 7 April: ChipSoft was hit by ransomware, and Z-CERT was notified the same day. As a precaution, ChipSoft disconnected Zorgportaal, HiX Mobile and Zorgplatform.
- 9 April: ChipSoft began bringing systems back in phases and issuing new access credentials to users. The impact on care was mainly logistical (busier service desks and more phone calls), and no critical care processes had stopped.
- 14 April: The services were still unavailable, and some patients couldn't see test results digitally. Z-CERT warned of follow-on phishing and fraud exploiting the news.
- 17 April: Forensics showed the attackers had stolen personal and medical data of patients from several Dutch ChipSoft customers, who were informed. Care providers that host ChipSoft software themselves or through a third party were not affected. Z-CERT saw no sign of an active threat in the HiX365 tenant, Zorgportaal, Zorgplatform or HiX Mobile.
- 30 April: ChipSoft said the data would not be published and that the attackers had destroyed it. Experts hired by ChipSoft said the deletion was "technically correct". Z-CERT said it had seen no evidence of this, but considered publication less likely "based on the outcome of the negotiations".
No ransomware group had been publicly named in these updates.
Who is affected
- Hospitals and care institutions using ChipSoft-hosted services (HiX365 and the connected portals), especially the customers whose patient data was taken.
- Patients who use Zorgportaal or HiX Mobile to see results and appointments, and those whose records were stolen.
- Integrators and app developers who connect to Zorgplatform or the portals and had to deal with disabled connections and reissued credentials.
What it means for developers and engineering teams
The most telling detail is who wasn't hit: providers running ChipSoft software themselves or through another host. The attack landed on the vendor's hosted environment, and every tenant connected to it shared the outage and the data exposure. Multi-tenant SaaS is efficient, but its blast radius covers every customer, so tenant isolation, per-tenant encryption keys and strict separation between the vendor's corporate IT and production need to be designed in from the start.
The containment step also matters. Cutting off Zorgportaal, HiX Mobile and Zorgplatform was the right defensive move, but it means every downstream integration must cope with the vendor going dark for weeks. If your system depends on a vendor API for core workflows, ask how it degrades: can staff keep working with cached or local data, and are fallbacks such as phone, paper or exports documented and practised?
Finally, reissuing credentials across a whole customer base is slow and error-prone. Integrations that use short-lived, centrally revocable credentials (OAuth client credentials, mTLS certificates with short validity) recover faster than ones built on static shared secrets.
What to do now
- If you integrate with ChipSoft services, rotate any credentials or API keys the vendor issued or stored, and validate reconnections using the vendor's official channels only.
- Expect themed phishing. Warn staff and patients that ChipSoft and hospitals won't ask for credentials or payment by email or SMS.
- Map your critical vendor dependencies and write down how each workflow degrades if that vendor disconnects for two weeks.
- Design integrations for revocation: short-lived tokens, per-tenant credentials, and a tested runbook for bulk re-issuance.
- Ask SaaS vendors about tenant isolation, including separation of corporate IT from production, per-tenant encryption, and how quickly they can cut off and restore individual connections.
- Follow Z-CERT and ChipSoft's official information pages for updates rather than third-party reports.