Category Archives: openness and transparency

Has DWP lost £400,000 worth of Universal Credit studies it commissioned?

By Tony Collins

On 12 March 2012, Chris Grayling, a minister at the Department for Work and Pensions, published a list of the DWP’s consultancy contracts.

Soon afterwards the question was asked: has the DWP published any of the consultants’ reports – nearly 50 of them commissioned from companies that included PricewaterCoopers, Atkins, Capgemini, IBM, Compass,  KPMG, Deloitte, Xantus, Gartner and Tribal?

No, said the DWP.

So I made an FOI request for two of the reports, on Universal Credit:

– Universal Credit Delivery Model Assessment Phase 1 and 2, and

– the Universal Credit End to End Technical Review.

The DWP could not find them. It didn’t even have a record of them.

Julie Kitchin, Senior Business Partner Operations at the DWP’s Financial Control Directorate, Risk Management Division at Leeds, said she requested a “thorough search of the Universal Credit Programme document library”.

And …

“Universal Credit Colleagues have confirmed that the Department does not hold documents with these titles or under these names.”

But Chris Grayling, a DWP minister, told the House of Commons that the reports exist. His written answer on 12 March 2012 referred to:

Universal Credit End to End Technical Review IBM £49,240
Universal Credit Delivery Model Assessment Phase 2 McKinsey and Partners £350,000

Julie Kitchin said she would check again and reply within 20 working days. “In the light of the additional information you have provided, I have asked the Universal Credit Programme to conduct a further search for the reports you have highlighted. ”

Comment:

Since the FOI Act came into force on 1 January 2005, the DWP has at no point granted any of my FOI requests or appeals. Its replies could be modelled on electronic birthday cards that play the same automated message every time you open them.

Perhaps the DWP could be the first department to use software to generate FOI replies without human involvement.

DWP hides already published Universal Credit report.

Chris Grayling’s written answer on DWP’s consultancy contracts

Millions of pounds of secret DWP reports

Lessons from an IT disaster

By Tony Collins

Only rarely is an independent report on an IT-related disaster published.  So North Bristol NHS Trust deserves credit for publishing a report  by Pricewaterhousecoopers into the problematic go-live of Cerner Millennium in December 2011.  PwC calls the Cerner system a “business-critical patient record system”.

The implementation, says PwC,  resulted in significant continuing  operational difficulty. PwC was asked to review the implementation, identify what went wrong and make recommendations.

What is clear from PWC’s report is that North Bristol NHS Trust repeated the known mistakes of other trusts that had gone live with Cerner Millennium:

–          A lack of independent challenge

–          Not enough testing of the system and new business processes

–          Inadequate contingency arrangements

–          Not enough time for data migration

–          Training systems not the same as those to be used

–          Preparations treated as an IT project, not a change programme.

–          Differences between legacy and Cerner systems not fully understood before go live

–          Staff did not always understand new or changed business processes

In 2007 the National Audit Office reported in detail on the lessons from the go-live of Cerner Millennium at Nuffield Orthopaedic Centre, Oxford in December 2005.

One of those lessons was that the Trust did not learn lessons from earlier NPfIT Cerner Millennium go-lives. This happened again at North Bristol, suggests the PwC report:

“There were not dissimilar Cerner implementations within the Greenfield [other ex-Fujitsu and now BT-managed Cerner Millennium implementations under the NPfIT] systems running a few months before NBT’s [North Bristol Trust] implementation. Similar difficulties were experienced there, but they were more successfully addressed.”

Below are extracts from PwC’s report “Independent review of Cerner Millennium implementation North Bristol NHS Trust”.

“The success of an implementation of this scale, complexity and timing depends on substantial, robust and enduring programme management focusing on:

–          The IT implementation. Incorporating configuration of Cerner Millennium, infrastructure, security, interfaces and testing;

–          The migration of data from the two legacy PAS systems into Cerner Millennium;

–          Change management to engage and train stakeholders, embed change in the organisation and ensure that processes and procedures are aligned to the new system;

–          Continuous communication with users about changes to business processes as a result of the implementation; and

–          Quality control criteria and the association governance to ensure that go-live went ahead in a safe and sustainable manner.

–          The Trust needed stringent programme management with programme and project managers of the highest quality, to ensure that effective governance and project planning procedures were followed.

–          The go-live decision and assurances needed to pass strict criteria with sufficient evidence to provide assurance to the board that all necessary activities were completed prior to go-live.

The implementation in both the wards and the Emergency Department (ED) went well. Staff in ED were well engaged in the project and as a result were fully aware of the changes to their business processes at go live. There were some minor system issues initially but these were resolved quickly and ED was fully operational with Cerner Millennium soon after go live. One of the underlying factors in the success of the deployment to ED was that there was no data migration required as the historical data remains in the old system.

The launch in the wards went as expected; the functionality was tested well and the data was loaded manually, although there now appear to be issues with staff engaging and using the system as intended.

The majority of problems encountered at go live related to the theatre and outpatient clinic builds.

