Category Archives: Cerner

Don’t fire staff before going live – lessons from a SAP project failure

By Tony Collins

When an NHS chief executive spoke at a conference in Birmingham about how he’d ordered staff cuts in various departments in advance of a patient administration system going live – to help pay for the new system – it rang alarm bells.  

This is because more staff are usually needed to cope with extra workloads and unexpected problems during and after go-live. That’s a lesson BT and CSC gradually learned from Cerner and Lorenzo go-lives under the National Programme for IT. It’s also a lesson from some of the case studies in “Crash”.

The trust chief executive who was making the speech was managing his go-live outside of the NPfIT. He didn’t seem to realise that you shouldn’t implement savings in advance of a go-live, that the go-live is likely to cost much more than expected, and that, as a chief executive, he shouldn’t over-market the benefits of the new system internally. Instead he should be honest about life with the new system. Some things will take longer. Some processes will be more laborious.

Bull-headed

If the chief executive is bull-headedly positive and optimistic about the new IT his board directors and other colleagues will be reluctant to challenge him. Why would they tell him the whole story about the new system if he’d think less of them for it? They would pretend to be as optimistic and gung-ho as he was. And then his project could fail.

Much of this I said when I approached the trust chief executive after his speech. It wasn’t any of my business and he’d have been justified in saying so. But he listened and, as far as I know, delayed the go-live and applied the lessons.

Disaster

Now a SAP project disaster in the US has proved a reminder of the need to have many extra people on hand during and after go-live – and that go-live may be costlier and more problem-laden than expected.

The Post-Standard reported last month that a $365m [£233m] system that was intended to replace a range of legacy National Grid’s payroll and finance IT has led to thousands of employees receiving incorrect payments and delayed payments to suppliers. Some employees were not paid at all and the company ended up issuing emergency cheques.

Two unions issued writs on behalf of unpaid workers, and the Massachusetts attorney general fined National Grid $270,000 [£172,500] for failing to comply with wage laws. New York’s attorney general subpoenaed company records to investigate.

Hundreds assigned to cope with go-live aftermath

National Grid spokesman Patrick Stella said the company has assigned hundreds of employees, including outside contractors, to deal with problems spawned by the new system. Many of them have been packed into the company’s offices in Syracuse in the state of New York. Others are dispersed to work at “payroll clinics,” helping employees in crew barns or other remote locations.

For more than a year National Grid worked to develop a new system to consolidate a patchwork of human resource, supply chain and finance programs it inherited from the handful of U.S. utilities it has acquired. The system, based on SAP, cost an estimated $365m, according to National Grid regulatory filings.

Stella said the glitches to be expected when a complex new system goes live were exacerbated in the wake of Sandy, when thousands of employees worked unusual hours at unusual locations. “It would have been challenging without Hurricane Sandy,” Stella said.

SAP software woes continue to plague National Grid.

Payroll blunder.

National Grid struggles to fix payroll problems.

Well done Eric Pickles – more open government to engulf councils

By Tony Collins

Few people have noticed but changes to the law next month could force councils to be much more open about big spending decisions including those that involve contracting out IT and other services.

It is a pity though that similar changes will not apply to the NHS.

The Local Government Association says that councils are already more open than Whitehall which is true.

Even so some councils are innately secretive about IT-related spending decisions, and discussions about projects that go wrong. Somerset County Council was notoriously secretive about its Southwest One joint venture with IBM in 2007. The deal has not made the expected savings and has consistently made losses. IBM claims the deal is a success.

Haringey Council’s “Tech refresh” project which went way over budget is another example. Evasive answers to opposition questions and meetings in secret were the norm.

Liverpool City Council was extraordinarily defensive and secretive about progress or otherwise on its Liverpool Direct Ltd joint venture with BT. The deal included giving BT control of IT.

Better public scrutiny

Now Local Government Secretary Eric Pickles has announced that changes to the law will mean that all decisions including those affecting budgets and local services will have to be taken in an open and public forum.

Ministers have put new regulations before Parliament that would come into force next month to extend the rights of people to attend all meetings of a council’s executive, its committees and subcommittees.

