Skip to content
DT Nova

Healthcare SaaS: what it is, the rules and how to build one

Healthcare SaaS is software for clinics, hospitals, care providers or patients that runs as a hosted service on a subscription: scheduling, practice management, patient engagement, telehealth, billing, analytics and many more. Building it means combining ordinary SaaS engineering with some of the strictest data rules there are. This guide explains the product types, the design choices that matter most, the rules in the United States, the EU and Germany, and a checklist to plan the build, with sources from the regulators and the law itself.

The short version

  • Decide early which markets you sell into. HIPAA, the GDPR and national health cloud rules each shape the architecture.
  • Design tenant separation, audit logging and encryption into the first version. They are very hard to add later.
  • Expect every customer to send a security questionnaire, and every hospital to ask for evidence such as ISO/IEC 27001, SOC 2 or a C5 attestation.
  • Integrate through standards, preferably HL7 FHIR, rather than custom interfaces per customer.
  • Check each feature against the medical device rules before you build it.

Types of healthcare SaaS

TypeTypical buyersMain data and systems
Practice management and schedulingClinics, dental and therapy practicesAppointments, staff rosters, patient administration
Electronic health recordsClinics, hospitals, care homesClinical record, orders, results, documents
Patient engagementProviders, insurersReminders, questionnaires, messages, education
TelehealthClinics, occupational health, mental health servicesVideo visits, messaging, prescriptions
Billing and revenue cycleProviders, billing companiesClaims, eligibility, invoices, payments
Remote monitoringProviders, device makersDevice readings, alerts; often a medical device
Analytics and qualityHospitals, health systems, payersAggregated clinical and operational data

Each type carries different data, risk and integration work. A scheduling product holds names, contact details and appointment types; an EHR holds the full clinical record. The more clinical the data, the heavier the security, the contracts and the sales cycle.

For the general definition and how SaaS compares with PaaS and IaaS, see what is SaaS.

Design choices that matter most

Tenant separation. Most healthcare SaaS is multi-tenant: one application serving many customers. Every query must be scoped to the tenant, enforced in one place in the code or by row-level security in the database, never by convention. Many products also support a separate database per tenant for large customers who require it, which costs more to run but answers the question every hospital security team asks.

Audit logging. Who viewed or changed which record, when and from where, kept apart from the data, readable by the customer's own staff and retained for the period their rules require. In healthcare, a view is as important to log as a change.

Identity. Staff sign in through the customer's own identity provider with single sign-on, and patients with strong authentication, such as a national e-identity where one exists. Roles follow the customer's organisation, and access to a patient is limited to those involved in their care.

Encryption and keys. Encryption in transit and at rest is the baseline; for sensitive products, keys per tenant held in a managed key service, so one customer's data can be destroyed on exit without touching the others.

Region and residency. Data stays in the region the customer's rules require, with backups and support access following the same rule. A product that sells in both the US and the EU usually runs separate regional deployments.

Interoperability. HL7 FHIR for clinical data exchange, standard formats for documents and identity, and a published interface for customers' own integrations. Each custom interface per customer becomes a maintenance cost for years.

United States: HIPAA and business associates

HIPAA applies to covered entities, such as providers and health plans, and to their business associates. Under 45 CFR 160.103, a business associate is a person who, on behalf of a covered entity, creates, receives, maintains or transmits protected health information, and the definition includes a subcontractor that does the same on behalf of a business associate. (Read on 11 November 2026.) For a healthcare SaaS company, that means a business associate agreement with each customer, and the same agreements with the hosting provider and every other supplier that touches the data.

The Security Rule's technical safeguards in 45 CFR 164.312 include audit controls that record and examine activity in systems containing electronic protected health information, automatic logoff after a period of inactivity, and encryption and decryption of that information. (Read on 11 November 2026.) Those map directly to product features, not only to policies.

European Union: GDPR, NIS2 and the EHDS

GDPR. Health data is a special category of personal data. As a SaaS supplier you are usually the processor for your customers' data, acting on their instructions under a data processing agreement, and the controller for your own account and billing data. A data protection impact assessment, a register of sub-processors and a clear retention model are expected by every European healthcare buyer.

