The Starting Point: Context, Not Severity
In practice, the obligation is more specific than that — and understanding where it sits can make the difference between a well-managed incident and a compliance gap.
The Care Quality Commission is not asking whether a fracture occurred. It is asking whether the circumstances surrounding it raise questions about care, safety, or oversight. That distinction is where most uncertainty sits, and where most mistakes are made.
The Governing Regulation
Fractures that meet the notification threshold fall under Regulation 18 of the Care Quality Commission (Registration) Regulations 2009, which governs notification of other incidents. This sits alongside the more commonly referenced statutory notifications for deaths, abuse allegations, and deprivation of liberty applications, but operates on slightly different criteria.
The question is not the severity of the injury alone — it is whether the incident is connected to the delivery of care in a way the regulator should be aware of.
The Key Question: What Were the Circumstances?
A fracture that occurs because of a known, pre-existing medical condition — advanced osteoporosis, for example, where bones fracture under minimal force with no involvement from staff — sits in a fundamentally different regulatory position from a fracture sustained during a fall in the service, during moving and handling, or in circumstances where the adequacy of supervision or risk management could be questioned.
The notification obligation is triggered not by the injury itself but by its context. Where a fracture follows a fall within the service, occurs during physical support or repositioning, arises from environmental risks within the premises, or raises any question about whether it might have been prevented, notification is expected.
In these cases the fracture is being reported not as a clinical outcome but as an incident that may indicate something about the systems, supervision, and care delivery surrounding it.
When Notification May Not Be Required
Where the injury is genuinely unconnected to the service — occurring outside the premises without staff involvement, or arising entirely from a medical condition with no contributory care factors — it is less likely to require notification.
But providers should be cautious about applying this exception too readily. The presence of a condition like osteoporosis does not automatically remove the notification requirement if a fall within the service contributed to the fracture, even partially. The question is always whether care delivery played any role.
Professional Judgement Under Pressure
What makes fracture notification challenging is that it requires professional judgement, often in difficult circumstances and under time pressure. Two incidents that appear clinically similar can sit in very different regulatory positions depending on the specific facts — the location of the fall, the risk assessment that preceded it, the staffing levels at the time, the individual's known risk profile, and the actions taken immediately afterwards.
That judgement must be defensible. Where a provider later decides not to notify and the incident is subsequently reviewed — in a safeguarding inquiry, a coroner's hearing, or a CQC inspection — the reasoning needs to be documented and coherent. "We did not think we needed to report it" is not a governance record. A clear, contemporaneous account of why the threshold was not considered met is.
The Practical Test
If there is genuine uncertainty about whether a fracture meets the notification threshold, the practical answer is almost always to notify. A report that turns out not to have been required creates no regulatory difficulty. A failure to report an incident that the regulator considers should have been notified creates a much more significant concern — not just about the incident itself but about the governance culture that produced the decision.
Timing Matters
Where a fracture does meet the notification threshold, the report should be made without delay. In practice this means as soon as the immediate safety and welfare of the individual has been secured and the basic facts of the incident are understood.
Waiting for investigation outcomes, internal reviews, or safeguarding conclusions before notifying is not the correct sequence — the notification should be made first, with further information provided as it becomes available.
Delays attract scrutiny independently of the incident. A provider that notifies promptly demonstrates that governance systems are functioning. A provider that notifies weeks later, particularly where external agencies were already involved, raises questions that compound the original concern.
What CQC Is Really Assessing
When the Care Quality Commission receives a fracture notification, the injury is the starting point, not the endpoint. The regulator is examining the systems that surrounded the incident: whether the risk was known and appropriately managed, whether preventive measures were in place and followed, whether staff responded correctly in the immediate aftermath, and whether the provider has the capacity to learn from what happened.
A fracture that was genuinely unforeseeable and handled well demonstrates functioning governance. A fracture that follows a known risk, a failed risk assessment, or an inadequate care plan tells a different story — regardless of the clinical outcome for the individual.
The practical test is straightforward: if the incident leads you to ask whether it could have been prevented, it is almost certainly something the regulator expects to hear about.