1. Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise IHE 2004-2005 Plans for Multi-domain Testing and Demonstrations Steve Moore Technical Project Manager (ITI, Rad)

2. Sept 13-15, 2004IHE Interoperability Workshop 2 Domains: IHE IT Infrastructure IHE Radiology Steve Moore Mallinckrodt Institute of Radiology +1 (314) 362 6965 moores@mir.wustl.edu

3. Sept 13-15, 2004IHE Interoperability Workshop 3 Domains: IHE Cardiology Teri Sippel Schmidt +1 (262) 966-7210 Tsippel@acc.org

4. Sept 13-15, 2004IHE Interoperability Workshop 4 Testing and Demonstration Technical Project Manager Role Define/produce/administer pre- Connectathon test plans and software Organize/manage Connectathon Technical details of demonstrations Serve as contact point for technical questions

5. Sept 13-15, 2004IHE Interoperability Workshop 5 Our role is part of the IHE Annual Process Educationa l Workshops Technical Framework Development Demonstration Planning “MESA” test tool and test plan development Work with vendors to complete MESA tests Vendors submit results from MESA tests Create “Connectathon” test plans document “Connectathon” results Input: Output: Our role: Manage trade show tech demonstrations Inter-vendor tested software; problems reported to vendors Publish Connectathon Results Successful “live” tradeshow demonstrations

6. Sept 13-15, 2004IHE Interoperability Workshop 6 What are the MESA tests? “Medical Environment Simulators and Analyzers” (MESA) Test plans and software Documents and software distributed to participating vendors at October workshop MESA tests must be successfully completed before the Connectathon Purpose:  Detailed tests regarding specific transactions  Tests small “steps”

7. Sept 13-15, 2004IHE Interoperability Workshop 7 What is the Connectathon? All participating vendor’s products together in the same place at the same time Experts from each vendor available for immediate problem resolution Test real-world clinical scenarios (Integration Profiles) Connectathon must be successfully completed before the tradeshow demonstrations Purpose:  Test “Integration Profile” level interoperability between vendors  Post results of Connectathon on public web servers In 2003-2004, 39 vendors tested 80+ Products in two 5-day events (Oct 2003, Jan 2004)  Not counting IHE-Europe or IHE-Japan

8. Sept 13-15, 2004IHE Interoperability Workshop 8 Connectathon Area

9. Sept 13-15, 2004IHE Interoperability Workshop 9 IHE-Europe: Padova, Italy, Spring 2004

10. Sept 13-15, 2004IHE Interoperability Workshop 10 “D-3” “Miss !!”

11. Sept 13-15, 2004IHE Interoperability Workshop 11 Real Project Management at Connectathon

12. Sept 13-15, 2004IHE Interoperability Workshop 12 Benefits of testing to Clinical Users Confidence that vendor software has been tested  At a detailed level per the IHE Technical Framework (MESA test tools)  At an interoperability level (Connectathon)  With other vendor’s implementations (Connectathon) Not being tested for the first time at your site (time, pain, and integration costs) Vendor Experts were on hand to report and debug interop problems, not just a service engineer now reporting a site-specific problem Clinical User must verify Connectathon tested software in appropriate product release (via RFP)

13. Sept 13-15, 2004IHE Interoperability Workshop 13 Benefits of testing to Vendors Reduce Costs!!! – problems caught earlier in software life cycle are much cheaper to fix Provides collegial forum between vendors to find and solve interoperability problems Experts simultaneously available from many vendors (saves time) Rewarded for being well prepared (opportunity to complete testing with more vendors) Increased customer satisfaction (less problems found on site)

14. Sept 13-15, 2004IHE Interoperability Workshop 14 Participant Responsibilities - Summary Attend Participant Workshop  Oct 27-28, 2004  one technical representative per system Complete all MESA tests provided by Technical Project Manager Submit “success logs” by cutoff date Actively participate in Connectathon  Jan 17-21, 2005  one technical representative for each registered system

15. Sept 13-15, 2004IHE Interoperability Workshop 15 Key Dates/Commitment Oct 27-28, 2004MESA Test tools: First full release Dec 1, 2004Connectathon system configuration complete Dec 23, 2004IHE ITI MESA test results due Dec 30, 2004IHE Cardiology MESA results due Jan 17-21, 2005Connectathon Feb 13-17, 2005HIMSS Annual Meeting March 6-9, 2005ACC Annual Meeting

16. Sept 13-15, 2004IHE Interoperability Workshop 16 If You Do Not Know … Ask Ask before the Connectathon

17. Sept 13-15, 2004IHE Interoperability Workshop 17 Real Project Managers

18. Sept 13-15, 2004IHE Interoperability Workshop 18Questions?

19. Sept 13-15, 2004IHE Interoperability Workshop 19 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