Pickles says the changes will result in greater public scrutiny. “The existing media definition will be broadened to cover organisations that provide internet news thereby opening up councils to local online news outlets. Individual councillors will also have stronger rights to scrutinise the actions of their council.

“Any executive decision that would result in the council incurring new spending or savings significantly affecting its budget or where it would affect the communities of two or more council wards will have to be taken in a more transparent way as a result.”

Councils will no longer be able to cite political advice as justification for closing a meeting to the public and press. Any intentional obstruction or refusal to supply certain documents could result in a fine for the individual concerned.

The changes clarify the limited circumstances where meetings can be closed, for example, where it is likely that a public meeting would result in the disclosure of confidential information. Where a meeting is due to be closed to the public, the council must now justify why that meeting is to be closed and give 28 days notice of such decision.

Chris Taggart, of OpenlyLocal.com, which has long championed the need to open council business up to public scrutiny, said

“In a world where hi-definition video cameras are under £100 and hyperlocal bloggers are doing some of the best council reporting in the country, it is crazy that councils are prohibiting members of the public from videoing, tweeting and live-blogging their meetings.”

These are the changes to be made by the  The Local Authorities (Executive Arrangements) (Meetings and Access to Information) (England) Regulations 2012 (the 2012 Regulations) which will come into force on 10 September 2012.

– Local authorities will have to provide reasonable facilities for members of the public to report council proceedings (regulation 4). This will make it easier for new ‘social media’ reporting of council executive meetings, opening proceedings to blogging, tweeting and hyper-local news/forum reporting.

– In the past council executives could hold meetings in private without giving public notice. From 10 September 2010 councils must give 28 days notice where a meeting is to be held in private, during which time people may make representations on why the meeting should be held in public. When the council wants to over-ride the notice period, it must publish a notice as soon as reasonably practicable explaining why the meeting is urgent and cannot be deferred (regulation 5).

– A document explaining the key decision to be made, the matter in respect of which a decision would be made, the documents to be considered before the decision is made, and the procedures for requesting details of those documents, has to be published (regulations 9).

– The new regulations create a presumption that all meetings of the executive, its committees and subcommittees are to be held in public (regulation 3) unless a narrowly-defined legal exception applies.

– Where the council has a document that contains materials relating to a business to be discussed at a public meeting, members of the local authority have additional rights to inspect such a document at least five days before the meeting (regulation 16). Previously no timescale existed.

– Where the council decides not to release the whole or part of a document to a member of an overview and scrutiny committee as requested by a councillor, it must provide a written statement to explain the reasons for not releasing such document (regulation 17).

– Documents relating to a key decision including background papers must be on the relevant local authority’s website (regulations 5, 6, 7, 9, 10, 14, 15, and 21).

Comment

Well done to Eric Pickles and the coalition. These are important and welcome changes. If council decision-makers know their discussions will be open to scrutiny they may give proper consideration to risks as well as the potential benefits of big IT-related investments. With inadequate scrutiny the potential benefits often drive decisions, which was the case with the flawed setting up of Southwest One. The press office at Liverpool City Council was so used to controlling information that its spokesman was outraged at questions we asked about its outsourcing venture with BT.

But what about the NHS?

It’s a pity the NHS is not subject to the new legal changes. Few trusts are open about their big IT-related investments; and when things go wrong, as has happened with some Cerner implementations, NHS trusts tend to lock all the doors, talk in whispers and instruct their press offices to issue statements that claim “teething troubles” have been largely addressed. The trust and everyone reading the statement know it is disingenuous but the facts to prove it are kept under wraps.

Organisations such as Imperial College Healthcare NHS Trust are taking decisions about major IT upgrades that could affect the safety, health and lives of patients without proper scrutiny. Pickles may want to mention his legal innovations to Andrew Lansley.

Eric Pickles announcement on opening up council discussions and decisions 

Cerner US-wide outage – what went wrong?

By Tony Collins

Hospital EMR and EHR has an account of what caused Cerner’s outage which affected its client sites across the USA and some international customers, according to reports.

