AI for the GP inbox, read inside the practice.
A GP's inbox fills every day with discharge summaries, specialist letters and reports. Each one has to be read, matched to the patient and actioned, and the actions are often buried on page three: a medication stopped, a test to repeat, a review in six weeks. An Ermos unit condenses each document on hardware inside the practice and lists what it asks of the GP.
How it works on the unit
Incoming letters and summaries are indexed on the unit from your existing inbox workflow.
Each document condenses to what happened, what changed and what is asked of the practice, with the source attached.
Medication changes in a discharge summary are listed against the current medication list in the record, for the GP to reconcile.
The GP checks the summary against the source, accepts it to the record and actions the follow-ups through your practice software.
The boundary, stated plainly
Summarising is administration. Deciding what a result means for the patient stays with the GP, and urgent results still go through the triage workflow in your practice software, which the unit never replaces.
Why on-premise matters here
A discharge summary is a hospital admission in one document: diagnoses, procedures, medications and social notes. On the unit it is processed inside the practice that already holds it, so no new recipient is created.
See what leaves the practice. What a hospital discharge summary gives away in ChatGPT or Claude: marked up item by item.
Common questions
Can AI summarise discharge summaries for a GP?
Does it replace our results triage?
Is the inbox sent anywhere to be summarised?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo