Public Health Data Standards Consortium phdsc

1. Public Health Data Standards Consortiumhttp://www.phdsc.org

2. Functional Standards for Electronic Data Exchange between Clinical Care and Public Health WORKING WITH VENDOR COMMUNITY:PHDSC COLLABORATION WITH IHEAnna Orlova, PhDExecutive Director PUBLIC HEALTH DATA STANDARDS CONSORTIUM~ 2007 BUSINESS MEETING OF MEMBERS ~ October 2-3, 2007, Hyattsville, MD

3. W W W . I H E . N E T Providers and Software Developers Working Together to Deliver Interoperable Health Information Systems in the Enterprise and Across Care Settings

4. Integrating the Healthcare Enterprise (IHE) Overview Presented by Dan Russler, M.D., IHE PCC Co-chair IHE Workshop – June 19, 2006

5. Why IHE? • 1970’s—Mainframe Era--$100,000 per interface • 1990’s—HL7 2.x--$10,000 per interface • 2000’s—IHE Implementation Profiles— Cheaper than a new phone line! How? IHE Eliminates Options Found in Published Standards

6. Who is IHE? • IHE is a joint initiative among: • American College of Cardiology (ACC) • Radiological Society of North America (RSNA) • Healthcare Information Management Systems Society (HIMSS) • GMSIH, HPRIM, JAHIS (laboratory) • American Society of Ophthalmology • American College of Physicians (ACP) • American College of Clinical Engineering (ACCE) • And many more…. • Began in 1997 in Radiology (RSNA) and IT (HIMSS) • International effort: IHE- Europe and IHE-Asia • Additional sponsors for Cardiology including ASE, ESC, ASNC, SCA&I, HRS and more

7. IHE Industry Professionals

8. IHE 2006 – Nine Active Domains Over 100 vendors involved world-wide,5 Technical Frameworks 37 Integration Profiles, Testing at Connectathons Demonstrations at major conferences world-wide 15 Active national chapters on 4 continents

9. IHE Standards-Based Integration Solutions Prof essional Societies Sponsorship Healthcare Providers & Software Developers Healthcare IT Standards General IT Standards HL7, DICOM, etc. Internet, ISO, etc. IHE Process Interoperable Healthcare IT Solution Specifications Interoperable Healthcare IT IHE Integration Profile Solution Specifications Interoperable Healthcare IT Solution Specifications IHE Integration Profi le Interoperable Healthcare IT Solution Specifications IHE Integration Profile IHE Integration Profile

10. IHE in 2007 – 18 Month Development Cycles • First Cycle: • Planning Committee Proposals: October, 2007 • Technical Committee Drafts: June, 2008 • Public Comment Due: July 2008 • Trial Implementation Version: August 2008 • Mesa Tool Test Results Due: December 2008 • IHE Connectathon: January 2009 • HIMSS Demo: February 2009 • Participant Comments Due: March 2009 • Final Implementation Version: June 2009

11. IHE Technical Frameworks Detailed standards implementation guides

12. Implementer Level Allscripts Canon CapMed Cardiac Science CGI-AMS CompassCare CPSI Dictaphone DR Systems Eastman Kodak Eclipsys Epic Systems HIPAAT HX Technologies INFINITT Technology Kryptiq McKesson MedAccess Plus Medical Informatics MediNotes MNI National Institute of Sci & Tech NextGen Healthcare Philips Medical ScImage Witt Biomedical DMP–French Natl. Personal EHR Health Level 7 HTP IEEE Midmark Diagostics Group HIMSS RHIO Federation Liberty Alliance Univ. of Washington Supporter Level: Acuo Bond Carefx Clearcube Organizational participant: American Coll. of Clinical Eng. Catholic Healthcare West US Dept of Defense US Dept of Veterans Affairs Dairyland EMC Identrus Intel Mediserve Medkey Motion Comp. Picis Pulse Sentillion HIMSS IHE Interoperability ShowcaseFebruary 2006 Participants Leadership Level Blue Ware Cerner GE Healthcare +IDX IBM Initiate Systems InterSystems MiSys Healthcare Quovadx Siemens

