PCEHR: What really went wrong

by Charles Wright on January 25, 2012

Anyone with the slightest idea of large-scale software development would have been staggered by the surpassing silliness contained in yesterday’s piece in the Medical Observer, in which “ehealth consultant” David More trots out his analysis of the problem which has brought the desktop software side of the PCEHR project to a temporary halt.

According to More, it would have been terribly easy to avoid trouble: “Had they planned properly they would have had a consistent data model for all the sites and they would have noted that there was this issue [at the outset],” he said. “It just reflects incompetence, frankly. If they knew what they were doing they would have addressed these problems before they started.”

The only illumination one could gain from that is that More simply had no idea of the cause of the problem, no inkling of a solution, and insufficient humility to admit that in truth, he’s not much of an ehealth expert. It really is long past time lazy journalists scratched him out of their sadly tattered contact books.

The very idea that you can anticipate every problem before you begin a hugely complex IT project and construct a data model that uncovers every deviation is ludicrous.

The very nature of software development is that it’s a process of getting things right. The recipe is largely the following: Develop, test, identify bugs, fix them. Endlessly repeat.

What happened in this particular case is that the wave site developments were a dynamic operation, with the developers constantly engaging with NEHTA staff to identify problems and challenges. As issues arose, NEHTA made changes to the specifications to address them. In parallel with that, the specifications were being run through further quality assurance testing.

As the work proceeded through 2011, NEHTA kept the sites informed about the changes that were being implemented to resolve their concerns, allowing them to integrate them in the work.

What when wrong, essentially, was that in October, the change log was finalised. The list of issues NEHTA provided at that point of things that would be fixed in November omitted a number of new items that had been included in response to feedback or problems, or new issues that were still to be identified during testing in November.

That meant developers working on the October change log would have had to upgrade their software later to reflect the changed specifications.

NEHTA decided that rather than have that happen, it was better to call a halt, have everyone build to the November specifications, and deploy the software once.

The main impact is that they deploy later than expected. Rather than February it’s more likely to be May. Of course this will be worked out between NEHTA and the sites, but it’s the sort of rational reaction coming from sites, rather than the sort of hysteria coming from some commentators.

Anyone who’s actually involved in doing ehealth, as opposed to just talking about how others should do it, will know that you have feedback loops on early versions of specs to later ones. They will also know that keeping a complete change log is essential. That is how you address this sort of issue before the project starts. Data models have nothing to do with it.

{ 5 comments }

PCEHR glitch: no lynch mobs please

by Charles Wright on January 24, 2012

It took a couple of days for The Australian and the usual suspects to catch up with the news of the problems with the specifications for the PCEHR which I reported on Sunday and again yesterday, which may explain the enthusiasm with which they have greeted confirmation of the story in a statement from NEHTA.

The Australian described it as “the latest blow for the Personally Controlled Electronic Health Record (PCEHR) project”. One can only presume they are scoring their own punches at the system – pretty well all of which have been low and wide of the mark – because I can’t recall any earlier blows. Concerns and criticisms surely don’t count, do they?

The PCEHR project hasn’t been perfect, largely because of the completely unrealistic timelines imposed by former Health Minister, Nicola Roxon, but compared to the record of IT development by federal and state bodies, it’s been remarkably smooth sailing.

That doesn’t mean that the problem isn’t serious. The fact that conflicting specifications seem to have been delivered last November is not something that instills confidence in the development and clinical community, but on the other hand, the fact that it was identified relatively quickly is surely a plus.

To say, as that well-known anti-NEHTA blogger David More does, that “the wheels have fallen off” and “NEHTA is utterly incompetent and is becoming the instigator of yet another failing over-reaching national ehealth program” is surely premature. Typically, of course, there’s a detectable edge of glee and self-congratulation, with More clearly including himself in the ranks of “the wise men who said you should learn to walk before running”.

Unlike More and The Australian, I’ve been speaking to people in the vendor and implementation world I regard as infinitely wiser. One of them described the situation as “not a show-stopper by any means”.

The developers were scheduled shortly to begin CAP testing – I presume that relates to clinical terminology testing under the SNOMED CT arrangements, but I invite correction – and that’s going to be put back by three to six weeks, assuming that there isn’t some serious issue that hasn’t yet been hinted at. The July 1 deadline is being seriously tested as a consequence, but that seems to me a political imperative, rather than one based on prudent judgment.

According to one of my vendor sources, “Some people have an agenda that they want to see the PCEHR fail. We want to see it work. The delay is understandable, and we don’t have a problem with it.”