Outpatients had the most disruption immediately after go live. The Trust’s back office team had not finished building the outpatient clinics in Cerner Millennium, so the new and old systems did not mirror each other and data could not successfully migrate. Changes continued to be made to clinics in the old PAS systems, and these were not all reflected in Cerner Millennium.

Ad hoc clinics were used in the old PAS system to allow overbooking to maximise activity. These were not separated from real clinics at go live and migrated to Cerner Millennium as real clinics. The ad hoc clinics in PAS had deliberately abnormal timings so they could be excluded from time-based reports, for example 12:30am and 5:30am. The system generated letters for these ad hoc out- of-hours clinics, and many were sent to patients.

In the old system, clinics for a number of consultants could be pooled to facilitate patients seeing the next available consultant.  All clinics in Cerner Millennium are specific to a consultant and this caused significant confusion to administration staff using the new system.

PAS [the legacy patient administration system] treats “weeks” differently to Cerner Millennium. On migration, weeks were misaligned and the dates for clinics and theatres was incorrect. This created huge confusion as patient notes did not agree with Cerner Millennium , despite exhaustive work before go live to ensure that all patient notes were ready for the clinics that should have been on the system.  This also affected information in letters, with patients advised to attend their appointment on the wrong date.

There was a further issue in theatres relating to theatre procedure codes. The Trust did not map the old procedure codes to the new to ensure that all the required procedures would be available in Cerner Millennium for the data to migrate successfully. The Trust identified this issue soon after go live and has run a parallel manual process to ensure patients received the correct procedures.

The training provided to staff by the Trust did not equip them to be able to use Cerner Millennium at go live. The training environment did not mirror the system the Trust implemented as certain elements of the system were not complete when the training domain was created. Theatre staff and outpatient appointments could not train on a system with theatre schedules and outpatient clinics built in.

The Trust is now beginning to move out of the crisis and return to normal operations.

Lack of effective quality controls

There was insufficient rigour over the controls criteria and sign off of the gateway reviews.

There was inadequate operational control over the go live process, such as clinic freeze and updates pre-, during, and post go-live. Evidence from the interviews suggests that:

  • There was little challenge to confirm that the gateway criteria had in fact been met.
  • There was no evidence presented to the Cerner Programme Board or the Trust Board to demonstrate that the gateway criteria had been met.
  • There was not enough focus on or monitoring of risks and issues and their impact on go live.
  • The cleansing of old and out-of-date data from the legacy PAS systems was inadequate; as a result, erroneous data became live data in the Cerner system.
  • Data Migration issues were not all resolved and their impact on go live was not considered.
  • The outpatient and theatre builds were neither complete nor accurate, and there were no controls which could have detected this before go live.
  • There were inadequate controls over clinic freeze and clinic changes prior to go live.

Lack of effective programme planning

Programme plans were not rigorously updated as the programme progressed and planning around training, testing and data migration and build was not robust. The Trust failed to recognise this programme as a change programme and did not effectively manage the engagement and feedback from their stakeholders. Evidence from the interviews suggests that:

  • The Trust did not factor contingency into its programme plan to account for changes to the go live date.
  • The Cerner Programme Management Office was not effective because of inadequate resource and programme tools.
  • The Trust had a lack of sufficiently skilled resources for a project on this scale.
  • The Trust’s operational staff were not fully engaged in the Cerner project.
  • The Cerner project was treated as an IT project and not a business change programme.
  • The training was inadequate and did not provide users with the skills they needed to be able to use the system at go live.
  • The testing focused on the functionality of the system and not end-user testing of the outpatient and theatre builds.
  • There was no end-user testing of the final outpatient clinic and theatre builds prior to go live.
  • There was lack of understanding of roles within the wider programme team.
  • External parties offered NBT help and advice. They felt that the advice was not taken and the help was refused.

Lack of effective programme governance

Programme governance processes were not reviewed and updated regularly to ensure that they were adequate and there was inappropriate accountability for key decision making. During the implementation, the Trust established new overarching change management arrangements for the Building our Future programme. Evidence from the interviews suggests that:

  • The Cerner Project team failed to comply with the Trust’s Building our Future governance processes
  • The information presented to the Cerner Programme Board and the Trust board by the Cerner Project team was inadequate for them to make informed decisions;
  • The Cerner Programme Board was not effective; and
  • Significant issues relating to the theatre and outpatient clinic build were not escalated to the Cerner Programme Board or the Trust board.

PwC’s Conclusions

For a programme of this scale and complexity, the management arrangements were not sufficiently extensive or robust. There were many issues with the software and data migration, the training of users and operational go live planning. The Trust Board and the Cerner Programme Board did not plan to have, and did not receive, independent assurance that the state of the programme supported a decision to go-live.

Complex IT implementations are never without risks and issues that need to be managed, even at the point of go live. The scale of the issues in this implementation was not properly understood by those with responsibility, and as a result they were not in a position to make sound decisions.

Many of the problems are associated with poor data and process migration. Staff found that a significant proportion of migrated data was incorrect in the new system, and this had rapid and substantial operational impact which has taken a considerable time to rectify with manual processes. Staff needed to be more directly involved in migration and process testing.

