Radiology Planning Committee

1. Radiology Planning Committee Sept 16, 17, 2004

2. Agenda • Thursday 8:30 – 5:30 • Agenda review (.5 hour) • Feedback from IHE workshop (.5 hour) • Year 7 Planning, including marketing (2.5 hours) • Working lunch • Radiotherapy – ASTRO (2 hours) • Handbook Development (2 hours) • Friday 8:00 – 3:00 • IHE web sites (0.5 hour) • RSNA 2004 planning (1.5 hours) • Business Cases (1.5 hour) • Handbook Development (2 hours) • Next steps and t-con schedule until RSNA (.5 hr)

3. Agenda • PDI Marketing Material • Business Case – Handbook • Success story authors and contributors have a t-con to review • 2-3 weeks before the user’s meeting we review the draft • RSNA Presentations • Abstract Sept 30, close of comments Oct 8. • Educational Sessions Draft Oct 22, Nov 5 • Template Effort – Next Steps, closing slide – Oct 8 • Review the presentations – Rad Plan t-con, Oct 29. • Technical Cmte Feedback on Year 7 – RSNA Meeting • Radiology Vendor Workshop, web conf – Oct 26 • Need to get on an Agenda for SCAR • Need to get a focused message in a General Session in SCAR-University • Chris to take the lead • Integration Handbook – March 15, 05 • Meeting with the user’s group – Friday, Dec 3, 8:30-10:30

4. Year 7 Planning • Discussion of Activity Proposals • Deployment Handbook • Teaching Files • Strategic Presentations • Etc. • Proposal of Slates • Voting on Slates • Address Roadmap

5. Radiology Year 7 Focus

6. Marketing Requests • Value/Pain Item Document • Toolkit for Champions • Success Stories • Feedback from Deployers to IHE • meeting of success story sites/champions at RSNA? • also allows cross-pollination

7. 1. Support User Deployment • Motivation: • Users Understand IHE and Want IHE but have problems implementing into their current architecture • They need deployment models and case studies • Activities: • Practical Deployment case studies • Business Case for key Profiles • Strategies for Legacy Integration • Review Case Studies/Success Stories (what is IHE helping, what is IHE missing) • Site Evaluation Tools • Engage consultants • X Availability of of Productized Mesa 2.0 for Elective use by Sites Acceptance Testing • Publish Connectathon Test Plan to inform user site testing • Database of Integ. Statements & CThon Results

