Data minimisation
Only the fields that are needed.
Spanish specific
Patient data protection: access, retention and deletion designed in from the start
Health data is particularly sensitive personal data under the GDPR. When building software we design data minimisation, access limits, retention periods and deletion rules from the start.
- English and community languages
- Patient data and GDPR in mind
- Roles and access log
First, which data is needed
Every field is questioned; unnecessary ones are not added. The patient form holds only information that serves its purpose.
Patients get a clear notice on how data is processed; we shape the text with your own legal adviser.
Technical measures
Connections are encrypted, users are limited by role and every access is logged. Backups and hosting location are set in writing.
We are software developers and do not give legal advice. For compliance assessment we work with your legal adviser.
Your benefits
Role-based access
Everyone sees only what their job needs.
Retention and deletion
Periods managed in settings.
Logging
Who looked at what, and when.
How we work
- 1
Clarify the need
By e-mail we discuss your processes, roles, existing systems and how data is moved, and set the scope in writing.
- 2
Build and connect
We build the solution around your workflow and connect it to e-mail, calendar, documents and payment.
- 3
Test and launch
We test every flow with realistic cases, train your team and go live only when it is right.
Spanish specifics
In Spain health data is particularly sensitive under the GDPR, and region rules and professional duties may apply. Scope is clarified with your legal adviser.
Frequently asked questions
Is the software GDPR-compliant?
The design follows GDPR principles; final compliance depends on your processes and legal assessment.
Where is data kept?
Hosting location is set with you in writing before development.
How is a deletion request handled?
A logged flow is set up for deletion and access requests.
Related topics
Roles, rights and access log
Roles, permissions and an access log in practice software: who sees what, who changed what. Quote by e-mail.
Learn moreData hosting and backup
Data hosting and backup for practice software: hosting location, encryption, backup and restore plan in writing. Quote by e-mail.
Learn moreElectronic patient record
Electronic patient record: consultation notes, history, documents and appointments in one file. Role-based access, logged actions. Quote by e-mail.
Learn more