The implementation was manifestly a complex change programme. But IT took the lead, and there was no intelligent customer with sufficient distance from IT to ensure products and progress were properly challenged.

There were not dissimilar Cerner implementations within the Greenfield running a few months before NBT implementation. Similar difficulties were experienced there, but they were more successfully addressed.”

PwC recommends that:

–  the Trust “stop and take stock”. It says  “The Trust needs to take stock of its position and develop a coherent and detailed plan for the remainder of the recovery stage. The Trust then needs to ensure that effective cross programme planning and governance arrangements are enforced for all current projects, especially those under the Building Our Future programme.”

PwC also recommends that the Trust carry out a:

–  Governance review

– Capability/capacity review

– Cross programme plan review

– Operational assessment

– Review of process and controls

– Review of information requirement

– Technical resilience/infrastructure review

– Review of access controls

Comment:

To me the PwC report throws up at least six points:

1) Are NPfIT go-lives more political than pragmatic?

In the 1990s Barclays Bank went live with new systems for all its branches. During the night (I was invited to watch the go-live at head office) the most striking element was a check list that asked questions on progress so far. The answers determined whether the go-live would happen. The check-list was completed repeatedly – seemingly endlessly – during the night.

Many  different types of mishaps could have stopped the go-live.  None did.  Go-lives of Cerner Millennium are different. They seem unstoppable, whatever the circumstances, whatever the problems.  There was nothing political about the Barclays go-live. But NPfIT go-lives are intensely political.

Would North Bristol’s board have accepted with equanimity a last-minute cancellation, especially after go-lives had been postponed at least twice before?

2)  Are NHS boards too focused on “good news” to oversee an NPfIT go live?

North Bristol NHS Trust deserves praise for publishing the PwC report.  But it’s not the whole story.  The report says little about any potentially serious impact on patients. Also it mentions (almost in passing) that the Trust board discussed in November 2011 the readiness of Cerner Millennium to go live. That discussion was probably positive because Millennium went live a month later. But there is no mention of that discussion in the Trust’s board papers for November 2011.

Why did the Trust discuss its readiness to go live in secret? And why did it keep secret its November 2011 report on its readiness to go live?

If North Bristol, like so many NHS trusts, is congenitally beset with a good news culture at board level, can the full truth ever be properly discussed?

3) Isn’t it time Cerner lessons were learnt?

After seven years of Cerner implementations in the NHS, several of them notorious failures, isn’t it time Trusts learnt the lessons?

4)  What’s the current position?

PwC’s report is succinct and professional. It’s also diplomatically-worded. There is little in the report that points to how the Trust is coping with the operational difficulties. Indeed it suggests the Trust is returning to normal. “The Trust is now beginning to move out of the crisis and return to normal operations,” says the PwC report. But that is, in essence, what the Trust has been saying publicly since January 2012.  PwC says nothing about whether the safety of patients has been jeopardized by the go-live.

5) Where were the Trust’s Audit Committee – and internal auditors?

Every NHS Trust has an audit committee and internal auditors to warn about things that are going wrong, or may go wrong. It appears that they were out to lunch when it came to North Bristol’s Cerner Millennium project and its consequences.  The Audit Committee seems hardly to have mentioned the project. Should North Bristol’s board hold the Audit Committee and internal auditors to account?

6) Is the Trust board to blame?

Perhaps rightly PwC does not seek to apportion blame. But did the Trust board ask the right questions often enough?  The tacit criticism in the PwC report is of the IT department and layers of management below board level. But is that criticism misdirected? If the board’s culture of encouraging good news – of “bring me solutions not problems” –  has not changed, perhaps little or nothing will have been learned from North Bristol’s IT-related disaster.

PWC report Independent review of Cerner Millennium implementation North Bristol NHS Trust.

Lessons from Nuffield Orthopaedic’s Cerner Millennium implementation in 2005.

North Bristol apologises over Cerner go-live.

New hospital system caused chaos.

MP asks why two Cerner systems cost vastly different prices.

NHS Trust has “major concern” over spend on Cerner

By Tony Collins

North Bristol NHS Trust reports in its latest board papers that  “overall the level of spending on Cerner continues to be a major concern and the IM&T Director is working to develop a plan to identify what will be needed in the current year”.

The trust went live with Cerner Millennium in December 2011 and had various problems which the Trust said had been “overcome” by 1 May 2012.

But the Trust’s board papers last month hint that some difficulties are continuing.

“There are also clearly still data issues from Cerner which are affecting these numbers which the team are working on,” says a North Bristol finance paper in June.

The overspend on Cerner is about £900,000 for a two-month period. The paper says the “costs of Cerner remain a risk as some of the forecast spend may need to be re-classified as revenue.

“The detail on this is currently being reviewed by the Director of IM&T and isn’t included in the month 2 position… There has been relatively little spend in capital with the exception of Cerner which has incurred £0.9m of cost for 2 months.”

The anticipated spending on the Cerner implementation for the Trust will be more than £5m.

