Patient data is the product's hardest constraint, not a feature.

Ormeda is multi-tenant by construction: a hospital cannot see another hospital's patients even if a query is written wrongly, because the access guard runs before the database is touched.

Fail-closed tenant isolation

Every clinical read and write checks a patient-access guard first. If the check cannot be answered, the request is refused, never allowed through by default.

GDPR consent & retention

Consent is recorded per purpose with a lawful basis, withdrawal and expiry. Document retention and disposal schedules are enforced by the system, not by a reminder.

Append-only audit trail

Who saw what, when, and from which address, across the entire platform. Records are never hard-deleted; an error becomes a marked correction with its history intact.

EU data residency

Patient data is stored and processed in the EU. Subject access and export requests are served from statutory endpoints that no commercial setting can switch off.

Granular roles

From owner to technician to patient, with department scoping. Role and module entitlement are enforced on the page, in the component and again on the API.

Read-only, never dark

Switching a module off makes it read-only rather than invisible. Clinical data stays readable because your retention duty outlives the contract.

Certification status. Ormeda is not currently marketed as a certified medical device. Where a hospital's procurement requires ISO 27001, MDR classification or a national accreditation, we will tell you exactly where we stand rather than imply a badge we do not hold.

Every look and every change leaves a record.

The audit trail is append-only and covers the whole platform. It answers the question that follows every incident and every inspection: who saw this record, what did they change, and when. The system writes it as the work happens; nobody types it up afterwards.

What is recorded

Every access to a patient record, not only every edit: the user, the time, the record and the address the request came from. Reads count, because the first question after an incident is usually who looked.

What cannot be deleted

Clinical records are never hard-deleted, and a signed clinical document locks the moment it is signed.

A correction is not an edit

A mistake in a signed record becomes a marked correction, made as an amendment that carries the corrector's name. The original stays in the history, so the record shows what was written at the time and what changed afterwards.

What an auditor can reconstruct

For any patient: who opened the record and when, what was written and signed and by whom, and every correction since, in the order it happened. The log is available to the hospital, which is the controller, not only to us.

What your security review will ask, answered in writing.

We answer procurement questionnaires and DPIA templates directly, with no sales call first. These are the questions every hospital pack asks, and the answers we can put in writing on the first day. The data processing agreement is published in full.

Your DPIA

We supply what a data protection impact assessment needs from the processor: the categories of data and of data subjects, health data under Article 9 included, the processing operations, the sub-processors and transfers, and the security measures. Send your template and it comes back filled in.

Controller and processor

The hospital is the controller of its patients' data. Ormeda is the processor and acts only on the hospital's documented instructions, under a data processing agreement written to Article 28 GDPR. Customer data is never used to train models, for advertising or for any purpose of ours.

Where the data is

Stored and processed in the EU, encrypted in transit with TLS 1.2 or higher and encrypted at rest. Every sub-processor is named with its location, and you get 30 days' notice before one is added or replaced.

Breach notification

We tell you about a personal data breach without undue delay and within 48 hours at the latest, with the information Article 33(3) GDPR requires as it becomes available.

Backups and staff access

Encrypted backups every day, kept for 30 days, with a tested restore procedure. Staff access to production is individual, logged and limited to named engineers.

Audits, exit and deletion

You, or an auditor you mandate, can audit us on 30 days' notice once a year, or sooner if a breach or a supervisory authority requires it. When the contract ends, your data stays exportable for 90 days, then is deleted from production and, within 30 more days, from backups, apart from what the law requires us to keep.

Common questions

Is Ormeda a certified medical device?

No. Ormeda is not currently marketed as a certified medical device. Where a hospital's procurement requires ISO 27001, MDR classification or a national accreditation, we tell you exactly where we stand rather than imply a badge we do not hold.

Where is patient data stored?

In the European Union. Data is stored and processed in the EU, and subject access and export requests are served from statutory endpoints that no commercial setting can switch off.

Can one hospital see another hospital's patients?

No. Ormeda is multi-tenant by construction and fails closed. Every clinical read and write checks a patient-access guard before the database is touched, and if that check cannot be answered the request is refused rather than allowed through by default.

What happens to clinical data when a module is switched off?

It becomes read-only, never invisible. Records are never hard-deleted. An error becomes a marked correction with its history intact, because a retention duty outlives the contract that created it.

Who can see what?

Roles run from owner to technician to patient, with department scoping, and entitlement is enforced on the page, in the component and again on the API. Every view and every edit is written to an append-only audit trail: who saw what, when, and from which address.

Do you answer procurement questionnaires and DPIAs?

Yes, directly, with no sales call required first. Send the questionnaire or the DPIA template and it comes back answered.

Send us your security questionnaire.

We answer procurement questionnaires and DPIA templates directly, no sales call required first.