Over at the Healthbase blog, Dr Eric Browne claims that there are critical failings with the HL7 Clinical Document Architecture (CDA) underlying the PCEHR’s messaging and calls for an end to all further work in this area, pending a thorough review.

“Having studied both the HL7 specifications in detail as well as dozens, if not hundreds of examples of CDA documents from around the world over the past 5 years,” he says, “I have come to the conclusion that there are significant safety and quality risks associated with relying on the structured clinical data in many of these electronic documents.”

His concerns arise from his study of six sample discharge summary CDA documents provided by NEHTA, and the fact that “data can be supplied simultaneously in two distinct, yet disconnected forms – one which is ‘human-readable’, narrative text displayable to a patient or clinician in a browser  panel;  the other comprising highly structured  and coded clinical ‘entries’ destined for later computer processing. The latter is supposed to underpin clinical decision support, data aggregation, etc. which form much of the justification for the introduction of the PCEHR system in the first place.”

According to Eric, the human readable data in the NEHTA examples bore no relationship to the coded data, to the extent that the entries looked fine in the discharge summaries, but according to the computer code the patients were all dead, one of them having been killed off at birth, according to the record.

It’s a rivetting piece of information, but one of my sources says that the data displayed in the live system is generated directly from the raw data. He suggests that the NEHTA samples were not representative of the way the system works. “They were samples that were not generated on a live system by a clinician.”

I would have thought that genuinely wise men would want to clarify issues like that before breaking the glass and pressing the big red button.

I understand that NEHTA’s clinical lead, Dr Mukesh Haikerwal, will be outlining the issues to medical colleges at meetings in Melbourne tomorrow. We’ll probably learn a lot more at that point. In the meantime, should we not perhaps be discovering whether the victim is deceased or even critically wounded, rather than trying to hang the accused?

{ 3 comments }

Uncertainty over PCEHR

January 23, 2012

The NEHTA lead sites involved in the roll-out of the PCEHR are in a state of bemused uncertainty, as they await details of the specification problems I wrote about yesterday. The mass media, medical and trade press, and for that matter the blogosphere and Twitterverse seem still to be unaware of the problem. As I understand it, [...]

Read the full article →

PCEHR hits problems

January 22, 2012

I’ve just heard a disturbing report from the implementation community that some problems have arisen with the specifications for the PCEHR. I understand that the problems involve a discrepancy between some of the specifications released to the different wave sites, and that an announcement will be made this week. My information suggests that the problem [...]

Read the full article →

HCN gets competitive in ehealth roll-out

January 19, 2012

As I have pointed out in the past, there’s a widespread view that HCN shot itself in the foot when it declined NEHTA’s invitation to join the desktop vendors’ panel, on the grounds that the funding being offered to make Medical Director  compliant with the government’s ehealth standards was “just laughable“. It seemed pretty clear [...]

Read the full article →

Apathy and ehealth

January 16, 2012

I was chatting to a GP friend on Saturday night at a Royal Tennis presentation dinner [at which, wonder of wonders, I picked up a minor trophy], and was fascinated by her suggestion that one reason patients haven’t been active participants in their healthcare is that in too many cases they believe that they can [...]

Read the full article →

Telehealth and mHealth: some pros and cons

January 10, 2012

After that less than stellar performance in the Sunday Age [below] Tim Barlass redeems himself with a fascinating piece about a trial in rural NSW in which elderly patients given a broadband “medibox” which monitored details of blood pressure, heart rate, blood oxygen and weight and logged them remotely to doctors, demonstrated a dramatic decrease [...]

Read the full article →

Sunday Age suffers telehealth incompatibility

January 9, 2012

If you read the Sunday Age story on the $6000 grant to doctors to encourage them to participate in telehealth, you’d more than likely be convinced that it’s been one of those  gravy train fiascos in which incompetent politicians and bureaucrats paid doctors a lot of money to buy technology that they could – and in [...]

Read the full article →

A future of healthegadgets

January 5, 2012

Just a couple of days ago, Shanna Crispin was musing in eHealth Insider about the increasing popularity of pesonal electronic health gadgetry and speculating on a new generation of futuristic devices “from smart clothes to avatars that can support rehab patients”. Withings’ next advance on its blood pressure monitor for iOS devices that allows users not only [...]

Read the full article →

An unhappy New Year for CSC

December 28, 2011

It’s already been something of an annus horribilis for CSC, but the final days of 2011 have brought even worse news for the company’s shareholders, with the announcement that it might be forced to write off the $1.5 billion value of a disputed contract with the NHS. Over at eHealth Insider, there’s a summary of [...]

Read the full article →