13. IHE Connectathon, January 2006 • 300+ participants, 120+ systems • 60+ systems developers • Four Domains: Cardiology, IT Infrastructure, Patient Care Coordination, Radiology • 2800+ monitored test cases

14. Results • Over 3000 attendees visited the HIMSS RHIO Showcase • 37 vendors demonstrated 48 systems • 700 attendees created and tracked their own health record • 63 educational sessions were presented • 5 International delegations • 3 VIP tours • 16 clinical scenarios were demonstrated

15. IHE Integration Profiles for Health Info NetsWhat is available and has been added in 2005 and is for 2006 Scanned Documents Lab Results Document Content ECG Report Document Emergency Referrals PHR Extracts/Updates Basic Patients Privacy Consents Format of the Document Content and associated coded vocabulary Format of the Document Content and associated coded vocabulary Format of the Document Content and associated coded vocabulary Format of the Document Content and associated coded vocabulary Format of the Document Content Patient Identifier Cross-referencing Establish Consents & Enable Access Control Cross-Enterprise Document Sharing Map patient identifiers across independent identification domains Imaging Information Registration, distribution and access across health enterprises of clinical documents forming a patient electronic health record Patient Demographics Query Medical Summary (Meds, Allergies, Pbs) Format of the Document Content and associated coded vocabulary Document Digital Signature Audit Trail & Node Authentication Format of the Document Content and associated coded vocabulary Attesting “true-copy and origin Request Formfor Data Capture Centralized privacy audit trail and node to node authentication to create a secured domain. External form with custom import/export scripting Consistent Time Notification of Document Availability Cross-enterprise Document Point-Point Interchange Notification of a remote provider/ health enterprise Coordinate time across networked systems Media-CD/USB & e-mail push Clinical and PHRContent Security Patient Id Mgt Health Data Exchange Other

16. AHIC-ONC BIO Consolidated Use Case Transaction Package Consumer/Patient Id X-ref Component Lab Report Document Component Lab Terminology Component Anonymize Biosurveillance Patient-Level Data to Public Health Document-based Submission HITSP Biosurveillance – Patient-level and Resource Utilization Interoperability Specification Transaction Package Manage Sharing of Docs Document-based Scenario Transaction Notif of Doc Availability Base Std HL7QBP^Q23 RSP^K23 Transaction Pseudonymize IHEXDS IHEPIXPDQ IHE XDS-I IHE NAV IHE XDS-MS IHE XDS-LAB Terminology Standards Base Std HL7CDA r2 Base Std ISO DTS/ 25237 Base Std ISO 15000ebRS 2.1/3.0 Base Std HL7 V2.5 Base Std DICOM Base Std LOINC HCPCS HL7 V3 CPT HL7 V2.5 SNOMED-CT CCC HIPAA ICD 9/10 LOINC SNOMED-CT DICOM NCCLS UCUM UB-92 URL FIPS 5-2 HAVE

17. PHDSC was Invited to Form Public Health Domain at IHE Providers and Software Developers Working Together to Deliver Interoperable Health Information Systems in the Enterprise and Across Care Settings

18. 2007 PHDSC Activities at IHE May – October • PHDSC-IHE Task Force to Develop a White Paper on Building a Roadmap for Interoperability for Public Health Over 60 participants from public health and clinical communities

19. 2007-2008 PHDSC Activities at IHE To be presented at the IHE Planning Meeting in October • Public Health Profile Proposal • Public Health Registry • Examples of Cancer and Immunization Domains • IHE Profile Change Proposal • Extended PDQ (Patient Data Query) for demographic information exchanges with public health systems • Examples of Cancer and Immunization Domains • IHE White Paper on Public Health Decision Support • Examples of Cancer and Immunization Domains

20. JOIN THE PHDSC-IHE TASK FORCE E-mail to Anna Orlova, PHDSC at aorlova@jhsph.edu

21. PHDSC was Invited to Form A Public Health Domain at IHE Providers, PUBLIC HEALTH and Software Developers Working Together to Deliver Interoperable Health Information Systems in the Enterprise and Across Care Settings