Say what you need.
The admin is already done.
Vernus is a quiet layer that sits on top of the clinical system you already use and runs tasks for you. You give an instruction in plain language, the same way you would talk to a colleague.
You speak, it works, you approve. Nothing enters the record without you.
The essentials, handled for you.
Ordering
Hover to previewPinned. Click to closeBloods, scans and imaging. You say what you want and the request comes back filled in.
On accept, the request is filed in your clinical system and kept on the results tracker until the result comes back.
Referrals
Hover to previewPinned. Click to closeDrafted as you speak, from the consultation and what is already in the record.
On accept, the letter is attached to the referral and sent by the route you choose, and the consultation is coded. Nothing leaves the practice before you have read it.
Letters and notes
Hover to previewPinned. Click to closeDictated and structured, in your words rather than out of a template.
On accept, the letter is saved to the record and queued to go out by your usual route.
Patient summaries
Hover to previewPinned. Click to closeHistory, medications and results, gathered before you open the door.
Nothing is written anywhere. A summary is for reading before the patient sits down, and it disappears when you are done with it.
Results tracking
Hover to previewPinned. Click to closeEverything you have ordered stays on the tracker until it is acknowledged. Nothing is lost.
On acknowledge, the result is filed in your name and comes off the tracker. Anything you have not acknowledged stays there and ages visibly.
Freestyle
Anything else that lives in your clinical system. Describe it and it does the rest.
It gets better the more you use it.
There is no migration and no second record to keep. It installs like an ordinary app on your machine.
You ask. It operates the system. You approve.
You ask
In plain language, spoken or typed, during clinic or between patients.
It works
Inside your existing system, through your own login, while you carry on.
You approve
Open the task, read the draft, then accept it, edit it or reject it.
A quarter to a third of the day, before anyone is seen.
This is not a side effect of the job. It has been measured, and it is one of the largest single claims on clinical time in the NHS.
of GP time goes on administrative tasks such as fit notes and certification.1
of their time is spent on admin and bureaucracy that does not always improve patient care, by GPs' own account.2
of admin for every hour of direct patient contact, measured across 137 UK doctors in training.3
In that last study, the doctors working on electronic records spent more of their time on admin than those still on paper, not less.3 Better software has not been the answer on its own.
Ten patients, fifteen minutes each. The clinical work is identical in both columns.
The same morning, with and without.
Illustrative, and drawn from an ordinary GP morning rather than a best case. We measure minutes saved against a baseline from day one of the pilot, and we will publish what we find.
Designed for clinician approval for every action. Full medical oversight.
Nothing enters the record without you.
Every action arrives as a draft on the tracker. You open it, read it, then accept it, edit it or reject it. There is no route by which something reaches a patient record, a colleague or a lab without a clinician explicitly actioning it.
Vernus never makes a clinical decision. It carries out the administrative work behind a decision you have already made.
Patient data is masked before it leaves
Identifiable detail is detected and removed on your machine, before anything is sent for processing.
Nothing is kept
No patient data is stored to disk or to the cloud, and none of it is used to train anyone's model.
It works within your access
Vernus uses your own login and permissions. It cannot see or do anything you could not.
A record of everything
Every instruction, draft and approval is logged and attributable, so an audit can follow the whole chain.
An emergency stop
You can halt anything mid task. It is always there and we expect it to be rarely used.
It fails safely
If your clinical system is down, or ours is, it stops and tells you plainly. It does not guess.
I built Vernus because I was spending my day completing admin, instead of seeing patients.
The clinical part of the job is the part I trained for. The rest is finding the right screen, filling the same fields again, and writing letters that say what I had already said out loud in the room.
So Vernus is built around how we actually work. You give an instruction the way you would give it to a colleague, and you check the result the way you would check a colleague's. Every extra minute on admin is a minute not spent with a patient or thinking about a patient's care.
If you would like to try it in your practice, I would like to hear from you.
NHS doctor. Founder of Vernus.
What colleagues ask first.
Does it change my clinical system?
No. It sits on top of what you already have and operates it through your screen as you work with the patient.
What happens if it gets something wrong?
You see it before anyone else does. Nothing is sent, filed or ordered until you accept it, so a wrong draft is a draft you delete. We track how often drafts are edited or rejected and report it.
Is it making clinical decisions?
No. It does administrative work only. The decision was yours before you said it out loud.
How long does it take to learn?
There is nothing to learn. If you can tell a colleague what you want, you can use it.
What does my IT provider need to do?
We involve them from the start and agree every step with them. Installation is an ordinary app install, and we resolve any permissions or conflicts with them before anything goes live.
What about patient data?
Identifiable detail is stripped on your machine before anything is sent, nothing is stored, and none of it trains a model. The full information governance position is documented and we go through it with you and your IT provider before the pilot starts.
Building it together, one step at a time.
Before anything goes live we test it in a test environment on dummy data, with your IT provider involved and agreeing each step. You will see it working on realistic practice data before you see it working on yours.
A direct line throughout
This is a live product. What you tell us changes it within days, not quarters.
Your practice as co-authors
We run it as a quality improvement project and publish the results with your team named.
Your data stays yours
Always, and you keep it at the end.
No obligation to continue
We review together honestly at the end. If it is working, we talk about what comes next.
Thank you.
We will be in touch shortly.