With the Jan. 30 release of the Office of the National Coordinator for Health ITs draft Interoperability Roadmap and Standards Advisory, the buzzword at the ONC Annual Meeting in Washington, D.C.which starts todayis interoperability.
Just days after the release of the documents for public comment, nationwide interoperable health ITthe theme of ONCs Feb. 2-3 meetingis on the minds of many attendees. ONCs draft Interoperability Roadmap and companion 2015 Interoperability Standards Advisory are being met with widespread approval by HIT stakeholders.
Charles Jaffe, M.D., CEO of Health Level Seven International (HL7), tells Health Data Management that his standards development organization, which is focused on healthcare information interoperability, applauds the ONC effort to develop a roadmap which he calls comprehensive in addressing the future state of interoperable health IT.
Its a great challenge to identify what we will be doing years down the road, but it certainly gives the community of developers and users an opportunity to see what might be part of regulation in the coming years, said Jaffe, who argues that no single entity or organization is going to solve the challenges to interoperability but instead requires a broad coalition of public-private partners.
He adds that the Standards Advisory is a terrific first start. I had discussions with ONCs Steve Posnack and Karen DeSalvo face to face last week and we reviewed what it means and what it doesnt mean. For most people, the advisory is a start in identifying what standards are used, what standards might be used, and what changes we need to make to the existing ones, Jaffe says.
However, Micky Tripathi, president and CEO of the Massachusetts eHealth Collaborative, is not quite as happy with the Standards Advisory as he is with the Interoperability Roadmap. When you think about some of the things that are articulated as best standards, I would recommend taking a step back and considering the maturity framework that the HIT Standards Committee approved and uses as a kind of litmus test, advises Tripathi. A standard should not only be published and be out there, but it should also actually be adopted and have some level of market adoption, because unless you do that it ends up becoming something thats thrown on the market and may or may not actually work.
Tripathy adds that there are a number of things in the Standards Advisory that are not widely deployed in the healthcare industry and dont meet that litmus test.
Stanley Huff, M.D., chief medical informatics officer for Intermountain Healthcare, makes the case that truly interoperable standards must become an integral part of health IT systems to enable them to talk to one another, rather than the current situation which involves what he calls point-to-point negotiation.
The situation we have today is that each system is based on different physical and logical structures for their data, as well as different coding systems, says Huff. We have some good standards and weve certainly learned a lot in creating standards, but the standards that we have today that are immediately available and ready to go dont lead to true interoperability.
FHIR on Fast Track
Huff, who is also a founding member of Healthcare Services Platform Consortiuma group of providers, IT vendors, system integrators and venture-led firms dedicated to solving the industry-wide interoperability problemsees real potential in HL7s Fast Healthcare Interoperability Resources (FHIR), a RESTful API that leverages the latest web standards.
FHIR is much easier and simpler to implement than a lot of the previous standards that weve had, he asserts. There is the opportunity for those FHIR services to be truly interoperable ifand theres a big if in therewe as a country and as people agree to the information models and terminology that were going to use for exchanging information.
A report released last year by ONC that was put together by JASON, an independent group of scientists that advises the U.S. government on science and technology, decried the lack of interoperability in the current health IT ecosystem and called for the creation of an open, interoperable health data infrastructure based on the adoption of public APIs. The Health IT Standards and Policy Committees JASON Task Force agreed with the JASON report's assessment that lack of an architecture supporting standardized APIs is a major impediment to achieving interoperability.
Tripathi, co-chair of the JASON Task Force, believes that ONCs Interoperability Roadmap is closely aligned with the task force recommendations, specifically the idea of having an evolutionary approach and moving to an open API-based world looking at document-level and data-level interoperability. In addition, as the manager of HL7s Argonaut Project to accelerate the development and adoption of FHIR, he calls current standards such as the Consolidated-Clinical Document Architecture (C-CDA) very cumbersome and unwieldy.
The purpose of the Argonaut Project is to rapidly develop a first-generation FHIR-based API and core data services specification to enable expanded information sharing for electronic health records and other health IT, based on Internet standards and architectural patterns and styles. He describes the project as a code documentation sprint.
The project includes the participation of several major vendors and providers including: athenahealth, Beth Israel Deaconess Medical Center, Cerner, Epic, Intermountain Health, Mayo Clinic, McKesson, MEDITECH, Partners Healthcare System, SMART at Boston Childrens Hospital Informatics Program, and The Advisory Board Company.
What the Argonaut Project represents is reflected in many ways in the Interoperability Roadmap, according to Tripathi. When you think about the idea of market-based governance and market accountability for interoperability, thats exemplified in the Argonaut Project because its a group of providers and vendors.
In fact, the Argonaut Projects charter expresses the hope that FHIRs successful and rapid adoption would preclude the need for further federal government intervention in interoperability standards while warning that a premature certification requirement might have an adverse effect on the development and adoption of this important work.
Nonetheless, Tripathi says that although FHIR-based standards are not mature enough for inclusion in 2015 Edition Certification he thinks they could perhaps be ready for certification in 2016 should ONC go that route. Regardless, HL7s Jaffe concludes: I think everybody recognizes that if it achieves its promise, FHIR will become a critical standard as we move forward.
Register or login for access to this item and much more
All Health Data Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access