Trust
Trust depends on how the system works.
Nerida is designed so the trustworthy behaviour is the default behaviour. Here is what that gives each person, and how it is done.
Understand who can access your clinical information, and control who helps with your care.
Keep private work separate from shared care, and delegate without broad exposure.
Help run the day without seeing information you do not need.
Work within defined project boundaries, with recorded use.
And for everyone
- Sensitive activity leaves a visible record.
- Records preserve their history when corrected.
- Access can be limited, and removed access stops immediately.
How Nerida supports this
- Access starts closed
- Clinical information is visible only where an explicit permission allows it.
- Checks happen on the server
- Requests for protected information are checked by the platform itself, not by what a screen hides.
- Information is layered
- Private, shared and operational information are kept apart, and moving between layers is a deliberate choice.
- Access leaves a record
- Patients can see a record of access to their clinical information.
- Corrections preserve history
- Clinical corrections append rather than overwrite. Lawful deletion and retention follow their own governed process.
- Protection in transit and at rest
- The production service will protect messages and data with encryption in transit and at rest.
The detail, for readers who want it
Working today: server-side permission checks on protected information; separated private, shared and operational layers; the patient-visible access record; append-only clinical corrections; small-group protection in research previews, which reduces identification risk.
Before live use: production deployment with backup and verified restore, independent security testing of the deployed system, and external clinical and legal review. Until then the platform runs on fictional data only.
This Website
The site holds itself to the same standard
Nerida collects no information directly through this static website: no cookies, no analytics, no third-party code, no forms. Our hosting provider processes standard technical request data to serve pages; the privacy notice describes this precisely.
Questions about security or privacy?
Security researchers and privacy-minded doctors are welcome to get in touch.