The form was never the hard part
Every hospital could create a reporting form. What was missing was the system around it: a way to build trust, sustain participation, and make sure reporting continued to lead somewhere.
Why we built it
We kept watching good reports go nowhere.
Critical Signal was not built from a market gap. It was built by three people who ran patient safety programs inside veterinary hospitals, hit the same wall every time, and got tired of rebuilding the same workaround out of forms and spreadsheets.
Stronger signals. Safer teams. Better patient outcomes.
Read the transcript
This time, the patient was fine, but the signal was still there. Across all veterinary medicine, our teams catch these risks every day. Unfortunately, these usually go nowhere.
For years, we call these moments incidents, and we stood around and asked each other who was to blame.
I built Critical Signal to ask a different question. Why did these events happen and how do we learn from it? Because what matters most in that moment isn't the form. It's the person who spoke up.
A good catch can only happen when people feel safe to raise their hands and trust that observations don't result in blame. That's just culture, and it's why Nexus protects every person behind every observation, not just the data.
It's natural to ask what changed for the patient, but true safety means identifying what changed in the system, what caused the failure, not who. Look there and you can actually see and identify change and see that it helped.
And that's what Nexus does, it turns your team's signals into structured intelligence. An observation becomes a signal, signal becomes learning, and learning becomes change that you can actually measure.
Report, learn, support, and improve. Every signal deserves to be heard, and Nexus helps your team learn from it.
The moment
A safety culture is decided in about ten seconds.
Not in a policy or a mission statement on the lobby wall. It is decided in the ten seconds after someone says, “I think I gave that patient the wrong dose.”
What happens next matters
Nothing gets written down. Now watch what that moment does downstream. The technician learns that disclosure costs something. Three shifts later, a different person notices a mislabeled syringe and hesitates.
What kept happening
Capturing the signal was never the hard part.
Every hospital we worked in could capture a signal. What was missing was a reliable way to carry it through review, response, action, and learning. When that process stopped short, teams learned something from that too: speaking up did not necessarily lead to change.
Reports piled up faster than anyone could review them
One person often became responsible for the entire queue on top of a full clinical workload. Reports waited, follow-up slipped, and eventually people stopped submitting them. There was rarely a moment when the program officially failed. It simply faded out.
The reaction taught the next lesson
A technician who hears, “How did you let that happen?” learns something about the cost of speaking up. So does every person within earshot, and that lesson follows them into the next near miss, concern, or mistake.
Capturing signals did not make them useful
Signals could be collected, but they often remained siloed and difficult to explore. Answering a basic question about what was happening in our own hospitals meant exporting data, rebuilding it in spreadsheets, and doing the analysis ourselves.
What we decided to build
Close the loop, or do not start.
Critical Signal Nexus was built around one idea: capturing a signal is only the beginning. A safety program has to carry that signal through understanding, ownership, action, and learning, then bring that learning back to the people doing the work.
Speaking up has to be easy
If reporting takes too much time or asks for too much certainty, important signals disappear before anyone can learn from them.
Understanding matters more than labeling
A report should lead to context, contributing factors, and patterns, not just a category and severity score.
Someone has to own what happens next
Improvement cannot belong vaguely to “the team.” Someone needs to own what happens next, and there needs to be a clear point when the organization comes back to see whether it worked.
Learning has to return to the floor
If the people who speak up never see what changed, reporting begins to feel like a one-way transaction. Learning has to return to the team so they can see that raising a signal led somewhere.
What came next
So we built the system we wished we had.
Critical Signal Nexus was built around a simple idea: a report should start the patient safety process, not end it.
Nexus keeps the work connected after someone speaks up, helping teams move from an individual safety signal to understanding, accountable improvement, reassessment, and shared learning.
Not another place to collect reports.A system for carrying the work forward.