Welcome Guest | Login | Register | Why Register?
HOME | CONTACT | NEWS ARCHIVE | DOCUMENT LIBRARY | FEATURES | COMMENT & ANALYSIS | EVENTS | RESEARCH REPORTS | CASE STUDIES | FORUMS

'Widespread concerns' about NPfIT penalties

01 Aug 2007

In a new survey NHS foundation trusts have reported 'widespread concerns' about the limited functionality of key systems  from the NHS National Programme for IT.

Some foundation trusts (FTs) that have sought to delay taking systems until problems are fixed say they have been told to expect fines running into many millions of pounds.  The FTs report that in many cases the nationally purchased software is incomplete or less capable than their current systems.

NHS Connecting for Health the agency running the £12bn NHS IT programme, and which drew up the contracts, including penalties termed 'non-deployment charges', confirmed to E-Health Insider that a number of trust chief executives had recently written expressing their concerns at the potential fines. The DH agency said no fines have yet been levied.

Carried out by the Foundation Trust Network, part of the NHS Confederation, the survey examined foundation trusts’ experiences of the National Programme for IT (NPfIT) and found “widespread concerns about the functionality of NPfIT systems as a whole”.

E-Health Insider has obtained a copy of the confidential June survey, which includes responses from 48 of the 54 FTs, representing the cream of the health service.

One acute FT reported being told that its local health community would have to pay a £20m fine if it decided not to take the early software offered for NHS Care Record System (CRS). Another reported facing a potential fine of £11m if it delayed installing software.

While national systems including e-booking and digital x-ray communication and storage are widely used, the report says ‘most’ FTs have opted out of certain parts of the national NHS IT system including the crucial CRS software required to develop electronic patient records.

Where some FTs have sought to opt out of using systems that only partly met their needs or were less capable than existing systems, they have been told they risk incurring penalty payments.

FTs reported being told they face penalty payments to Connecting for Health (CfH) and its prime contractors if they refuse to install software they don't judge to be fit for purpose. The 'non-deployment charges' form part of the local service provider (LSP) contracts for the NHS IT programme to which the Department of Health committed all English NHS trusts in 2001.

The biggest concerns about the software on offer centre on problems with the CRS, mental health systems and maternity, but also extend to picture archiving and communications systems (PACS) – often cited as the great successes of the programme.

The survey results make damning reading, detailing FTs’ concerns about the limitations of key systems being provided by the NPfIT programme. “Almost every respondent had concerns about the functionality of some part of the system and most had opted out of certain parts of the NPfIT system,” says the survey report.

NPfIT systems identified as particularly problematic include patient administration systems (PAS), mental health and maternity. The greatest cause of concern was the CRS based on Cerner’s Millennium and iSoft’s Lorenzo software delivered by LSPs.

“Most problems reported were around the CRS systems where acute FTs reported that CRS represents poor value (even though it comes at zero cost as part of the core) as a result of key gaps in functionality.”

The report says that twelve FTs, a quarter of the total, reported “major problems in the PAS with one FT having identified 60 areas less efficient than current PAS where new processes will need to be introduced at significant additional costs.”

One FT quoted in the survey said: “We have concerns that the PAS solution Lorenzo will deliver less functionality than we currently have.”

According to the survey while most FTs are using elements of NPfIT systems “they have all needed to put in place additional systems to support those functions to make them more compatible with their needs.

One unidentified respondent is quoted as saying: “I have a great deal of concerns around the functionality of the product as do my other SRO colleagues I work with. It would appear this is now being seen as delivering a target rather than being seen as getting the product right before we start to deploy it into much larger organisations, the provider [Fujitsu] cannot get it right in places such as Weston and NOC - what is the hope for larger organisations?”

Another major area of concern is mental health where the report says: “The lack of mental health functionality, particularly with Cerner Millennium products is of great concern. Mental health FTs also report that PACS and other parts of NPfIT systems such as maternity, theatres and ambulance are not relevant to them.” Three trusts reported problems with maternity functionality as a reason for opting out of NPfIT – two have taken alternatives and one is planning to.

In addition, early implementers whose programmes had been halted as a result of development problems, reported having already spent heavily on staff teams and training and expect to need to invest even more “in the millions” at the next implementation date at the end of 2008.

According to the report: "Whilst the majority of trusts are using NPfIT, they have all needed to put in place additional systems to support those functions to make the system more compatible to their needs."

Despite the extent of the problems cited, FTs report that when they have sought to delay implementations until systems meet their needs or opt-out of taking NPfIT systems entirely they have been told they face fines running into millions or even tens of millions of pounds.

The report says: “The acute FT reporting problems with CRS wanted to opt for the later R2 phase has been told that it will have to pay the £20m that this will cost the local health community.”

Another acute trust seeking to opt out of CRS reported it had been told that although it would not face fines its decision “will cost the local health community £11m.”

“One acute trust was considering going outside for PACS and has been told they will not receive PDC [Public Dividend Capital] unless they go with Connecting for Health, and in addition will receive a fine of £3.5m. There have also been rumours of more significant fees/connectivity charges coming if they don’t fall in line which could push the figure to over £5m.”

