1. Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise IHE Conformance: Connectathons, Integration Statements & RFPs Kevin O’Donnell (Toshiba Corp.) Co-chair, IHE Radiology Planning Cmte

2. Sept 13-15, 2004IHE Interoperability Workshop 2 IHE Process Select a Real World Integration Problem TM Identify a specific information flow between several systems Define a coherent set of transactions For each transaction:  Select an existing standard (e.g. HL7, DICOM)  Detail how to use the standard to implement the transaction Bundle it up as an “Integration Profile” Do Cross-vendor testing at a “Connectathon” Use Integration Profiles as a Common Language for:  Vendors to claim in Integration Statements  Users to request in RFPs

3. Sept 13-15, 2004IHE Interoperability Workshop 3 Standards (DICOM, HL7, etc) Users IHE Vendors RFP (Profiles & Actors) Standards (DICOM, HL7, etc) Standards (DICOM, HL7, etc) IHE Integration Statement (Profiles & Actors) IHE Connect -athon Results Select IHE Profiles IHE Integration Profiles IHE Integration Profiles IHE Integration Profiles IHE Technical Framework Product with IHE IHE Connectathon IHE Demonstration Real-World Integration Problems Key Documents in a Proven Process

4. Sept 13-15, 2004IHE Interoperability Workshop 4 IHE Integration Profiles: A Common Language Volume 1 of Technical Framework Describes the integration scenario Identifies the actors and transactions Volume 2+ of Technical Framework Provides clear implementation specification for each Transaction

5. Sept 13-15, 2004IHE Interoperability Workshop 5 Key Documents Connectathon Results from IHE  What IHE Profiles a vendor has demonstrated an ability to implement Integration Statements from Vendors  What IHE Profiles a specific product supports RFPs from Customers  What IHE Profiles a customer wants

6. Sept 13-15, 2004IHE Interoperability Workshop 6 IHE Annual “Connectathons” Voluntary Participation Project Management by Mallinckrodt Pre-Validation Tools (MESA) Defined Test Protocols with Verification Engineering event  congregation of technical talent  coding is not a problem Massive Cross-vendor Testing  An Unmatchable Testing Opportunity

7. Sept 13-15, 2004IHE Interoperability Workshop 7 IHE Connectathon Managed by the IHE Sponsors

8. Sept 13-15, 2004IHE Interoperability Workshop 8 Connectathon Benefits Thinking your interpretation is right vs. Knowing your interpretation is right  Specs are complex Finding your bugs  Access to the complete chain of systems  Testing with many partners Fixing them quickly  Structured testing environment – already on the same page  Detailed diagnostic data  Access to experts and engineers Fixing them here  Less embarrassing than fixing them at the customer site

9. Sept 13-15, 2004IHE Interoperability Workshop 9 Connectathons are Global Recent Connectathons:  IHE North America  Radiology – Chicago – October 2003  IT Infrastructure San Diego - January 2004  IHE Europe  Radiology, IT Infra, & Laboratory - Padova (Italy) April 2004  IHE Japan  Radiology Tokyo – February 2004 Upcoming Connectathons:  IHE North America  IT Infra, Lab, Cardiology, Radiology - January 2005

10. Sept 13-15, 2004IHE Interoperability Workshop 10

11. Sept 13-15, 2004IHE Interoperability Workshop 11

12. Sept 13-15, 2004IHE Interoperability Workshop 12 RFPs & IHE Integration Statements Be Brief?  “The system must support DICOM” Be Effective?  “The system must support the following DICOM services according to the following 100 pages of specifications” > Be Both < RFPs  “The system must support IHE Scheduled Workflow as an Acquisition Modality” IHE Integration Statements  Version 2.1 of the Jupiter 3 CT supports IHE Scheduled Workflow as an Acquisition Modality

13. Sept 13-15, 2004IHE Interoperability Workshop 13 IHE Integration Statement

14. Sept 13-15, 2004IHE Interoperability Workshop 14 Leveraging IHE Integration Statements Vendors  Claim IHE Compliance in an explicit way  Can rely on an objective and thorough specification (IHE Technical Framework)  Willing to accept contractual commitments  Willing to correct “implementation errors” Buyers  Can compare product integration capabilities  Simplify and strengthen their RFPs  Can leverage a public and objective commitment  Decreased cost and complexity of interface deployment and management

15. Sept 13-15, 2004IHE Interoperability Workshop 15 Integration Statements Brief and Accurate RSNA Link Page  Post Integration Statements on your website  RSNA/HIMSS/ACC will be happy to link to them  Format & Contents: Refer to Appendix D in Radiology TF Volume 1 or Appendix C in IT Infra TF Volume 1 Coming Soon: IHE.net RFPs Easier to analyze and match Less variability

16. Sept 13-15, 2004IHE Interoperability Workshop 16 IHE – Driving Market Adoption IHE User Success Stories – Submitted since RSNA 2002 (IHE Becomes Reality) Provider Demonstration of their IHE Success – Planned for RSNA 2004. IHE measures success on:  Compliant products availability  Provider deployed integrated systems

17. Sept 13-15, 2004IHE Interoperability Workshop 17 More information…. IHE Web sites: http://www.himss.org/IHE http://www.rsna.org/IHE http://www.acc.org/quality/ihe.htmhttp://www.acc.org/quality/ihe.htm. Technical Frameworks: ITI V1.0, RAD V5.5, LAB V1.0 Technical Framework Supplements - Trial Implementation May 2004: Radiology August 2004: Cardiology, IT Infrastructure Non-Technical Brochures : Calls for Participation IHE Fact Sheet and FAQ IHE Integration Profiles: Guidelines for Buyers IHE Connect-a-thon Results Vendor Products Integration Statements