Your consultation, documented for you
Emedis listens to your consultation in real time, transcribes both doctor and patient speech, auto-fills the clinical record, and generates a three-tier differential diagnosis and editable SOAP note — so you can stay focused on your patient.
Invite-only — onboarding is high-touch via the Emedis team.
GPs spend too much time on documentation
General practice runs at pace. Between live consultations, typing up notes, coding records, and dictating referrals, documentation eats into time that should belong to the patient. Best practice calls for a complete SOAP note after every consultation — but under time pressure, notes are too often written in shorthand or finished after hours.
Every consult
Needs a complete, coded clinical note — subjective, objective, assessment and plan
After hours
When documentation often gets finished — at the cost of personal time
The full picture
PMH, medications, allergies and examination deserve to be captured, not abbreviated
How Emedis works
Three steps from opening a consultation to a signed-off SOAP note.
Step 1
Record the consultation
Start a consultation in Emedis. The browser captures audio via your device microphone — no specialist hardware needed. A speech-recognition model transcribes it in real time with speaker labels, distinguishing your speech from the patient's.
Step 2
Auto-fill the record and differential
As the conversation unfolds, Emedis extracts structured clinical data into a live form: presenting complaint, history of presenting complaint, past medical history, current medications, allergies, vital signs, and examination findings. Simultaneously, a three-tier differential — Most Likely, Expanded, and Can't-Miss — is built with guideline-style citations.
Step 3
Review, edit, and sign off
Every AI-generated field is editable — you remain the clinical author. Lock any field you've manually verified so AI updates don't overwrite your corrections. When the consultation ends, Emedis produces a complete, editable SOAP note and a printable consultation report. You review, approve, and sign off.
Everything your consultation needs
Built specifically for general practice workflows, structured to standard clinical-record and SOAP conventions.
Streaming transcription with two-speaker diarisation — doctor and patient speech labelled separately throughout the consultation.
Presenting complaint, HPC, PMH, medications, allergies, vital signs, examination findings, and more — populated automatically as you consult.
Most Likely, Expanded, and Can't-Miss diagnoses, each with relevant clinical guideline references cited inline.
A structured Subjective / Objective / Assessment / Plan note generated at the end of each consultation, fully editable before sign-off.
Export a clean, formatted report of the consultation — suitable for your records or for sharing as part of a referral.
Multi-tenant architecture with row-level security: each practice's data is separated in the database. Practice 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 the server of Emedis' hosting provider. The location of the production environment has not been decided yet: Emedis proposes a data centre in the European Union, to be confirmed in the contract with each customer. The current pilot runs on a server in the United Kingdom. Consultation audio is not stored. Audio and the text generated from it are processed by open AI models that Emedis runs on rented GPU servers; the current release uses no external language-model provider.
Access follows the treating team
Doctors see their own patients. A practice 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-practice isolation
Row-level security in the database keeps each practice'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-practice isolation. Formal security certifications are on our roadmap and are not yet in place.
Built for general practice
Emedis is structured to standard clinical-record and SOAP conventions and is designed around the workload and workflow of a busy GP surgery across Europe.
- Physicians managing a full patient list who want to reduce post-consultation admin
- GP practices looking to improve the completeness and consistency of clinical records
- Practices where clinicians are completing notes outside core hours
- Clinical leads exploring AI-assisted documentation as a quality improvement initiative
Not suitable for: emergency settings, secondary care, 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 a regulated medical device?
No. Emedis Cloud is a clinical documentation and decision-support tool. It assists clinicians by suggesting structured records and differential diagnoses, but all output must be reviewed and approved by the treating clinician. Emedis is not a substitute for clinical judgement and is not currently registered as a medical device.
Where is patient data stored?
Consultation records are stored on the server of Emedis' hosting provider. The location of the production environment has not been decided yet: an EU data centre is proposed, and the current pilot runs on a server in the United Kingdom. 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; 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 (for example Anthropic, Groq or Cerebras) is used by the current release: if the model is unavailable, the AI features stop and nothing is sent elsewhere. Deepgram (EU endpoint) is a fallback for speech recognition only, used if the customer has enabled it. 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 practice managers see patient records?
Not by default. Practice 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 practice 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-practice isolation. The hosting location of production is still to be decided.
Ready to reduce your documentation burden?
Emedis is now onboarding a small number of pilot GP practices across Europe. Get in touch to start a conversation.