Comment:

It’s not unusual for hospitals to run into trouble with a Cerner Millennium implementation.  When confronted with serious IT-related difficulties private sector organisations sometimes confront what has gone wrong with urgency, pragmatism and trying not to pretend things are better than they are.

Public sector organisations, when facing IT-related difficulties, can fall into the trap of concentrating on what has gone right, and talk as little as possible about the problems. Indeed North Bristol’s latest board papers hardly mention the Millennium difficulties.  There is not a mention in the Audit Committee report. Not a mention in the board agenda.  Only a finance report says that spending on Cerner is a major concern. Elsewhere in the board papers there are short, oblique references to data difficulties.

“With reference to the figures in Table 3, it was confirmed that all patients had been contacted but accuracy of the data could still not be guaranteed and reporting continued to be 2 months behind…  There were also a lot of duplicate referrals on the system.  This was being rectified but may affect billing,” says one board paper.

It would be wrong to suggest that a culture of accentuating the positive and hunching the shoulders at the negative has anything to do with IM&T. It’s one of the differences between the private and public sectors.

North Bristol’s board needs to be more open. If it cannot admit its difficulties how will it tackle them? And what is the point of taxpayers paying for internal auditors that simply assure the board they are doing a great job?

NPfIT Cerner go-live at North Bristol has more problems than anticipated.

Halt Cerner implementations after patient safety problems at five hospitals says MP

Richard Granger “ashamed” of some systems

North Bristol overspends £1m on Cerner

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.

Civil service reform plan – real change or a tweak?

By Tony Collins

The civil service reform plan is to be published this afternoon, at 3.30pm.  The Cabinet Office minister  Francis Maude and Sir Bob Kerslake, the head of the civil service, write about it in today’s Daily Telegraph.

They say that the plan will help deliver a civil service culture that is “pacier, more innovative, less hierarchical and focused on outcomes not process”. They write:

“We also need sharper accountability, in particular from permanent secretaries and those leading major projects, and we need more digital services, better data and management information and for policy and implementation to be linked seamlessly together…”

In the same edition of the Telegraph Andrew Haldenby,  director of the independent think tank Reform, criticises the reform plan which, although not yet published, has been foretold in newspapers including the Financial Times yesterday.

He said the reform plan will “leave the flawed structures of Whitehall in place and do no more than propose some minor variations on a theme”.

We await publication of the paper before we judge it. We hope it will, at least, require the publication of “Gateway” review reports on the progress or otherwise of major IT-enabled projects.

Without timely publication of the Major Projects Authority’s Gateway reports, MPs and the public will continue to learn of failed schemes such as the NPfIT and Firecontrol when it is too late to do much about any rescue; and without contemporaneous publication there will continue to be no accountability for the rigour or otherwise of the reviews, or their outcome.

Civil service reform – meltdown or business as usual? – Institute for Government

Cabinet Office promises unprecedented openness on big, risky projects.

Civil service shake-up – Guardian

Cabinet Office promises unprecedented openness on risky projects

By Tony Collins

The Cabinet Office has defended its decision not to publish “Gateway” review reports on the progress or otherwise of large and risky IT and construction projects.

Gateway reviews are regular, short and independent audits on the state of medium and high-risk projects. Their publication would allow  MPs and the public to have an early warning of a major project in trouble – rather than know of a project failure only after it has happened.

Campaigners have sought for a decade to have the review reports published; and the  Information Commissioner, in requiring the publishing of ID Card gateway reviews under FOI,  dismissed the generalised arguments put forward by officials for Gateway reviews to remain confidential.

The Conservatives, when in opposition, promised to publish Gateway review reports if they came to power. But departmental heads and senior officials have stopped this happening.

Now the Cabinet Office, in a statement to The Guardian, has suggested that the first annual report of the Major Projects Authority will more than compensate for the non-publication of Gateway review reports.

The statement says that the Authority’s ( delayed)  first annual report will “bring unprecedented scrutiny and transparency to our most expensive and highest risk programmes, changing forever the culture of secrecy that has allowed failure to be swept under the carpet”.

The statement continues:

“Historically, fewer than a third of government major projects have delivered to original estimates of time, cost and quality. Since April 2011 the Major Projects Authority has enforced a tough new assurance regime and begun raising leadership standards within the Civil Service.”

The Guardian asked the Cabinet Office whether the traffic light red/amber/green status of Gateway reviews will be published.  The spokesman replied:

“The annual report will contain details of the status of major projects.“

Comment:

We applaud the Major Projects Authority in scrutinising, and in rare cases helping to stop,  departmental projects that don’t have adequate business cases. The Authority’s work is vital in pre-empting ridiculous schemes such as the NPfIT.

But project  disasters that rely on  IT continue, at the Ministry of Justice for example.  Like the National Audit Office, the  Major Projects Authority has limited resources and cannot scrutinise everything. Even if it could, the system of government is not set up in such a way as to allow the Authority to have final say over whether a project is stopped, curbed or re-negotiated.

Preventing failure