Yet another FT, which chose to go with a non-NPfIT system said it "expects to incur penalties", though another that went outside NPfIT said it didn't expect to face such charges.

Richard Bacon MP, and member of the Commons Public Accounts Committee, told EHI that the threat of penalties fitted with a pattern of bullying from the centre, with CfH telling trusts what they have to do. "It is extraordinary, as they are meant to be helping trusts not threatening to penalise them."

CfH confirmed the existence of the penalty payment clauses in LSP contracts designed to ensure trusts implement the centrally-purchased systems. The agency declined to provide details of the upper limits of potential non-deployment fines, which it is understood can be levied by either CfH or the LSPs.

Richard Jeavons, CfH's director of service implementation, said in a statement to

E-Health Insider: "I've had enquiries from FT chief executives about the matter. We would certainly wish to address any concerns which the FT community has in our normal and ongoing dialogue with them.”

A CfH spokesperson confirmed that the provision for non-deployment charges existed in the LSP contracts, but declined to state how big such charges could be. They added: "To date no non-deployment charges have been enforced."

A senior LSP figure contacted by EHI described the fines in contracts as akin to a game played by the contracting parties "our fines cancel out their fines".

None of the three LSPs working on the programme – Computer Sciences Corporation, Fujitsu and BT – were willing to comment officially on non-deployment charges and whether they had been threatened or sought from trusts, saying the information was "commercially confidential."

© 2007 E-HEALTH-MEDIA LTD. ALL RIGHTS RESERVED.

1

Coercive power

02 Aug 07 08:54

It is said that, of all the ways of exercising power, coercion is the least likely to win commitment.

QED


2

Madness!

02 Aug 07 11:23

i have been a regular follower of news relating to the NPfITCfH since the programme began but this is the first time i have heard of this ridiculous plan to fine hospitals for NOT taking software that is not fit for purposes and in terms of functionality would repreesent a step BACKWARDS For end users!

Has the DoH gone mad? what happened to all the heavy penalties that were supposed to be laid on LSPs for late delivery of products? are there any news articles about this? are they getting fined?


3

Halleluiah

david.birch@ascend.demon.co.uk

02 Aug 07 12:59

Halleluiah! At last this situation is beginning to be acknowledged - but are the right people listening? Some of us who have worked in the front line of patient care over the years and who have been involved in attempting to make these very systems fit the UK NHS?s long-embedded cultural healthcare requirements and practices, have been beating our heads against deaf stony walls for several years now. As I have said before on this forum, American products, with their underlying financial based architecture, are US solutions aimed at a US market. I am sure I am note the only person who can say they have struggled to be heard by the decision makers for these vendors, when we tell them that these systems have serious deficiencies for the UK market.

Sadly, clinical and managerial functional requirements specifications appear to have been at the bottom of the priority list for whoever designed the original contracts for the LSPs.

I must concur with the previous response ('Madness'), these products are not yet fit for purpose - but was that purpose every adequately explained?


4

Fines and liabilities

02 Aug 07 14:45

As a balance to the supplier obligations in the LSP contracts, Trusts (Foundation or not) were bound into systems that are proving quite inadequate. We have asked many times, but no-one seems prepared to quantify exactly how much the fines would be.

But perhaps worse than this, the LSPs are also able to charge the NHS for delays, which arise because they would not listen to reason. We have repeatedly been told that the design and technology is the LSPs business, the delays are because their product is not fit to deploy, yet this appears to cost the NHS more.

At best, the NHS can advise, and provide Clinical Subject Matter Expertise.

And as the closing remark in your article.everything is "commercially confidential". So serious planning, and objective balancing of benefits against costs cannot be done.

The key problem is with the NCRS contracts with the LSPs.


5

'Encouragement to take duff/incomplete goods'

02 Aug 07 22:54

Spare a thought for the unsuccessful bidders in the initial exercise. EITHER - You invested a lot in presenting your case, you were told it was not up to spec OR- You went so far then backed off for commercially prudent reasons What must be going through their minds now that the 'big and beautiful' cannot meet the spec either; was it a fuzzy spec or were they fooling themselves and talking too good a show??

Either way, the NHS has not (yet) got what it needs - lets dissassemble the offerrings, look closely at the useful bits and put effort into making those deliver across the board - otherwise all the local investment in management of change will be obsolete before it has a chance to be used!


6

The Emporer's New Clothes?

03 Aug 07 11:19

Or the bubble waiting to burst - excuse me if my metaphors are of no better quality that the software we are being forced to implement. Yes it does seem outrageous that NHS organisations could be penalised in this way for not adopting software that is not fit for purpose - presuambly it's too late to undo as this was all 'stitched up' in the contact. Would whoever agreed this contract on behalf of the NHS be equally happy in their personal lives if they were fined for not buying a car with no wheels? :)


7

Transparency

03 Aug 07 11:45

