Profiles

IHE Integration Profiles describe a specific integration problem, and document the equipment roles, standards and design details for vendors to implement products that cooperate to address that problem. Integration Profiles offer a convenient way for vendors and users to reference the functionality defined in the IHE Technical Framework without having to restate all of the detail regarding IHE actors and transactions. For convenient reference, each Profile has a short acronym.

Each domain manages a collection of Profiles shown below. Alternatively, there is an alphabetized index of Profiles.

IHE Radiology Profiles

• [SWF] Scheduled Workflow integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.

• [PIR] Patient Information Reconciliation coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients.

• [CPI] Consistent Presentation of Images maintains consistent intensity and image transformations between different hardcopy and softcopy devices.

• [XDS-I] Cross-enterprise Document Sharing for Imaging shares DICOM images, diagnostic reports and related information across a network of care sites.

• [TCE] Teaching File and Clinical Trial Export lets users flag DICOM images and related information for automatic routing to teaching file authoring or clinical trials management systems.

• [IRWF] Import Reconciliation Workflow manages importing images from CDs, hardcopy, etc. and reconciling identifiers to match local values.
• ...

IHE Cardiology Profiles

• [CATH] - Cardiac Cath Workflow ...

• [ECHO] - Echocardiography Workflow ...
• ...

IHE IT Infrastructure Profiles

• [CT] Consistent Time ensures system clocks and time stamps of computers in a network are well synchronized (median error less than 1 second).

• [ATNA] Audit Trail and Node Authentication describes certificate-based node authentication and transmitting PHI-related audit events to a repository. This helps sites implement confidentiality policies.

• [RID] Request Information for Display provides simple (browser-based) read-only access to important patient-centric clinical information (e.g. allergies or lab results) located outside the user’s current application.

• [EUA] Enterprise User Authentication enables single sign-on by facilitating one name per user for all devices and software that participate in this profile.

• [PIX] Patient Identifier Cross Referencing cross-references patient identifiers between hospitals, sites, RHIOs, etc.

• [PSA] Patient Synchronized Application enables single patient selection for the user working in multiple applications on a workstation desktop. With this Integration Profile patient selection in any of the applications causes all other applications to tune to that same patient. This allows a clinician to use the application they are most familiar with to select the patient and have that selection reflected in the other applications they are using follow along.

• [PDQ] Patient Demographics Query lets applications query a central patient information server and retrieve a patient’s demographic and visit information.

• [XDS] Cross Enterprise Document Sharing registers and shares electronic health record documents between healthcare enterprises, ranging from physician offices to clinics to acute care in-patient facilities.

• [PWP] Personnel White Pages provides basic directory information on human workforce members to other workforce members and applications.

IHE Patient Care Coordination Profiles

• [MS] Medical Summaries defines the content and format of Discharge Summaries and Referral Notes.

• [XPHR] Exchange of Patient Health Record Data describes the content and format of summary information extracted from a PHR system for import into an EHR system, and visa versa.

• [EDR] Emergency Department Referral allows clinicians to create electronic referrals to the emergency room including the nature of the current problem, past medical history, and medications. Upon arrival of the patient to the Emergency Department, the patient is identified as a referral, and the transfer document is incorporated into the EDIS. This profile builds on medical summaries by adding structures to pass data specific for ED referrals such as the estimated time of arrival and method of transport.

• [BPPC] Basic Patient Privacy Consents

provides a mechanism to record the patient privacy consent(s), a method to enforce these consents, and supports the creation of an Affinity Domain defined consent vocabulary that identify information sharing policies.

• [PPHP] Pre-procedural History and Physical describes the content and format of an electronic Preprocedural History and Physicial document.