Gateway review reports are a critical component in preventing IT-related project failures. If officials know the whistle is going to be authoritatively blown on their failing schemes they are likely to do all they can to avoid failure in the first place. If they know that nobody will be aware of doomed schemes until those involved have left or moved, they will have less incentive to make projects a success.

An annual report is no substitute for the contemporaneous publishing of Gateway review reports. Each Gateway review is several pages and puts into context the traffic light red/amber/green status of the project. An annual report will not contain every Gateway review report. If just the traffic light status is published that will be a start, but without the context of the report what will it mean?

[And it’s worth bearing in mind that the first annual report of the Major Projects Authority is already six months late.]

The non-publication of Gateway review reports is  a victory by senior officials over ministerial promises.  How can we believe that the coalition is committed to unprecedented openness when the final say remains with Sir Humphrey?

Cabinet Office promises to challenge culture of secrecy on IT projects.

Whitehall to relent on secrecy over mega projects?

Francis Maude talks open govt – and Whitehall does the opposite

By Tony Collins

“If people do not know what you’re doing, they don’t know what you’re doing wrong.” – Sir Arnold Robinson, Cabinet Secretary in a discussion on open government in Yes Minister.

Francis Maude, the Cabinet Office minister, said all the right things at the Intellect World Class Public Services conference 2012.

He said that:

– smaller, innovative and efficient suppliers were finding themselves locked out of the supply of services to Government because of what was described by Parliament as a powerful “oligopoly” of large suppliers

– for the first time in Government “we are using agile, iterative processes, open source technology platforms and world-class in-house development teams alongside the best digital innovation the market can offer”

– “We must eliminate failure waste. At the moment, a large proportion of our service delivery costs are incurred through incomplete or failed digital transactions. And these transactions create cross-channel duplication, which burdens the user and costs Government a huge amount in repeated costs. For HMRC alone, they estimate that 35% of calls to its contact centres are avoidable, which would save £75m.”

– “Transparency is a defining passion for this Government …”

Comment:

How much influence does Maude really have? Can he persuade permanent secretaries to effect major change? The evidence so far is that departmental officials and Maude have different ideas on what reform means.

In “Yes Minister” civil servants were proud of a new hospital that was the best run and most hygienic in the country, with no medical staff, 500 administrators and no patients.

Maude may also recall that Antony Jay and Jonathan Lynn, the acclaimed writers of Yes Minister, spoke of the Whitehall law of inverse relevance – “the less you intend to do about something, the more you have to keep talking about it”.

Open government? 

Perhaps civil servants are letting Maude get on with talking the talk while they find every way to keep things much as they are. A good example: The Guardian reported yesterday that a key part of the Government’s transparency drive has stalled amid reports of ministry opposition.

The paper’s political editor Patrick Wintour reported that plans to publish regular ‘traffic-light’ progress reports on large, costly and risky IT projects “appear to have been shelved”.

When it comes to IT this could have been the coalition’s most important single reform. It would have given MPs and the public a way of knowing when mega projects such as Universal Credit are failing. Usually we don’t know about a failed IT-related project unless there is a leak to the media, or the National Audit Office finds out and decides, with its limited budget, to do a study.

Sir Bob Kerslake, who is head of the civil service,  had indicated to MP Richard Bacon that “Gateway” review reports on large and risky IT and construction projects may be published in the civil service reform plan which is expected to be released this month.

Gateway reports to go unpublished?

Now it seems that departmental civil servants  have persuaded the Sir Bob not to publish “Gateway” reports. So the secrecy over the progress or otherwise of government mega projects is set to continue.

Yes, civil servants will allow the Cabinet Office to have its way on the publication of data about, say, some government spending. But it’s becoming clear that the civil service will not allow any publication of its reports on the progress or otherwise of major projects. It has been that way since Gateway reviews were introduced in 2001.

Some senior officials – by no means all – say they want a confidential “safe space” to discuss the progress of projects. The reality is that they do not want outsiders – MPs, the media and NAO auditors – meddling in their failing schemes – schemes such as Firecontrol and e-filing at the Ministry of Justice.

Unlike Maude, senior civil servants have what Jay and Lynn call a “flexible approach to open government”. This means in practice that Whitehall will happily release data – but not project reports on which the civil servants themselves can be judged.

Activity is not achievement

Maude’s speeches will give the impression of activity. But activity is the civil service’s substitute for achievement. I quote Jay and Lynn again, in part because their depiction of Whitehall seems to have been taken as serious wisdom by those officials who think Sir Humphrey a character worth living up to.

It’s time Maude and his team got a grip on departments. Until they do, permanent secretaries and their senior officials will regard Maude as trying to get out of situations that don’t need getting out of.

Whitehall to relent on secrecy over mega projects?

The empty hospital – Yes Minister

Government’s transparency drive stalls.

HMRC loses an important voice on its board

By Tony Collins

Steve Lamey, who is leaving HM Revenue and Customs as Director General, Benefits and Credits, has worked tirelessly to improve the organisation’s systems and administration; and he has gained a reputation for listening to IT suppliers.

