{"id":360,"date":"2013-11-12T11:03:23","date_gmt":"2013-11-12T01:33:23","guid":{"rendered":"http:\/\/blog.healthbase.info\/?p=360"},"modified":"2013-11-12T11:13:30","modified_gmt":"2013-11-12T01:43:30","slug":"the-power-the-glory-and-the-dangers-of-structured-health-data","status":"publish","type":"post","link":"http:\/\/healthbase.info\/blog\/?p=360","title":{"rendered":"The Power, the Glory and the Dangers of structured health data"},"content":{"rendered":"

It is now over eighteen months since I publicly aired my grave concerns<\/a> regarding a \u00a0critical safety issue for Australia’s Personally Controlled Electronic Health Records (PCEHR) system, which centred around the lack of scrutiny of the quality of data in CDA documents to be contributed to people’s records. I have no idea if anyone other than Grahame Grieve<\/a> took my concerns seriously. Certainly, no-one else has ever contacted me regarding the serious safety and quality issues I raised at the time, least of all NEHTA.<\/p>\n

But it does appear that safety and quality issues have been getting slightly more attention in recent months than they did 18 months ago – at least in Australia. And on this front, I have some further good news.<\/p>\n

By way of background, for most of that 18 months I was working for SA Health on the integration and migration of ( mainly Adelaide-based public ) hospital systems to work with a new potentially statewide public hospital EMR and Patient Administration System known affectionately as EPAS. The network’s “central” components comprise a number of Allscripts Sunrise products, an Intersystems Ensemble Integration Engine, and an Enterprise Patient Master Index built around the IBM \u00a0Initiate EMPI product. It is undoubtedly one of Australia’s largest health system integration undertakings, with over 200 interfaces supported by the single integration engine. I was responsible for the specification and documentation of many of these interfaces and for testing a number of key ones, including much of the integration with EPAS. Nearly all of the interfaces use \u00a0some variant of HL7 v2.3.1. I \u00a0became acutely aware of the structural and semantic issues associated with integration on this scale, and even more so with the issues pertaining to codes and code mapping. The primary clinical system, Sunrise Clinical Manager, alone has well over a thousand code tables (Dictionaries) many of which were in a cyclical state of flux during the configuration and testing phases of the project. Over 10,000 new codes were introduced just to describe patient locations – hospitals, campuses, wards, rooms, beds, chairs etc. in a uniform fashion. The integration task was, and still probably is, a herculean task. We had full time team of 12 involved.<\/p>\n

Despite HL7’s dominance in the e-health messaging world over the past 15 or so years, there has never been any viewer produced anywhere in the world (to my knowledge) that allows or assists technical IT people, let alone clinicians, to view HL7 messages in a “meaningful” way, with their codes decoded into human readable form. Until now!<\/p>\n

I have spent the past two months changing the situation. I’ve taken the embryonic version I started for Healthbase Australia’s Pathology message validator some 2.5 years ago and radically improved it to the point where I think it worth making it available to the community. The current incarnation “understands” most of the internal HL7 \u00a0message codes, it can display the meaning of SNOMED, LOINC, AMT, AUSTPATH, some ICD-O morphology codes, ISO+ units, and I have started to incorporate the new Pathology Units and Terminology descriptions developed under the Royal College of Pathologists Australasia (RCPA) \u00a0led PUTS project. The view hides, by default, the arcane codes used by HL7 and presents pathology, diagnostic imaging and other HL7 v2 based messages in a form readily understandable to clinicians and even patients. It follows the evolving Australian AS4700.2 standard, and conventions. It renders inline images directly, it supports and displays embedded narrative reports – PIT, JPG, HL7 formatted text, PDF, RTF and HTML as described in the Standards Australia Handbook HB262. \u00a0It supports the viewing of multiple messages per file.\u00a0<\/p>\n

The previous federal Health Minister announced shortly before the September election, some funding and an undertaking to accelerate the uploading of pathology results to the PCEHR. From the rumours that have been going around, this is likely to be done using PDF versions of each report, uploaded somehow from GP desktops. If only we could, instead, harness the power already inherent in the HL7 v2 messages already sent by most pathology labs to GP systems. The Healthbase Results Viewer<\/a> gives a glimpse of how that might add value that a PDF file could never do. The following image is a snapshot of a result where the viewer has interpreted the structured data and automatically added links to one or more detailed authoritative web sites describing the tests undertaken, their context for use, their typical reference ranges and any qualifiers and warnings. The two authoritative sources for this test information, that I have already built into the viewer are the LabTestOnline site and the RCPA manual. The viewer links directly to the relevant test page. Moreover, to illustrate how universal \u00a0and flexible an approach this is, I have also included links to much of the Spanish version of LabTestsOnline and the viewer picks up these links through a LOINC\/viewer\/labtestonline synonym table.<\/p>\n

\u00a0<\/p>\n

\u00a0<\/p>\n

\"Path<\/p>\n

But I think what the viewer has most to offer, is the ability to dramatically allow focus on quality and safety issues, particularly around coding, code mapping and display names. It allows clinicians to assess and address message quality and safety issues in a way never before possible.<\/p>\n

So if you sit on a safety and quality committee, if you are a vendor or developer of healthcare software that shares information electronically, if you contribute to e-health messaging standards, if you are a systems integrator, health informatician, clinical terminologist, if you are a clinician or researcher with a focus on the quality of data in e-health, then you cannot take your role seriously without having the ability to assess that quality \u00a0in the millions of messages being exchanged daily via HL7. This is true if you live in Namibia, New York or Newcastle. You now have the ability to shine a light on what until now has been far too dark a place for most people to venture. If you care about quality and safety, please switch on the light!<\/p>\n

http:\/\/pathology.healthbase.info\/viewer<\/a> .<\/p>\n","protected":false},"excerpt":{"rendered":"

It is now over eighteen months since I publicly aired my grave concerns regarding a \u00a0critical safety issue for Australia’s Personally Controlled Electronic Health Records (PCEHR) system, which centred around the lack of scrutiny of the quality of data in CDA documents to be contributed to people’s records. I have no idea if anyone other […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39,5],"tags":[20,50,61,32],"class_list":["post-360","post","type-post","status-publish","format-standard","hentry","category-exchange-formats","category-pathology","tag-hl7","tag-hl7-cda","tag-pathology","tag-pcehr"],"_links":{"self":[{"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/360","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=360"}],"version-history":[{"count":3,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/360\/revisions"}],"predecessor-version":[{"id":370,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=\/wp\/v2\/posts\/360\/revisions\/370"}],"wp:attachment":[{"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=360"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=360"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/healthbase.info\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=360"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}