IHE Cardiology ACC 2007 Interoperability Showcase A Visual Representation of the self- certified IHE implementations of Vendor’s Products tms

Document Revision history V2.0 – reviewed by PC with many change requests, August 3rd, 2006 V3.0 – incorporated changes requested in August meeting. V4.0 – minor editorial changes V5.0 – incorporated decisions per Oct 5th Interoperability Showcase tcon V6.0 – incorporated decisions per Dec 14th, 2006, Strategic Development tcon

Goal Goal: (per IHE Cardiology Planning Committee decision at the June F2F meeting in Baltimore, MD) Highest priority: Develop a matrix to be displayed and highlighted at the ACC 2007 IHE Interoperability Showcase which will clearly illustrate to clinical users which vendors and which products have adopted and integrated IHE connectivity into their products, including releasing that software to the field.

Typical software lifecycle process incl IHE Time(not to scale) Product conception Requirements Definition Draft IHE Integration Statement Software Development (many sw builds) Internal sw validation MESA testing sw build Connectathon sw build Alpha release To clinical site With IHE connectivity? sw build Beta release To clinical site With IHE connectivity? sw build General Release to Clinical sites Verify and Publish IHE Integration Statement Field Maintenance Verify and Publish IHE Integration Statement

Note “gold star” was previously awarded here time Product conception Requirements Definition Write and/or Publish IHE Integration Statement Software Development (many sw builds) Internal sw validation MESA testing sw build Connectathon sw build Alpha release To clinical site With IHE connectivity? sw build Beta release To clinical site With IHE connectivity? sw build General Release to Clinical sites Verify and Publish IHE Integration Statement Field Maintenance Verify and Publish IHE Integration Statement

Connotations, notes, and history Gold stars were previously awarded for the Connectathons and there was no incentive and no repercussions for not continuing to develop the IHE software into the General Release of a product. Users were misled into thinking that a “gold star” meant the IHE connectivity was available in their product. “Gold stars” and “black dots” have been used in the past and have connotations such that they should not be used again. Need new icons. Added from the August 2006 PC tcon: PC (Aug 2006 tcon) agreed that the “IHE connects” logo could not be used since it has the connotations of a certification body such as UL This needs to be a self certification process, preferably using the IHE product registry/database, if it comes to fruition in time. Companies should not need to prove incorporation of IHE software into a software build outside of an Integration Statement. Added from the December 2006 Strategic Development tcon: There should only be 3 icons, not 4. The Commercial Release and the Integration Statement icons should be merged so more clearly illustrate commercial release. For a clinical installation icon, vendors must be required to privately (not published) provide the name of the site and the contact information. It should be clarified that a Connectathon icon infers that the software must be in some sort of pre-production release of software.

Candidates for recognition criteria at ACC 2007 time Product conception Requirements Definition Draft IHE Integration Statement Software Development (many sw builds) Internal sw validation MESA testing sw build Connectathon sw build Alpha release To clinical site With IHE connectivity sw build Beta release To clinical site With IHE connectivity? sw build General Release to Clinical sites Verify and Publish IHE Integration Statement for General Release Field Maintenance Verify and Publish IHE Integration Statement

Examples of Matrix Echo Workflow and Measurements Vendor Product Software release Echo Workflow Actors: Acq Image Image Modality Mgr Display Company XYZ My echo cart V7.41b Cardiac PACS My EMR ABC IHE is a clinical-industry partnership – but it is driven by the clinical community – Great support from the ACC and ESC, and from clinicians from specialty societies

Matrix Elements Examples Connectathon only – probably most common example, initially Connectathon

Matrix Elements Examples Connectathon and Integration Stmt for General Release IHE Integration Statement Connectathon

Matrix Elements Examples All required criteria met = 3 icons (need some sort of symbol (smiley, exclamation point?) to indicate that they hit the maximum possible steps) ! IHE Integration Statement w/ commercially available sw rev Connectathon IHE Connectivity Installation

Matrix Elements Criteria Recommended milestones to earn the maximum (3) number of icons: Integration Statement Published with a specific Commercially Released software release number required, where Commercially Released means software release is being shipped (ie., it is a catalogue line item) Connectathon – (NA, Euro, or Japanese) – product release, pre-production release, or platform tested IHE connectivity operating in at least one clinical site – self certified – must provide name of site and contact to Showcase Project Manager (name and contact will not be published, only used to demonstrate validity.)

Other issues/notes/rules Include Connectathon and results from all three Regions (North America, Europe, Japan) Include results from all previous Connectathons Create matrix columns for all existing IHE Cardiology + XDS Profiles (except DRPT!) Recognized method to publish Integration Statement = published link on www.ihe.net Need self certification of software release based on software revision number identified in Integration Statement or press release Need self certification of clinical installation and operating, site name and contact must be submitted, but will not be published Recognize commercially available product releases only (ie., it has to be in a price book/catalogue line item). This is true for IT systems also where IHE is often configuration parameters. An Integration Statement which is published for unreleased software (even if it went to the Connectathon) will not be recognized – it must be a Commercially Available release of software.