New Zealand’s $16 Billion Public Health System Runs on a Single Excel Sheet

This is a note for Future John: New Zealand’s $16 Billion Public Health System Runs on a Single Excel Sheet.

From the report:

Notably, one major issue was through a significant reliance on the use of an Excel file to manage the consolidated financials of the organisation. This spreadsheet was the primary data file used by HNZ to manage its financial performance. It consolidated files from each district into a single spreadsheet, and key reports, such as the monthly finance report, were produced from it. The use of an Excel spreadsheet file to track and report financial performance for a $28bn expenditure organisation raises significant concerns, particularly when other more appropriate systems are present on the IT landscape.

This Excel file is flawed in that:

  • Financial information was often ‘hard-coded,’ making it difficult to trace to the source or have updated data flow through.
  • Errors such as incorrectly releasing accruals or double-up releases were not picked up until following periods.
  • Changes to prior periods and FTE errors in district financial reporting Excel submissions, would not flow through to consolidated file.
  • The spreadsheet can be easy to manipulate information as there is limited tracking to source information where information is not flowing directly from accounting systems.
  • It is highly prone to human error, such as accidental typing of a number or omission of a zero.

The cumbersome process of collecting data also meant monthly financial reporting usually took 12-15 days to consolidate and 5 days to analyse. Adding to that the time associated with the creation of the monthly finance reports and circulation of these to the Board, there was an inevitable challenge of obtaining real-time financial information from one source of truth.

Voyager bug fix

This is too cool. A core dump then binary patch to work around memory hardware failure 15 BILLION MILES AWAY: How NASA Fixed a Software Bug 15 BILLION MILES AWAY | Voyager 1

Arduino Keyboard library not working on Debian KDE

Man, I just spent quite a bit of time diagnosing this particular issue.

The problem was that my Symbol Keyboard stopped working. This is a USB keyboard I made from an Arduino Leonardo. The touch screen was working okay, but the keypresses weren’t being delivered over USB.

Long story short, the 7-port USB 3.0 hub attached to my workstation needed rebooting! I disconnected the power supply and disconnected the upstream USB cable to remove both sources of power, then when I reconnected everything my stuff started working again, including my symbol keyboard.

Lesson learned: if you’re debugging a USB device failure try plugging the device directly into the host to avoid any potential issues caused by your hub(s).

It was lucky I had a spare 104-key USB keyboard in the cupboard because I needed one while diagnosing this issue (the Windows box I was using only has a tenkeyless 87-key keyboard plugged into it but the Windows alt-key codes require use of the number pad).

The latest incarnation of my symbol keyboard looks like this:

John's symbol keyboard