It makes the point that the problem had little or nothing to do with the cloud.

The Los Angeles Times reports that within minutes of the outage, doctors and nurses reverted to writing orders and notes by hand, but in many cases they no longer had access to previous patient information saved remotely with Cerner.

“That information isn’t typically put on paper charts when records are kept electronically,” said the newspaper which quoted Dr. Brent Haberman, a pediatric pulmonologist in Memphis as saying, “If you can’t get to all the patient notes and all the previous data, you can imagine it’s very confusing and mistakes could be made…A new doctor comes on shift and doesn’t have access to what happened the past few hours or days.”

Hospital EMR and EHR

Some hospitals cope well through the outage

Some lessons from a major outage

By Tony Collins

One of the main reasons for remote hosting is that you don’t have to worry about security and up-time is guaranteed. Support is 24x7x365. State-of-the-art data centres offer predictable, affordable, monthly charges.

In the UK more hospitals are opting for remote hosting of business-critical systems. Royal Berkshire NHS Foundation Trust and Homerton University Hospital NHS Foundation Trust are among those taking remote hosting from Cerner, their main systems supplier.

More trusts are expected to do the same, for good reasons: remote hosting from Cerner will give Royal Berkshire a single point of contact to deal with on technical problems without the risks and delay of ascertaining whether the cause is hardware, third party software or application related.

But what when the network goes down – across the country and possibly internationally?

With remote hosting of business-critical systems becoming more widespread it’s worth looking at some of the implications of a major outage.

A failure at CSC’s Maidstone data centre in 2006 was compounded by problems with its recovery data centre in Royal Tunbridge Wells. Knock-on effects extended to information services in the North and West Midlands. The outage affected 80 trusts that were moving to CSC’s implementation of Lorenzo under the NPfIT.

An investigation later found that CSC had been over-optimistic when it informed NHS Connecting for Health that the situation was under control. Chris Johnson, a professor of computing science at Glasgow University, has written an excellent case study on what happened and how the failure knocked out primary and secondary levels of protection. What occured was a sequence of events nobody had predicted.

Cerner outage

Last week Cerner had a major outage across the US. Its international customers might also have been affected.

InformationWeek Healthcare reported that Cerner’s remote hosting service went down for about six hours on Monday, 23 July. It hit “hospital and physician practice clients all over the country”. Information Week said the unusual outage “reportedly took down the vendor’s entire network” and raised “new questions about the reliability of cloud-based hosting services”.

A Cerner spokesperson Kelli Christman told Information Week,

“Cerner’s remote-hosted clients experienced unscheduled downtime this week. Our clients all have downtime procedures in place to ensure patient safety. The issue has been resolved and clients are back up and running. A human error caused the outage. As a result, we are reviewing our training protocol and documented work instructions for any improvements that can be made.”

Christman did not respond to a question about how many Cerner clients were affected. HIStalk, a popular health IT blog, reported that hospital staff resorted to paper but it is unclear whether they would have had access to the most recent information on patients.

One Tweet by @UhVeeNesh said “Thank you Cerner for being down all day. Just how I like to start my week…with the computer system crashing for all of NorCal.”

Another by @wsnewcomb said “We have not charted any pts [patients] today. Not acceptable from a health care leader.”

Cerner Corp tweeted “Our apologies for the inconvenience today. The downtime should be resolved at this point.”

One HIStalk reader praised Cerner communications. Another didn’t:

“Communication was an issue during the downtime as Cerner’s support sites was down as well. Cerner unable to give an ETA on when systems would be back up. Some sites were given word of possible times, but other sites were left in the dark with no direction. Some sites only knew they were back up when staff started logging back into systems.

“Issue appears to have something to do with DNS entries being deleted across RHO network and possible Active Directory corruption. Outage was across all North America clients as well as some international clients.”

Colleen Becket, chairman and co-CEO of Vurbia Technologies, a cloud computing consultancy, told InformationWeek Healthcare that NCH Healthcare System, which includes two Tampa hospitals, had no access to its Cerner system for six hours. The outage affected the facilities and NCH’s ambulatory-care sites.