NIS2. Healthcare providers are among the sectors covered by Directive (EU) 2022/2555. Article 21(2) requires covered entities to address supply chain security, including the security of their direct suppliers and service providers. (Read on 11 November 2026.) Even when the SaaS company is not covered itself, its hospital customers will pass those requirements on in contracts and questionnaires.

The European Health Data Space. The European Commission's EHDS page sets out the timeline: by March 2027 the Commission adopts key implementing acts; from March 2029 patient summaries and ePrescriptions are exchanged in all Member States; and from March 2031 medical images, laboratory results and hospital discharge reports follow. (Read on 11 November 2026.) The regulation also creates a single market for electronic health record systems, so products that act as EHR systems should plan for its requirements now.

Germany: cloud rules for health data

Germany has a specific rule for health data in the cloud. Section 393 of the Fifth Book of the Social Code, SGB V § 393, lets healthcare providers, health insurers and their processors use cloud computing for health and social data only in Germany, another EU Member State, an equivalent state or a third country with an adequacy decision, and only if the processing body has an establishment in Germany. It also requires a current C5 attestation for the cloud systems used, based on the C5 criteria catalogue of the German Federal Office for Information Security, and from 1 July 2025 that generally means a C5 Type 2 attestation, with a transition period for systems first put on the market after that date. (Read on 11 November 2026.) For a SaaS company selling to German providers, the choice of hosting provider and the company's own presence in Germany become part of the go-to-market plan.

Medical device or not?

Most healthcare SaaS, such as scheduling, billing, messaging and administration, is not a medical device. Features that diagnose, monitor a condition with alerts, calculate doses or recommend treatment can be, under the EU Medical Device Regulation or FDA oversight, and then the product needs a quality management system, clinical evaluation and technical documentation. Our guide to hospital mobile apps explains how the EU and US rules classify medical software. For how such software is built inside a quality system, see medical device software development.

Build checklist

  • Target markets and the rules each brings: HIPAA, GDPR, national cloud rules.
  • Product type, the data it holds and the medical device question per feature.
  • Tenant model: shared database, database per tenant, or both.
  • Identity: single sign-on for staff, strong authentication for patients, roles.
  • Audit log design, retention and customer access to it.
  • Hosting region, backups, support access and the sub-processor list.
  • Interfaces: FHIR resources, documents, customer integrations.
  • Evidence customers will ask for: security policies, penetration tests, ISO/IEC 27001, SOC 2 or C5.
  • Contracts: data processing agreements, business associate agreements, service levels.
  • Exit: how a customer gets its data back and how it is deleted.

How we help

We build healthcare SaaS products from the first scope to production and maintenance, with EU hosting by default, regional deployments where a product sells abroad, and the code in the client's own repository. For a first version and fundraising-ready code, see startup software development. For the patient-facing video side, see telemedicine app development; for rosters, healthcare scheduling software; and for administrative automation, read RPA in healthcare. When the product is the patient record itself, see EHR software development. Before selling to hospitals, a security audit gives you the evidence their questionnaires ask for.

Questions people ask

What is healthcare SaaS?

Healthcare SaaS is software for healthcare organisations or patients that is delivered as a hosted service on a subscription, rather than installed on the customer's own servers. Examples are practice management, scheduling, patient engagement, telehealth, billing and analytics products.

Is a healthcare SaaS company a HIPAA business associate?

Usually, yes, when it serves US covered entities. A business associate is anyone who creates, receives, maintains or transmits protected health information on behalf of a covered entity, and its subcontractors, such as the hosting provider, are business associates too. Each link in the chain needs a business associate agreement.

Can we host health data from German customers in any EU cloud region?

Not without conditions. German law, section 393 of the Fifth Book of the Social Code, lets healthcare providers and their processors use cloud services for health data only in Germany, the EU or an equivalent or adequate country, with an establishment in Germany, and with a current C5 attestation for the cloud systems used. Check the current requirements with your advisers before selling there.

Single-tenant or multi-tenant for healthcare?

Multi-tenant with strong logical separation suits most products and keeps operations simple. Large hospital customers sometimes require their own database or their own environment. A good design supports both: a shared application with a separate database per tenant where the contract needs it.

Is healthcare SaaS a medical device?

Most of it is not: scheduling, billing, messaging and administration are not medical devices. Software intended to diagnose, monitor or guide treatment can be, under the EU Medical Device Regulation or FDA oversight. Decide per feature before building it.

Sources