Your consultation, documented for you
Emedis listens to your consultation in real time and transcribes it in Greek or English, fills the pre-operative and follow-up forms from it, checks for red flags and drafts an editable SOAP note — so you can stay focused on your patient.
Invite-only — onboarding is high-touch via the Emedis team.
Documentation takes time that belongs to the patient
Cardiac surgery is documented at length: the pre-operative assessment, the follow-up after the operation, red flags, notes and reports. Typing it all up between patients, or after clinic hours, takes time that should belong to the patient.
Every visit
Needs a complete record: history, medications, allergies, findings and plan
After hours
When documentation often gets finished, at the cost of personal time
Every detail
Medications, allergies and red flags deserve to be captured in full, not abbreviated
How Emedis works
Three steps from opening a consultation to a signed-off record.
Step 1
Record the consultation
Start a consultation in Emedis, log the patient’s consent and speak as usual. The browser captures audio from your device microphone, with no special hardware, and a speech-recognition model transcribes it in real time, in Greek, English or both.
Step 2
Fill the record and the forms
As the conversation unfolds, Emedis extracts the clinical record into a live form: complaint, history, medications, allergies, vital signs and findings. In a pre-operative or post-operative consultation it fills the hospital form from the visit when the consultation ends, and it checks the visit for red flags.
Step 3
Review, edit, and sign off
Every field the AI writes is editable: you remain the clinical author. When the consultation ends, Emedis drafts an editable SOAP note and a printable PDF report in English or Greek. You review, approve and sign off.
Everything your consultation needs
Built for cardiac surgery: the pre-operative and post-operative workflow, in Greek and English.
Streaming transcription of the consultation in Greek or English, kept with the record. The audio itself is not stored.
Complaint, history, medications, allergies, vital signs and findings, filled in as you consult and editable at any time.
The pre-operative Initial Consultation Form and the post-operative Follow up Form, filled from the visit when you ask and finalised only by a doctor.
The transcript, the vital signs and the medication list are checked for red flags. Each one shows why it was raised, and a doctor confirms or dismisses it.
A Subjective / Objective / Assessment / Plan note, editable until sign-off, and a printable PDF report in English or Greek.
Row-level security in the database separates each organisation's data, so a user reaches only their own organisation's records. Organisation managers see clinical content only if they are also treating clinicians.
Privacy and data protection
Emedis is designed with patient privacy as a core constraint, not an afterthought.
Patient identity encrypted before it is stored
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.
Where patient records are stored
Consultation records are stored on an application server of Hostinger International Ltd in Manchester, United Kingdom. The United Kingdom benefits from an adequacy decision of the European Commission under Article 45 of the GDPR. Consultation audio is not stored. Audio and the text generated from it are processed only by open AI models that Emedis runs on rented GPU servers in data centres in the European Economic Area (at present the Czech Republic and Iceland). Patient data is not sent to any third-party AI service, and no other party receives it.
Access follows the treating team
Doctors see their own patients. An organisation manager can give a doctor or a nurse access to a patient list or to one patient, and the change is recorded. 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.
Per-organisation isolation
Row-level security in the database keeps each organisation's records separate: a user reaches only the rows of their own organisation, and the isolation is covered by automated tests.
Status: Emedis Cloud is in an early-access pilot. This page describes the release being prepared for go-live; some of the measures are built and tested but not yet deployed in every environment. It is built around GDPR principles: data minimisation, server-side encryption of patient identifiers, removal of the identifiers from text before AI processing, and per-organisation isolation. Formal security certifications are on our roadmap and are not yet in place.
Built for cardiac surgery teams
Emedis follows the workflow of a cardiac surgery department: the pre-operative assessment and the follow-up after the operation.
- Surgeons who want to spend less time typing up pre-operative and post-operative visits
- Departments looking to improve the completeness and consistency of records and forms
- Teams where clinicians are completing notes outside clinic hours
- Clinical leads exploring AI-assisted documentation as a quality improvement initiative
Not suitable for: emergency settings, or any situation where the clinician cannot review and approve AI-generated content before acting on it. Emedis is a documentation and decision-support aid — clinical responsibility remains with the treating clinician.
Frequently asked questions
Is Emedis CE-marked as a medical device?
No. Emedis Cloud has not undergone medical-device conformity assessment and is not CE-marked or otherwise certified as a medical device. It is not intended to diagnose, treat or make clinical decisions. It is a documentation and decision-support aid: the differential considerations (AI) and the suggested questions it displays are aids for the clinician’s documentation and reasoning, not a diagnosis, and every output is a draft for the treating clinician to review and approve.
Where is patient data stored?
Consultation records are stored on an application server of Hostinger International Ltd in Manchester, United Kingdom, which benefits from an adequacy decision of the European Commission under Article 45 of the GDPR. The patient’s name, date of birth, ID or ARC number and phone numbers are encrypted by the Emedis server before they are stored. Audio is not stored. Audio and the text generated from it are processed by open AI models that Emedis runs on rented GPU servers in the European Economic Area (at present the Czech Republic and Iceland); see the sub-processors page.
What AI models does Emedis use?
Emedis runs open-weight models on GPU servers it rents: Whisper for speech recognition and Gemma for extracting the clinical record, drafting notes and forms, and checking for red flags. No external language-model provider is used: if the model is unavailable, the AI features stop and nothing is sent elsewhere. The patient's own identifiers are removed from text before it reaches the language model, and if that cannot be done nothing is sent. Audio cannot be redacted. Other people named in a consultation can remain in the text, so it is treated as personal data.
Can organisation managers see patient records?
Not by default. Organisation managers manage accounts, seats and access, and see usage statistics; they see clinical content only if they are also treating clinicians. A manager can give a doctor or a nurse access to a patient list or to one patient, and every such change is recorded. Emedis platform administrators are not meant to read clinical content; the technical restrictions on their access are being completed before go-live.
How do I sign up?
Emedis Cloud is currently invite-only. There is no public self-sign-up. To request access, contact us by email and we will arrange an onboarding call. Each organisation is onboarded personally by the Emedis team.
What compliance certifications does Emedis hold?
Emedis Cloud is in an early-access pilot and does not yet hold formal security certifications; these are on our roadmap ahead of broader commercial rollout. In the meantime it is built around GDPR principles: data minimisation, server-side encryption of patient identifiers, removal of the identifiers from text before AI processing, open models run under Emedis’ control, and per-organisation isolation. Production is hosted in the United Kingdom (Manchester).
Ready to reduce your documentation burden?
Emedis is now onboarding a small number of pilot cardiac surgery teams. Get in touch to start a conversation.