Lessons?

A HIStalk reader said Cerner has two electronic back-up options for remote hosted clients. Read-only access would have required the user to be able to log into Cerner’s systems, which wouldn’t have been possible with the DNS servers out of action last week.

Another downtime service downloads patient information to local computers, perhaps at least one on each floor, at regularly scheduled intervals, updated say every five minutes. “That way, even if all connection with [Cerner’s data centre] is lost, staff have information (including meds, labs and more) locally on each floor which is accurate up to the time of the last update”.

Finally, says the HIStalk commentator, “since this outage was due to a DNS problem, anyone logged into the system at the time it went down was able to stay logged in. This allowed many floors to continue to access the production system even while most of the terminals couldn’t connect.”

But could the NHS afford a remote hosted service, and a host of on-site back-up systems?

Common factors in health IT implementation failures

In its discussion on the Cerner outage, HIStalk put its finger on the common causes of hospital IT implementation failures. It says the main problems are usually:

– a lack of customer technical and implementation resources;
– poorly developed, self-deceiving project budgets that don’t support enough headcount, training, and hardware to get the job done right;
– letting IT run the project without getting users properly involved
– unreasonable and inflexible timelines as everybody wants to see something light quickly up after spending millions; and
– expecting that just implementing new software means clearing away all the bad decisions (and indecisions) of the past and forcing a fresh corporate agenda on users and physicians, with the suppplier being the convenient whipping boy for any complaints about ambitious and sometimes oppressive changes that the culture just can’t support.

Cerner hosting outage raises concerns

HIStalk on Cerner outage

Case study on CSC data centre crash in 2006

Will health IT market “heat up” when NPfIT contracts expire?

By Tony Collins

At a second-quarter earnings call, Marc Naughton, Chief Financial Officer at US-based health software supplier Cerner, singled out the UK as one country where there will be probably be “a lot of demand” for new health IT products and services subject to capital being available.

He said,

“As more and more of those trusts are becoming foundation trusts, which means they control their capital outlet – outlay as opposed to the government putting the dollars out there – we think that’s going to turn into a more normalised US-type market where each trust is going to go out to the market and look to acquire technology.

“In 2015, the current NHS [NPfIT] contracts expire. So almost all of those trusts are going to be looking in the market in some form or fashion, probably depending on their access to capital.

“So we think that market is one that could heat up in 12 to 18 months from now, assuming that they can get access to capital. But it is going to be a little bit lumpy.”

 

Cancer waits mix-up – how concerned is the Trust?

By Tony Collins

When a passenger jet crashes, if the airline’s next board meeting barely mentions it, and instead discusses a catering award and a staff survey, those booked on flights with the airline may have cause for concern.

So should patients at Imperial College Healthcare Trust be concerned that the trust has not mentioned in its latest published board papers a blunder that led to the Trust’s losing track, for nearly a year, of hundreds of patients with possible cancer?

The Department of Health requires that patients who go to their GP with symptoms that may indicate cancer are seen by a specialist within a maximum of two weeks.

Records incomplete

But Imperial has lost track of an unknown number of patients who went to their GPs with signs of possible cancer. It has been checking 900 hospital records which it found were incomplete.

For some of the patients the blunder won’t matter:  they will have been called by staff at GP practices, some of whom have systems that track patients under the two-week rule.

But some patients might have slipped through the net and not been alerted by Imperial to their urgent appointments. Imperial has no clear idea how many.

It has asked GP organisations for help in contacting patients, their carers or representatives, to‘ascertain whether the patient has received treatment or still requires treatment’”.

What detail has emerged on the problem has come not from Imperial but from NHS North West London which is a single management team that represents eight PCTs.  NWL  covers St Mary’s Hospital, Paddington, Hammersmith Hospital and Charing Cross Hospital, which are all managed by Imperial.

“Substantial concern”

NWL has what it calls “substantial concern” about the problems at Imperial. In addition to the problem reporting its two-week cancer waits, the Trust is trying to clear a backlog of patients who have waited more than 18 weeks from referral to consultant-led treatment.

