1. Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure Technical & Planning Committees

2. Sept 13-15, 2004IHE Interoperability Workshop 2 IHE IT Infrastructure 2004-2005 Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Audit Trail & Node Authentication Centralized privacy audit trail and node to node authentication to create a secured domain. New Patient Demographics Query New Personnel White Page Access to workforce contact information New Cross-Enterprise Document Sharing Registration, distribution and access across health enterprises of clinical documents forming a patient electronic health record New

3. Sept 13-15, 2004IHE Interoperability Workshop 3 IHE IT Infrastructure 2004-2005 Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Consistent Time Coordinate time across networked systems Audit Trail & Node Authentication Centralized privacy audit trail and node to node authentication to create a secured domain. New Patient Demographics Query New Personnel White Page Access to workforce contact information New Cross-Enterprise Document Sharing Registration, distribution and access across health enterprises of clinical documents forming a patient electronic health record New Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user

4. Sept 13-15, 2004IHE Interoperability Workshop 4 Simple and rapid access to patient information Access to existing persistent documents in well-known presentation formats: CDA, PDF, JPEG. Access to specific key patient-centric information for presentation to a clinician : allergies, current medications, summary of reports, etc.. Links with other IHE profiles - Enterprise User Authentication, Patient Identifier Cross-referencing and Cross Enterprise Document Sharing Retrieve Information for Display Abstract / Scope

5. Sept 13-15, 2004IHE Interoperability Workshop 5 User Convenience:  Healthcare providers can "see" the information. A significant integration step.  Workflows from within the users’ on-screen workspace or application.  Complements multiple simultaneous apps workflow of Patient Synchronized Apps Broad Enterprise-Wide access to information:  Web technology for simple clients  Clinical data handling fully assumed by the information source that holds clinical data. Retrieve Information for Display Value Proposition

6. Sept 13-15, 2004IHE Interoperability Workshop 6 Standards Used:  Web Services (WSDL for HTTP Get).  General purpose IT Presentation Formats: XHTML, PDF, JPEG, CDA L1 (HL7)  Client may be off-the-shelf browser or display application. Two services :  Retrieve of Specific Information: Patient centric: patient ID Type of Request (see next slide) Date, Time, nMostRecent  Retrieve a Document Object Unique Instance Identifier (OID) Type of Request Content Type Expected Retrieve Information for Display Key Technical Properties

7. Sept 13-15, 2004IHE Interoperability Workshop 7 Transaction Diagram Retrieve Information for Display Display Information Source Retrieve Specific Info for Display [11] Summary of Laboratory Reports Summary of Radiology Reports Summary of Cardiology Reports Summary of Surgery Reports Summary of Intensive Care Reports Summary of Emergency Reports Summary of Discharge Reports List of Allergies List of Medications Retrieve Document for Display [12] Persistent Document Types of Requests Summary of All Reports Summary of Prescriptions

8. Sept 13-15, 2004IHE Interoperability Workshop 8 Query Keys – Transaction [11] Retrieve Specific Information for Display Parameter Name Request Type patientID lowerDate Time upperDate Time MostRecen tResults REQ R R O O R Description requestType specifies what type of information shall be retrieved. This parameter shall always be valued. This attribute identifies the subject of the results being queried for. Its value shall include identification of assigning authority. Used to constrain the earliest date/time of creation of information. Used to constrain the latest date/time of creation of information. The numeric value that indicates the number of most recent results to be included into the response, i.e., 1 indicates to provide the latest result.

9. Sept 13-15, 2004IHE Interoperability Workshop 9 Query Keys – Transaction [12] Retrieve Document for Display Parameter Name Request Type Document UID Description This parameter is required to have a value of “DOCUMENT”. Identifies document’s UID as known to both actors. REQ R R PreferredC ontentType This parameter is required to identify the preferred format: JPEG. PDF, CDA L1 that the document is to be provided (as MIME content type). R

10. Sept 13-15, 2004IHE Interoperability Workshop 10 Retrieve Information for Display Retrieved Data Presentation and Format - Non Persistent Data Content and Presentation is left to the Information Source Actor. - Persistent Data Documents are provided by the Information Source Actor in one of the Display Actor proposed formats: JPEG, PDF, CDA L1

11. Sept 13-15, 2004IHE Interoperability Workshop 11 More information…. IHE Web sites: http://www.himss.org/IHE http://www.rsna.org/IHE http://www.acc.org/quality/ihe.htmhttp://www.acc.org/quality/ihe.htm. Technical Frameworks: ITI V1.0, RAD V5.5, LAB V1.0 Technical Framework Supplements - Trial Implementation May 2004: Radiology August 2004: Cardiology, IT Infrastructure Non-Technical Brochures : Calls for Participation IHE Fact Sheet and FAQ IHE Integration Profiles: Guidelines for Buyers IHE Connect-a-thon Results Vendor Products Integration Statements