TrueNAS for Medical Practices and MVZ: KBV-Compliant Storage Without the Cloud

Patient records, DICOM images, referral letters, lab findings — a medical practice easily generates several terabytes of sensitive data. Those data do not belong in an anonymous cloud, but in a storage system that satisfies the KBV IT security guideline, GDPR Art. 9 and Section 630f of the German Civil Code (BGB) at the same time. TrueNAS is one of the most pragmatic solutions on the market for this: run locally, ZFS-based, with full access logging and encryption at rest — and without the recurring license fees of proprietary healthcare storage. This article covers what matters for a TrueNAS-based practice archive, how to connect the common German practice management systems, and where TrueNAS sensibly ends.

What the KBV Guideline and Section 630f BGB Mean for Storage

The KBV IT security guideline under Section 75b SGB V has been mandatory since 2021. For the practice archive it requires — among other things — a controlled permission model, logged access, a backup concept and, depending on the tier, encryption of data at rest. In parallel, Section 630f BGB regulates the medical documentation duty: patient files must be kept for at least ten years after the treatment ends, and radiology and radiation-related records for up to 30 years.

For storage infrastructure this translates into:

• Verifiable retention for more than a decade, independent of whether the PVS or radiology vendor could do it internally
• Tamper-resistant deletion — neither staff nor an attacker should be able to alter records unnoticed
• Access logging for every file operation, so an audit or supervisory review has evidence
• Encryption at rest — hard drives stolen in a break-in must not contain readable patient data
• Geo-redundant backup for the case where the entire practice is hit by water damage or ransomware

TrueNAS covers all of this with ZFS snapshots, ZFS encryption, SMB auditing and replication. What TrueNAS is not: a PVS replacement, a DICOM archive in the narrow sense, or a TI component. It is the underlying storage layer on which the PVS and imaging systems park their data safely.

TrueNAS in a Medical Practice: Why Local Storage Beats Cloud

Cloud storage has its place, but for practices there are three very concrete reasons why a locally operated TrueNAS is usually the better choice:

Data sovereignty. Patient data are special categories of personal data under GDPR Art. 9. Handing them to a US-based — or even any not explicitly EU-contract-compliant — cloud requires a proper data processing agreement, a data protection impact assessment and a clean contract. The reality of a TI-connected practice rarely allows for that.

Bandwidth and availability. Pulling multi-gigabyte DICOM studies over a 50/10 VDSL line is no fun. A local TrueNAS delivers 1 GbE or 10 GbE inside the practice network even when the internet uplink is down.

Cost. Cloud storage sounds cheap, but with terabyte volumes and ten-year retention it quickly runs into the low hundreds per month. A TrueNAS server usually amortizes in under 24 months and then runs for years.

We covered the broader cloud vs. local topic in TrueNAS vs. Synology and TrueNAS Cloud Sync for Offsite Backup.

MVZ IT Requirements for Practice Storage

A German MVZ (Medizinisches Versorgungszentrum, a multi-specialty care center) differs from a single-doctor practice in significant ways: multiple specialties, often multiple locations, usually centrally hosted PVS and a higher degree of formalization. IT requirements follow suit:

• Central storage across sites, typically over VPN or a dedicated MPLS backbone
• Separation by specialty — radiology, laboratory, surgery and general medicine need different shares and permissions
• Higher capacity, because DICOM studies, endoscopy videos and sonography images add up quickly
• Cleaner role separation between physicians, medical assistants and external IT
• Auditability for internal quality management and external certifications

A single TrueNAS system covers this with datasets, per-specialty shares and Active Directory integration. Details on AD integration are in our article TrueNAS SMB with Active Directory.

PVS Integration: SMB Shares for Medistar, Turbomed and Duria

Practically all German practice management systems — Medistar, Turbomed, Duria, Albis, x.isynet, S3 — support storing documents and findings on an SMB share. TrueNAS ships with a mature SMB server that matches a Windows file server for compatibility and audit capability.

A typical single-practice setup with Medistar or Turbomed:

• Dataset praxis-daten for general practice documents
• Dataset pvs-dokumente as the PVS storage target
• Dataset dicom-import for manually imported imaging studies
• Dataset arztbriefe for referral letters ready to send and archived ones
• Dataset roentgen-archiv separated, because the 30-year retention applies here

Each dataset gets its own SMB share with clearly defined permissions. Assignment happens either via local practice users on TrueNAS or — better — through an Active Directory join if a practice domain controller exists.

The SMB protocol level matters: at least SMB 3.0 with signing enabled and — optionally — SMB encryption. That way traffic between the PVS server and TrueNAS inside the practice network is no longer plaintext.

For a deeper look at SMB configuration, see our post on TrueNAS SMB best practices.

Encryption at Rest and in Transit

Higher KBV tiers require encryption of data at rest. TrueNAS implements this with ZFS Native Encryption per dataset:

• On dataset creation a passphrase- or key-based key is defined
• All files are encrypted before being written
• Snapshots and replication targets stay encrypted — without the key, the recipient only sees ciphertext
• On reboot the key must be supplied so the datasets can be unlocked

For the practice this means: if the server is stolen from the server room, the patient data are worthless to the thief. Important — and we have to say this honestly — the key must be stored safely. A lost key means lost access to the data, as with every serious crypto system.

Transport encryption is handled by SMB 3 (inside the LAN) and WireGuard or OpenVPN (for site-to-site links). Details on VPN site coupling are in OPNsense WireGuard VPN setup.

Access Logging and Audit Trail for the Practice

The KBV guideline and GDPR require traceable access. TrueNAS offers two layers:

