Patient information under special-category rules
Health data carries the heaviest protection European law provides. "Encrypted in transit and at rest" describes almost every product on the market and does not answer the question of who can read it.
Healthcare teams have to keep patient discussion confidential and keep operational records available, and most platforms make you choose one. Enclessa separates them: direct and group direct messages are end-to-end encrypted, so clinical conversation is unreadable to the server and to us, while operational channels stay server-readable and therefore searchable, retainable and exportable. The People module records absence without a diagnosis field, because a collaboration platform has no business holding one.
At a glance
- Clinical discussion
- End-to-end encrypted direct and group messages
- Operational channels
- Server-readable, searchable, exportable
- Sickness records
- No diagnosis field exists
- Hosting
- European Union
- Certification
- None claimed — see the security page
The constraints this sector actually has
Shift work means asynchronous handover
The people who need the message are rarely at a desk when it is sent. Notification control that respects a night shift is not a nice-to-have.
Operational records still have to be findable
Rosters, equipment, escalation and estate management are not clinical, and burying them in encryption makes them unusable for no protective benefit.
Staff records are their own regime
Personnel data, sickness and absence carry duties distinct from patient data and should not live in a spreadsheet on somebody’s desktop.
What Enclessa does about them
Questions
Healthcare: common questions
Encrypted collaboration, hosted in Europe.
Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
No card required to create a workspace.