Integrating the Healthcare Enterprise

1. Integrating the Healthcare Enterprise ACC 2005 Demonstration Jon Elion MD, FACC, Heartlab Inc. IHE Cardiology Technical (Co-Chair) & Planning Committees IHE Interoperability Workshop

2. Introduction • A demonstration of IHE interoperability is planned for the March 2005 meeting of the American College of Cardiology (Orlando) • The demonstration will target clinical Cardiologists, Cardiology Administrators, and Information Services (IS) staff • For many, this will be their first exposure to IHE Elion – p. 2

3. Presentation Formats • Kiosk in the ACC exhibit area of the exhibits hall (video loop) • Small theater presentations (slide shows) • Technical Demonstration area (2500 square feet reserved). Clinical scenarios will be used as the basis of interactions with participants. Elion – p. 3

4. Technical Demonstration • Will focus on showing how clinically-relevant problems can be solved with IHE • Clinical Scenarios: • Cath: Primary Angioplasty for an Acute MI on an unregistered patient (“John Doe”) • Echo: Emergency (unordered) echo in the ICU • Echo: Stress echo (coordinated views and stages) • ECG: Retrieve ECG for Display Elion – p. 4

5. Cardiac Cath Workflow: Acute MI • The patient with an acute MI is rushed to cath without being registered or creating an order. Labeled as “John Doe” with a temporary patient ID. • He is admitted into the Hospital Information System and an order placed for the cath. The previous cath images can now be retrieved and reviewed. • Other systems (hemodynamics, angiographic images, etc.) are automatically and consistently updated from “John Doe” to the real patient name and ID. • IHE Technical Context: The scenario described above is accomplished using Use Case C5 of the Cath Workflow Profile: Patient Not Registered at ADT and Procedure Not Ordered. Elion – p. 5

6. Echo Workflow: Emergency Echo (ICU) • As an Echo technologist is leaving the ICU the attending physician walks up and requests an urgent echo exam for a patient in the room next door. • The technologist uses the Patient ID from the wrist band, performs the echo and reconnects the mobile echo system to the network (so that the images are available for viewing from the PACS Image Manager). • The patient demographics are validated and updated in the images. An order is created after the fact for future tracking. • IHE Technical Context: The scenario described above is accomplished using the Echo Workflow Profile Use Case E4: Intermittently Connected Modality with Ad Hoc Procedure, Patient Registered, Unscheduled Procedure. Elion – p. 6

7. Echo Workflow: Stress Echo • A demonstration of the consistent formatting of quad-screen displays for viewing diagnostic stress echo studies, no matter what order the images were obtained. • Show the ability to view by stage (different views on the screen during a given stage) or by view (given stages on the screen for the same view) • IHE Technical Context: The scenario described above is accomplished using the Stage and View extensions in the IHE CARD-TF 2:4.2. Elion – p. 7

8. Retrieve ECG for Display • The cardiologist is logged into an Electronic Medical Record (EMR) system and is reviewing patient George Brown’s information. This patient was admitted this morning for mild but reoccurring chest pain. • She selects the ECG icon and the most recent ECG for the correct patient is automatically and effortlessly displayed. The cardiologist did not need to log into an additional system and did not need to reenter the specific patient information to display. • IHE Technical Context: The scenario described above is accomplished the Retrieve ECG for Display profile. Elion – p. 8