Selling to a German hospital or practice as a small foreign SaaS: the data processing agreement, the domestic-branch rule and what the IT team asks first
Section 393 SGB V limits health data processing to the EU or adequacy countries and asks for a domestic German branch. Why Standard Contractual Clauses cannot save third-country remote support, the mandatory section 203 StGB criminal secrecy clauses in your AVV, branch setup costs, and the eight questions German clinic IT teams ask first.

Your software demo with the German hospital clinic director or medical practice head went great. They want to roll your SaaS out to thirty clinicians next quarter. But before anyone touches an invoice, an email arrives from the hospital's Datenschutzbeauftragter (DSB, the data protection officer) and the IT security department with an attached Auftragsverarbeitungsvertrag (AVV) and a detailed compliance questionnaire citing section 393 of the fifth Social Code (SGB V). If you are a foreign software company, this is where the commercial conversation collides with German healthcare law.
Germany's Digital-Gesetz (DigiG) updated section 393 SGB V to clarify how hospitals, medical centers (MVZ), and doctors can use cloud computing. Our earlier piece walked through the BSI C5 audit catalogue required under paragraph 3. But most foreign software vendors lose the deal long before an audit report is signed: they get tripped up on paragraph 2's location and domestic-branch rules, remote technical support from outside the EU, the criminal secrecy commitments under section 203 StGB, and the initial security checklist. Here is what the law requires, how the IT team reads your architecture, and what you need in your legal and technical pack.
The short version
- Section 393 paragraph 2 SGB V is strict on geography: Cloud processing of patient data is permitted only within Germany, the EU/EEA, or third countries with an official European Commission adequacy decision under Article 45 GDPR (such as Switzerland, the UK, or US companies certified under the EU-US Data Privacy Framework).
- Standard Contractual Clauses (SCCs) do not work: Under standard GDPR, companies routinely transfer data to the US or India using Article 46 SCCs. Section 393 SGB V does not recognize SCCs or Binding Corporate Rules for statutory healthcare data. If a third country lacks an adequacy decision, processing there is illegal under German social law.
- Remote support (Fernwartung) is processing: If your engineers in India, the US (without DPF certification), or Southeast Asia log in to troubleshoot a database or view unencrypted error logs with patient names, that counts as illegal third-country processing. Support access must be confined to the EU or adequacy territories, or completely blocked from seeing plaintext patient data.
- The domestic-branch rule (Inländische Niederlassung): Paragraph 2 says the data-processing entity must have a domestic branch in Germany. Hospital legal teams interpret this as requiring the cloud vendor to have a registered presence (Handelsregister branch or German subsidiary) or to contract via an authorized German distributor.
- Criminal secrecy under section 203 StGB: Doctors face criminal penalties (up to one year in prison) for leaking patient secrets. Your AVV must include a formal, written undertaking binding all your employees who could touch data to section 203 StGB.
- The IT security questionnaire: German hospital IT and security officers ask eight specific questions about hosting tier, database residency, support bastions, encryption keys, sub-processors, and breach reporting. Knowing the right answers upfront prevents months of deadlocked procurement.
Where patient data can live: section 393 paragraph 2 and the no-SCC rule
Section 393 paragraph 2 of the Social Code Book V defines the legal boundary for cloud services. The exact text sets out three allowed territories: Germany (Inland), an EU member state, or a country with an adequacy decision under Article 45 GDPR. The table below shows what this means in practice across typical hosting and SaaS setups.
| Location / Transfer Mechanism | Status under § 393 Abs. 2 SGB V | What the Hospital Legal Team Checks |
|---|---|---|
| Germany (Frankfurt, Falkenstein, Nuremberg) | Fully Compliant | Primary choice. Preferred by 100% of municipal and church hospital groups. |
| Other EU / EEA State (Ireland, France, Netherlands) | Legally Permitted | Permitted by statute. Some public clinics still request proof that no backup leaves the EU. |
| Adequacy Country (UK, Switzerland, Japan, Canada commercial) | Permitted with DPO Review | Legally valid under Art. 45 GDPR. Hospital DSBs require exact citation of the adequacy decision. |
| US with EU-US Data Privacy Framework (DPF) | Permitted with Caveats | Vendor must be active on the US Department of Commerce DPF list. Clinic DSBs often push for EU-only storage regardless. |
| Standard Contractual Clauses (SCCs / Art. 46 GDPR) | Strictly Invalid | Immediate deal killer. Section 393 SGB V omits Art. 46 transfers entirely. SCCs cannot legalize patient data hosting. |
| Third country without adequacy (India, Philippines, Brazil) | Prohibited | Storage, replication, or unencrypted transit through these countries violates German social secrecy law. |
For a standard B2B SaaS company selling into manufacturing or retail, signing the standard EU Standard Contractual Clauses (SCCs) and conducting a Transfer Impact Assessment (TIA) is standard practice. In German healthcare, SCCs are useless. If your database sits in an AWS US region, or if your backup snapshots sync to an S3 bucket in Virginia without an active DPF certification, the hospital's legal counsel cannot approve the contract.
The domestic-branch rule: who must have an office in Germany?
Section 393 paragraph 2 concludes with the clause: "...sofern die datenverarbeitende Stelle über eine Niederlassung im Inland verfügt" (provided that the data-processing entity has a domestic branch). This requirement causes massive friction for foreign software companies. German legal scholars debate whether "datenverarbeitende Stelle" refers solely to the hospital (the controller) or extends to the cloud service provider and its sub-processors.
In practice, German hospital data protection officers and public tender committees adopt the strict interpretation: the entity signing the contract and processing patient data must have a legally recognized establishment in Germany. Their reasoning is jurisdictional: German regulatory authorities (the Landesdatenschutzbeauftragten and social insurers) must be able to enforce sanctions locally without cross-border legal treaties.
If you are a US, UK, or EU-based SaaS vendor with no German presence, you have four practical ways forward. The table below details the real costs, timelines, and procurement acceptance for each.
| Structure | Estimated Cost (EUR) | Time to Setup | Hospital Acceptance |
|---|---|---|---|
| 1. Registered Branch (Zweigniederlassung) | EUR 1,200 - 3,000 (notary + commercial register + translation) | 4 to 8 weeks | High. Meets the literal Handelsregister branch requirement. |
| 2. German Subsidiary (GmbH or UG) | EUR 2,500 - 4,500 legal/notary + EUR 25,000 share capital (EUR 12,500 paid in for GmbH) | 3 to 6 weeks | Gold standard. Eliminates all branch objections from hospital boards. |
| 3. German Reseller / Distribution Partner | 15% to 30% margin on software contract | 2 to 4 weeks | High. The local partner signs the AVV as prime contractor with the clinic. |
| 4. EU Freedom of Services Legal Defense | EUR 0 (or EUR 2,000 legal opinion memo) | Immediate | Low to medium. Works occasionally for French or Dutch SaaS, but many public clinics refuse to take the legal risk. |
For a small software vendor closing its first German clinic contract worth EUR 15,000 per year, incorporating a GmbH is rarely justified on day one. Partnering with an established German healthcare IT system integrator (Systemhaus) or registering a formal branch (Zweigniederlassung) in Frankfurt or Munich is the typical path.
Remote support from third countries: where deals die
Many foreign SaaS vendors host their production systems on AWS Frankfurt or Hetzner Falkenstein, believe they are 100% compliant, and then fail the technical review on remote maintenance (Fernwartung). Under German data protection law, accessing a system from abroad to view, inspect, or troubleshoot data is legally treated as an export and processing of that data.
If a customer submits a support ticket, and an on-call engineer in Mumbai, Manila, or California logs into the production database or opens an application log that displays patient names, clinical notes, or insurance identifiers, an illegal international data transfer has occurred under section 393 SGB V.
To satisfy a German hospital IT department, your technical support architecture must fall into one of the compliant tiers shown below.
| Support Architecture | Technical Implementation | Compliance Status |
|---|---|---|
| Global Follow-the-Sun Support | Engineers worldwide access production environments via VPN/bastion to triage tickets. | Non-compliant. Banned if staff sit in non-adequacy third countries. |
| Dedicated EU Support Ring | Only engineers physically located in the EU/EEA or adequacy countries hold production access credentials. | Fully Compliant. Standard model used by enterprise health SaaS. |
| Supervised Bastion Session (Four-Eyes Principle) | Third-country engineers can only connect via a monitored screen-share session explicitly authorized by the hospital IT team. | Acceptable with conditions. Requires customer consent per session and full audit logging. |
| Zero-Knowledge / End-to-End Encryption | Patient data is encrypted client-side in the browser; the SaaS vendor holds zero decryption keys. | Gold standard. Support staff cannot see plaintext patient records even with raw DB access. |
If you do not have staff in the EU, the practical engineering fix is data pseudonymization and scrubbing in logs. Strip all patient health identifiers (names, dates of birth, social security numbers) at the ingestion boundary before logs touch tools like Datadog, Sentry, or CloudWatch. If your third-country engineers only see synthetic IDs and stack traces, the compliance barrier is dramatically lower.
The German health AVV: what section 203 StGB requires
An Auftragsverarbeitungsvertrag (AVV) is Germany's implementation of the GDPR Article 28 Data Processing Agreement. But while a standard commercial AVV is 6 to 10 pages, a German healthcare AVV contains specific clauses anchored in social data protection (section 80 SGB X) and the German Criminal Code (section 203 StGB).
Section 203 of the Strafgesetzbuch (StGB) criminalizes the unauthorized disclosure of private secrets by medical professionals, pharmacists, and health insurers. In 2017 and 2024, the law was modernized to permit healthcare providers to engage external IT service providers ("mitwirkende Personen") without committing a crime—provided that those external providers are contractually bound to the same criminal secrecy obligations.
Here are the five mandatory clauses you will encounter in every hospital AVV:
- 1. Written section 203 StGB Secrecy Undertaking (Verpflichtungserklärung): Every employee, subcontractor, or contractor at your company who could theoretically access patient data must sign a formal declaration acknowledging that disclosing medical secrets carries a prison sentence of up to one year or a criminal fine.
- 2. Strict Sub-processor Pre-approval: Standard SaaS terms usually say: "We may add sub-processors and will notify you 30 days in advance via our website." German hospitals reject this outright. The AVV requires prior written authorization or an explicit veto window of at least 14 to 30 days before any new hosting, database, or analytics sub-processor touches data.
- 3. Pass-through of Section 393 and C5 Obligations: Any sub-processor in your chain that stores or processes health data must be bound by the same geographic restrictions and security standards (including C5 attestation compliance) that bind you.
- 4. Strict Incident Notification Deadlines: While GDPR Article 33 gives controllers 72 hours to notify regulators, hospital AVVs typically require you to report security incidents, suspected data leaks, or unauthorized access within 24 hours (and sometimes "unverzüglich", without undue delay).
- 5. Complete Deletion and Return Protocols: Upon contract termination, the vendor must provide written certification that all primary data, replica sets, disaster recovery snapshots, and cache layers have been cryptographically erased within a specified window (typically 30 days).
What the clinic IT team and DSB ask first: the 8 security questions
Before the hospital legal team signs the AVV, the IT security department (IT-Sicherheit) and the Data Protection Officer (DSB) will send their supplier assessment questionnaire. Below are the eight questions you will be asked, why they ask them, the compliant answer, and the instant rejection answer.
| Question (German & English) | What They Are Testing For | Compliant Answer | Deal-Breaker Answer |
|---|---|---|---|
| 1. Wo befindet sich das primäre Rechenzentrum und das Backup-RZ? Where are primary and backup data centers? | Compliance with § 393 Abs. 2 SGB V geographic constraints. | Both primary and secondary sites are in Germany (e.g., AWS eu-central-1 Frankfurt or Hetzner Falkenstein). | Primary is in Frankfurt, but automated disaster recovery backups sync to US-East (Virginia). |
| 2. Verfügt Ihr Unternehmen über eine inländische Niederlassung? Does your company have a domestic branch? | Direct legal enforceability under German jurisdiction. | Yes, registered branch (Zweigniederlassung) in Frankfurt HRB 12345 or contract via German distribution partner. | No, we are a Delaware LLC / UK Ltd with no European presence or registered entity. |
| 3. Haben Support-Mitarbeiter im Drittland Zugriff auf Produktivdaten? Do third-country support staff have access to live data? | Cross-border data transfer violations under social secrecy rules. | Support is strictly restricted to EU-based staff, or patient data is client-side encrypted / scrubbed from all logs. | We use global follow-the-sun support where engineers in India or the US log directly into the prod DB. |
| 4. Liegt ein BSI C5-Testat (Typ 1 oder Typ 2) vor? Do you have a BSI C5 attestation? | Fulfillment of § 393 Abs. 3 SGB V cloud security standards. | Current C5 Type 2 report (or C5 Type 1 for systems launched under 18 months ago, plus audit roadmap). | We have SOC 2 Type 2 or ISO 27001 only, and have never reviewed the BSI C5 criteria catalogue. |
| 5. Werden Mitarbeiter auf § 203 StGB verpflichtet? Are staff bound to section 203 StGB criminal secrecy? | Preventing criminal liability for the hospital's treating physicians. | Yes, 100% of employees with access sign a formal § 203 StGB criminal penalty undertaking. | Our standard US/UK employee NDA covers confidentiality; we do not sign foreign criminal code forms. |
| 6. Wie erfolgt die Verschlüsselung ruhender und übertragener Daten? How is encryption handled in transit and at rest? | Technical and Organizational Measures (TOMs) under § 391 SGB V. | TLS 1.3 in transit with PFS; AES-256 at rest with customer-managed or dedicated KMS keys. | TLS 1.1/1.2 supported for legacy clients; data encrypted at rest with shared multi-tenant keys. |
| 7. Wie wird der administrative Zugriff auf Systeme gesichert? How is administrative access secured? | Privileged access management and audit trail integrity. | Hardware MFA (FIDO2/WebAuthn), dedicated bastion with session recording, zero direct root logins. | Shared admin credentials or SMS-based MFA without centralized immutable audit logging. |
| 8. Welche Unterauftragnehmer werden eingesetzt? Which sub-processors are in your service chain? | Control over the entire data supply chain (IaaS, PaaS, monitoring, email). | Exhaustive list provided with hosting locations; all sub-processors located in Germany or the EU. | Unspecified third-party analytics and error tracking tools (e.g., Mixpanel, Google Analytics, US Sentry). |
Five steps to prepare your German hospital sales kit
If you are a small foreign software vendor planning to sell into the German healthcare sector, do not wait until procurement begins to organize your compliance paperwork. A typical hospital buying cycle takes four to nine months; discovering in month five that your error logging architecture disqualifies you from signing the AVV burns months of pipeline.
Here is the followable preparation checklist:
- 1. Spin up an isolated German / EU cloud cell: Provision a dedicated environment in Frankfurt (e.g. AWS eu-central-1, Azure Germany West Central, or Hetzner). Ensure that databases, object storage, and backup retention policies remain 100% within the European Union.
- 2. Audit your sub-processor list for US analytics: Remove client-side trackers, US-hosted session replays, and unvetted crash reporters from any page where authenticated clinic users log in. Every external script loaded on that page is scrutinized by the hospital DSB.
- 3. Implement a section 203 StGB employee signing routine: Draft a standard German/English Verpflichtungserklärung gemäß § 203 StGB. Have all your developers, DevOps engineers, and support personnel sign it as part of their employment file.
- 4. Establish your domestic corporate presence: If you have immediate pipeline, register a branch office (Zweigniederlassung) in a German commercial register or sign an agreement with a German medical software distribution partner who can act as prime contractor.
- 5. Build your security pack: Prepare a ready-to-send PDF bundle containing: your Technical and Organizational Measures (TOM-Katalog), your section 393 compliance statement, your C5 attestation or implementation roadmap, your complete sub-processor list with data centers, and your pre-signed AVV.