Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sydney 2002 plenary final


Published on

  • Be the first to comment

  • Be the first to like this

Sydney 2002 plenary final

  1. 1. Michael Mair Timaru Eye Clinic New Zealand Sydney 24-25 April Health Information Technology Standards
  2. 2. Why do we need Standards?
  3. 3. Why do we need Standards?
  4. 4. Why do we need Standards?
  5. 5. Why do we need Standards?
  6. 6. Why do we need Standards?
  7. 7. Why do we need Standards?
  8. 8. <ul><li>Healthcare Information is increasingly transmitted electronically. </li></ul><ul><li>For Healthcare IT systems to exchange information, they can either: </li></ul><ul><ul><li>communicate via custom interfaces </li></ul></ul><ul><ul><li>share a common data format </li></ul></ul><ul><li>Custom interfaces are costly to design and difficult to maintain (~ $100k each). </li></ul>Why Standards? A common data format is cost-effective, but needs up-front agreement and commitment = “a Standard”. Sydney 24-25 April
  9. 9. Other Examples of Standards <ul><li>Mobile Phones (“GSM”) </li></ul><ul><li>CDs </li></ul><ul><li>ATMs </li></ul>Sydney 24-25 April
  10. 10. Healthcare Economics <ul><li>… . are adversely affected by poor documentation quality. In the United States alone, the cost of information capture is estimated to be over $50 billion annually. A significant portion of this cost is likely to be due to inefficiencies... </li></ul>Sydney 24-25 April
  11. 12. … into this
  12. 13. The need to share more healthcare data <ul><li>with other clinicians in the same team </li></ul><ul><li>with other healthcare professions </li></ul><ul><ul><li>doctors, nurses, physiotherapists, midwives, dieticians... </li></ul></ul><ul><li>with other disciplines </li></ul><ul><ul><li>a diabetic patient may also be under ophthalmology, nephrology, orthopaedics, chiropody, wheelchair clinic. </li></ul></ul><ul><li>with other institutions </li></ul><ul><li>with patients and their families </li></ul>Sydney 24-25 April
  13. 14. Growing numbers of concepts <ul><li>Around half of the concepts believed to exist in the world (500,000) are in the medical domain </li></ul>Sydney 24-25 April
  14. 15. Gartner’s Vision for Healthcare: The Next 10 years <ul><li>Analyzed the future of Healthcare on a two axis continuum: </li></ul><ul><ul><li>Accountability for Payment (single purchaser Vs – multiple purchasers (consumers are purchasers) </li></ul></ul><ul><ul><li>Standards and Structured Data (‘blurry islands of data’ Vs ‘robust data sharing’) </li></ul></ul>Sydney 24-25 April
  15. 16. Healthcare 2010 Matrix Accountability for Payment (single Vs multiple purchasers) Structured Data Standards Development Sydney 24-25 April
  16. 17. All stakeholders would benefit from Structured Data standards Under both ‘centralized’ and ‘user pays’ models, Healthcare provision gets more rational with Structured Data Standards Sydney 24-25 April
  17. 18. The Health Standards Committee of the International Organization for Standards ISOTC/215, Mission Statement: <ul><li>“ Standardization in the field of information for health, and Health Information and Communications Technology (ICT), to achieve compatibility and interoperability between independent systems. Also, to ensure compatibility of data for comparative statistical purposes (e.g. classifications), and to reduce duplication of effort and redundancies. “ </li></ul>Sydney 24-25 April
  18. 19. Interoperability has two components <ul><li>Interoperability: </li></ul><ul><li>“ Ability of two or more systems or components to exchange information and to use the information that has been exchanged ” </li></ul><ul><ul><li>[ IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries, IEEE, 1990] </li></ul></ul>Sydney 24-25 April Semantic interoperability Functional interoperability
  19. 20. Standard Generalized Mark Up Language (SGML) <ul><li>Origin from efforts 30 years ago to rationalize the publishing process </li></ul>Gave the ability to classify, compute, combine, and manipulate information without putting it in a database HTML (Hypertext Mark Up Language) is an application of SGML Sydney 24-25 April
  20. 21. XML—(eXtensible Markup Language) from the World Wide Web Consortium <ul><li>Emerging standard for content-aware Web pages that will replace HTML </li></ul><ul><li>Separates data display from semantics </li></ul><ul><li>Provides atomic metadata about object in a document </li></ul><ul><li>Non-proprietary </li></ul><ul><li>Vendor, platform, application neutral </li></ul>Sydney 24-25 April
  21. 22. XML Limitations <ul><li>XML describes grammars--is a syntactic standard--no way to recognize semantic units </li></ul><ul><li>XML does NOT create a data model by itself </li></ul><ul><li>BUT: XML will be the common data format that goes ‘down the wire’! </li></ul>Sydney 24-25 April
  22. 23. How to achieve Structured Data <ul><li>Natural Language Processing </li></ul><ul><li>Controlled Vocabularies </li></ul><ul><li>Knowledge Based Models </li></ul>Sydney 24-25 April
  23. 24. Natural language processing (NLP) <ul><li>Natural language processing (NLP), or natural language understanding (NLU), can turn free text into structured data. </li></ul><ul><li>However without prior agreement on the meaning of terms used, its usefulness is limited </li></ul>Sydney 24-25 April
  24. 25. Controlled Vocabularies <ul><li>SNOMED International, from the College of American Pathologists ‘Systematized Nomenclature of Medicine’ . </li></ul><ul><li>Includes REED Codes (formerly from UK) </li></ul><ul><li>The International Classification of Diseases (ICD9 and ICD 10) owned by the WHO </li></ul><ul><li>LOINC The Logical Observation Identifiers Names and Codes from the Regenstrief Institute </li></ul>Sydney 24-25 April
  25. 26. Growth of SNOMED (from Sydney 24-25 April
  26. 27. What is a Knowledge Based (KB) Model? <ul><li>A knowledge based model is capable of expressing instances of domain knowledge (knowledge about something) </li></ul><ul><li>Most modern applications are written with‘Object Orientated’ programming </li></ul><ul><li>A ‘knowledge based’ model defines the classes and relationships making up the domain of interest, which become‘objects’ when instantiated.. </li></ul>Sydney 24-25 April
  27. 28. Controlled Vocabularies are not enough <ul><li>We still need a separate class of clinical entities that get coded, e.g. blood pressure, intra-ocular pressure, macular appearance... </li></ul><ul><li>These will need to include the 5 WH of their capture (the what, where, why, when, who) </li></ul><ul><li>It is the definition and collection of these that makes up a ‘knowledge base’ </li></ul>Sydney 24-25 April
  28. 29. Examples of KB Models <ul><li>The Health Level Seven (HL7) v3 Reference Information Model (RIM) </li></ul><ul><li>The Good Electronic Health Record (GEHR) Object Model (GOM) </li></ul><ul><li>The Health Records Committee of the Centre Europeen de Normalization (CEN) Four Part Standard ( ENV 13606) </li></ul><ul><li>The Common Object Request Broker Architecture Medical Model (CORBAmed) </li></ul>Sydney 24-25 April
  29. 30. Only two. since a Recent ‘Memorandum of Understanding’ between GEHR and CEN, CORBA (Aix en Provence Nov 2001) <ul><li>Open EHR foundation : GEHR Object Model/CEN ENV13606/CORBAmed, for a g lobal EHR architecture </li></ul><ul><li>HL7 v3 RIM Reference Information Model. HL7 version 2.* is already widely used in healthcare messaging. www.HL7org </li></ul>Sydney 24-25 April
  30. 31. Digital Imaging and Communications in Medicine (DICOM) <ul><li>Formed in 1983 by American College of Radiology (ACR) and the National Electrical Manufacturers Association </li></ul><ul><li>permits the transfer of medical images in a multi-vendor environment. </li></ul><ul><li>facilitates the development and expansion of picture archiving and communication systems, and interfacing with medical information systems. </li></ul>Sydney 24-25 April
  31. 32. A Convergence is apparent: (from Tom Beale of GEHR) <ul><li>A general model of &quot;containers” and “content”.. The &quot;container&quot; can be equated with: </li></ul><ul><ul><ul><ul><li>Documents (including in the web sense of a unit of information transmission) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The unit of committal to record systems </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The unit for security setting </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The unit of transmission of health info. </li></ul></ul></ul></ul><ul><li>The container is called a &quot;transaction&quot; in GEHR, a &quot;component&quot; in CEN 13606, and a Clinical Document Architecture unit (CDA) in HL7 speak </li></ul>Sydney 24-25 April
  32. 33. Baskets and Objects <ul><li>The ‘standard’ might consist of standard ‘baskets’ that could be containers for standard ‘objects’. </li></ul><ul><li>Objects are already common place in modern programming, easy to ‘align’ </li></ul><ul><li>A non-proprietary protocol already exists to securely exchange them - the Simple Object Access Protocol (SOAP) </li></ul><ul><li>Subjective-Objective-Assessment-Plan is a common record keeping format (SOAP units from Lawerence Weed) </li></ul>Sydney 24-25 April
  33. 34. The standard in a nut-shell (or basket….) Share ‘SOAPS’ with ‘ SOAPS’ (but there can be multiimedia objects in the baskets as well..) Sydney 24-25 April
  34. 35. From:JJ Michon, M.D. Duke University School of Medicine HTML & XML Tags <ul><li>HTML -Display </li></ul><ul><li><TITLE> </li></ul><ul><li><HEAD> </li></ul><ul><li><BODY> </li></ul><ul><li><TABLE> etc. </li></ul><ul><li>XML -Semantics (limited) </li></ul><ul><li><PT ID#> </li></ul><ul><li><IMAGE TYPE> </li></ul><ul><li><DIABETES </li></ul><ul><li>DURATION> </li></ul><ul><li><LAST DFE> </li></ul><ul><li><BLOOD SUGAR LEVEL> </li></ul><ul><li><LASER HISTORY> </li></ul><ul><li><VISUAL ACUITY> etc </li></ul>=> METADATA Sydney 24-25 April
  35. 36. Data ‘Objects’: the HL7 Structured Documents group is looking at: <ul><ul><ul><li> GEHR Archetypes </li></ul></ul></ul><ul><ul><ul><li> CEN Archetypes </li></ul></ul></ul><ul><ul><ul><li> 3M Information Models </li></ul></ul></ul><ul><ul><ul><li> SNOMED/DICOM Microglossary </li></ul></ul></ul><ul><ul><ul><li>A convergence in now possible </li></ul></ul></ul>Sydney 24-25 April
  36. 37. <ul><li>Is a kind of container. </li></ul><ul><li>A snapshot of the patient’s health event </li></ul><ul><li>Includes: referrals and discharge summaries </li></ul><ul><li>Includes as data types: structured data, free text, images and multimedia </li></ul>The Health Event Summary (HES): What is it? 2 Sydney 24-25 April
  37. 38. Why HES? <ul><li>HES can provide the standard architecture for effective electronic transmissions of clinical / health data between providers </li></ul><ul><li>Provides a credible foundation architecture for evolution towards electronic healthcare record </li></ul>4 Based on standard Stakeholder support Sydney 24-25 April
  38. 39. Clinical Guidelines and Decision Support <ul><li>There are already a number of ‘engines’ that deliver these services to Electronic Health Records </li></ul><ul><li>It is important that there is a level of the ‘standard’ which is non evaluative or prescriptive </li></ul><ul><li>Clinical Guidelines should not be intrinsic to the standard. The container should be ‘dumb’ </li></ul>Sydney 24-25 April
  39. 40. If such a ‘standard’ was achieved <ul><li>conduct and control of health services would remain entirely local, including access control </li></ul><ul><li>the ‘means of production’ of health information would not be owned (a non proprietary standard) </li></ul><ul><li>there would potentially be access to the huge resource of shared data for research and feedback into clinical practice </li></ul>Sydney 24-25 April
  40. 41. If such a ‘standard’ was achieved <ul><li>The same standard would work for complex and simple record taking systems </li></ul><ul><li>it would facilitate the private ‘open source’ developer </li></ul><ul><li>‘ compliance’ would be the same as ‘use’ </li></ul><ul><li>no need to reconfigure existing software </li></ul><ul><li>the existence of the standard would give vendors a goal, would be a facilitator.. </li></ul>Sydney 24-25 April
  41. 42. The ‘transcending’ benefit…... <ul><li>the same standard containers for all technological levels and cultures </li></ul><ul><li>it might prove a catalyst for global healthcare, and a global currency for it </li></ul><ul><li>it might become a channel for free decision support… </li></ul><ul><li>who knows where it might lead.. </li></ul>Sydney 24-25 April
  42. 43. With thanks to:: <ul><li>Liora Alschuler </li></ul><ul><li>Thomas Beale </li></ul><ul><li>Jane Curry </li></ul><ul><li>David Lloyd </li></ul><ul><li>JJ Michon </li></ul><ul><li>Peter Schloeffel </li></ul><ul><li>Klaus Veil </li></ul><ul><li>Peter Waegemann </li></ul><ul><li>………… .and many others </li></ul>Sydney 24-25 April
  43. 44. Sydney 24-25 April 2002 Timaru Eye Clinic, New Zealand. THANK YOU FOR YOUR ATTENTION !