Two Whistleblowers: The Pattern DHCW Cannot Explain
A senior role was created, filled, actively building a team — then eliminated after the holder was allegedly dismissed. The role reappeared at a lower grade. A second case followed. DHCW has never publicly addressed the pattern.
17 February 2026 · 7 min read
This article deals with Employment Tribunal claims that are currently pre-hearing. It is important to distinguish clearly between verified facts drawn from public records — NHS Jobs postings, organisational structures, Senedd transcripts — and allegations contained in tribunal filings that have not yet been tested in court. We make that distinction throughout.
What follows is not an account of individual grievances. It is an account of a structural pattern — one that DHCW has never publicly acknowledged and cannot easily explain.
The Chief DevOps Officer: A Timeline From Public Records
The following timeline is constructed entirely from publicly available NHS Jobs postings and organisational records.
October 2023: NHS Jobs publishes vacancy M9025-23-0222. The role is Chief DevOps Officer at Digital Health and Care Wales, Agenda for Change Band 9 (£101,000-£117,000). It reports to Sam Lloyd, then a senior director. This is a serious appointment — Band 9 is the second-highest banding in the NHS pay structure, reserved for roles with strategic organisational responsibility.
Late 2023 / Early 2024: The appointment is made. The exact date is not publicly recorded, but subsequent postings confirm the role was filled.
October 2024: NHS Jobs publishes vacancy M9025-24-0162. The role is Head of Software Engineering, Band 8c (£71,000-£82,000). The job description states that this role reports to the Chief DevOps Officer. This posting confirms two things: the Chief DevOps Officer was in post as of October 2024, and they were actively building a team beneath them. An organisation does not recruit subordinates for a role it intends to eliminate.
December 2024: The Chief DevOps Officer is allegedly dismissed. An Employment Tribunal claim is filed alleging unfair dismissal and whistleblowing detriment. The claim is currently pre-hearing.
2026: NHS Jobs publishes vacancy M9025-26-0007. The role is Senior DevOps Engineer — a downgraded replacement for the Chief DevOps Officer position. The banding is lower. The seniority is lower. The strategic scope is narrower.
These are facts. They are drawn from public job postings that anyone can verify. They are not allegations, and they do not depend on the outcome of any tribunal.
The Second Case
At least one additional senior employee has allegedly been dismissed from DHCW in circumstances connected to the raising of concerns. An Employment Tribunal claim has been filed. The case is pre-hearing, and fewer public details are available.
We note the existence of this second case not to make claims about its merits, but to establish that the Chief DevOps Officer's experience is not an isolated incident. When a pattern involves more than one person, it ceases to be a personnel matter and becomes an organisational question.
The Role Downgrade
The sequence of NHS Jobs postings tells its own story.
In 2023, DHCW decided it needed a Chief DevOps Officer at Band 9 — a role commanding a salary of £101,000 to £117,000, positioned at the strategic level of the organisation, reporting directly to a senior director. This was not a casual hire. It represented a judgement by DHCW's leadership that the organisation required senior DevOps capability.
By 2026, that judgement had been reversed. The replacement role — Senior DevOps Engineer — sits at a lower band, carries less authority, and has a narrower remit. The organisation did not simply lose a senior employee and replace them. It removed a senior employee and then downgraded the function they led.
This pattern has a specific organisational meaning. When a role is eliminated after its holder is removed, the message to the organisation is clear: the problem was not performance — it was the person. And when the role is recreated at a lower level, the message is clearer still: we want the function, but we do not want anyone with the seniority or authority to challenge us.
Whether or not this interpretation is correct in DHCW's specific case is a matter for the Employment Tribunal. But the pattern is visible to anyone who reads the job postings.
The Convergence With Level 3
The timeline of the Chief DevOps Officer's tenure converges with DHCW's broader programme failures in ways that demand attention.
October 2024: The Chief DevOps Officer is in post and actively recruiting a team. The Head of Software Engineering vacancy confirms they are building capability.
December 2024: The Chief DevOps Officer is allegedly dismissed.
January 2025: The CEO of DHCW appears before the Senedd's Health and Social Care Committee. She is unable to provide programme delivery timelines. She reveals that only 7% of GP practices are using electronic prescriptions — the organisation's most advanced programme.
March 2025: The Welsh Government imposes Level 3 escalation across DHCW's entire programme portfolio, citing systemic delivery failures.
The proximity of these events raises an obvious question: was the Chief DevOps Officer raising concerns about the very programme failures that became publicly undeniable within months of their departure? We do not know. That is a matter for the tribunal. But the timeline is suggestive, and DHCW has offered no public explanation.
What DHCW Does Not Publish
Most NHS organisations in the UK publish annual data on:
- Whistleblowing disclosures: How many concerns were raised, through what channels, and what actions were taken
- Disciplinary proceedings: Aggregate data on formal disciplinary actions
- Staff turnover and leavers analysis: Who is leaving, from which roles, and why
DHCW publishes none of this.
The absence of data is not neutral. If the Chief DevOps Officer's case and the second case are genuinely anomalous — if DHCW is, in general, an organisation that welcomes concerns and protects those who raise them — then publishing the data would demonstrate that. Whistleblowing numbers would show a healthy flow of concerns handled appropriately. Disciplinary data would show no pattern of action against those who speak up. Leavers analysis would show retention consistent with sector norms.
The fact that DHCW publishes none of this data, in circumstances where at least two Employment Tribunal claims allege whistleblowing-related dismissals, invites an inference that the data would not be reassuring.
This is not speculation. It is a statement about the evidential value of absence. When an organisation facing serious allegations about its treatment of whistleblowers chooses not to publish data that could exonerate it, the reasonable conclusion is that the data would not serve that purpose.
What We Are Not Saying
We are not saying that the Chief DevOps Officer or the second claimant will succeed in their tribunal claims. Those claims will be tested against evidence, and the tribunal will reach its own conclusions.
We are not saying that DHCW dismissed these individuals because they were whistleblowers. That is the allegation, not a finding.
What we are saying is this:
The public record shows that a senior role was created, filled, actively building a team, and then eliminated after the holder's departure — with the function subsequently recreated at a lower grade.
The public record shows that at least two Employment Tribunal claims have been filed by former senior employees alleging connections between their dismissals and the raising of concerns.
The public record shows that DHCW publishes no whistleblowing data, no disciplinary data, and no leavers analysis that would allow external scrutiny of how it treats those who speak up.
The public record shows that these events occurred in the same period as programme failures so severe that the Welsh Government imposed its highest level of intervention.
These facts form a pattern. DHCW has never publicly addressed that pattern. Until it does, the questions will remain.