Data practices

This page summarises, in plain language, how Emedis Cloud handles patient and clinical data in the release being prepared for go-live. Some measures described here are built and tested but not yet deployed in every environment. It is a practical overview — not a contract. A full Privacy Policy and a GDPR Article 28 Data Processing Agreement are being prepared with legal counsel; contact us to discuss data-protection terms before onboarding your organisation.

Who provides Emedis Cloud

Emedis Cloud is provided by TP Emedis AI LTD, a company registered in the Republic of Cyprus, with its registered office at 1 Apriliou 52, 7600 Athienou, Larnaca, Cyprus. For the patient data processed in the product, the customer (the hospital or clinic) is the controller and TP Emedis AI LTD is the processor.

Where records are stored

Consultation records and the encrypted patient identity are stored on an application server of Hostinger International Ltd in Manchester, United Kingdom (see the sub-processors page). The United Kingdom benefits from an adequacy decision of the European Commission under Article 45 of the GDPR. Consultation audio is not stored.

Patient identifiers

The patient's name, date of birth, ID or ARC number and phone numbers are encrypted by the Emedis server (AES-256-GCM, with a separate key for each organisation) before they are stored. The keys are kept outside the database. The server decrypts the identity only for users who are allowed to see that patient. This is not end-to-end encryption: the server can read the identity when an authorised user opens the record. A keyed hash (blind index) lets the system find duplicate patients without storing the identifier in clear.

AI processing

To transcribe the consultation and to draft the record, notes and forms, the audio and the text generated from it are processed by open AI models that Emedis runs on GPU servers rented from Runpod, Inc. in data centres in the European Economic Area (at present the Czech Republic and Iceland). The models run only on those servers. Patient data is not sent to any third-party AI service, and no other party receives it: the GPU servers reach the application server through a private encrypted tunnel that they open themselves, with no proxy or content-delivery network of another company in the path. Before text goes to the language model, the patient’s own identifiers are removed on the server, and if that cannot be done nothing is sent. Audio and document images cannot be redacted; they are processed as captured, and audio is not stored. Other people named in a consultation can remain in the text, so it is treated as personal data. Each provider, with its role and location, is listed on our sub-processors page.

Who can see clinical content

Doctors see their own patients. An organisation manager can give a doctor or a nurse access to a patient list or to a single patient; such changes are recorded in the audit trail. Nurses see only what they were granted. Managers do not see clinical content unless they are also treating clinicians. Emedis platform administrators are not meant to read clinical content; the technical restrictions on their access are being completed before go-live. Access is enforced by row-level security in the database.

Clinician responsibility

All AI-generated content must be reviewed and approved by a qualified clinician before any clinical decision is made. Emedis Cloud is a documentation and decision-support aid. It has not undergone medical-device conformity assessment, is not CE-marked and is not intended to diagnose, treat or make clinical decisions; the differential considerations and suggested questions it displays are aids for the clinician’s documentation and reasoning, not a diagnosis.

Retention, rights and certifications

Data-retention schedules, data-subject-rights workflows (access, rectification, erasure, portability) and formal security certifications are being finalised. Emedis Cloud is in an early-access pilot. Contact us for the current status before relying on any specific commitment.