1 / 14

NHIN Semantic Interoperability 29 August 2006

NHIN Semantic Interoperability 29 August 2006. Mike Cummens, MD Dave Riley. What is the TSB?. The people, processes, tools and content needed by the DoD to achieve semantic interoperability within the enterprise Semantic Interoperability

gwenr
Download Presentation

NHIN Semantic Interoperability 29 August 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NHIN Semantic Interoperability 29 August 2006 Mike Cummens, MD Dave Riley

  2. What is the TSB? • The people, processes, tools and content needed by the DoD to achieve semantic interoperability within the enterprise • Semantic Interoperability • Appropriate, accurate, automated use of information generated by diverse systems • Information is acted on exactly as if it had been generated internally in each application’s native format • Accomplished using a content development component and a runtime component Northrop Grumman Private / Proprietary Level I

  3. Terminology Service Bureau - Architecture Northrop Grumman Private / Proprietary Level I

  4. How does the TSB fit in the NHIN? • Use the Content Development Environment • MHSCore Ontology • Add participating vendor specific ontologies and system mappings • Use the Runtime Environment • Runtime Ontology Exports • Services Northrop Grumman Private / Proprietary Level I

  5. Adding TSB to the NHIN Architecture MPI NHIN DB TSB Runtime ONTOLOGY NHIN Services NHIN Web App NHIN Web Services Test WS Client DoD Web Service DoD WS Client EPIC Web Service EPIC WS Client Northrop Grumman Private / Proprietary Level I

  6. How will TSB be used in NHIN? • To demonstrate semantic interoperability • Appropriate, accurate, automated use of information generated by diverse systems • Information is acted on exactly as if it had been generated internally in each application’s native format • Systems to be interoperable • DoD AHLTA clinics • EPIC hospitals or clinics • Content to be interoperable • Problem list • Active medical diagnoses or symptoms Northrop Grumman Private / Proprietary Level I

  7. Using TSB in the NHIN Architecture MPI NHIN DB TSB Runtime ONTOLOGY NHIN Services NHIN Web App NHIN Web Services Test WS Client DoD Web Service DoD WS Client EPIC Web Service EPIC WS Client Northrop Grumman Private / Proprietary Level I

  8. EPIC EPIC ID TSB SNOMED CT Concept ID DoD MEDCIN ID Problem List Data • Real timesemantic interoperability mediation between EPIC sites and DoD sites Northrop Grumman Private / Proprietary Level I

  9. Required Enhancements to TSB • Map EPIC terminology to SNOMED CT • Currently available for license from third party vendor • Integration of EPIC to SNOMED CT map into TSB • Quality review • Manual edit • Creation of Translation Rules • Complex or context dependent mapping Northrop Grumman Private / Proprietary Level I

  10. Advantages of Using TSB in NHIN for Central Terminology Mediation • Availability • Sites submit HL7 messages with content coded in local terminology • MEDCIN, EPIC, Cerner, SNOMED CT, etc. • Reusability • Centralized map of each vendor terminology to core terminology • Ease of maintenance • Centralized version updates Northrop Grumman Private / Proprietary Level I

  11. Back Up Slides Northrop Grumman Private / Proprietary Level I

  12. CHCS II TSB Content TMIP TSB Content CHDR TSB Content PKC/Medcin/SNOMED CT TSB Content NHIN TSB Content Terminology Service Bureau – The Big Picture Terminology Service Bureau SNOMED CT (Core) PKC MHS Ontology Other MEDCIN Other Northrop Grumman Private / Proprietary Level I

  13. Components of Computable Data Ontology • Concepts • Concept relationships • Concept definitions • Terms • Hierarchies • Clinical propositions • Standard terminologies • Mappings • Not patient specific Used By Information Model • Instances of data using model and dictionary • Event based • Constrained by model • Patient specific Used By • Structural layout • Clinical definition • Hierarchical in nature • Contains fields for discrete values • Fields tied to dictionary • Defines “valid data” • Not patient specific Repository Northrop Grumman Private / Proprietary Level I

  14. Planned and Future Uses of Central Terminology Mediation • Increase breadth and depth • Breadth • Medications • Laboratory results • Imaging results • Procedures • Continuity of care record • Depth • Wiki ontology process to add additional sources • Maintain quality • Upper ontology • OWL • RACER Northrop Grumman Private / Proprietary Level I

More Related