It is time the NAO demanded that all this 'commercial confidence' is no longer in the interests of the NHS, DoH, Government as a whole and the tax-payer!

A full and public enquiry will show up a lot more of these contractual 'irregularities' that ought to be put right now before they seriously impact on quality of patient care.


8

Progress

03 Aug 07 12:24

In the whacky world of CfH, this is progress of a sort - at least they've given up trying to tell us in acute care that these systems are good value and fit for purpose...


9

Project Deliverable

06 Aug 07 16:45

If, as a Project Manager, I attempted to deliver to a user a system that does not meet user requirements, the project would have been deemed to have failed. One of basic tenets of Prince2, or any other project method, is to deliver what the user requires; this is so basic that it beggars belief that Trusts could be penalised for not accepting a sub-standard product. I suppose that if these sub-standard products are implemented under duress, the subsequent deleterious effect on Trust performance will be a cause for further criticism!!!


10

The danger is in the precedent

07 Aug 07 14:52

I think the problem is the way in which systems were declared "fit for purpose"

A lot of this work was done with early adopters, most of whom had a failing supplier or no system in place previously. In addition, the go-lives were limited, and in most instances only covered deployment to a handfull of staff.

These limited deployments didn't really give a full picture of the organisation requirements, as more difficult services, or those with existing functionally rich systems weren't considered.

Unfortunately the way the contracts were written meant that even if only 1 person successfully went live with an LSP system, the deployment was considered a success for the whole organisation i.e. Suburbia PCT is now live with System X - when in reality, only a handful of staff were actually using the system.

These precedents and the "positive spin" of the LSP's (and I believe CfH not asking too many questions as they were under pressure to show results too) set the stage for pressure on other organisations to comply - i.e. if Suburbia PCT are using this successfully, why aren't you?

Organisations began to be pressured by CfH and SHA's to take the products, as the LSP's who had "successfully deployed" solutions as per the contract requirements then wanted the volume they were promised in the contracts. As a result, some NHS orgs gave in and took systems which weren't really wanted by staff or clinicians - which often lead to mal-content and mistrust of CfH/NPfIT systems and is probably the reason for most of the bad press on this site.

Unfortunately, cracks started to appear, as the "fit for purpose" solutions kept failing to meet the requirements of most NHS orgs, who were more aware of their needs and were buoyed up by the horror stories from other orgs started to dig their heels in.

IMHO hereby lies the reason for a lot of the tension between the NHS and CfH. CfH believe the systems work and are annoyed at NHS orgs for not deploying the solutions, and NHS orgs are annoyed at CfH for trying to palm them off with what they see as sub-standard products.

Call me a conspiracy theorist, but I believe the LSP's saw this coming and have played both sides against each other beautifully over the past 12 months. They can now capitalise on this by using the clauses in the contracts designed to penalise them to hit back at the NHS with their own delay charges - well played gents...


11

In a bind.

nhstechie@btinternet.com

07 Aug 07 21:19

The key issue is the fact that the LSPs were granted exclusive contracts for the supply of EPR systems to the English NHS.

All Trusts can legitimately refuse to deploy such LSP systems if they are not fit for purpose - so long as they continue to use their existing systems and don't buy from anyone other than an LSP.

In theory, we could buy from another LSP but now that we effectively have a duopoly each offering a far less than perfect solution without a convincing argument that fit for purpose products will be delivered in the next 2 or 3 years, we are in a bind.

Those of us hoping that achieving FT status would give us a way out have now apparently had that hope dashed - unless an FT is prepared to challenge the assumption that the DoH/LSP exclusivity agreement extends to FTs which by definition sit outside central government control.


12

Cerner CRS, a potted version

08 Aug 07 12:33

There have been many comments about "not fit for purpose" and in many areas of functionality I can see why. However speak to someone who has used the system in the States and you find it can do whatever you want, if you have the opportunity to get what you want, be it all expensive. The idea of one size fits all is what's at the root of the problem. Let the Trusts truly localise the system to fit it's purpose and you'll get different feedback. It won't happen of course because the contract is signed for the spec that everyone is getting and is at risk of causing the programmes downfall.


13

blame

justme0501@yahoo.com

09 Aug 07 05:31

Your working with a company (Cerner) that is in business to make money...Fujitsu gave contract specifications, the company felt they could meet those specifications (of course based on the NHS specifications) and all plans went forward. It isn't a question of what the Trusts may feel is acceptable, it is a matter of if the company can deliver what was promised. Don't blame those who accepted the specification, as the specification continues to change...blame your government for lack of a specification that met the needs of the Trusts!!!


14

NPfIT LSP penalty tension

09 Aug 07 13:18

With the increased tension between CfH and the LSPs over money, one can't help but wonder if the CfH contracts allow for the sort of procurement, implementation payment milestones for each site , product, stage achievement. That was always fair and prudent in the old days, recognising both the need for a supplier income stream and for some delivery quality leverage by the purchaser.

Search
News Features Jobs Newsletters
latest forum posts
latest forum posts
Top jobs
More
Top jobs

Featured_recruiters
Featured_recruiters