Slashdot Mirror
Arguing For Open Electronic Health Records
mynameismonkey writes "openEHR guru Tim Cook, writing in a guest blog at A Scanner Brightly, discusses why Electronic Health Record developers should use open standards. Why are so few doctors using EHR systems? And, as more and more hospital EHR systems come online across the country, what do we have to fear from proprietary databases? It's one thing to find out your social security number was stolen. Now add your mental health and STD results to those records."
The UK has spent the last 5 years trying to build a common Health Record Database for all NHS patients. Those of you that are aware, the HNS is a public run service that covers the health needs of the entire population, although Private medical Insurance is available if required at extra cost. So far this "Database" has cost the UK Taxpayer £12 billion ($24 US Dollars) and has delivered nothing but chaos, confusion and a lack of investment in frontline databases that are currently in use, meaning that records go missing, data discs with confidential data get lost etc... http://news.bbc.co.uk/1/hi/uk/7158498.stm
The fundamental problem is that politicians think that databases are the answer to everything, being handy for issuing speeding fines, holding criminal records and identity details of everybody in the country, but they haven't quite got round to the concept that the accuracy the data within a database is the most important aspect and it is often the data processing factor that often falls down. They forget the basic fundamental questions like:-
How long does the data take to propagate into the system properly? If I tax my car late on Friday will the computer database not be updated until Monday, meaning that I'm going to be constantly pulled over by the Police and threatened with my transport being impounded for the weekend, even though it is perfectly legal?
What happens if the data is incorrect? Our beloved UK government wants an all encompassing ID card system, which will reference a number of different databases. How can they be absolutely sure that the data is at least 6 sigma (3.4 defects per million records) if not 100% correct (note that the old saying 99.9% doesn't even being to recognise the real accuracy required).
If the data is incorrect who is responsible? If there are many bodies involved, you can guarantee that none of them will agree who is at fault until lawyers get involved, especially if they are civil servants and/or politicians.
Who ensures that the data is secure? We in the UK had ZIP encrypted discs containing details of 25 million people (about 2/5 of the UK population) lost by the HRMC recently. http://news.bbc.co.uk/1/hi/uk_politics/7117291.stm
One the face of it using an open system for designing a database is a good idea in principle, but it is the people that are responsible for these databases that need to know exactly why they are important and why reliance on such databases is a recipe for disaster if proper considerations are not made. Part of the problem is that many of the people choosing these databases probably don't have a first clue in how a database works, that is the problem we face.
I did notice that this week the new Australian Prime Minister Kevin Rudd cancelled a National ID card system that was planed by the Howard Administration. This move appears to come from somebody that appears to understand the complex nature of such a system, its cost and its lack of benefit. There are many ways that can be used to determine somebodies identify (bank cards, passport, birth certificate) and having all of them referenced at the same place isn't the most cost effective solution.
In the UK, the government has invested vast sums of money into a system called "Choose and Book." It's billed on the slim selling point of offering patients greater choice in hospital care but the most cursory look at the technology involved shows that the biggest effect is that of centralising patient's records.
Aside from the fact that patients can be offered a choice in secondary care already (by their doctor referring them to somewhere else), the system is buggy and flawed. The doctors don't want it, there have been national campaigns by the public against it, but the government is doing every single thing they can to force it on people up to and including financially penalising doctor's practices for not using it. The motivations are (a) presumed financial interests in the big companies that are providing the system and (b) a burning desire to get hold of everyone's personal medical data for government and police purposes.
It's not even legal as the responsibility for patient confidentiality belongs to the patient's own GP and if there's a misuse, they will be the ones legally to blame for sharing the data. There's some information on it here
If there's a need for easily transportable medical records, then this can be resolved by putting the data in the patient's hands. Public-Private key technology, or even hashes of the data, could be used to ensure accuracy. The solution is not that complicated, but in the UK we're having a very hard fight getting it.
Aide-toi, le Ciel t'aidera - Jeanne D'Arc.
It's impossible to store in a structured manner health information because it's so complex and individualized. Think about how to store the following.
1) "My arm hurts right here!" "Show me?" "Here!" "Wait, it's here now" "No no, it's here now"
2) "It itches sometimes" "when?, where?, duration? during aligment of planets!?"
3) "You need to take xyz, twice a day for two weeks. Come back in 3 month, and let's do another check up."
If anyone wants to know how complex it is, try reading the DICOM standard which is just for medical *image* storage and exchange. It's about 3500 pages. The code for medical billing, which the article mentions, is already the size of a dictionary. And all it contains is entries for a simple code and a one or two sentence description.
Realistically, the best approach may be PDF's and full text search. Anything else is just not going to capture the full extent of the medical history.