Health Level 7

From LIMSWiki
Jump to: navigation, search
The Reference Information Model (RIM) is an important component of the HL7 v3.0 standard and is based on XML.

Health Level Seven (HL7) is an international non-profit volunteer-based organization involved with the development of international health care informatics interoperability standards.[1] The HL7 community consists of health care experts and information scientists collaborating to create standards for the exchange, management, and integration of electronic health care information.

The term "HL7" is also used to refer to some of the specific standards created by the organization (e.g., HL7 v2.x, v3.0, HL7 RIM).[2] HL7 and its members provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information. v2.x of the standards, which support clinical practice and the management, delivery, and evaluation of health services, are the most commonly used in the world.[3]

History

The International Organization for Standardization (ISO) got involved with standardizing network exchanges of data between computers around 1979, creating the Open Systems Interconnect (OSI) standards model. These formal OSI standards ranged across seven levels, from OSI Level 1 (physical layer, e.g. communication over coaxial cable) to OSI Level 7 (application layer, e.g. communication between clinical software). By 1981, researchers at University of California - San Francisco had created a proprietary protocol that unbeknownst to them at the time fit under the OSI Level 7 model. The protocol was developed for clinical purposes such that "computers exchanged several core messages, including the synchronization of patient admission-discharge-transfer information, orders from clinical areas, and the display of textual results to the clinical areas."[4]

By 1985, Simborg Systems (which developed hospital information systems) sought to have a non-proprietary protocol created because "standardization efforts at the time was either fragmented, in a different direction or with a different scope."[4] This led to a push to create a new standards organization, with initial meetings occurring at the end of March 1987. The meetings produced the term "HL7" and prompted a non-profit organization to be created, eventually known as Health Level Seven International. Version 1.0 of the HL7 specification was released in October 1987. The direction of HL7 was largely led by Simborg Systems; however, with greater practical use seen in furthering the protocol and non-profit, the first non-Simborg Systems chairperson, Ed Hammond, took the reigns in 1989.[4] By June 1990, Version 2.1 was published and included mechanisms for results reporting and billing. By the early- to mid-1990s news of HL7 was beginning to spread to international clinical sectors, particularly parts of Europe, including Netherlands, Germany, Canada, Japan, Australia, and the United Kingdom.[4][5]

In June 1994 the American National Standards Institute (ANSI) awarded Health Level 7 International status as an accredited standards developer. Version 2.2 became an official ANSI standard in February 1996. HL7 had roughly 1,700 members from various health care industries around the globe by the late 1990s.[5]

Version 3.0 of the HL7 standard was released in late 2005, which internationalized it and made it more consistent and precise.[6] Where the 2.x standards eventually received wide adoption for their flexibility and available implementation options, the 3.0 standards, in contrast, departed from that flexibility in order to be more "definite and testable, and provide the ability to certify vendors' conformance."[7] In 2009, Corepoint Health reported that most HL7 messaging was occurring using 2.3 and 2.3.1 models, with 3.0-based messages representing only a tiny fraction of all interfaces[8]; in 2012 Corepoint Health's Rob Brull estimated that more than 90 percent of all healthcare systems were still utilizing 2.x models.[9] That trend continued, with several experts proclaiming the standard to be more or less a failure.[10][11]

In early 2012, HL7 announced the HL7 FHIR (Fast Healthcare Interoperability Resources) initiative, which would utilize the best aspects of both 2.x and 3.0 standards, optimally resulting in a standard that is 20 percent the size of 3.0 but still meet the operation requirements of 80 percent of systems using the standard.[12] FHIR is being built on RESTful web services and provides modular, extensible "resources" to provide some flexibility but within a more fixed framework.[13] In December 2014, HL7 announced the Argonaut Project, meant "to hasten current FHIR development efforts in order to create practical and focused guidelines and profiles for FHIR by the spring of 2015."[14]

Standards

In total HL7 develops conceptual standards (e.g., HL7 RIM), document standards (e.g., HL7 CDA), application standards (e.g., HL7 CCOW), and messaging standards (e.g., HL7 v2.x and v3.0). Messaging standards are particularly important because they define how information is packaged and communicated from one party to another. Such standards set the language, structure, and data types required for seamless integration from one system to another.[15] Business use of the HL7 standards requires a paid organizational membership in HL7, Inc. HL7 members can access standards for free, and non-members can buy the standards from HL7 or ANSI.

HL7 v2.x and 3.0 are the primary standards from the organization. They provide a framework for data exchange among clinical and healthcare systems in an ideal format. The 2.x standards are flexible, with several implementation options, loosely geared towards "clinical interface specialists" working to move clinical data in the application space. The 3.0 standards are designed to be more fixed, precise, and international, geared towards governments and end users of clinical applications.[8]

While HL7 v2.x and 3.0 are the primary standards, a few other important standards and components are associated with HL7, as detailed below.

Reference Information Model (RIM)

