1 / 13

IHE Cardiology

IHE Cardiology. ACC 2007 Interoperability Showcase Thoughts on panels to illustrate vendor/product milestones with IHE. tms. Document Revision history. V2.0 – reviewed by PC with many change requests, August 3rd, 2006 V3.0 – incorporated changes requested in August meeting. Goal.

quang
Download Presentation

IHE Cardiology

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IHE Cardiology ACC 2007 Interoperability Showcase Thoughts on panels to illustrate vendor/product milestones with IHE tms

  2. Document Revision history • V2.0 – reviewed by PC with many change requests, August 3rd, 2006 • V3.0 – incorporated changes requested in August meeting.

  3. Goal Goal: (per IHE Cardiology Planning Committee decision at the June F2F meeting in Baltimore, MD) 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.

  4. 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 Field Maintenance Verify and Publish IHE Integration Statement Verify and Publish IHE Integration Statement

  5. 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 Field Maintenance Verify and Publish IHE Integration Statement Verify and Publish IHE Integration Statement

  6. 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. • PC agreed to award “IHE connects” logo to sum of milestones 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, perhaps using the IHE product database, if it comes to fruition. • Companies should not need to prove incorporation of IHE software into a software build outside of an Integration Statement.

  7. 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 Field Maintenance Verify and Publish IHE Integration Statement Verify and Publish IHE Integration Statement

  8. Examples of Matrix Echo Workflow and Measurements

  9. Matrix Elements Examples Integration Statement only IHE Integration Statement w/ sw rev

  10. Matrix Elements Examples Connectathon and Integration Stmt IHE Integration Statement Connectathon

  11. Matrix Elements Examples All required criteria met = IHE logo IHE Integration Statement w/ sw rev Connectathon Release – Which one?!? Any? IHE Connectivity Installation

  12. Matrix Elements Criteria • Recommended milestones to earn the maximum (4) number of icons: • Integration Statement Published with a specific software release number required • Connectathon – (NA, Euro, or Japanese) • IHE connectivity operating in at least one clinical site • Released in at least Alpha software release

  13. 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, prefer site name be submitted, but not required Do we note state of release (alpha/beta/general) on matrix? Can a company publish an Integration Statement with an unreleased software revision (may not release- engineering only, e.g., Connectathon)? Can you ever have an “Integration Statement” icon without a “Software Release” icon?

More Related