8. 2. Promote Vendor Implementation • Motivation: • Customers are finding few vendors; few products; few profiles and perceive IHE as risky/not ready yet • Vendors need more motivation on the marketing side and more support on the engineering side • Activities: • Understand and Resolve Issues with Vendor Products • Why they can’t implement IHE actor(s) for profile(s) • Collect/Collate Market Data (#prod. implementations, #field deployment) • XUse Plan & Tech Face-to-Face Meetings to Kick-start Vendors • (Q: Do we need more vendors or more profiles?) • Get Vendor Product Decision Makers to Attend Have Luminaries Speak to the Value • X“Generate more user demand”, “help them understand value” • Next-Gen Connectathon Tools – MESA 2.0 • Document Intrinsic Benefits to Vendors of IHE • Cost/Benefits of Connectathon, New Capabilities drive upgrade cycle, etc.

9. Promote User Understanding • Motivation: • It’s Still Too Hard for Users to Understand • It’s Still Not on the Radar of Most Users • Activities: • Refine Profile Structure so it’s easier to Understand • Continue work on Departmental Workflow • Improve Materials for Educating Customers – likely falls out of other activities • Broader outreach to users who haven’t heard of IHE, e.g. more direct contact materials such as bulk mailing • Work on IHE Web Site Development (IHE.net) • Find ways to make and publish many more success stories • Focus on getting some mid-tier sites, getting quantitiative

10. Develop New Profiles • Motivation: • There are still Profiles worth addressing • Activities: • Continue Addressing Radiology Issues such as Dept. WF, Federated PACS, Teaching Files, Clinical Trials, (Anonymization), New CT/MR Content, Dose Recording, CT/PET Fusion, etc. • Teaching File • Explore DICOM – Next Gen Reporting – Multimedia, CDA-SR, etc. • Explore Multi-site Patient Sneakernet Flow • Cross-Enterprise Image Sharing • Follow the usual proposals/tech review/selection process • Tech Cmte work might be reduced to advice/review/finalization if text is written by “side-committees” • Consider a large profile takes 40-60% of TC Bandwidth, a small profile 20-40%

11. Consolidate Domains • Motivation: • The Domains aren’t very well integrated • We need to promote convergence and interaction amongst the Domain groups • Activities: • Concerted Review of IT, Card, Lab Profiles to spotdivergences • Maintain/cleanup Technical Framework(s) • Document some general models (e.g. Dept. WF, content flow) • Replace/Cleanup Basic Security • Apply/Configure Profiles from other Domains to Radiology (Audit Trails, XDS, RID, PIX, Config. Mgt., etc) • Document Cross-Domain Profile Use Cases/Synergies • Work on Multi-Domain Connectathon/Demo Synergies • Organize Multi-Domain Documentation (i.e. Tech Framework) • Improve Cross-Domain communications • Further document IHE processes, guidelines, criteria, etc. • Address overlap areas, HL7 Versioning, etc.

12. Expanding in Radiotherapy • Thu, Sept 16, 1-2:30 pm • American Society for Therapeutic Radiology & Oncology (ASTRO) • Jennifer J. Padberg, MPH,Director of Research, ASTRO • Dr. Jatinder Palta, UFL • Dr. Bruce Curran, UM • Dr. Tripuneni • Dr. David Murray, Chairman, DICOM Working Group 7 (RT)

13. ASTRO • Radiotherapy Domain – 30 min • Expectations of ASTRO – 15 min • Explain the IHE process – 15 min • Identify next steps – 30 min • Create a new domain, Sponsor organizations • Recruit vendors • Need to create committees • Collaboration with Radiology • Seed with existing committee members • International aspect (US and Europe) • Kick-off meeting, Goal for demo at a show

14. ASTRO (Discussion) • Scope out the problem • Involve AAPM, ASTRO • Had a Conf call for next steps • Current approved structure: • President has invited AAPM, RSNA, ACR to suggest the names of committees • Tech Cmte headed by Bruce Curran • Clinical Cmte headed by Prabhakar Tri… • Corporate meeting at ASTRO. Tentative times available to them • Meeting in Altanta, Oct 3rd – 7th • Corporate Advisory Group (11 Elected individuals by vendors) • Corp Breakfast meeting (a representative from each exhibitor) • Follow with a meeting of the ASTRO leadership • RSNA will appoint some people to these committees?

15. ASTRO (How we came about) • Deal with DICOM domain • Need clinical committee • Facilitate early discussion – What type of profiles to be developed • Identified those who have the incentive to solve the integration problem • Working Group 7 generally holds a meeting at NEMA meeting, early in the year in Washington • Planning meeting at RSNA – Someone at IHE provide an overview and guidance • Kick-Off meeting at the tail of NEMA in Washington

16. RSNA 2004 – Chris Carr • Overview • Educational Sessions • Timeline for development • Reviews and Final Text • Vendor PDI activity/communications • Communication to the Radiologists, Physician • User Success Stories: 14, hands-on from 4 sites bringing equipment, etc. for roughly IHE workflow. • Bringham and Women’s Hospital – ADT, OP • Wisconsin – OF, PACS, Modality, PGP, non-radiology modality • Cleveland Clinic – Post Processing Workflow, 3D • Univ. of Maryland – Diagnostic Workstation, Reading room, some structured reporting functions • Need to get a clear list of IHE profiles being demonstrated • Past stories to be updated for those who did not submit new ones

17. RSNA 2004 – Chris Carr • PDI Messaging • Reliable CD • Creator Benefits • Receiver Benefits • IHE-PDI: “CDs that work” • IHE-CD: “One that works” – Try for yourself • 3 lines of instructions of what to do on the CD • CD contents – medical, disclaimer and instructions to use the CD. • 22 vendors participating: 18 importers, 21 creator • Pre-mailing to target audience • On-site: Kiosks on entrance to North and South hall. • Showcase exhibit booth, will have a station • All attendees will have a coupon to get CD-Wallet with PDI-CD, once they complete the tour.

18. RSNA 2004 – Chris Carr • PDI Mailer: To go out in mid-October • 5000 attendees will get a mailing describing PDI demo and a CD. Flyer that describes the demo, participating companies, what to do with the CD • IHE Demo Participant: Signage • Chris to finalize PDI materials and review it with planning committee on a t-con • Inforad Showcase Exhibit

19. Integration Handbook • Review by Section • Authors present their work according to the sections in outline (2, 3, 4) • Discussion and comments • Assign authors for Introduction (section 1)

20. Integration Handbook • Section 2 – 2 hours (9 sections) • Section 3 – 2 hours • Section 4 – 2 hours

21. ? Questions from Workshop ? • Make the Test plans available to implementors? Should it be public information? • Sanjay: Yes. Make them public. • Nogah, developed acceptance testing plan based on TF – can there be a forum to share them? • Sanjay: IHE Users forum. If the creators agree to share them. • There could be many product implementations which may be limited in IHE capabilities. Can a reference to particular version be added to Integration Statement. • Sanjay: This has been discussed before. We can recommend add to comments • Include in the Integration Statement, where tested – Connectathon, Beta test on-site, etc. • Sanjay: We can recommend add to comments. This is good information. Only issue is parts may be Connectathon only, others on-site. • Optional functionality to become required in a profile after lapse of a certain time period (1-2 years) • Sanjay: For later discussion in the committees.