The Reference Information Model (RIM) is an important component of the HL7 Version 3 standard. RIM expresses the data content needed in a specific clinical or administrative context and provides an explicit representation of the semantic and lexical connections that exist between the information carried in the fields of HL7 messages.[16] The standard is accepted as official by the ISO as ISO/HL7 21731; the original was approved in 2006, with a revised version appearing in 2014.[17]

Clinical Document Architecture (CDA)

The Clinical Document Architecture (CDA) is an XML-based markup standard intended to specify the encoding, structure, and semantics of clinical documents for exchange.[18] The standard is accepted as official by the ISO as ISO/HL7 27932; the most current version comes from 2009.[19]

Clinical Context Object Workgroup (CCOW)

The Clinical Context Object Workgroup (CCOW) family of standards are designed to enable disparate applications to share user context and patient context in real-time, particularly at the user-interface level. CCOW implementations typically require a CCOW vault system to manage user security between applications. The primary standard under CCOW is the Context Management Specifications (CCOW), which "serves as the basis for ensuring secure and consistent access to patient information from heterogeneous sources."[20] This standard is accepted as official by ANSI as ANSI/HL7 CMS V1.6.

Fast Healthcare Interoperability Resources (FHIR)

The Fast Healthcare Interoperability Resources (FHIR) standard was announced in 2012. FHIR was originally built on RESTful web services and provides modular, extensible "resources" to provide some flexibility but within a more fixed framework. During the development phase of FHIR, the driving fundamental principles were[21]:

  • prioritize implementers as the target user of the standard;
  • provide a flexible framework for interoperability;
  • limit complexity to where it's most needed;
  • keep conformance requirement minimal but also provide varying degrees of rigor;
  • leverage open source development principles;
  • make the standard available without cost;
  • support multiple exchange architectures;
  • leverage common web technologies;
  • make the standard forward and backward compatible; and
  • design, publish, and implement associated specifications using widely available tools.

In February 2014, Health Level Seven International published FHIR as a "Draft Standard for Trial Use" (DSTU), Release 1, version DSTU 1 (v0.0.82).[22] By December 2014, a broad cross-section of stakeholders committed to the Argonaut Project[23], which was dedicated to providing accelerated funding and political will to publish FHIR implementation guides and profiles for query/response interoperability and document retrieval by the spring of 2015. It would then be possible for medical records systems to migrate from the current practice of exchanging complex clinical document architecture (CDA) documents and instead exchange sets of simpler, more modular and interoperable FHIR JSON objects.[24] By August 2016, the CEO of HL7 was suggesting that although still a draft standard, FHIR was already capable of providing valuable features to early adopters.[25] In March 2017, the first standards for trial use or STU version of FHIR was released as Release 3. It included coverage of a variety of clinical workflows, a resource description framework format, and a variety of other updates.[26] Revision 4 was released in January 2019, with the key takeaway that "applications that implement the normative parts of R4 no longer risk being non-conformant to the standard," with those normative parts largely being "the RESTful API, the XML and JSON formats, the terminology layer, the conformance framework as well as Patient and Observation resources."[27]

Further reading

External links