“Systematic failings”

NWL executives report that Deloitte has carried out an external audit and “concerns remain about record keeping at Imperial”.  The executives say that “systematic failings” have been identified which will take time to resolve. This issue will be given close attention in the coming year, says NWL.

Patient safety an issue?

NWL also says that a “Clinical Review” is being carried out and a panel is being set up to look at the clinical issues that have arisen at Imperial. “The Director of Nursing confirmed that the clinical review would look at all patients affected by the problems at Imperial …”

In contrast to the concerns about Imperial’s performance among London PCTs, Imperial seems a little surprised that we are even investigating the problems.

“The problems are administrative and nothing to do with IT,” said a spokesperson.

The Trust is right. The problems are nothing to do with IT.  And yet the problems may be everything to do with IT. Appointments for patients with possible cancer have not been entered onto IT systems – and where they have, data has been incorrect, entered into duplicate records, or not followed up to check appointments were kept, or the patient seen for treatment and investigations.

Eye off the ball?

For nearly a year the problem was not spotted, which has left some North West London executives wondering how it could have happened. It is known the Trust has devoted time and attention of senior management to a replacement of existing systems with Cerner, under the National Programme for IT.  Has the Trust taken its eye off the ball while making plans for Cerner?

Some working in the NHS may ask whether it was more important for the Trust to have ensured that appointments for possible cancer were entered correctly onto existing systems, and routines written into software to provide alerts when cancer records were not closed off, or were incomplete.

**

Below are some of the comments of NWL PCTs about Imperial’s problems. Their concerns raise questions about whether the Trust’s processes and administration are stable enough for a transition from existing IT to new systems, which could cause further disruption.

These are some NWL statements in its board papers relating to Imperial:

“It was reported that at Imperial, the calculations of the backlog of referrals had been completed and work is underway to clear the backlog. However Deloitte has carried out an external audit and concerns remain about record keeping at Imperial. Systematic failings have been identified which will take time to resolve. This issue will be given close attention in the coming year.

“A Clinical Review is being carried out and a panel is being set up to look at the clinical issues that have arisen. The Director of Nursing confirmed that the clinical review would look at all patients affected by the problems at Imperial …”

Does NWL always trust what Imperial says?

Jeff Zitron [Chair, NHS NW London, Inner & Outer NWL Sub Clusters] said that the Board needs evidenced assurance that the issues that have arisen at Imperial and North West London Hospitals are being adequately addressed.

**

“Trish Longdon [Vice-chairman, NHS North West London Cluster Board] noted that although the Imperial targets were shown as ‘Green’  this does not reflect the true position. This was agreed and it was noted that they were in fact being treated as if they were Amber.”

“Urgent meeting”

“The Chairman asked for an update on the situation at Imperial College Healthcare Trust which had been the subject of substantial concern at the last INWL Inner North West London NHS] Board meeting. The INWL Board had agreed that an urgent meeting should be held with the Chairman and Chief Executive of Imperial, involving the CCG Chairs, the Tri-Borough Cabinet Members for Health, himself and Anne Rainsberry [Chief Executive North West London Cluster]. This was taking place later that day.”

Clinical harm?

“ Following investigation of Serious Incidents in May 2011, ICHT [Imperial College Healthcare NHS Trust] is unable to provide sufficient assurance of robust data quality in regard to reported performance for 18 weeks RTT [Referral To Treatment], cancer waiting times and the elective waiting list.

The Trust board have approved a reporting break until end of June 2012 which has been agreed by the Cluster in conjunction with NHS London. To ensure due diligence, an independent audit of waiting list management across all specialities has been undertaken and a set of recommendations made.

“ICHT continue to provide shadow reports to NHS NWL during this period with weekly reporting. Some evidence of improved performance management is observed. However this is not yet consistently embedded Trust- wide and clearance of the current backlog of patients is not at sufficient pace to meet the agreed trajectory…

“A clinical review will be undertaken to ensure that patients have not experienced harm due to an elongated wait.”

**