In 2007 he  won a British Software Satisfaction award for his work in promoting collaboration within the business software industry. He joined HMRC in October 2004 as CIO.

He is perceived to be leaving at a time when there are a number of vacancies at the top of HMRC. Accountancylive reported last month there was an “exodus”of senior officials from HMRC, and morale is said to be low.  But a man as influential as Lamey can do only so much.  Anyone who wants to effect major change at  HMRC must move an iceberg with a rowing boat. That said there have been some HMRC IT-related successes.

Was Lamey an unexploded force at HMRC?

But it’s conceivable that Lamey could have achieved more if he had carried on the way he started: by highlighting the need for change.

He unwittingly made a name for himself in 2005 after a speech he gave to a Government IT conference in which he revealed some of the corporate weaknesses of HMRC, an the organisation he had  joined not long before.

He  probably had not expected  his comments to be reported first in Computer Weekly and then on the front page of the Daily Telegraph.

At that time Lamey was HMRC’s new CIO. He told delegates of some of his discoveries, namely that:

– At least 31 million wrongly addressed letters were being sent out.

– Nearly half of self-assessment tax forms were being incorrectly processed and had to be done again.

–  he had been struck by the out-of-date computer systems. He told the conference: “If I were an information technology historian I would love it. We need to move on from there.”

– his  “biggest, biggest, biggest challenge” was correcting “poor quality data”.

Later a Daily Telegraph article, quoted me as saying “Mr Lamey’s frank assessment of the state of the tax department’s processes and systems is a rare and fresh approach for a senior government official.”

But was Lamey muzzled?

After that article it seems that Lamey was effectively muzzled, at least from making disclosures in public about HMRC’s flaws. Board papers at the time indicated that senior civil servants at HMRC would, in future, have to clear their public speeches in advance. Lamey did not make a similar speech in public again, not to my knowledge at least.

Richard Bacon MP, a member of the Public Accounts Committee, spoke at the time of the apparent attempts by HMRC to silence Lamey.

“It was refreshing to have a senior IT specialist, who is familiar with the business issues, and who is prepared to identify clearly what the scale of the problems is. Unless you’ve got that degree of frankness and candour, I don’t think you’re really going to solve the underlying problems. The alternative is to be in denial, to suggest that the problems don’t exist. It is plain that they do.”

The then Shadow Treasury minister Baroness Noakes, who was formerly a partner at KPMG, said she was concerned that it was already hard for parliament to discover how well HMRC was managing its business.

She said HMRC was “apparently silencing people from telling the truth”. She added “Speaking the truth [in the public sector] in the way you do in the private sector may well not be as acceptable.”

Would Lamey have been even more influential if he had continued – in public – to point to the weaknesses HMRC needed to tackle?

So defensive is HMRC that it considered a positive PR campaign to highlight its strengths after the loss of two CDs which contained the details of 25 million people.

Can an organisation that intuitively discounts and suppresses the negatives while trumpeting the positives ever properly reform itself? Probably not. If you cannot accept you have problems you cannot resolve them. We wonder how HMRC is getting on with its part of the Universal Credit project … its officials say all is well.

Attempts to constrain HMRC directors.

Front page Telegraph article with references to Steve Lamey’s speech

HMRC honcho poached.

Time for truth on Universal Credit

Hungry re-seller bags Steve Lamey.

Whistleblower punished?

Whitehall to relent on secrecy over mega projects – after 10-year campaign?

By Tony Collins

The Cabinet Office may be about to change its decade-old policy of not publishing reports on  the progress or otherwise of its large, costly and risky IT-based projects.

A change of policy from secrecy to openness would give MPs and the public warning of when a major project is in trouble and needs rescuing or cancelling.

Parliament last to know

For more than a decade campaigners have sought to persuade successive governments to publish “Gateway” reviews, which are short independent audits on the state of big projects.  The secrecy has meant that Parliament is usually the last to know when new national schemes go wrong. IT-related failures have hit many public services including those related to tax, benefits, immigration, passports, the fire service, prisons, schools examinations, student loans, the police and health services.

Now Sir Bob Kerslake, head of the civil service, has hinted to campaigning Conservative MP Richard Bacon that the Cabinet Office may change its policy and publish the “red, amber, green” status of large projects as they are routinely assessed.

Kerslake was replying to Bacon at a hearing of the Public Accounts Committee meeting on transparency. Bacon pointed out at the hearing that the Public Accounts Committee had, years ago, called for Gateway reviews to be published.

Not learning from mistakes

“Something I have always been puzzled by is why government does not learn from its mistakes particularly but not only in the area of IT where things go wrong again and again, again and again,” said Bacon. “I have come to the conclusion government does not learn from its mistakes because it does not have a learning curve. If you don’t have a learning curve you are not going to learn.”

He cited the example of how Ian Watmore, Permanent Secretary at the Cabinet Office, had, at Bacon’s request, arranged for an “Opening Gate” report on Universal Credit to be published in the House of Commons library.

