This page provides professional guidance and does not replace legal advice. Always agree your data protection concept, the data protection impact assessment and the contracts with your data protection officer.
Health data is generated everywhere today: in the HIS, on therapy and diagnostic devices, in questionnaires, in apps and via wearables. Anyone who brings it together and analyses it takes on responsibility for the most sensitive data there is. This guide shows which requirements the GDPR places on the processing of health data, how to implement them technically and how to demonstrate them.
Which legal basis fits which use is covered in the guide Using wearables in compliance with the GDPR. What additionally applies to AI applications is set out in the guide AI and health data. This guide is about the technical and organisational measures.
Health data under Art. 9 GDPR
Under Art. 4(15) GDPR, health data is any personal data that provides information about the physical or mental health status of a person. That means more than diagnoses. Readings such as heart rate, strength values or a gait analysis are also included as soon as they can be attributed to a person.
As a special category under Art. 9 GDPR, its processing is prohibited in principle unless an exception applies, such as treatment, explicit consent or research with safeguards. Two obligations follow from this, and they are the subject of this guide:
- Protect: Art. 32 GDPR requires technical and organisational measures appropriate to the risk. With health data, the risk is high.
- Demonstrate: under Art. 5(2) GDPR, you must be able to prove compliance. This is the accountability principle.
Data compliance: what you need to demonstrate
Data compliance means that processing demonstrably complies with the rules. With health data, data protection officers, ethics committees, payers and supervisory authorities typically ask for this evidence:
| Evidence | Basis | What you provide |
|---|---|---|
| Legal basis and purpose | Art. 6, Art. 9, Art. 30 GDPR | Record of processing activities |
| Consent | Art. 7 GDPR | Documented consent with time, scope and withdrawal |
| Permissions | Art. 25, Art. 32 GDPR | Roles and permissions concept |
| Access | Art. 5(2), Art. 32 GDPR | Log of access and changes |
| Data processing | Art. 28 GDPR | Contracts with all service providers |
| Technical and organisational measures | Art. 32 GDPR | The operator’s documentation of technical and organisational measures (TOMs) |
| Risk assessment | Art. 35 GDPR | Data protection impact assessment |
| Deletion | Art. 5(1)(e), Art. 17 GDPR | Deletion concept with periods |
Software cannot replace much of this evidence, but it can make it considerably easier to provide: by documenting consent, permissions and access itself, rather than having them maintained in spreadsheets and folders.
Roles and permissions concept
The permissions concept defines who may see and edit which data. The underlying principle is need to know: each person sees only what they need for their task. In practice, two levels have proven effective:
- What may someone do? Roles determine the functions, such as recording measurements, approving reports or managing users.
- Which data does someone see? Attributes such as department, ward, study or confidentiality level determine which people and findings are visible.
It is important that the same rules also apply to interfaces. A permissions concept that takes effect in the user interface but not for exports or an API has a gap.
In the Datico® Life Hub, Roles & Rights implement exactly these two levels: function-based roles, in which each function is individually enabled or blocked, and attribute-based rights that determine which people and data are visible. This means, for example, that findings marked as highly confidential remain reserved for doctors. The same rules apply to access via the Smart API, the BI Connector and the MCP Server.
Audit Trail: demonstrating every access
An Audit Trail records who accessed, changed or deleted which data and when. It answers the questions that come first after an incident or a request for access: who saw this finding? Who changed this value, and what was there before?
For an Audit Trail to serve as evidence, it should be:
- complete: logins, read and write access, changes with before and after states, deletions, consent and changes to rights,
- immutable: not even administrators can change or delete entries,
- precise: with an unambiguous timestamp,
- analysable: exportable with filters for audits and requests for access.
The Audit Trail of the Datico® Life Hub meets these points: entries are immutable, even for administrators, accurate to the second in UTC and can be exported with filters as Excel or PDF. In addition, it stores the context of the measurement for every reading, such as the device, software version and last calibration. This helps not only with data protection but also with quality assurance.
Hosting: cloud, Germany or on-premises
Where health data is stored determines several checkpoints at once: third-country transfers, data processing on your behalf and, for professionals bound by confidentiality, professional secrecy.
| Cloud with a third-country link | Cloud in Germany | On-premises | |
|---|---|---|---|
| Third-country transfer | Review under Art. 44 et seq. GDPR required | Not applicable if there is no access from third countries | Not applicable |
| Data processing agreement | Yes, including sub-processors | Yes | Only for maintenance and support |
| Operation and updates | With the provider | With the provider | In your IT |
| Typical use | Rarely for health data | Clinics, rehabilitation, practices, research | Very high requirements, own data centres |
The GDPR does not prescribe a hosting location. Hosting in Germany with no third-country link does, however, avoid the time-consuming review of transfers and makes it easier to agree matters with data protection officers. For doctors, therapists and other professionals bound by confidentiality, Section 203 of the German Criminal Code (StGB) also governs the conditions under which external service providers may be given access to patient data.
The Datico® Life Hub runs in a separate database for each customer on servers in Germany, with no transfer to third countries. The software is developed in Germany. Where requirements are higher, you operate it in your own infrastructure. All connections use encrypted transmission with TLS 1.2 or higher.
Data processing under Art. 28 GDPR
Every service provider that stores or processes health data on your behalf needs a data processing agreement. Among other things, it governs the subject matter and duration, the type of data, the right to issue instructions, technical and organisational measures, sub-processors and the return or deletion of data at the end.
Pay particular attention to the list of sub-processors: hosting, support and email delivery are often separate service providers, and each of them must also meet the requirements. Datico® concludes such an agreement with every customer and provides its technical and organisational measures on request.
Pseudonymisation and data minimisation
Art. 25 GDPR requires data protection by design: systems should, by themselves, process only the data that is necessary. Two means are particularly helpful:
- Data minimisation: record and pass on only the values needed for the purpose. For reports, scores or group values are often enough instead of all individual values.
- Pseudonymisation: name and identity are replaced by an identifier, and the key is held separately. Pseudonymised data remains personal data, but the risk falls considerably. Art. 32 explicitly names it as an appropriate measure.
In the Datico® Life Hub, study data can be kept in pseudonymised form according to the study protocol.
Deletion and retention
Health data may only be stored for as long as the purpose requires or a retention obligation applies. The two can conflict: consent is withdrawn, but the treatment records must be retained. For medical records in Germany, a period of ten years after the end of treatment generally applies (Section 630f(3) of the German Civil Code (BGB)), while studies have their own periods.
A deletion concept therefore defines, for each type of data, when it is deleted, who deletes it and how the deletion is documented. In the Datico® Life Hub, deletions are logged in the Audit Trail, and data can be exported in open formats at any time, for example via the Excel Export. This also helps with requests for access under Art. 15 and with the right to data portability under Art. 20 GDPR.
If something does happen: data breaches
In the event of a personal data breach, you must generally notify the supervisory authority within 72 hours (Art. 33 GDPR). With health data, the individuals concerned often have to be notified as well (Art. 34). Without a log, it is hardly possible to say which data is affected. With a complete Audit Trail, the scope can be narrowed down quickly.
Checklist: processing health data in compliance with the GDPR
- Record processing operations: a record of processing activities with purpose and legal basis under Art. 6 and Art. 9 GDPR.
- Document consent: demonstrable, separated by purpose, revocable at any time.
- Draw up a permissions concept: roles for functions, attributes for data, the same rules for interfaces.
- Log access: a complete, immutable Audit Trail.
- Determine the hosting location: check for third-country links, take professional secrecy under Section 203 StGB into account.
- Conclude contracts: data processing under Art. 28 GDPR, check sub-processors.
- Document TOMs: encryption, separation of customer data, data backup, recovery.
- Carry out a data protection impact assessment: generally required for extensive processing of health data (Art. 35 GDPR).
- Minimise data: pseudonymise where a link to the person is not needed.
- Draw up a deletion concept: periods for each type of data, taking retention obligations into account.
- Prepare for data subject rights: fulfil access, rectification, erasure and data portability within a reasonable time.
- Define an emergency plan: who does what within 72 hours in the event of a data breach.
You will find more about hosting, contracts and the protective measures of the Datico® Life Hub under Trust and security, and the standards used under Standards. If you would like to go through your project with us, arrange a personal initial consultation. We will be happy to provide you with our technical and organisational measures for this.
Frequently asked questions
What is health data under the GDPR?
Under Art. 4(15) GDPR, data concerning health is personal data relating to the physical or mental health of a person which reveals information about their health status. This includes diagnoses and findings, but also readings such as heart rate, blood pressure or the results of a gait analysis. It is one of the special categories under Art. 9 GDPR.
What does data compliance mean for health data?
Data compliance means that processing demonstrably complies with the rules: the GDPR, national law such as the German Federal Data Protection Act (BDSG) and professional regulations, contracts and internal requirements. With health data, the evidence is what matters most: documented legal bases and consent, a permissions concept, logged access, data processing agreements and a deletion concept.
What is an Audit Trail and is it mandatory?
An Audit Trail records who accessed, changed or deleted which data and when. The GDPR does not prescribe the term, but it does require you to be able to demonstrate compliance with the principles (Art. 5(2)) and to safeguard the integrity of the data (Art. 32). With health data, logging access is therefore indispensable in practice.
Does health data have to be hosted in Germany?
The GDPR does not require hosting in Germany, but it does require that transfers to countries outside the EU take place only on a basis under Art. 44 et seq. Hosting in Germany with no third-country link avoids this review and makes it easier to agree matters with data protection officers. For professionals bound by confidentiality, Section 203 of the German Criminal Code (StGB) must also be observed.
How long may health data be stored?
Only as long as is necessary for the purpose or as long as a retention obligation applies. For medical treatment records in Germany, a retention period of ten years after the end of treatment generally applies (Section 630f(3) of the German Civil Code (BGB)). Studies and other purposes have their own periods, which are set out in the deletion concept.
Where does Datico® store health data?
In a separate database for each customer on servers in Germany, with no transfer to third countries. Datico® concludes a data processing agreement under Art. 28 GDPR with every customer. On request, the Datico® Life Hub runs in your own infrastructure.
Related features
- Audit TrailYou can trace every measurement with its context, and every action in the system, completely – even years later.
- Double Opt-InYou only process data once the person concerned has given verifiable consent in two steps.
- Excel ExportYou define once what your export looks like and can then generate Excel files yourself at any time for any people, events and periods.
- Roles & RightsYou define who may use which function and see which data – down to function and attribute level.
- Secure Data TransmissionYour data is encrypted on every transmission path and is held in a dedicated database on servers in Germany.