“Anne Rainsberry [Chief Executive North West London Cluster] referred to a range of discussions taking place on Imperial’s performance issues, focussing on the backlog of the Referral to Treatment waiting lists which had resulted in a reporting break being granted.

“Work was concluding at the end of April [2012] to reduce the original backlog of patient cases and enable reporting systems to get back on track in June. A clinical review had also started to determine if any risks to patients had arisen due to the delays. The review findings would be brought back to the Board…

“Anne Rainsberry referred to a meeting she had attended with the Department of Health to review Imperial‟s approach to resolving these issues.”

Big organisational challenge

“Simon Weldon [Director of Commissioning and Performance, North West London Cluster Board] … asked the NWL Board to be aware of the enormity of the organisational challenge facing Imperial and that remedial actions would take time to take effect.”

Imperial responds

Campaign4Change put it to Imperial College Healthcare NHS Trust that there is nothing in its latest published board papers to show the trust is concerned about the problems relating to cancer waits and lost appointments. We said that PCT papers referred to  “substantial concern” but there was nothing similar in Imperial’s latest published papers. We let Imperial know we would be asking the question: how concerned is Imperial about the confusion over cancer waits?

This was the reply of Imperial’s spokeswoman (in full)

“The safety of patients is our absolute priority. Our Trust is taking the issues involved in the current situation very seriously and at all times the well-being of the patients we serve is foremost in our minds.

“We acknowledge that some patients may have been caused additional pain and anxiety associated with a prolonged wait for diagnosis and treatment and worked to address the problem as robustly and quickly as possible.”

Separately, in May 2012, Imperial told us that it was in the process of validating 900 patient records that indicate that a patient might have been waiting longer than two weeks.

At that stage it had closed more than 400 of the 900 records “as the majority indicated that patients have either received or are receiving treatment, or that the patient did not attend their appointment and their GP had advised there was no need for further follow up”.

The spokeswoman said “To date our investigations have found no suggestion that any delay in treatment has caused a patient to come to serious harm.”

She said “This is not an IT issue, but an administrative issue related to the physical input and extraction of data from patient records. It is entirely unrelated to IT systems.”

Comment

It is extraordinary that Imperial is seeking to replace existing systems when it is organisationally in a questionable state. Simon Weldon, Director of Commissioning and Performance, North West London Cluster Board, referred to the “enormity of the organisational challenge facing Imperial”.

Under the NPfIT, a number of implementations of Cerner at several NHS sites have gone badly wrong – and they did not have Imperial’s problems before going live. It would be common sense for Imperial to get its data accurate and its management processes and checks reliably in place before attempting a major switch of IT systems.

Two other things are particularly worrying: Imperial appears not to concede in public it has any major problems, and it appears to separate IT from administration.

Having the best IT in the NHS is of limited value if important parts of the Trust are in a state of administrative disorder.  If data is unreliable, incomplete and inaccurate, and solid processes are not in place to ensure that the correct data is entered into systems when it needs to be entered, and routines are not in place to provide alerts and follow-ups, costly hardware and software may not compensate. Is this an IT issue or not? Does that matter?

We would not like to see a Cerner NPfIT debacle similar to the ones at Barts in London, Royal Free Hampstead, and at hospitals in Oxford, Milton Keynes, Weston-super-Mare, Morecambe Bay, Worthing and Bristol.

But is Imperial particularly concerned? Is it in denial over the seriousness of its problems? Why is it reporting its position at Green when North West London NHS regards its position as Amber? Why do its latest published board papers not mention its problems tracking patients under the two-week rule? Is the Trust so preoccupied with replacing its existing systems with Cerner that it is not doing the basics well?

One specialist in the NHS said: “If the Trust wasn’t spending so much time and effort doing the Cerner deployment then maybe they would have concentrated its scarce resources on performing the  job of managing patients.”

Accountability for failure in the NHS is poor to non-existent. So will Imperial be able to do what it wants regardless?

Troubled Cerner NPfIT go-lives, so far:

Barts and The London

Royal Free Hampstead

Weston Area Health Trust

