This is the page you reach from Maintenance & updates in the sidebar. It shows you the managed service you
receive on your own server, and it is written so that you can evidence it to your regulator or inspector
without asking us for anything.
Two things are worth knowing before the details:
The first thing on the page, headed Maintenance & updates. It answers the question an inspection asks first:
when was this server last updated, and what happened?
| On the card | What it tells you |
|---|---|
| Updates applied | The last completed run, counted: "12 updates applied on 14 October 2026, 3 of them security fixes." Before anything has run it reads "No maintenance runs recorded yet." |
| Restart | not needed, waiting — will happen in a quiet window, or done. A restart is never silent: a security-critical one waits for a 7-day notice and then happens in a quiet window; anything else waits up to 30 days and then gets a second notice before it proceeds. |
| Next scheduled run | The next planned run, date and time in UTC. If it reads not scheduled, no date has been recorded against your server yet — that does not mean your server is unpatched; your server keeps to its own schedule, below. |
| Failed runs | A green badge reading "No failed runs in the last 30 days", or a red one giving the number. A failed run is never retried blindly — we look at what happened and run it again properly. |
| View all | The full list of runs (below). |
| Download | The same records as a file you can keep or hand to an inspector (below). |
View all opens the full record of runs against your server. Each row gives the date and time (UTC), the
server, the kind of run, the result, how many updates were applied, how many remain
outstanding, and the restart state.
Each row opens to show the individual packages — the version before, the version after, and whether each one
was a security fix. That is the level of detail an inspector asks for when they want more than a count.
Both downloads are generated from the record of what your server actually did. Neither you nor we can edit them
by hand after the fact.
Download (CSV) — one row per run, with the columns:
date, finished, box, kind, trigger, outcome, applied, outstanding, reboot, summary,
evidence_path
Download package detail — one row per package behind each run, with the columns:
date, box, package, from, to, security
Between them, an inspector can see what happened, when, with what result, which packages moved and from which
version to which, and whether security was involved — from your own login, with no request to us.
You do not need to remember any of this, but it is what you are receiving:
| What | When |
|---|---|
| Security updates | Continuously, as they are published |
| Full update run | Monthly, on your server's own slot — outside your clinic hours and clear of the nightly backup |
| Restarts, when one is needed | In a quiet window, after the notice period above — never silently, and never left undone |
| Your server's own images (database, storage) | Refreshed quarterly |
A run happens on that schedule whether anyone is watching or not. Nothing about your patching depends on you
doing anything.
If you want to know what we promise about all of this, and what happens when something goes wrong, see
Patching — What We Promise, and What Happens When Something Goes Wrong.
What a client can see about their patching, and how they prove it
goes through the same evidence from an auditor's point of view.
VeriPath keeps its own engineering view of the estate — server health (disk, memory, CPU), database metrics,
backup status and the tunnel between your server and our platform. Those cards are our monitoring surface,
not part of your dashboard, and they are not shown to your practice. In short, so you know what is covered:
Your part is the record of the maintenance itself, which is what this page gives you.
Why is my view empty?
Because nothing has finished running on your server yet. The record fills in as runs complete — the first one
usually appears within a month of your service starting, and often sooner.
How quickly does it update?
As soon as your server finishes a run and posts its record. You do not need to refresh anything special; loading
the page shows the latest.
Can I see exactly which packages were updated, and prove it?
Yes — Download package detail gives one row per package with the before and after versions and whether each
was a security fix, and each row in View all opens to the same detail.
Do I have to do anything to keep my server patched?
No. That is the managed service. The schedule runs on your server's own timers.
What happens if a run fails?
It shows as a failed run, with the count of failures in the last 30 days on your card. A failure is never retried
blindly: we look at what happened and run it again properly.
Who can see this page?
Anyone in your practice with an admin or manager role. It uses your normal login — there is no separate account.