1. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 1 Semantic Interoperability Architecture Pilot Group Started Early 2005 Health Informatics Identified as Critical for Emergency Management In SWANS Conference Registry-Repository Identified as Need for Semantic Interoperability Intersection of Two Domains is Key: Emergency Management Health informatics Central Location for Accessing IT Standards, Standards Development Organizations (SDOs), Services, Service Providers, Transaction History (Audit Trail) Last Key IT Need: Guidance: Evaluating and Using Standards, Ontologies & Taxonomies

2. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 2 Combined SICop & DoN Presentation

3. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 3 Combined SICop & DoN Presentation

4. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 4 Combined SICop & DoN Presentation

5. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 5 2006 OASIS Symposium Highlights Health Informatics Registry Focus on Functionalities Included in Registry-Repository Diagram Shows Structure and Use of Registry-Repository Multiple Information Resource Access NIST Health Standards Landscape NIST XML Standards Development Resources Issues Highlighted Semantic Interoperability Perspectives Contractual Perspective

6. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 6 2006 OASIS Symposium Presentation

7. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 7 2006 OASIS Symposium Presentation

8. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 8 2006 OASIS Symposium Presentation

9. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 9 Problem: Registry Interface too Complex

10. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 10 Problem: Registry Interface too Complex

11. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 11 Solution: Web Application Interface

12. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 12 Solution: Web Application Interface

13. Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 13 Semantic Interoperability Architecture Pilot Group Started Early 2005 Now: Integrated Response Services Consortium Health Informatics Critical for Emergency Management & Economy Overall Intersection of Two Domains Remains Key: Emergency Management Health informatics Central Location VITAL for Accessing IT Standards, Standards Development Organizations (SDOs), Services, Service Providers, Transaction History (Audit Trail) Last Key IT Need: Guidance: Evaluating and Using Standards, Ontologies & Taxonomies