The international experience in interoperability of health information 170505


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The international experience in interoperability of health information 170505

  1. 1. The international experience ininteroperability of Health InformationSystemsGeorge KakoulidisCEO, Apollo SA 8th WORLD HELLENIC BIOMEDICAL CONGRESS
  2. 2. HL7 Hellasin this Presentation Interoperability definitions HL7 Standards Interpretability Tools The Future
  3. 3. HL7 HellasHealth Care Industry Health Care is an industry where a diverse set of players must collaborate to provide a wide array of services Primary Hospital Pharmacy Doctor’s Office Employee Employer PATIENT DATA Chem Lab Insurance Secondary Hospital Home Health Care Nursing Home Care
  4. 4. HL7 HellasHealthCare Enterprise involve complex processes involve clinical and administrative tasks large volumes of data large numbers of patients and personnel performed either by humans or by automated systems
  5. 5. HL7 HellasDefinition What is computer interoperability?  "The ability of two or more systems or components to exchange information and to use the information that has been exchanged.“  [Institute of Electrical and Electronics Engineers IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries, IEEE, 1990]
  6. 6. HL7 HellasDefinition What is application integration?  "The way to create interoperability solutions in HealthCare Information Systems "  " The successful integration of disparate systems, applications, data, vendors, functions"
  7. 7. HL7 HellasHistorical need for Integration 1960 1980 1990 2000 So me Al No EA Min LA Ma ot Int nee WA I er f N/ inf d i-L ace N r WA am s an es N
  8. 8. HL7 HellasProblems in HealthCare IT  Hospitals never had a lot of money  Lots of Departments with unique IT solution  Multiple proprietary systems, varying platforms, different languages  Local data /Lack of Standards  Structured and Unstructured data (free text)  All systems Must work together
  9. 9. HL7 HellasWhat need integration ?  Hospital service-related functions, as ADT, Order Entry, Result Reporting, Materials Management, Patient Accounting, Medical Chart  Departmental systems, as Clinical Laboratory, Pharmacy, Radiology, Pathology  Resource management, scheduling, physician billing
  10. 10. HL7 HellasInteroperability  “Interoperability” can only be achieved through the use of data standards and clinical terminologies.
  11. 11. HL7 HellasStandards Why Standards ?  HealthCare information is increasingly transmitted electronically  In order to exchange information using common data format cost effective  Examples (Mobile –GSM, ATMs,)
  12. 12. HL7 HellasWhat standards are needed?  Communication standards  Data interchange standards  Information model standards  Vocabulary standards  Security standards
  13. 13. HL7 HellasStandards – HL7 HL7 provides a set of communication standards as a cost-effective approach for connecting disparate information systems in health.
  14. 14. HL7 HellasHL7 Health Level Seven is an ANSI Standards Developing Organization Mission : "To provide a comprehensive framework and related standards for the exchange, integration, sharing, and retrieval of electronic health information that supports clinical practice and the management, delivery and evaluation of health services. Specifically, to create flexible, cost effective standards, guidelines, and methodologies to enable healthcare information system interoperability and sharing of electronic health records.“ (Source: HL7 Mission statement, revised 2001)
  15. 15. HL7 HellasHL7 History 1987 : Start work as a standard 1990 : First standard (v2.1) 1993/94: First International Affiliates join. 1994: HL7 becomes ANSI-accredited. August 2001: 1st V3 Draft is released. June 2003: HL7 V2.5 released.
  16. 16. HL7 HellasHL7 Organization ANSI-approved Standards Developing Organisation (SDO). Not-for-profit. >2200 members. >500 corporate members. Local organisations in more than 27 countries.
  17. 17. HL7 HellasWhy HL7 ? International Standard since 1991 International Standard since 1991 Used Worldwide (27 HL7 Affiliates) Used in EU (Germany, Holland, Finland, Italy etc) HL7 HL7-TC251 Task Force ANSI Standard ANSI Standard Used in Real-life for more than 10 years Open Standard continuously updated Latest Version 2.5 (Conformance Statements)
  18. 18. HL7 HellasHL7 Facts HL7 is not a software application The HL7 standard is a ‘book of rules’ prime objective of HL7 is to simplify the implementation of interfaces between healthcare software applications HL7 has grownup and become the de facto model for the entire healthcare industry’s data exchange challenges.
  19. 19. Interoperability & HL7 HL7 HellasConsiderations HL7 is not a plug and play Not all the Health Information Systems have HL7 interface Complex data exchanges needs special software applications like “Interface Engines”
  20. 20. HL7 HellasInterface Engines Mission Critical Component Formatting Messages and Routing them Complex data exchanges needs special software applications like “Interface Engines” or “Integration Engines”
  21. 21. HL7 HellasInterface Engines Hospital’s Clinical Data “Telephone Exchange”
  22. 22. HL7 HellasInterface Engines Past  complicated issue  required extensive programming expertise from IT stuff  hard to deal with different HL7 versions and formats  different communication points  complicated administrative tasks  maintenance and support was very complex Today  Graphical UI  Easy of use  Ready Protocol Libraries (HL7 Versions)  Different ways to Communicate
  23. 23. HL7 HellasLarge Scale Implementation Health Regional System Sub-Systems CDR Scheduling Portal ERP MIS Scheduling Integration Engine Hospital 1 Hospital 10 Reg.Centers HIS IE IE …… HIS - ERP ERP - MR ADT LAB LAB PACS
  24. 24. HL7 HellasIntegration strategy Integration Engine on its own is not enough! Need Master Patient Index for validation Need highly skilled IT resources Need money to invest in integration (not a given today)
  25. 25. HealthCare Interoperability the Future HL7 HellasWhat we expect ? HL7 v3.0  Promise of plug and play interoperability  Robust approach to development  Widespread support Open Systems Integration of Services and Technologies Use of new Technologies in Software Integrations  Web Services  Service Oriented Architecture