The Societal Impact of Badly‑Organised TidyTuesday on the NHS
The Societal Impact of Badly‑Organised TidyTuesday on the NHS
By Hannah Miskell – The Daily Code‑Citizen
When data scientists in Oakland decided to give the world a “weekly tidy‑up” of open‑source datasets, they didn’t anticipate a national health crisis. A week after the 12th sprint of badly‑organised TidyTuesday, the NHS has been running a new specialty: Data‑Driven Chaos Busters.
1. The Emergency Response Team
The National Health Service has quietly set up a dedicated desk for dealing with the aftermath of randomised. “We’ve got a queue of spreadsheets that somehow claim the ‘Mortality Rate 2.0’ is still rising despite the pandemic being in 2050,” says Dr. Emma Cadwell, lead of the new “Strategy and Interpretability” unit (previously known as the Emergency Ward). “We’re not sure whether the trend is a mistake in the data or an actual surge in bad coding practices.”
The team’s mission: decide which plots are legitimate and which should be relegated to a “Throw‑away‑on‑Park” bin – a literally named bin at the back of the IT department. “We’ve had to start using Ouija boards in the office,” admits one coder, voice not revealed for fear of being caught in the wrong spreadsheet.
2. Twitches and Mis‑plots
When a TidyTuesday club from Manchester posted a dataset on “the mysterious rise of nosy neighbours”, the response was immediate. “I thought this chart was about neighbours, but it turned out to be a line graph of how many people enjoyed having a banana in their teacup on Tuesdays!” giggled Jane, a junior palliative‑care nurse who has spent the last two days crying into her coffee.
The hospital has begun to schedule “Data‑vs‑Reality” days, where staff sit in a circle and compare raw data to what the patient actually needs – that is, actually.
3. The Spring Cleaning of the NHS
The introduction of a WhatsApp group called “untidy” has seen doctors swapping garbled code for memes, but not all is lost. In one bright corner of the East London fold, a team discovered that a poorly‑labelled regression analysis on “The Impact of 1% off‑label aspirin” actually contained clues to a dormant outbreak of S. aureus in the hospital’s fridge.
“We’re calling this our ‘Data Detective Unit’,” says NHS spokesperson Mr. (simply called) Brian, who has only ever been involved in staffing when the staff have expressed intrigue about Rangers/Man U. “We’re on the case. We’ll investigate, call in the detectives – maybe the Department of Data and Analytics’ Detective Division.”
4. A Borrowed Happy Hour
In order to stop the spread of software errors, the NHS has begun a coffee‑break programme. Snobs of dryness (the NHS Connectors dott in<olak) buy a cup, each coming with a QR‑code linked to a supposedly "tidy" table. They then break into mutterings like, “I think this data is poorly cleaned – it's a syntax error!” next to the fluorescent lights that flicker in the off‑hour.
5. Policy-upwards and Check‑In
A budgetary beacon popped up the next day, with a committee dabbling in what it needs to be spending on “Data‑Innovation”, “Data‑Integrity”, and, oddly, “Pint‑size corner solutions for night shift frustration.” The noticed that, in repeating TidyTuesday’s disorganised nature, a new generation of squad‑fighting staff might discover new code-breaking worlds peaking under charters: Scripto‑Mancerism.
Probably, the biggest silver lining is that, because of the chaotic TidyTuesday drives, NHS staff now feel a lot more in sync with their favourite part of the data‑science process: being a bit unguided, unscripted, unpredictable. And in the words of Dr. Cadwell: “They might need simple charts after all, not the tidy tabula‑replica of 2011. #DataNow."
Hannah Miskell works for The Daily Code‑Citizen and does not recommend coding over tea.
