Ermos AI for recall and administrative letters.
Recalls, reminders, results-available letters, administrative notices: high volume, template driven, and each one still touches an identifiable patient's details. An Ermos unit drafts them from your templates on-site, so the routine correspondence gets faster without patient information going anywhere.
How it works on the unit
Your letter templates and the relevant recall or follow-up lists are indexed on the unit inside the practice.
Recall runs draft as a batch in your wording, each letter populated from the record it belongs to.
Practice staff scan the batch, pull exceptions, and approve. Clinical questions in a letter route to a practitioner before approval.
Approved letters send and file through your existing practice software, exactly as manual ones do.
The boundary, stated plainly
These are administrative communications. Anything clinical in content is drafted for practitioner review, and the decision to recall a patient remains a clinical workflow in your practice software, not something the unit initiates.
Why on-premise matters here
A recall list is a list of patients and why they need to come back, which is health information. Batch-drafting it on a cloud service is a disclosure at scale; on the unit it is not a disclosure at all.
Common questions
Does the unit decide who gets recalled?
Can letters be personalised safely?
What volume can it handle?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo