1. Integrating the Healthcare Enterprise IHE Radiology: How and Why Chris Carr Director of Informatics Radiological Society of North America (RSNA)

2. How and Why in Radiology Brief History Role of societies

3. What’s the problem? ADT/ HIS CIS RIS Cardio Cath Lab LIS PACS POCT OR Mods Pharm Islands of data within and among departments

4. Impact of Problem Study: 57 manual steps in typical radiology exam/reporting process – 80% added no value to care provided Radiology report often unavailable at time of medical decision making Other basic quality issues: cost, efficiency, errors Hinders innovation: larger data sets, 3D reconstruction, decision support, etc.

5. How to connect them? Standards

6. Why get involved? Workflow/dataflow problems require coordinated implementation of standards Tricky problem for marketplace to solve Role of society in communicating members’ interests Effectiveness of care provided by membership is at stake

7. Standards Experience: DICOM

8. Where IHE began 1997: “Skybird” meetings – Jointly hosted by HIMSS and RSNA – General invitation to SDOs, other associations, industry – Open forum on general question: How can we improve systems/data integration and improve care? – Lots of discussion, no definitive conclusions

10. Where IHE really began October 1998: convened group of key vendors with society oversight Agreed to discuss common problems Identify low hanging fruit to pluck for public demonstrations Started building consensus on process steps in typical radiology encounter

12. Which led to... Publication of first Technical Framework document (April 1999) Organization of first IHE Connectathon (October 1999) Presentation of first IHE demonstrations (RSNA, Nov-Dec 1999; HIMSS, Feb 2000)

13. IHE Year 1 Demos

14. Role of societies Oversee, organize and support development process Oversee, organize and support education and promotional efforts to encourage adoption: deployment process

15. Role of societies Liaison to key membership to organize and provide input to the process – Development scope priorities – Deployment plans – Outreach for expansion into other domains IHE Process is user-directed and vendor-driven

16. Timeline for development DateEvent JulyPlanning and Technical Committees: Initial annual organizational meeting Planning Committee: Initial Integration Profile development proposals August - September Planning Cmte: Development and review of Integration Profile proposals OctoberPlanning Cmte: Selection of Integration Profiles for development as sections of Technical Framework November - January Technical Committee: Development of Technical Framework Supplements to support new Integration Profiles and other changes FebruaryTech Cmte: Publication of Expanded Technical Framework for public review MarchPublic Review period for expanded Technical Framework AprilTech Cmte: Resolve public comments on extensions to Technical Framework and publish draft for Trial Implementation. NovemberTech Cmte: Resolve comments on Technical Framework and publish final stable version.

17. Timeline for deployment DateEvent AprilRSNA: Invitation to vendors to participate in testing and demonstration process; hold vendor workshop AprilSubmission of titles, abstracts and learning objectives for educational sessions at RSNA annual meeting JuneVendor applications due for participation in testing and demonstration process JulyParticipant meeting or Web conference AugustDevelopment and review of promotional materials SeptemberParticipant submission of MESA tools test results OctoberConnectathon testing event; results published in promotional materials DecemberEducational and promotional activities at RSNA annual meeting

18. Questions? Materials available on the Web sites at: www.rsna.org/IHE www.himss.org www.himss.org