{"id":5335,"date":"2020-08-26T09:43:54","date_gmt":"2020-08-26T09:43:54","guid":{"rendered":"https:\/\/clinlabint.3wstaging.nl\/electronic-health-records-and-the-lab\/"},"modified":"2021-01-08T11:36:47","modified_gmt":"2021-01-08T11:36:47","slug":"electronic-health-records-and-the-lab","status":"publish","type":"post","link":"https:\/\/clinlabint.com\/electronic-health-records-and-the-lab\/","title":{"rendered":"Electronic health records and the lab"},"content":{"rendered":"

Two opposing agendas confront clinical labs in terms of electronic health records (EHRs): privacy\/security on the one side, and interoperability, on the other. The former involves an inward push for isolation, while the latter tends to pull technology in the other direction.
There also is a major financial challenge. While healthcare providers have been given a host of incentives to adopt EHRs (especially in the US), labs have been pretty much left out on their own.<\/strong><\/p>\n

EHRs and lab systems populate different worlds<\/strong>
Clearly, lab-compatible EHR systems which meet both (privacy and interoperability) criteria promise the quickest returns. EHR developers have however shown little enthusiasm, until recently, to incorporate clinical lab requirements as a sufficient driver, while laboratory system vendors have tended to ignore EHRs or postpone taking them into account until EHR development has matured sufficiently.  <\/p>\n

US EHR adoption drives lab applications<\/strong>
In the US, this limbo is being shaken up by healthcare providers, who are compelling vendors to take account of their need for EHR-friendly clinical lab systems.
At end 2012, the US Centers for Disease Control and Prevention (CDC) released a survey which found 72 percent of office-based physicians using EHR systems, up from 48 percent in 2009 and 18 percent in 2001. 
The reason for the dramatic increase in EHR adoption lies in the Meaningful Use requirements of the 2009 Health Information Technology for Economic and Clinical Health Act, also known as the HITECH Act. The Act provides billions of dollars in incentive payments through the Medicare and Medicaid programmes to increase physician adoption of EHR systems. <\/p>\n

Clinical labs are now being lifted by the rising tide of EHR adoption. According to the US Office of the National Coordinator for Health Information Technology (ONC), the \u201cavailability of structured lab results within the EHR contributes to office efficiencies while also assisting providers in the ability to make real time decisions about the patient\u2019s care.\u201d
The ONC explicitly specifies the threshold for EHR-friendly clinical lab practices in Stage 1 \u2013 of over 40 percent of all lab test results ordered by a provider and incorporated in certified EHR technology as structured data.
Stage 2 Meaningful Use requirements, finalised in August 2012, increase the clinical lab results threshold to 50 percent. The ONC has subsequently announced plans to assess health information exchange (HIE) in clinical laboratories.<\/p>\n

Labs left to own resources<\/strong>
While healthcare providers have the financial incentives of the HITECH Act, clinical labs have been left to their own resources to set up interfaces from their laboratory information systems (LIS) to providers.
Compounding this has been inconsistencies in the way different EHR systems generate lab test orders.
However, the alternative has been stark \u2013 to be left out of referrals from tests.<\/p>\n

EHR systems remain heterogeneous<\/strong>
The US EHR landscape is however hardly uniform. As of September 2013, there were 3,652 non-enterprise certified ambulatory EHR software systems, almost half of which were classified as \u201ccomplete\u201d to qualify for Meaningful Use Stage 1 or Stage 2.
In spite of efforts to set standards for semantic interoperability of healthcare data, standards so far are only syntactic (based on HL7 and XML). 
The alternative, to develop a common US-wide EHR system, has been accepted as being technically insurmountable \u2013 due to hurdles in specifying, developing, testing and deploying standardized tools, common architectures and vocabularies, within secure, real-time and scalable networks, and doing all this within the fast-changing world of information and communications technologies.
For proponents of a decentralized approach to EHR technology, in the US in particular, the sharp increase in offtake of EHR systems has shown that it has delivered \u2013 as far as healthcare IT objectives are concerned.<\/p>\n

EHR faces teething problems<\/strong>
Still, teething troubles for EHRs also clearly remain.
In early September 2013, one of the leading EHR systems, from EPIC, crashed across seven major healthcare facilities of Sutter Health, a nearly 100 year-old healthcare provider in California. Some suspect the role of a routine upgrade a few days earlier in the EHR system, which was launched by Sutter at a cost of $1.2 billion in 2004, but has so far reached only a halfway mark.<\/p>\n

EHR challenges for labs remain to be resolved<\/strong>
Such issues with the evolution of maturity of EHRs pose especially major problems for labs, who (as mentioned) have to develop and fund interfaces between their LISs and the EHRs of their client physicians but are also forced to cope with the lack of uniform EHR standards. <\/p>\n

Some vendors have nevertheless sought to fill the gap.
A leading example is HDD Access, a joint initiative by the US Department of Defense, the Department of Veterans Affairs and 3M Health Information Systems to create a public use version of 3M\u2019s Healthcare Data Dictionary (HDD). HDD Access consists of a relational database and Application Programming Interface (API) runtime services to which other applications can interface. The terminology is organized as a controlled medical vocabulary \u2013 a comprehensive set of clinical and other concepts used in healthcare.
HDD Access offers specific benefits for integrating LIS and EHR platforms. Independent of source system, it can track local fields and translate them into laboratory concepts. Nevertheless, HDD Access warns that it is \u201cnot a standard terminology and is not a replacement for standard terminologies.<\/p>\n

In effect, in the US, clinical labs are likely to continue to face a host of technical challenges with respect to EHRs in the years to come.

EHR Big Bang fizzles in Europe<\/strong>
Unlike the US, Europe made a massive effort in 2004 to devise common semantic standards for EHR interoperability as part of its Single eHealth Area. The EU\u2019s EHR objectives sought to integrate all patient information \u2013 from primary to tertiary settings, and include emergency and in-patient care. Also on the radar were ambitious plans to connect pharmacies as well as the web of disparate billing\/reimbursement procedures, and do so across Europe.
In mid\u20132008, the EU Commission set 2015 as the target year for EHR interoperability, to ensure that key EHR datasets could cross European borders, and do so in conformity with medical rules and other relevant legal frameworks. <\/p>\n

In January 2011, however, these ambitions were put on the backburner, after an official report criticized the effort as being both impractical and \u2018grandiose\u2019. The report found that a pan-EU EHR system would neither be technically feasible, cost-effective or even medically justified, and instead urged more emphasis on decentralized efforts \u2013 in other words, just like the US.
Technical challenges aside, massive differences in physician and medical cultures across Europe played a major role in derailing efforts toward a common EHR. Or, as EuroRec, an umbrella organization tasked with pan-EU EHR implementation, states: it was \u201cwidely recognized that social and organizational aspects are as likely to ruin an implementation process as technical factors are.\u201d<\/p>\n

European focus shifts to national efforts<\/strong>
The EHR focus in Europe has now totally shifted to national efforts. A new eHealth Governance Initiative (eHGI) encourages cooperation \u201cbetween Member States\u201d and \u201cbetween national authorities and standardization bodies\u201d, and seeks to \u201cenable the recommendation of standards and (harmonized) profiles based on selected use cases.\u201d On the technical side, compared to the Big Bang efforts of the Single eHealth Area, it also aims to \u201clink and harmonize coding systems\u201d and \u201cfacilitate access to existing standards and medical vocabularies.\u201d
The second area for Europe\u2019s EHR focus is a minimalistic intra-EU\/regional approach embodied in a project called epSOS, which dates back to 2008, but was (temporarily) eclipsed by the ambitions of the Single eHealth Area. epSOS, which went live in April 2012, has the modest goal of connecting 20 EU nations (and 3 non-EU members) to a secure database, and sharing only Patient Summaries and ePrescription records via IHE X* profiles. Its target consists of Europeans holidaying overseas.<\/p>\n

Today, EHR adoption varies considerably in Europe. The Nordic countries have been using the technology for over a decade and are fairly advanced as a result in EHR implementation.
However, adoption in France, Germany, Spain and the UK is \u2018on course\u2019 with the US.<\/p>\n

Shift from Single eHealth Area encourages new EHR-directed lab applications<\/strong>
The shift away from forcing through a Single eHealth Area has also opened the way for innovative working approaches aimed at clinical labs. One good example of this is Valle de los Pedroches Hospital at Cordoba, Spain, which has  designed and implemented a unified lab test request module for the Andalusian regional EHR.
In spite of some outstanding issues (such as rigidity in error solving, and the need to adapt to a new nomenclature), implementation of the laboratory module in the EHR improved the analytical process, with better patient safety and less programming or container errors and shorter response times. Clinical professionals gave a rating of 7.8 out of 10, positively highlighting the speed at which results are delivered and their integration in the EHR.
Such efforts are likely to grow with time.<\/p>\n","protected":false},"excerpt":{"rendered":"

Two opposing agendas confront clinical labs in terms of electronic health records (EHRs): privacy\/security on the one side, and interoperability, on the other. The former involves an inward push for isolation, while the latter tends to pull technology in the other direction. There also is a major financial challenge. While healthcare providers have been given […]<\/p>\n","protected":false},"author":2,"featured_media":10564,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[52],"tags":[],"class_list":["post-5335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-featured-articles"],"_links":{"self":[{"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/posts\/5335"}],"collection":[{"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/comments?post=5335"}],"version-history":[{"count":0,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/posts\/5335\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/media\/10564"}],"wp:attachment":[{"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/media?parent=5335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/categories?post=5335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/clinlabint.com\/wp-json\/wp\/v2\/tags?post=5335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}