Data minimisation in preventive management

Minimisation limits personal data to what each preventive purpose requires. It affects forms, permissions, integrations and retention.

In brief

Minimisation limits personal data to what each preventive purpose requires. It affects forms, permissions, integrations and retention.

Contents
  1. What minimisation means
  2. Starting with the purpose
  3. Application to health data
  4. What is shared also matters
  5. Review example
  6. Documenting and reviewing the decision
  7. Related concepts
  8. References

A–Z dictionary →

What minimisation means

Minimisation means determining which personal information is necessary for a specific purpose and avoiding collecting or sharing additional data without justification. It does not mean working with insufficient information for prevention. Analysis should distinguish the process’s technical needs from the convenience of having every piece of data in case it might be useful someday.

Starting with the purpose

Before adding a field, identify which decision it enables, who needs it and what happens if it is not collected. An equipment issue record, an accident investigation and a medical record have different purposes and recipients. Using a single form with every field for every process can multiply unnecessary information exposure.

Application to health data

Occupational health information requires particular attention. An organisational function’s need to know a preventive conclusion does not imply access to the clinical detail supporting it. Competent professionals determine which information should be communicated under the applicable framework, keeping information flows and permissions separate where required.

What is shared also matters

An integration can transmit many fields even when the screen displays few. Exports, reports, emails and automated connections should therefore be reviewed. Minimisation applies to working copies and test environments, where fictitious or appropriately protected data may be used. Visually hiding a column does not prevent it from remaining in the downloaded file.

Review example

In a hypothetical example, a monitoring dashboard needs to show how many reviews are pending at each workplace. Aggregate information may suffice for that purpose, without diagnoses or clinical documents. If an authorised person needs to manage a particular appointment, they access the corresponding individual workflow. The same level of detail is not distributed throughout the organisation.

Documenting and reviewing the decision

The justification for fields, recipients and periods is retained and reviewed when the purpose changes. Reducing information does not authorise deletion of records subject to mandatory retention. The GDPR provides the general principle within its scope; specific preventive and healthcare obligations must be analysed with competent responsible people and applicable legislation.

References

  1. BOE: General Data Protection Regulation. Official source
  2. AEPD: principles of personal data processing. Official source

Editorial information

Publication date: 1 November 2026.

Editorial responsibility: Sabentis Editorial Team.

Author: Pablo RodríguezLinkedIn

Executive Vice President of the ORP International Foundation and Chief Financial Officer of Sabentis.

Request a Demo

Discover all that Sabentis can do for your organization.

Try Sabentis

request a demo
stars 5
GetApp Software Advice Capterra