Automation
AvailableThe admin between the care, done for you
A rule reads: when something happens, only if certain things are true, then do these things. That is the whole model. No scripting, no deployment, and a dry run against a real record before anything goes live.
67
events to trigger on
17
record types covered
30 days
maximum delay on an action
What you get
Practice managers · Operations leads · Reception
- When
- Statuses changing, records created or updated, alerts added, comments posted, forms submitted, payments received, reports confirmed, letters signed, invoices sent — across patients, procedures, bookings, invoices, payments, leads, reports, letters, tasks and inventory.
- Only if
- Narrow it with conditions on the record's own fields — equals, in, contains, empty, or a date compared against another date, with an offset. Every condition must hold.
- Then
- Email or text the patient from a template, email staff by name or role, write a field, or move a booking's status or category. Actions run in order.
- Time it properly
- Delay an action by minutes, hours or up to thirty days. Delayed work waits where staff can see and cancel it, and re-checks that the record still qualifies before it runs — so a patient whose situation changed is not messaged anyway.
- Safe by default
- A cooldown stops the same record being acted on twice. Imported automations arrive switched off until a person turns them on. Every run is logged with what matched and what it did.
Ready to make healthcare run better?
MedOS helps healthcare organisations connect fragmented operations, reduce manual admin, improve visibility and deliver a smoother patient journey.