SMB audit log — configurable per share. It logs file access, create, delete, rename and permission changes. Logs can be forwarded to an external log server (Graylog, Wazuh or DATAZONE Control) — which is also the recommendation, so logs do not sit on the same host that might be compromised.

ZFS snapshots as evidence — a snapshot is immutable unless explicitly destroyed. If a file existed on March 15 and was changed on March 20, snapshots make that traceable. For a practice audit this is a valuable tool.

For a typical practice we recommend hourly snapshots for 24 hours, daily snapshots for 30 days and monthly snapshots for at least a year. Details in Benefits of TrueNAS Snapshots.

Snapshots, Replication and the 10-Year Retention

Section 630f BGB requires ten years of retention, the radiation ordinance up to 30 years. That is not a job for an SD card or a USB stick. For a TrueNAS-based practice archive we usually build a three-tier concept:

1. Primary storage on TrueNAS with ZFS and snapshots
2. Secondary TrueNAS in a separate room or site, attached via ZFS replication
3. Offsite copy either in a second MVZ location or encrypted in a German data center

That covers the 3-2-1 rule: at least three copies, on two different media, one of them offsite. We covered this more broadly in 3-2-1 Backup Rule and ZFS Backup Strategies.

For the oldest data — for example treatment years older than ten — an archive dataset can be mounted read-only and be pulled to external cold storage once per year.

Backup Strategy for an MVZ Environment

An MVZ with several sites has the advantage that a second site can act as a backup target. A typical setup:

• Site Munich: TrueNAS main system, active practice storage
• Site Nuremberg: TrueNAS secondary, receiving replication snapshots
• Link: site-to-site WireGuard over business internet, at least 100/40 Mbit
• Replication: hourly for hot data, daily for archives
• Additionally: encrypted cloud backup for the last seven days in a German data center

That covers both the KBV requirement for geo-redundant backup and the multi-site reality typical of an MVZ.

Hardware Sizing for Medical Practices and MVZ

We deliberately do not throw fixed prices around here — hardware pricing shifts quarter to quarter, and we don’t want to convey false certainty. Configuration and pricing ranges we create individually via the TrueNAS configurator or during a consulting call.

As a rough scale:

• Small single-doctor practice — 2 to 4 doctors, ~2 TB PVS data, no imaging: compact TrueNAS entry class, hybrid or SSD
• Mid-size practice with imaging — 5 to 10 doctors, 10 to 30 TB payload, DICOM studies: mid-size rackmount TrueNAS with ZFS mirror and metadata VDEV on SSD
• MVZ with multiple sites — 20+ doctors, several specialties, 50 TB+: TrueNAS Enterprise with high availability and a separated backup instance

Concrete models and the right TrueNAS series can be found on our TrueNAS product pages. One side note: the earlier TrueNAS M50 and M60 are end-of-life — for new projects we currently recommend the M30, M40 or the R series, depending on requirements.

Limits and Important Notes

To avoid false expectations — what TrueNAS is not:

• Not a TI connector replacement. The German telematics infrastructure runs through a gematik-certified connector. TrueNAS is internal practice storage.
• Not a PVS. Medistar, Turbomed, Duria and the rest stay as standalone systems — TrueNAS is their storage target.
• Not a PACS in the narrow sense. True radiology imaging workflows need PACS software. TrueNAS can be the storage backend behind a PACS — the PACS itself is a different thing.
• Not a replacement for a data protection impact assessment. Technology helps, but the documentation duty stays with the practice owner.

For the networking side — firewall, VLAN separation, KBV-compliant network layout — read our post OPNsense for the Medical Practice. Network and storage are two sides of the same KBV coin.

How DATAZONE Contributes

We plan, deliver and operate TrueNAS systems in medical practices and MVZ — including the PVS integration, the KBV process documentation and ongoing monitoring through our DATAZONE Control platform. Pricing frames and matching configuration we prepare individually — the best starting point is a conversation about the concrete practice situation.

FAQ

Is a TrueNAS GDPR-compliant in a practice?

A TrueNAS can be operated in a GDPR-compliant way — technology alone is not enough, though. Encryption, access logging, permission management and backup are prerequisites. In addition, a process documentation, a deletion concept and a data protection impact assessment for the processing of health data under GDPR Art. 9 are required.

Does TrueNAS replace the TI connector?

No. The TI connector is a gematik-certified component for connecting to the German telematics infrastructure. TrueNAS is internal practice storage and has nothing to do with TI certification. The two systems complement each other but do not replace each other.

Which practice management systems can connect over SMB?

Practically every common German PVS — Medistar, Turbomed, Duria, Albis, x.isynet, MediStar and others. They typically expect a UNC path to a Windows-compatible SMB share. The TrueNAS SMB server delivers this with SMB 3.0 and optional encryption.

How long must patient data be retained?

Section 630f BGB requires at least ten years after the end of treatment. The radiation ordinance, the radiation protection act and individual professional rules require up to 30 years. In practice we plan for 15 years and set up a separate long-term dataset for radiation-related records.

What does a TrueNAS for a medical practice cost?

We deliberately do not quote fixed prices — hardware component prices move too much. We prepare an individual price frame for every practice via our TrueNAS configurator or directly in a consulting call. The frame depends strongly on capacity, redundancy and whether high availability is required.

Can TrueNAS connect multiple practice sites?

Yes. ZFS replication allows datasets to be synchronized between multiple TrueNAS systems, synchronously or asynchronously — ideal for an MVZ with several sites. The site-to-site link is usually implemented via WireGuard or OpenVPN on an OPNsense firewall.

---

Are you planning a KBV-compliant practice archive or consolidating an existing MVZ storage? We advise from concept to daily operations — get in touch.