integrating the healthcare enterprise ihe 2004-2005 plans for multi-domain testing and...

Integrating the Healthcare EnterpriseIntegrating the Healthcare Enterprise

IHE 2004-2005 Plans for Multi-domain

Testing and Demonstrations

Steve MooreTechnical Project Manager (ITI, Rad)

Sept 13-15, 2004 IHE Interoperability Workshop2

Domains:Domains: IHE IT Infrastructure IHE IT Infrastructure

IHE Radiology IHE RadiologySteve MooreMallinckrodt Institute of Radiology+1 (314) 362 [email protected]


Domains:Domains: IHE Cardiology IHE Cardiology

Teri Sippel Schmidt+1 (262) [email protected]


Testing and DemonstrationTesting and DemonstrationTechnical Project Manager RoleTechnical Project Manager Role

Define/produce/administer pre-Connectathon test plans and softwareOrganize/manage ConnectathonTechnical details of demonstrations

Serve as contact point for technical questions


Our role is part of the IHE Annual Our role is part of the IHE Annual ProcessProcess

EducationaEducational l

WorkshopsWorkshops

Technical Technical Framework Framework

DevelopmentDevelopmentDemonstration Demonstration

PlanningPlanning

““MESA” test tool and MESA” test tool and test plan developmenttest plan development

Work with vendors to Work with vendors to complete MESA testscomplete MESA tests

Vendors submit results Vendors submit results from MESA testsfrom MESA tests

Create “Connectathon” Create “Connectathon” test planstest plans

document “Connectathon” document “Connectathon” resultsresults

Input:Input:

Output:Output:

Our role:Our role:

Manage trade show Manage trade show tech demonstrationstech demonstrations

Inter-vendor tested Inter-vendor tested software; problems software; problems reported to vendorsreported to vendors

Publish Publish Connectathon Connectathon

ResultsResults

Successful “live” Successful “live” tradeshow tradeshow

demonstrationsdemonstrations


What are the MESA tests?What are the MESA tests?

“Medical Environment Simulators and Analyzers” (MESA) Test plans and softwareDocuments and software distributed to participating vendors at October workshopMESA tests must be successfully completed before the ConnectathonPurpose: Detailed tests regarding specific transactions Tests small “steps”


What is the Connectathon?What is the Connectathon?All participating vendor’s products together in the same place at the same timeExperts from each vendor available for immediate problem resolutionTest real-world clinical scenarios (Integration Profiles)Connectathon must be successfully completed before the tradeshow demonstrationsPurpose: 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


Connectathon AreaConnectathon Area


IHE-Europe: Padova, Italy, IHE-Europe: Padova, Italy, Spring 2004Spring 2004


Project Management at Project Management at ConnectathonConnectathon


““D-3”D-3”“Miss !!”“Miss !!”


Benefits of testing to Clinical Benefits of testing to Clinical UsersUsers

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 problemClinical User must verify Connectathon tested software in appropriate product release (via RFP)


Benefits of testing to VendorsBenefits of testing to VendorsReduce Costs!!! – problems caught earlier in software life cycle are much cheaper to fixProvides collegial forum between vendors to find and solve interoperability problemsExperts 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)


Participant ResponsibilitiesParticipant Responsibilities- Summary- Summary

Read Technical FrameworkSubmit application forms to sponsors (ACC/HIMSS/RSNA)Attend Participant Workshop Oct 27-28, 2004 one technical representative per system

Implement one or more Integration Profiles completelyComplete all MESA tests provided by Technical Project ManagerSubmit “success logs” by cutoff dateActively participate in Connectathon Jan 17-21, 2005 one technical representative for each registered system

Follow demonstration rules (if you are in a demonstration)


Key Dates/CommitmentKey Dates/CommitmentOct 15, 2004 Applications due

Oct 27-28, 2004 Participant WorkshopMESA Test tools: First full release

Dec 1, 2004 Connectathon system configuration complete

Dec 23, 2004 IHE ITI/Radiology MESA test results due

Dec 30, 2004 IHE Cardiology MESA results due

Jan 17-21, 2005 Connectathon

Feb 13-17, 2005 HIMSS Annual Meeting

March 6-9, 2005 ACC Annual Meeting


If You Do Not Know …If You Do Not Know …

AskAsk before the ConnectathonAsk a Technical Project Manager


Project Managers Available Project Managers Available During this MeetingDuring this Meeting

Steve Moore IT Infrastructure Radiology

Teri Sippel Schmidt Cardiology


Real Project ManagersReal Project Managers


Questions?Questions?


More information….More information….IHE Web sites:

http://www.himss.org/IHEhttp://www.rsna.org/IHEhttp://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

http://www.rsna.org/IHE

http://www.acc.org/quality/ihe.htm

http://www.acc.org/quality/ihe.htm