But, said Bacon, when an IT journalist applied to the Department for Work and Pensions, under the FOI Act, for the release of all Gateway reports on Universal Credit, the DWP would not publish any of them  – and even refused an FOI request to release the report Watmore had arranged to be placed in the House of Commons library, which Bacon obtained.  “So there is still a culture of intuitive, instinctive secrecy,”  Bacon said. Kerslake replied:

“Yes, actually we are looking at this specific issue as part of the Civil Service Reform Plan….I cannot say exactly what will be in the plan because we have not finalised it yet, but it is due in June and my expectation is that I am very sympathetic to publication of the RAG [red, amber, green] ratings.”

Bacon pointed out that the Cabinet Office Structural Reform Plan Monthly Implementation Updates had said Gateway reviews would be published.  But the commitment was removed for no apparent reason. When the Cabinet Office was asked why,  it said the Structural Reform Plans were only ever “drafts”.

Bacon asked Kerslake if the Government now plans to publish the Gateway reports.  “The Cabinet Office Structural Reform Plan Monthly Implementation Updates originally said Gateway reviews would be published  and then it somehow got downgraded into a draft; and from what’s publicly available at the moment the position of the government is not to publish Gateway reviews.  You sound as if you’re saying that’s going to change. Is that right?” asked Bacon.

“Watch this space,” replied Kerslake. “I am sympathetic. I generally broadly welcome, in principle, the idea of publishing information but there are lots of risks …”

Peter Gershon introduced Gateway reviews when he was Chief Executive of the Office of Government Commerce, which is now part of the Cabinet Office’s Efficiency and Reform Group. The reviews are carried out at key decision times in a project and are sometimes repeated:

  • Gateway Review 0 – Strategic assessment
  • Gateway Review 1 – Business justification
  • Gateway Review 2 – Procurement strategy
  • Gateway Review 3 – Investment decision
  • Gateway Review 4 – Readiness for service
  • Gateway Review 5 – Benefits realisation

Are Gateway reviews a success?

Gateway reviews are now supplemented by regular assurance audits carried out for the Cabinet Office’s Major Projects Authority. None of the reports is published.

Gateway reviews have not stopped costly failures such as Firecontrol or the NPfIT.  One permanent secretary told an MP that the reviews in his department were considered unimportant by senior responsible owners, for whom the reports are written. This may be because SROs often have charge of many projects; and even their SRO responsibilities are often in addition to their main jobs.

But Gershon had high hopes of Gateway reviews when they were introduced in February 2001. This is evident from the number of times he referred to Gateway reviews at one hearing of the Public Accounts Committee in December 2001.

 “… as the Gateway review process cuts in, which I have referred to on a number of occasions when I have appeared at this Committee …”

“… Through things like the Gateway process we are helping to sharpen the focus on the whole life aspects of these and other forms of complex projects in public sector procurement…”

“ …First, we have the introduction of the Gateway review process…”

“ … The Gateway process is a demonstrable example of how we have introduced a technique to support that whole life approach…”

“… If you look at the guidelines around the Gateway review process that is one of the things that is tested by these independent reviews …”

“… we recognised that that was a problem some time ago, which is why in the Gateway review one of the things that is explicitly tested is things like the skills and capabilities of the team at the design and build stage and that the skills and capabilities of the team at the procurement stage …”

“… in this area with the Gateway review process, from when we first launched it last February, we have been helping the department take a whole life approach to these forms of complex projects …”

“… Part of the Gateway Review process is to get a much sharper insight on to where we see good things happening where we can encourage other clients to replicate them…”

“… Now, with the Gateway Review process, my experience has been because of where we have deliberately focused the attention on the early life of projects where there is the greater scope for management to take corrective action, the accounting officers are paying a lot of attention to the recommendations that are emerging because, much to my surprise, most of them do not seem to like coming here defending what has gone wrong in the past. They seem to welcome the recommendations that we are providing to them to help try to get projects on to much stronger foundations in the future…”

“… With the Gateway Review, my experience has been that the Accounting Officers respond to the recommendations very positively…”

“…Gateway Reviews explicitly test how the department is planning in the pre-contract phase to secure ongoing value for money in the post-contract phase…”

“… Take, firstly, the Gateway Review process. That is testing various points in the life cycle of the project, from the very earliest stage…”

“… I would certainly expect in Gateway Reviews that the review team would be testing what methods were in place to facilitate the ongoing management of the contract…”

“… I think it is encouraging that Sir Ian Byatt thought the Gateway Review process had sufficient value to recommend it in his own review…”

And so forth.

Comment:

We applaud Richard Bacon MP for his persistent call for Gateway reports to be published.

Gateway reviews have defeated expectations that they would stop failures; and the National Audit Office tells us that central departments don’t even request Gateway reviews on some big and risky projects although they are supposed to be mandatory.

But Gateway and other project assurance reports could prove invaluable if they are published. In the public domain the reports would enable Parliament and Francis Maude’s “armchair auditors” to hold officials and SROs to account for projects that are in danger of failing. That would be an incentive for officialdom to fail early and fail cheaply; and Gateway reviewers may take greater care to be neutral in their findings – not too lenient, or too harsh – on the basis that the reports would be open to public scrutiny. SROs would also have to take the review reports seriously – not just put them in a draw because nobody knows about them anyway.

