My teenage son is becoming quite the proficient coder. Recently, we were talking about one of the basic ideas behind programming: “if this, then that.” The logic is pure and binary: if this happens, then do that.
It sounds wonderfully simple. Medicine, of course, rarely works like that. This feels particularly true when assessing an unwell child. Children do not present in clean lines of code. Families do not move through tidy algorithms. Risk can appear not only in the handover between clinicians, but in the gaps between what each of us sees, knows and assumes.
I was recently involved in developing the Irish College of GPs Paediatric Sepsis General Practice Update. This Irish national GP-focused educational resource was developed in collaboration with colleagues from general practice, paediatric emergency medicine, intensive care and the National Clinical Programme for Sepsis.
On the face of it, we were writing a document. What we were really doing was bringing different perspectives into the same space, in a way we don’t always get to achieve in clinical practice. The GP sees a ten-minute snapshot of an unwell child. The paediatric emergency clinician receives the referral. The intensivist pre-empting the worst-case scenario. National programme colleagues are thinking about consistency and implementation. Each perspective brings a different question, a different threshold, a different kind of expertise.
Each of those questions is valid. None is complete on its own. That is the idea I keep coming back to. No single speciality sees the whole journey.
This realisation is crucial in paediatric sepsis, where the early picture is often uncertain. We want to recognise the child who may be seriously unwell without treating every acute infection as sepsis. We want clear escalation, but not unnecessary panic. We want safety-netting, but not as a substitute for escalation. We want guidelines, but we also need clinical judgment when the child in front of us does not fit neatly within them.
This exercise was not about one speciality teaching another. It was about recognising that each part of the system holds expertise that the others do not.
Shared learning does not mean asking one group to explain itself to another. It means creating enough trust to let different perspectives challenge and sharpen the work.
That was the real value of the process. The conversation mattered at least as much as the outcome and, most importantly, it brought a stronger result.
Like a computer programme that becomes more than the lines of code behind it, the final resource was stronger because different people had written, tested, challenged and refined it from different angles. The same is true for clinical care.
Children do not move through healthcare in neat, speciality-shaped blocks. They move through relationships, conversations and handovers. The story changes as they move. Sometimes the diagnosis becomes clearer. Sometimes the concerns become more acute. Sometimes the most important information is not a number, but an intuition that “this illness is different.”
Shared learning helps us sit with that uncertainty without dismissing it. It enables us to pass on our thoughts in a way that makes sense to the next person.
The “if this, then that” thinking of one clinician can be very useful. But we often need something broader: if this happens here, what might it mean there? If we ask this question now, what might it add to the story later? If a parent is worried, how do we make sure that concern is heard?
Our job is not only to do our own part well, but to know what value it adds, and how it works alongside the parts written by others.
Not just “if this, then that,” but “if this, then what next?”