References

  1. "About Health Level Seven International". Health Level Seven International. http://www.hl7.org/about/index.cfm. Retrieved 02 March 2012. 
  2. "Healthcare Interoperability Glossary". Corepoint Health. Archived from the original on 15 January 2016. https://web.archive.org/web/20160115213217/http://www.corepointhealth.com/resource-center/healthcare-interoperability-glossary. Retrieved 15 April 2020. 
  3. Shaver, D. (2010). "The HL7 Evolution - Comparing HL7 Versions 2 and 3" (PDF). Corepoint Health. Archived from the original on 03 March 2016. https://web.archive.org/web/20160303221932/http://corepointhealth.com/sites/default/files/whitepapers/hl7-v2-v3-evolution.pdf. Retrieved 15 April 2020. 
  4. 4.0 4.1 4.2 4.3 Spronk, René (05 September 2014). "The Early History of Health Level 7". Ringholm BV. http://www.ringholm.com/docs/the_early_history_of_health_level_7_HL7.htm. Retrieved 17 February 2015. 
  5. 5.0 5.1 Di Lima, Sara N.; Johns, Lisa T.; Liebler, Joan Gratto (1998). A Practical Introduction to Health Information Management. Jones & Bartlett Learning. ISBN 9780834212312. https://books.google.com/books?id=vX_zVaMlR8sC&pg=PA90. Retrieved 17 February 2015. 
  6. Shaver, D. (05 October 2006). "What Is HL7 Version 3 or V3?". Health Standards. http://healthstandards.com/blog/2006/10/05/what-is-hl7-version-3-or-v3/. Retrieved 15 April 2020. 
  7. "HL7 Version 3 Product Suite". Health Level 7 International. 15 May 2014. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=186. Retrieved 18 February 2015. 
  8. 8.0 8.1 Shaver, D. (2009). "The HL7 Evolution: Comparing HL7 Version 2 to Version 3, Including a History of Version 2" (PDF). Corepoint Health. Archived from the original on 03 March 2016. https://web.archive.org/web/20160303221932/http://corepointhealth.com/sites/default/files/whitepapers/hl7-v2-v3-evolution.pdf. Retrieved 15 April 2020. 
  9. McNickle, M. (25 April 2012). "8 common questions about HL7". Healthcare IT News. HIMSS Media. https://www.healthcareitnews.com/news/8-common-questions-about-hl7. Retrieved 15 April 2020. 
  10. Morin, J. (04 January 2011). "Will HL7 V3 Adoption Take Off in 2011? 5 Points and 1 Caveat". Caristix Blog. Caristix. http://caristix.com/blog/2011/01/will-hl7-v3-adoption-take-off-in-2011/. Retrieved 18 February 2015. 
  11. Grieve, G. (15 August 2011). "HL7 needs a fresh look because V3 has failed". Health Intersections Blog. Health Intersections Pty. Ltd. http://www.healthintersections.com.au/?p=476. Retrieved 18 February 2015. 
  12. McKenzie, L. (February 2012). "HL7’s Next Generation Standard is Coming: Keep Calm, Carry On". Healthcare Information Management & Communications Canada 26 (1). Archived from the original on 09 January 2014. https://web.archive.org/web/20140109022012/http://www.healthcareimc.com/node/515. Retrieved 15 April 2020. 
  13. Brull, R. (26 March 2013). "5 Things to Know About HL7 FHIR". Health Standards Blog. Health Standards. http://healthstandards.com/blog/2013/03/26/hl7-fhir/. Retrieved 15 April 2020. 
  14. Kern, C. (12 December 2014). "HL7 Advancing FHIR". Health IT Outcomes. Jameson Publishing. https://www.healthitoutcomes.com/doc/hl-advancing-fhir-0001. Retrieved 15 April 2020. 
  15. Kim, K. (July 2005). "Creating Clinical Data Standards in Health Care: Five Case Studies" (PDF). California HealthCare Foundation. Archived from the original on 10 September 2012. https://web.archive.org/web/20120910215044/http://www.kathykim.com/sitebuildercontent/sitebuilderfiles/ClinicalDataStandardsInHealthCare.pdf. Retrieved 15 April 2020. 
  16. "HL7 Reference Information Model". Health Level 7 International. http://www.hl7.org/implement/standards/rim.cfm. Retrieved 17 February 2015. 
  17. "ISO/HL7 21731:2006". International Organization for Standardization. https://www.iso.org/standard/40399.html. Retrieved 15 April 2020. 
  18. Boone, Keith W. (2011). The CDA Book. Springer Science & Business Media. pp. 17–21. http://books.google.com/books?id=rwa6DDB4jY8C&pg=PA17. Retrieved 17 February 2015. 
  19. "ISO/HL7 27932:2009". International Organization for Standardization. https://www.iso.org/standard/44429.html. Retrieved 15 April 2020. 
  20. "Product CCOW". HL7 Wiki. Health Level 7 International. 27 October 2010. https://wiki.hl7.org/index.php?title=Product_CCOW. Retrieved 15 April 2020. 
  21. "Fundamental Principles of FHIR". HL7 Wiki. Health Level 7 International. 17 September 2014. Archived from the original on 17 November 2014. https://web.archive.org/web/20141117041614/https://wiki.hl7.org/index.php?title=Fundamental_Principles_of_FHIR. Retrieved 15 April 2020. 
  22. =HL7 International (February 2014). "HL7 Fast Healthcare Interoperability Resources Specification 'FHIR', Release 1". http://www.hl7.org/implement/standards/product_brief.cfm?product_id=343. Retrieved 15 April 2020. 
  23. HL7 International (04 December 2014). "HL7 Launches Joint Argonaut Project to Advance FHIR" (PDF). http://www.hl7.org/documentcenter/public/pressreleases/HL7_PRESS_20141204.pdf. Retrieved 15 April 2020. 
  24. Braunstein, M. (26 January 2015). "Can Argonaut Project Make Exchanging Health Data Easier?". InformationWeek. https://www.informationweek.com/strategic-cio/can-argonaut-project-make-exchanging-health-data-easier/a/d-id/1318774. Retrieved 15 April 2020. 
  25. Murphy, K. (09 August 2016). "Health IT Standard FHIR Ready to Advance Interoperability". EHR Intelligence. https://ehrintelligence.com/news/health-it-standard-fhir-ready-to-advance-interoperability. Retrieved 15 April 2020. 
  26. Miliard, M. (22 March 2017). "HL7 publishes a new version of its FHIR specification". Healthcare IT News. https://www.healthcareitnews.com/news/hl7-publishes-new-version-its-fhir-specification. Retrieved 15 April 2020. 
  27. Sullivan, T. (02 January 2019). "HL7 releases FHIR 4". Healthcare IT News. https://www.healthcareitnews.com/news/hl7-releases-fhir-4. Retrieved 15 April 2020.