Anyone running a medical practice or MVZ in Germany does not just process ordinary personal data — they process special categories of personal data under GDPR Art. 9. For a regular customer database a solid TOM concept is enough. For health data, genetic data, biometric identification data and data about a person’s sex life there is a fundamental prohibition on processing — lifted only by narrow exceptions, in particular the exercise of a profession by a healthcare provider (Art. 9 para 2 lit. h GDPR).
What does that mean for the storage infrastructure underneath? It has to prove it meets the elevated protection requirements. This article covers the concrete technical and organizational measures GDPR Art. 9 requires in a medical practice, how TrueNAS meets them in day-to-day operation, and where TrueNAS alone does not cut it. As an authorized iXsystems partner we build these setups regularly in southern Germany — so this is written from what works, not from a white paper.
GDPR Art. 9 in a Medical Practice: Which Data Is Affected
In practice many data types fall under Art. 9, not only the classic patient record in the practice management system (PVS):
- DICOM studies from X-ray, CT, ultrasound, endoscopy videos
- Lab findings as PDFs, HL7 messages, fax imports
- Referral letters and reports in the practice inbox
- E-prescription and electronic sick-leave data, even when they run over the TI
- Vaccination and preventive-care documents, often scanned
- Appointment calendars with pre-visit diagnosis hints — yes, the calendar too
- Staff health data when practice MFAs are themselves patients
All of this eventually lands on a network share — via the PVS, scanners or document management systems. We covered the fundamentals of the practice archive itself in TrueNAS for Medical Practices and MVZ — this article focuses on the GDPR duties specifically.
Health Data on TrueNAS: Encryption at Rest and in Transit
Art. 32 GDPR calls for encryption or pseudonymization of special categories as part of adequate protection measures. In practice that means two directions: data must be encrypted on disk (at rest) and on the way between server and client (in transit).
At rest: ZFS dataset encryption. TrueNAS uses native ZFS encryption with AES-256-GCM at dataset level. One encrypted dataset per department — general practice, radiology, lab — each with its own key. If a disk goes in for repair, the data stays unreadable. One rule: the key must not sit on the same system in plain text. We use either passphrase-protected datasets with manual unlock after reboot, or separate key management on a hardware token. More in TrueNAS Dataset Encryption with ZFS Encryption and on key handling in Backup Encryption and Key Management Done Right.
In transit: SMB with AES encryption. TrueNAS SCALE and 25.10 Goldeye support SMB3 with enforced encryption, but it has to be switched on — the default still allows unencrypted connections. We set smb encrypt = required per share and verify with Wireshark against the practice PC.
TrueNAS 27 GA is scheduled for early December 2026 and brings further improvements to key rotation. For live practices we currently still recommend the stable 25.10 Goldeye — GA plus two patch cycles is the better base for regulated environments.
Logging: the Underrated Half of Art. 9
Encryption alone is not enough. Art. 32 GDPR also requires the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing. Translated: you have to be able to show who accessed which file when. In a data protection incident, those are the first questions from the state data protection authority.
TrueNAS provides two mechanisms for this:
- SMB auditing: enabled per share, logs read, write, rename and delete operations including user name, timestamp and file
- ZFS event daemon (zed): logs all pool and dataset events, from snapshot creation to scrub result
Audit logs have to leave the system — onto a separate logging target, otherwise an attacker can manipulate them. We typically forward them via syslog to a central log server or, for larger MVZs, to a Graylog or Wazuh stack. Foundations on GDPR logging are in GDPR Logging Obligations 2026.
What Belongs in the Log, and What Does Not
Too much logging is itself a data protection problem: logging every read of a medical assistant on every file is employee surveillance. Too little logging and you have nothing in your hand. Our standard for practices:
- Read and write accesses on highly sensitive datasets (psychotherapy, HIV, addiction medicine) fully
- Write, rename and delete operations on standard patient data
- No content-level logs
- Log retention at most 90 days, aggregated statistics after that
Backup Strategy for Health Data under Art. 9
Backup is mandatory under GDPR Art. 32 — but for health data with a twist: the backup inherits the protection level of the original. An unencrypted backup of an encrypted practice archive is a compliance violation, not a pragmatic shortcut.
Our standard setup for a practice or a smaller MVZ:
- Primary TrueNAS with encrypted datasets in the practice rack
- Replication target TrueNAS at a second site or secured basement, encrypted ZFS replication
- Snapshot schedule: hourly for 48 hours, daily for 30 days, monthly for 10 years (patient records!)
- Immutable backup: daily backup to a TrueNAS target system with dataset snapshots under a locked snapshot hold
The 10-year monthly branch sounds like a lot, but with ZFS snapshots only changed blocks consume space. For the 30-year radiology duty we add a separate cold-storage line, ideally with tape-out through Proxmox Backup Server. The pattern for replication to an encrypted target without exposing the key is in TrueNAS Replication with ZFS Encryption Key.
Retention under Section 630f BGB: 10 Years and Then Really Gone
Section 630f BGB requires patient records to be kept for at least ten years after treatment. The part that gets forgotten: after that period they must be deleted, unless other retention duties apply. Art. 17 GDPR additionally gives the data subject a right to erasure.
For the TrueNAS archive this means:
- Granular datasets per year or per patient so that deletion is technically possible — one 500 TB monster share is dead for deletion
- Documented retention concept as part of the TOM
- Snapshot awareness: a deleted record keeps living in snapshots until the lifecycle ends
- Cryptographic erasure: a dataset is effectively deleted by destroying the key
For practices with a mixed patient base, a mix works best: monthly or quarterly datasets backed by a clean year-end deletion routine.
Hardware Sizing: Which TrueNAS Models Fit Practices
For a single-doctor practice or a small group practice, a TrueNAS Mini R or an M30 is usually enough — depending on data volume. For an MVZ with several sites and a radiology connection, the M40 is the sweet spot between capacity, performance and price. The older M50 and M60 are now EOL and no longer shipping new. If you want to build a fitting configuration, our TrueNAS Configurator walks you through the relevant options — with price ranges on request, because hardware prices for specialty components (NVMe, SAS, 10/25 GbE) move around. For maintenance and support on existing systems, see TrueNAS Support.
What TrueNAS Alone Does Not Cover
A TrueNAS archive is the foundation, not the full Art. 9 proof. What you also need:
- TOM documentation with concrete references to the TrueNAS settings
- Data protection impact assessment (DPIA) for special categories
- Record of processing activities per Art. 30 GDPR
- Confidentiality obligations for all authorized users
- Incident response plan with notification paths to the state DPA
As an IT provider for medical practices we help practices tie TrueNAS and GDPR documentation together. The tech side is the smaller part — clean documentation and recurring review are the real work. In return, if the state DPA shows up, you have evidence in your hand.
FAQ
Is encrypting only the PVS backup enough?
No. Art. 32 GDPR requires protection for the whole processing. If the live archive sits on an unencrypted SMB share and only the backup is encrypted, you still have an incident after a break-in. Encryption at rest has to apply across the whole data path — primary, replication and offsite.
Is two-factor authentication for the TrueNAS admin mandatory?
Not explicitly required by Art. 9, but in practice not negotiable anymore. Every admin access on a health-data system should have MFA — ideally a hardware token. TrueNAS SCALE and 25.10 Goldeye support TOTP and FIDO2 natively. Practice roles (MFA, doctors) authenticate via the practice AD, same recommendation.
How often should restore tests be performed?
At least once per quarter, documented with date, person responsible and the dataset restored. That is less a GDPR duty and more one from the KBV guideline and Section 630f BGB. Practically: restore one patient dataset from an old snapshot and compare it against live state.
Can I put health data in a cloud like AWS or Azure?
Not without further measures. Special categories need, on top of the standard DPA, a clean legal basis, a DPIA, standard contractual clauses for non-EU hosters and often a Schrems II assessment. For most practices and MVZs this is not economically workable. Local operation on TrueNAS with controlled offsite backup is the legally cleaner and usually cheaper option.
What happens in a health data incident?
If an incident poses a risk to data subject rights, you have 72 hours to inform the supervisory authority (Art. 33 GDPR). For high risk you also inform patients directly (Art. 34 GDPR). For a practice this needs a clear process — who is informed, which logs are reviewed, how the notification is worded. TrueNAS audit logs are key here, which is why their external storage matters.
How much does a GDPR Art. 9 compliant TrueNAS setup cost?
Depending on size, data volume and redundancy, a practice solution lands in the mid to upper four-digit range for hardware, plus setup and maintenance. We put together price ranges on request because components (NVMe, SAS, networking, second site) vary. More important than the absolute number is usually the comparison with the yearly cost of a cloud solution over 10 years — TrueNAS almost always comes out notably cheaper, with a better GDPR position.
More on these topics:
More articles
TrueNAS for Architecture Firms: CAD, Rendering and Project Storage Without SMB Stuttering
Practical guide to CAD storage for architecture firms: TrueNAS with SMB Multichannel, 10 GbE, snapshots per milestone. Autodesk-ready, honestly sized.
Measuring TrueNAS Performance with fio and iozone: Methodology, Pitfalls and How to Get Honest Numbers
Measuring TrueNAS performance in practice: how to set up fio and iozone sensibly, why the ARC cache distorts almost every result, and what benchmarks really tell you and what they do not.
TrueNAS with Let's Encrypt: Automating SSL Certificates for UI, WebShare, and Apps
TrueNAS Let's Encrypt in practice: ACME setup in 25.10 Goldeye, DNS-01 for wildcards, assignment to UI, WebShare and Apps, auto-renewal without downtime.