Building Healthcare Apps in Israel: Regulation, Privacy, and What Actually Ships

TL;DR: Healthcare apps in Israel ship when regulation and integration are planned from day one. Four rules shape the work: the Privacy Protection Law and its 2025 Amendment 13, the Ministry of Health's cloud circular, the Medical Equipment Law for clinical software, and the IS 5568 accessibility standard. Add HMO and hospital integrations, and a realistic MVP takes 9-12 months to reach production.

Healthcare apps stall on regulation and integration

The technology is rarely the problem. The regulatory and integration requirements are underestimated. A healthcare app that works in a demo but can't connect to an HMO's systems or pass a security review never launches.

We've built healthcare products for pharmaceutical companies, clinic chains, hospitals, HMOs and digital health startups. Here's what we wish someone had told us before our first project.

The Israeli regulatory landscape

Privacy Protection Law (1981) and Amendment 13. Health data counts as sensitive information under Israel's privacy law, which means stricter security and consent requirements. Amendment 13, in force since 14 August 2025, gives the Privacy Protection Authority power to impose significant monetary sanctions and requires many organizations to appoint a privacy protection officer. Enforcement used to be light. That has changed.

Ministry of Health cloud rules. Director General Circular 2/2021 allows health organizations to use cloud services, including hosting outside Israel. Each project needs a documented risk assessment and approval from the organization's cloud committee. High-risk projects also need a recommendation from the Ministry's sectoral cloud committee. Data sent abroad must meet the Privacy (Transfer of Data Abroad) Regulations. AWS publishes a detailed summary of the circular.

Medical device classification. Israel's Medical Equipment Law, 2012 includes software in its definition of medical equipment. If your app provides clinical recommendations, it may need registration with the Ministry of Health's Medical Devices Division (AMAR), which adds months of regulatory work. If it only presents data without clinical interpretation, you may avoid this classification. The distinction matters enormously for your timeline and budget.

Integration with Israeli healthcare systems

Israel's four HMOs (Clalit, Maccabi, Meuhedet and Leumit) each integrate differently. Plan for different APIs, data formats and approval processes with each one.

Ofek, Israel's national health information exchange, connects all four HMOs and about 50 hospitals. The Ministry of Health's Eitan project is its successor. It is the closest thing to a unified data layer.

Our recommendation: Design for the lowest common denominator integration first, then optimize. Build your app with a clean abstraction layer between your business logic and the HMO integration code. When an HMO changes its API (and it will), you change one adapter and leave the rest of the application alone.

What separates healthcare apps that ship from those that don't

Clinical workflow understanding. Before writing any code for TokiDoc, our telemedicine project, the developers shadowed doctors for two weeks and observed real clinical workflows: how doctors review history before a visit, take notes between patients and prioritize the next case. The app had to match how doctors actually work during consultations.

Offline capability. Clinic connectivity can be unreliable. Any app used by clinicians needs to work offline and sync when connectivity returns.

Accessibility compliance. Israel's Service Accessibility Regulations (2013) require websites and apps to meet Israeli Standard IS 5568. Its current edition (September 2023) adopts WCAG 2.0 Level AA with Israeli changes. For healthcare, this is non-negotiable, because patients with disabilities depend on these tools.

What we've shipped in Israeli healthcare

• [Care Laser](/cases/care-laser): a patient self-service app for Israel's largest aesthetic clinic chain. It syncs in real time with the existing CRM across 33 branches, with no backend migration. It went from brief to full 33-branch deployment in 6 months.
• [TokiDoc](/cases/tokidoc): Israel's first complete telemedicine platform, with a doctor portal, a patient app and end-to-end encrypted video with live medical documentation. It connects to EMR, lab, imaging and scheduling systems.
• [Pfizer I Grow](/cases/pfizer): a game that helps children with growth hormone deficiency accept daily injections. It tracks injection sites and sends real compliance data to physicians. We built it in 6 months with child psychologists, and Pfizer named it its Top Innovative Project of 2015.
• [Savyon Diagnostics](/cases/savyon-diagnostics): an on-device computer vision SDK that reads COVID-19, pregnancy and ovulation tests inside major Israeli hospital and HMO apps. No data leaves the phone during scanning. During the pandemic, it supported millions of COVID tests.
• [Check2Fly](/cases/check2fly): Israel's COVID-era border system, integrated with the Ministry of Health. It handled millions of sensitive health records with zero security incidents.

Frequently asked questions

How long does a healthcare app take to build in Israel? MVP: 4-6 months of development, plus 3-6 months for regulatory approvals and HMO integrations. Total realistic timeline: 9-12 months to production.

What does it cost? Budget $200K-400K for an MVP with one HMO integration. A full production app with all four HMOs and regulatory compliance: $500K-800K.

Can we use cloud infrastructure outside Israel? Often, yes. The Ministry of Health's cloud circular allows it after a risk assessment and approval, and data transfers abroad must meet Israel's privacy regulations. AWS and Azure both run cloud regions in Israel, which simplifies high-risk projects.

Building a healthcare app? We've navigated Israeli healthcare regulations for years.