1. Overview of IHE IT Infrastructure Integration Profiles IHE IT Infrastructure Technical Committee Charles Parisot, GE Medical Systems Information Technologies

2. HIMSS/RSNAIHE IT Infrastructure2 IHE Integration Profiles B A Proven Standards Adoption Process IHE Integration Profiles: – Detailled selection of standards and options each solving a specific integration problem – A growing set of effective provider/vendor agreed solutions – Vendors can implement with ROI – Providers can deploy with stability Standards Easy to Integrate Products IHE Integration Profile A IHE Demonstration IHE Connectathon Product With IHE User Site RFP IHE Technical Framework

3. HIMSS/RSNAIHE IT Infrastructure3 The Product World….. Product XYZ from Vendor T

4. HIMSS/RSNAIHE IT Infrastructure4 The IHE World…. IHE Actor Actor IHE Transaction IHE Actor

5. HIMSS/RSNAIHE IT Infrastructure5 Mapping IHE to Products Poduct XYZ from Vendor T IHE Actor Actor IHE Transaction IHE Actor

6. HIMSS/RSNAIHE IT Infrastructure6 The IHE Technical Approach Identify the transactions required to integrate a specific information flow between several information systems/devices For each transaction, select a single standard (e.g.HL7 messages, RFC) for use in implementing the transaction Specify in detail the use of the standard in implementing the transaction

7. HIMSS/RSNAIHE IT Infrastructure7 IHE : An Integration Profile  24: Report Submission Structured Report Export: 28   25: Report Issuing Report Creator  26: Query Reports  27: Retrieve Reports Report Repository Report Reader External Report Repository Access Report Manager Enterprise Report Repository Transactions Actors cooperating through Transactions to perform a specific task

8. HIMSS/RSNAIHE IT Infrastructure8 IHE IT Infrastructure 5 Integration Profiles Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems

9. HIMSS/RSNAIHE IT Infrastructure9 IHE IT Infrastructure 5 Integration Profiles Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user

10. HIMSS/RSNAIHE IT Infrastructure10 Abstract / Scope Simple and rapid access to patient information Access to existing persistent documents in well- known presentation formats: CDA, PDF, JPEG. Access to specific key patient-centric information for presentation to a clinician : allergies, current medications, summary of reports, etc.. Links with other IHE profiles - Enterprise User Authentication & Patient Identifier Cross-referencing. Retrieve Information for Display

11. HIMSS/RSNAIHE IT Infrastructure11 Value Proposition: User Convenience: – Healthcare providers can "see" the information. A significant integration step. – Workflows from within the users’ on-screen workspace or application. – Complements multiple simultaneous apps workflow of Patient Synchronized Apps Broad Enterprise-Wide access to information: – Web technology for simple clients – Clinical data handling fully assumed by the information source that holds clinical data. Retrieve Information for Display

12. HIMSS/RSNAIHE IT Infrastructure12 Key Technical Properties: Standards Used: – Web Services (WSDL for HTTP Get). – General purpose IT Presentation Formats: XHTML, PDF, JPEG plus CDA L1. – Client may be off-the-shelf browser or display app. Two services : – Retrieve of Specific Information: Patient centric: patient ID Type of Request (see next slide) Date, Time, nMostRecent – Retrieve a Document Object Unique Instance Identifier (OID) Type of Request Content Type Expected Retrieve Information for Display

13. HIMSS/RSNAIHE IT Infrastructure13 Transaction Diagram Retrieve Information for Display Display Information Source Retrieve Specific Info for Display [11] Summary of All Reports Summary of Laboratory Reports Summary of Radiology Reports Summary of Cardiology Reports Summary of Surgery Reports Summary of Intensive Care Reports Summary of Emergency Reports Summary of Discharge Reports List of Allergies List of Medications Retrieve Document for Display [12] Persistent Document Types of Requests

14. HIMSS/RSNAIHE IT Infrastructure14 IHE IT Infrastructure 5 Integration Profiles Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications

15. HIMSS/RSNAIHE IT Infrastructure15 Abstract / Scope Patient Synchronization of Multiple Disparate Applications Single Patient Selection When combined with PIX Profile, allows patient synchronization across patient identity domains Patient Synchronized Applications

16. HIMSS/RSNAIHE IT Infrastructure16 Value Proposition: User Convenience: – Eliminates the repetitive task of selecting the patient in each application – Permits the user to select the patient in the application for which they are most familiar and / or appropriate to the clinical workflow Patient Safety: – Ensures all data being viewed across applications is for the same patient Patient Synchronized Applications

17. HIMSS/RSNAIHE IT Infrastructure17 Key Technical Properties: Standards Used: – HL7 Context Management “CCOW” Standard, Version 1.4 – Support for both Windows and Web Technology – Support of “Patient Subject” IHE Constraints: – Specifies use of Patient.Id.IdList item Ensures maximum interoperability with PIX Profile Protects against future deprecation of patient identifier items Patient Synchronized Applications

18. HIMSS/RSNAIHE IT Infrastructure18 Transaction Diagram Patient Synchronized Applications

19. HIMSS/RSNAIHE IT Infrastructure19 IHE IT Infrastructure 5 Integration Profiles Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains

20. HIMSS/RSNAIHE IT Infrastructure20 Patient Identifier Cross-referencing Abstract / Scope Allow all enterprise participants to register the identifiers they use for patients in their domain Support domain systems’ queries for other systems’ identifiers for their patients Optionally, notify domain systems when other systems update identifiers for their patients

21. HIMSS/RSNAIHE IT Infrastructure21 Patient Identifier Cross-referencing Value Proposition Maintain all systems’ identifiers for a patient in a single location Use any algorithms (encapsulated) to find matching patients across disparate identifier domains Lower cost for synchronizing data across systems – No need to force identifier and format changes onto existing systems Leverages standards and transactions already used within IHE

22. HIMSS/RSNAIHE IT Infrastructure22 Patient Identifier Cross-referencing ID Domains & Transactions

23. HIMSS/RSNAIHE IT Infrastructure23 Patient Identifier Cross-referencing Key Technical Properties Standards Used – HL7 Version 2.3.1 and Version 2.4 ADT Registration and Update Trigger Events –A01: inpatient admission –A04: outpatient registration –A05: pre-admission –A08: patient update –A40: merge patient Queries for Corresponding Identifiers (ADT^Q23/K23) Notification of Identifiers Lists Updates (ADT^A31) Key Properties – ADTs remain in charge of their domains – No need for a master ID or MRN, but supported as another ID domain

24. HIMSS/RSNAIHE IT Infrastructure24 IHE IT Infrastructure 5 Integration Profiles Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems

25. HIMSS/RSNAIHE IT Infrastructure25 Enterprise User Authentication Abstract / Scope Support a single enterprise governed by a single set of security policies and having a common network domain. Establish one name per user that can then be used on all of the devices and software in a healthcare enterprise. Facilitate centralized user authentication management. Provide users with single sign-on.

26. HIMSS/RSNAIHE IT Infrastructure26 Enterprise User Authentication Value Proposition Start at the beginning – Recognize user authentication as a necessary step for most application and data access operations. – Enable benefits from future integration profiles, such as authorization management. Achieve cost savings/containment. – Centralize user authentication management. – Simplify multi-vendor implementations Provide workflow improvement for users. – Increase user acceptance. – Decrease unproductive user task-switching time. Increase level of assurance in security protection.

27. HIMSS/RSNAIHE IT Infrastructure27 Enterprise User Authentication Key Technical Properties Standards Used – Kerberos v5 (RFC 1510) Stable since 1993, Widely implemented on current operating system platforms Successfully withstood attacks in its 10-year history Fully interoperable among all platforms – HL7 CCOW user subject Minimal Application Changes – Eliminate application-specific, non-interoperable authentication. – Replace less secure proprietary security techniques.

28. HIMSS/RSNAIHE IT Infrastructure28 Enterprise User Authentication Transaction Diagram

29. HIMSS/RSNAIHE IT Infrastructure29 IHE IT Infrastructure 5 Integration Profiles Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Consistent Time Coordinate time across networked systems

30. Synergy between IHE IT Int. Profiles RID with EUA/CT & PIX Display Client Authentication Agent Time Client Information Source Kerberos Authentication Server Time Server Patient Identity Consumer Patient Identity X-ref Manager Example of support of multiple actors/profiles

31. Synergy between IHE IT Int. Profiles Apps with PSA, EUA & PIX Application A Client Authentication Agent Time ClientKerberos Authentication Server Time Server Patient Identity Consumer Patient Identity X-ref Manager Context Manager Application B Context participant Example of support of multiple actors/profiles

32. How to proceed with IHE IT Infra 1. Read IHE Fact Sheet & this presentation www.himss.org/ihe 2. Read ITI Technical Framework Vol 1 Integration Profiles www.himss.org/ihe : www.himss.org/ihe 3. Read ITI Technical Framework Vol 2 Transactions www.himss.org/ihe : www.himss.org/ihe 4. Join the IHE IT Infrastructure Tech. Committee consolidation meeting July 28- August 1 in Oakbrook (Chicago).

33. How to proceed with IHE Radiology 1. 12 Radiology Integration Profiles that can be combined with the IT Infrastructure Int. Profiles. www.rsna.org/ihe 2. Read Rad Technical Framework Vol 1 (Int. Profiles) www.rsna.org/ihe : www.rsna.org/ihe 3. Read Rad Technical Framework Vol 2 (transactions) www.rsna.org/ihe : www.rsna.org/ihe

34. HIMSS/RSNAIHE IT Infrastructure34 IHE Integration profiles Patient Informa- tion Reconci- liation, Access to Radiology Information Consistent Presentation of Images Basic Security - Evidence Documents Key Image Notes Simple Image and Numeric Reports Presentation of Grouped Procedures Post- Processing Workflow Reporting Workflow Charge Posting Scheduled Workflow

35. HIMSS/RSNAIHE IT Infrastructure35 Scheduled Workflow Profile Registration Orders Placed Orders Filled Film Folder Image Manager & Archive Film Lightbox report Report Repository Diagnostic Workstation Modality acquisition in-progress acquisition completed images printed Acquisition Modality

36. HIMSS/RSNAIHE IT Infrastructure36 Integration profiles, the easy way to deal with transactions easy-to-understand, coherent functional sets and a convenient way for users and vendors to communicate about integration requirements and needed functionality in daily life.