The CMA has exposed something veterinary practices have been missing for years...

Updated: 16 hours ago
I've spent far too much time recently buried in the CMA's final Order for veterinary practices and, having got to the other side of it, I think it exposes a gap in the way veterinary practices work that has been there for years.
The final package contains 162 pages of PDFs, plus the complaint log spreadsheet, covering pricing, estimates, prescriptions, medicines, complaints, cremation, ownership and quite a bit more.
You can find the full CMA Order and supporting package here, along with the rather more digestible CMA guide to what veterinary businesses and vets need to do.
The thing that struck me is quite simple.
Our PMS records what happened.
Our protocols tell us what should happen next.
What's missing is a way of making sure that next thing happens.
The bit between knowing and doing
We're very good at recording the clinical journey. Consultations, findings, diagnoses, treatment, medicines, estimates and invoices all have a home in the PMS. We've spent years training vets to document medicine properly. It's second nature.
We're pretty good at writing protocols too. Veterinary practices are full of SOPs, policies and guidance explaining what should happen in a particular situation. We write them, update them and accumulate an awful lot of them.
The problem comes afterwards.
Our beautiful SOPs sit in dusty folders, on shared drives or stuck to the back of a lab cupboard door waiting for the next PSS inspection. However good the protocol is, it still relies on somebody knowing it exists, finding it in the moment and remembering to follow it.
We've built an awful lot of veterinary practice around people remembering what comes next and then trying to make sure it happens between everything else that's going on.
We see the consequences every day. Client callbacks get missed, blood results don't get reported, the order misses something, a job gets handed to somebody who thought somebody else was doing it. Everybody intended to do it, everybody was busy, something else happened and the thing disappeared into the day.
That's not a criticism of practices. I've run them and I know exactly how this happens. The animals come first, the phone rings, an emergency walks through the door, somebody asks you a question and priorities change.
The CMA brings that missing operational layer into focus
Complaints are a particularly good example.
From 22 March 2027, the new complaints requirements apply to both large and small veterinary businesses. A complaint can be spoken or written and made to any member of staff where a pet owner is expressing dissatisfaction and looking for a resolution or outcome.
At that point the practice has ten working days to try to resolve it informally. Where that doesn't happen, it becomes what the Order calls an Actionable Complaint.
That starts another sequence of things that need to happen. There are deadlines for acknowledgement and response, requirements around investigation and communication, and a prescribed Complaint Log containing information about how the complaint was handled and what happened.
Having a complaints policy doesn't make any of those things happen.
Putting another note in the PMS doesn't really solve it either.
Somebody needs to recognise what's happened, get it to the right person, know what needs doing and by when, have the relevant information available, bring other people in where necessary, keep an eye on deadlines, follow the thing through and leave an accurate record of what happened.
Complaints make the problem particularly easy to see, but they're far from the only example. The CMA requirements around estimates, prescriptions, medicines and pricing create more situations where something happens in the practice and something else now needs to follow.
That's exactly what Helm has been built for
We started building Helm because veterinary communication was scattered everywhere.
Important conversations happen in WhatsApp and Teams. Jobs get handed over verbally. Useful knowledge gets buried in folders. Tasks live on Post-it notes or in people's heads. Something can begin in the PMS, continue by email and finish in a conversation nobody else knew had happened.
As Helm has developed, we've realised that communication is only part of the problem.
Helm is the operational layer that sits alongside the PMS.
The PMS remains the clinical and financial record. Helm gives the work around care somewhere to happen.
That means conversations can become tasks, work can have a clear owner, deadlines can be scheduled and followed, and the right guidance can be available when somebody needs it. Work can move between people without losing the context around it, while leaving a useful record of what happened.
For the things that need more structure, Helm has workflows.
Resolve, for example, brings that approach to complaint handling. A complaint can be captured when it happens and handed to the right person, with the relevant people, information, actions and deadlines brought together as the case progresses. The investigation, response and outcome become part of the same piece of work rather than another trail of emails, notes and spreadsheets.
Echo does the same for pet insurance. It brings together the patient record, policy information, estimates, treatment, people, decisions, submission and follow-up so that the claim can move through the practice as a piece of work rather than simply another form to complete.
Alongside those workflows are Discussions, Tasks and Know-how, dealing with the hundreds of less complicated things that need to happen in a practice every day.
That's an important distinction. Helm hasn't been built to replace the PMS. It has been built to work alongside it, dealing with the operational work that happens around the clinical record.
Compliance can be part of doing the work
This is where I think the CMA changes become particularly interesting.
Practices won't just need policies describing what should happen. They'll increasingly need to be able to show what did happen.
Who picked it up? What did they know at the time? What needed doing? Who did it? When did it happen? What was the outcome?
I don't think the answer should be another collection of compliance spreadsheets sitting alongside another collection of SOPs.
The record should come from doing the work.
If somebody handles a complaint through Resolve, for example, the dates, people, decisions, actions and outcome are being captured because they're part of handling the complaint. The evidence doesn't need to be reconstructed afterwards from emails, diary entries and somebody's memory.
Software can't make a veterinary practice compliant, and we wouldn't claim that it can. What Helm can do is give practices a much better way to put their processes into practice, make sure the work gets to the right people and keep track of what happened.
The CMA didn't create the problem, but it has made the opportunity much clearer
That's probably my biggest takeaway from those 162 pages.
The operational gap was already there. We've been living with it every time somebody says “I thought Sarah was doing that”, every time a callback disappears into a busy afternoon and every time somebody goes looking for the protocol they vaguely remember exists somewhere.
The CMA has simply made the consequences of that gap much easier to see.
For me, that's also the positive bit. We now have a much clearer idea of what good operational systems in veterinary practice need to do.
Your PMS records what happened. Your protocols tell you what should happen next. Helm has been built to help make sure that next thing happens.
That's the work around care.



Comments