We welcome Kerslake’s comments but hope that he and his colleagues plan to publish more than the RAG (Red/Amber/Green) status of projects. Otherwise they will be missing an opportunity.  Gateway reports and other assurance reviews are expensive. Reviewers can earn up to £1,000 a day. This money  could be well spent if the reviews are to be published; but it will add to public waste if the reports are kept secret and continue to be deemed pointless or unimportant by departments.

It is ironic, incidentally, that the Ministry of Justice, which introduced the FOI Act, gives advice to departments to keep the RAG status of Gateway reviews confidential. In its advice on Gateway reviews and the FOI, the MoJ tells departments that the “working assumption” is that the substance of the Gateway reports should be kept confidential until at least two years have elapsed.

It’s time for a culture change. Maybe the Civil Service Reform Plan next month will be worth reading.

Fire ‘superstations’ without software cost £1m a month – The Times

By Tony Collins

The Times reports today that taxpayers are paying more than £1m a month on the rent and upkeep of fire control rooms across England that have never been used. The purpose-built control centres look ready for immediate use, with open-plan desks fitted with desktop monitors and keyboards, and huge screens on a wall at the front of the control rooms which are supposed to help fire and rescue crews mobilise appliances and manage incidents.

Only there’s no working software.  The Department for Communities and Local Government negotiated the end of a contract with the main contractor EADS for software to run the regional control centres in December 2010. Officials concluded that the software could not be delivered within an acceptable timeframe. The regional control centres were completed before the IT project was cancelled.

The cost of the centres has been uncovered after a request under the FOI Act. The Times devotes much of its page three to a story under the headline:

Revealed: scandal of the £1m-a-month fire service ‘superstations’ lying empty.

Only one of nine regional centres is in use. The other eight incur rent, electricity, water and repair costs at £1,134,566 a month. Costs will be incurred for years because there are no break clauses in the agreements to lease the buildings. Two leases come to an end in 2027, one in 2028, two in 2032, three in 2033 and one in 2035.

A spokesman for the Department said that agreement has been reached for a further two of the buildings to be used by local fire authorities. Officials are searching for public or private sector tenants to occupy the other regional centres.

Lord Prescott, the former Deputy Prime Minister, who authorised the start of the technology project in 2004,  said he had been kept in the dark by civil servants on the rising costs of the scheme. He said it had been on budget when he left the department in 2007.

Eric Pickles, the Communities Secretary, said the failure of Firecontrol was an “expensive reminder of why you can’t trust Labour to run anything”. But the Coalition’s coming to power has not stopped central government IT-related failures.

Why Firecontrol failed

Firecontrol  followed the same tracks to a cliff edge that have caught out civil servants, ministers and suppliers on other government  computer-related projects.

The National Audit Office and the Public Accounts Committee found that  the Firecontrol project was rushed, had little support from those who would use it, costs and complexity were underestimated, there was an over-reliance on consultants and a lack of accountability for decisions made  – or not made.

The idea was to replace 46 local control rooms with nine, linked regional centres, which would be equipped with new standardised computer systems to handle calls, mobilise equipment and manage incidents.

But the project was cancelled in December 2010 with ministers unsure the technology would ever work. The NAO estimates that £469m will be wasted on the project.

The NAO found that the scheme was “flawed from the outset”, largely because local fire and rescue officers did not want regional centres or major changes in the way they worked.  Introducing any large new system is difficult but with enthusiastic support serious problems can sometimes be overcome; but introducing a complex new system without support from those who would use it means staff will have little incentive to find ways around problems.

The NPfIT [National Programme for IT in the NHS] failed in part because it lacked support among GPs and NHS staff; and the complexity of introducing standardised technology in semi-autonomous hospitals – each one with different ways of working – was underestimated. It was the same with Firecontrol.

The complexity of introducing standardised systems in regional centres with no goodwill among staff – was underestimated.  From the start many local fire and rescue officers criticised the lack of clarity on how a regional approach would increase efficiency. “Early on, the Department’s inconsistent messages about the regionalisation of the Fire and Rescue Service led to mistrust and some antagonism,” said the NAO.

The technology project was rushed while local fire crews were excluded from project discussions. “The project progressed too fast without essential checks being completed. For example Departmental and Treasury approval was given without proper scrutiny of the project’s feasibility or validation of the estimated costs and savings,” said the Public Accounts Committee. The project went ahead before the full business case was written.

A review of the project as early as April 2004 found that the scheme was already in poor condition overall and at significant risk of failing to deliver. But the “Gateway” review report was kept secret for seven years.

Is the stage set for IT disasters in government to continue? So far the Coalition has decided, like Labour, to keep secret all internal reports on the progress or otherwise of its mega projects, including Universal Credit, though the policy on secrecy may be about to change, which Campaign4Change will report on separately.

Firecontrol – same mistakes repeated on other projects.