Summary
Regulation 12 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 requires care and treatment to be provided in a safe way, and names assessing risk, doing all that is reasonably practicable to mitigate it, and, at paragraph 2(i), working with others where responsibility for a patient is shared with or transferred to them so that timely care planning takes place. Results are where that paragraph bites. A system that records a result arriving has evidenced delivery. What the duty reaches for is acknowledgement, which is a named person, a time and a decision, plus an escalation when none of those happen.
The unread result is the most reliably serious failure in outpatient medicine and the least likely to be noticed while it is happening. Nothing alarms. A document arrived, and the system that received it is satisfied.
Regulation 12 does not mention results. It asks whether care was provided safely, and names what a provider must do when responsibility for a patient is shared or handed over. A results pathway is the commonest place in a clinic where that happens several times a day.
Part of the CQC hub, with the framework explained, a readiness checklist and 10 guides.
See it in your clinicEvery result with a named reader, a time and a decision, and an escalation when it has none of them.
Request a demo| State | What a system usually records | What the duty reaches for |
|---|---|---|
| Sent by the laboratory | A delivery timestamp | Nothing yet. Delivery is the laboratory's evidence, not the clinic's |
| Received into the clinic | A document in an inbox or a file store | Still nothing. A received result and an unread result look identical |
| Read by a named clinician | Often not recorded at all | A person, a time and what they decided |
| Acted on, or deliberately not | The action, if it happened in the same system | The decision joined to the result, including a decision that no action was needed |
The paragraph most people have not read
Regulation 12(2) lists the things a registered person must do to provide care and treatment safely. Most of the list is familiar. Paragraph 2(i) is the one rarely quoted, and it requires that where responsibility for the care and treatment of service users is shared with, or transferred to, other persons, the provider works with those persons, the service user and other appropriate persons to ensure that timely care planning takes place.
A results pathway is a chain of exactly those transfers. The clinic requests, a laboratory performs, a result returns, a clinician interprets, and somebody tells the patient. Each handover is a point at which responsibility moves, and the regulation asks what the provider did to make the next step happen on time.
Arrival is not reading, and systems conflate them
The structural problem is that almost every clinical system models a result as a document with a delivery time. Delivery is a fact about transport. It says a file moved and says nothing about whether a human being looked at it or what they concluded.
The distinction matters because the two failure modes are opposite. A result that never arrived is visible, because somebody is waiting for it. A result that arrived and was not read is invisible, because the system shows it present and correct. The second is the one that causes harm, and it is the one an inbox cannot surface.
Acknowledgement, and what makes it evidence
The control is an acknowledgement that carries three things. The clinician who read the result, the time they read it, and the decision they reached, including a decision that no action was needed. The last is the one most often left blank, and it is the one that distinguishes a considered normal result from an unexamined one.
An acknowledgement with no decision attached evidences that somebody opened a document. That is better than nothing and it is not what the duty is asking about, because the question an assessor or a coroner reaches is what was concluded rather than what was opened.
The escalation, which is the only part that works unattended
Every control above depends on somebody doing something. The part that does not is the escalation, which is the rule that notices a result with nobody's name against it after a defined period and puts it in front of a person who can act.
This is the difference between a system that records a duty and a system that discharges it. A clinic can have a perfect acknowledgement field and still miss a result, if nothing in the software minds that the field is empty. The question to put to a supplier is not whether results can be acknowledged. It is what happens on day seven when one has not been.
Where this meets the records duty
Regulation 17 requires an accurate, complete and contemporaneous record of the care and treatment provided and of the decisions taken in relation to it. A decision about a result is one of those decisions, which means the acknowledgement is not an administrative flag. It is part of the clinical record.
That reframes where it should live. A results workflow in a separate product, joined to the record by a patient name, produces a decision that exists outside the record of the care it relates to. Our page on what documentation software has to prove covers why that join is the thing worth examining.
What we are not claiming
This page describes what the regulations require and what systems can evidence. It is not clinical advice, it says nothing about how any particular result should be interpreted or escalated, and it does not substitute for your registered manager's judgement or for the guidance CQC publishes. Where a decision turns on detail, the legislation linked below governs rather than this summary of it.
wai is not CQC registered and makes no claim to be. CQC registers providers of regulated activities rather than software. The registration and the duty stay with the clinic.
Where wai sits
This is the problem wai was built around. A result is held as an item of work with an owner rather than as a document in a store, it carries the named clinician who reviewed it and what they decided, and an item sitting unread past its window raises itself rather than waiting to be noticed.
Nothing about that is a compliance feature. It exists because an unread result is the failure a clinic fears most, and the evidence it happens to produce for Regulation 12 and Regulation 17 is a consequence rather than the design goal. The wider map is in software and CQC, what is actually being assessed.
Put the test to any supplier on your list, including us. Ask for the list of results received more than seven days ago with no clinician's name against them. Clinicians still decide what enters the record.
Ask any system for the list of results received more than seven days ago with nobody's name against them. The length of that list is the answer.
Request a demoFrequently asked questions
Which regulation covers following up test results?
Regulation 12 on safe care and treatment. It requires risks to be assessed and mitigated, and at paragraph 2(i) requires the provider to work with others where responsibility for a patient is shared or transferred, so that timely care planning takes place. A results pathway is a chain of exactly those transfers.
Is recording that a result arrived enough?
No. Arrival is a fact about transport and says nothing about whether anybody read the result or what they concluded. A received result and an unread result look identical in an inbox, which is why the second failure mode is the invisible one.
What should a result acknowledgement contain?
Three things. The clinician who read it, the time they read it, and the decision reached, including an explicit decision that no action was needed. The last is most often left blank and is the one that distinguishes a considered normal result from an unexamined one.
Why does escalation matter more than acknowledgement?
Because every other control depends on somebody acting. A clinic can have a perfect acknowledgement field and still miss a result if nothing in the system minds that the field is empty. The question for a supplier is what happens on day seven when a result has not been acknowledged.
Is a results decision part of the clinical record?
Yes. Regulation 17 requires a contemporaneous record of the care and treatment provided and of the decisions taken in relation to it, and a decision about a result is one of those. That is why a results workflow sitting in a separate product joined only by patient name is worth examining.
What is the single best question to ask a results vendor?
Ask for the list of results received more than seven days ago with no clinician's name against them. A system that can produce it has the concept of an unacknowledged result. A system that cannot has been treating delivery as the end of the process.
Sources
The results nobody has read
Fifteen minutes on your workflows. If it is a fit we reply within 24 hours.
Partner with us
See it on your own patients, then build it with us
Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.
Read how results explained works in a clinic