Milton Keynes Hospital NHS Trust

Worthing and Southlands

Barnet and Chase Farm Hospitals NHS Trust

Nuffield Orthopaedic

North Bristol.

St George’s Healthcare NHS Trust

University Hospitals of Morecambe Bay NHS Foundation Trust

Birmingham Women’s Foundation Trust

NHS Bury

*We acknowledge Pulse which broke the story on Imperial’s cancer wait problems.

GPs asked to contact hundreds of patients who may have missed treatment after hospital’s cancer referrals blunder  – Pulse

London LMCs alert over Imperial cancer waits mix-up – Pulse.

GPs kept in the dark over hospital cancer blunder – Pulse

Other links:

Halt NPfIT Cerner deployments says MP Richard Bacon

Bacon calls for halt on Millennium.

Cerner system “too entrenched to be scrapped”

By Tony Collins

A report by Deloitte on problematic Cerner installations at some hospitals in Australia calls for the government to appoint a chief medical information officer to oversee computer projects across the State.

The Deloitte report is a reminder that new IT in hospitals can have good – and adverse – safety implications for patients.

Obtained by the Sydney Morning Herald under Australia’s Freedom of Information Act, the Deloitte report is said to accept complaints last year that the system put patients’ health at risk by providing insufficient alerts to clinicians when messages did not reach their destination.  Deloitte found no evidence of harm to patients.

Though the Deloitte report is specific to the Cerner “FirstNet”  system as installed at some emergency departments in New South Wales, the idea of a chief medical information officer is arguably a good one for the UK where the Department of Health’s CIO (currently Katie Davis, interim Managing Director, NHS Informatics) is not responsible for the medical implications of IT go-lives in NHS hospitals.

New systems bypass the sort of regulation that helps protects the public against harm from medical devices. After hospital IT disasters there is no requirement for a genuinely independent investigation, as happens after airline crashes.

The Sydney Morning Herald [SMH] reports Deloitte as saying that the FirstNet system, which was installed to help run emergency departments across New South Wales, is chronically underfunded.

Deloitte was asked to report on the system after some hospital staff last year lost confidence in the software and returned to manual record-keeping.

Despite continuing problems and excessive time spent on data entry, the FirstNet system is too entrenched to be scrapped and the government should instead invest in bringing it up to scratch, said Deloitte.

”With some exception, FirstNet reporting is inadequate for effective governance of [emergency department] operations,” said Deloitte as reported by the SMH.

Nurses and doctors had complained that the system increased the amount of time they spent at a screen and reduced contact with patients. But the Deloitte report said more time spent on data entry ”was essential to realise the eventual benefits of an eventual [electronic medical record]”, such as greater accuracy of test results and medicine orders.

Upgrades were improving safety at some hospitals but needed to be across the state.

The government should appoint a chief medical information officer to oversee computing projects across the state, and pay for continuing development and training for FirstNet, said Deloitte.

The Health Minister, Jillian Skinner, said clinicians did not want to scrap FirstNet because they didn’t “want to start anew”.

The list of hospitals that have had serious problems after IT installations is growing, in part because the increasing use of technology in healthcare. Though hospital staff tend to learn in time to manage new systems, the unanswered question is whether patient care and treatment – and potentially their health and safety – should be damaged in an unregulated way until the problems are solved or mitigated.

Below is the UK list where it is known that the installation of new IT has caused serious disruption.  Any effect on individual patients has gone unreported:

Barts and The London

Royal Free Hampstead

Weston Area Health Trust

Milton Keynes Hospital NHS Trust

Worthing and Southlands

Barnet and Chase Farm Hospitals NHS Trust

Nuffield Orthopaedic

North Bristol.

St George’s Healthcare NHS Trust

University Hospitals of Morecambe Bay NHS Foundation Trust

Birmingham Women’s Foundation Trust

NHS Bury

**

Links:

Does Hospital IT need airline-style certification?

Hospital computer system found lacking – Sydney Morning Herald

Jon Patrick’s essay on the effectiveness and impact of Cerner’s FirstNet system in some hospitals in New South Wales.