Difference between revisions of "Profiles"

From IHE Wiki
Jump to navigation Jump to search
m
Line 2: Line 2:
  
  
Each [[Domains| domain]] specifies a collection of Profiles for problems directly related to their domain.  The list of currently available profiles may be accessed through the links below.  Alternatively, there is a complete list as an '''[[:Category:Profiles| alphabetized index of Profiles]]'''.
+
Each [[Domains| domain]] specifies a collection of Profiles for problems directly related to their domain.  The list of profiles for each IHE Domain may be accessed directly.  Alternatively, a complete list is provided as an '''[[:Category:Profiles| alphabetized index]]'''.
  
  

Revision as of 22:59, 6 December 2006

IHE Integration Profiles describe the solution to a specific integration problem, and document the various systems roles, interoperability standards and design details for implementors to developp systems that cooperate to address that problem. IHE Integration and Content Profiles offer a convenient way for implementors/vendors and users to reference the interoperability capabilities defined in the IHE Technical Framework without having to restate all of the technical details and profiling of standards that ensure actual interoperability. IHE abstracts the communicating systems as IHE actors and specifies the transactions supporting the information exchange that meet the intended use case. For convenient reference, each Profile has a short acronym.


Each domain specifies a collection of Profiles for problems directly related to their domain. The list of profiles for each IHE Domain may be accessed directly. Alternatively, a complete list is provided as an alphabetized index.


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.



IHE Cardiology Profiles

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.
  • [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 Laboratory Profiles

IHE Patient Care Coordination Profiles

  • [MS] Medical Summaries defines the content and format of Discharge Summaries and Referral Notes.
  • [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.

IHE Patient Care Devices Profiles

IHE Eyecare Profiles

IHE Radiation Oncology Profiles