The December 2022 issue of IEEE Spectrum is here!

Close bar

The Financial Times of London published a story late yesterday saying that CSC, which holds a £3.3 billion  National Health Service (NHS) contract to supply two-thirds of England with an electronic health record (EHR) system based on the iSoft Lorenzo EHR system, is "on the brink of being fired" from a large portion of its NHS contract.

In April 2009, the  NHS gave both CSC and BT (which supplies EHR systems to the London region) a deadline of 31 March 2010 to get their EHR offerings installed and operating with minimal problems at a large, acute-care NHS Trust hospital.  If  they could not, the NHS would look at its "alternatives" such as letting acute-care hospitals choose their own EHR supplier instead of having to use the NHS mandated supplier.

BT successfully installed its Cerner-based EHR system at Kingston Hospital by the due date, but CSC missed its installation deadline at the Morecambe Bay NHS Trust’s hospitals. According to this story in ComputerWeekly, that even though CSC's drop-dead delivery deadline looks like it has been pushed back into late April, the company may not be able meet that date either.

Christine Connelly, NHS's chief information officer, said that if CSC doesn't deliver soon, the NHS has the option of canceling part of CSC's contract that has to do with providing EHR systems to acute-care hospitals. That would cost CSC about £1 billion, as well as place the whole £12.7 billion UK national EHR effort at risk..

Early last month, CSC defended its National Programme for IT efforts in an interview with ComputerWorldUK.  Andrew Spence, UK healthcare strategy director for CSC, claimed that the company was "ruthlessly focused" on delivering a working EHR system to Morecambe Bay.

In fact, just a few weeks ago, CSC's EHR supplier iSoft claimed in an eHealth Insiderarticle that it was "on track"  to deliver as required at Morecambe Bay by yesterday.

Seems both companies have a lot of explaining - or excuse making - to do.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less