|
|
| Line 1: |
Line 1: |
| '''IHE Integration Profiles''' describe the solution to a specific integration problem, and document the system roles, standards and design details for implementors to develop systems that cooperate to address that problem. | | '''IHE Profiles''' provide a standards-based framework for sharing information within care settings and across networks by addressing critical interoperability issues related to the following important key areas: |
|
| |
|
| IHE Profiles are a convenient way for implementors and users to be sure they're talking about the same solution without having to restate the many technical details that ensure actual interoperability. | | Information Access for Care Providers and Patients |
| | Clinical Workflow |
| | Privacy & Security |
| | Administration |
| | IT Infrastructure |
| | Each IHE Profile describes a clinical requirement and solution for systems integration. It defines functional components, called IHE Actors, by specifying in careful detail the transactions each IHE Actor must perform, based on standards such as HL7FHIR, DICOM, HL7, and many others. This detail allows health IT professionals to implement IHE Profiles in health IT systems. |
|
| |
|
| For convenient reference, each Profile has a short acronym.
| | '''IHE Profiles are documented in IHE’s Technical Frameworks''', detailed technical specifications that serve as implementation guides for effective systems integration. |
|
| |
|
| | Referencing IHE Profiles gives implementers and users a common language for solutions backed by detailed specifications to ensure interoperability. |
|
| |
|
| Each [[Domains| domain]] specifies a collection of Profiles for problems directly related to their domain (see the lists below).
| |
|
| |
|
| Alternatively, see the '''[[:Category:Profiles| alphabetized index of Profiles]]'''.
| | IHE Technical Framework documents are available at [https://profiles.ihe.net/ profiles.ihe.net]. Or, follow the links below for a specific IHE domain's Technical Framework documents. |
|
| |
|
| | * [https://profiles.ihe.net/CARD/index.html Cardiology] |
|
| |
|
| __TOC__
| | * [https://profiles.ihe.net/DENT/index.html Dental] |
|
| |
|
| ==[[Radiology| IHE Radiology]] Profiles==
| | * [https://profiles.ihe.net/DEV/index.html Devices] |
|
| |
|
| * [SWF] [[Scheduled Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams. | | * [https://profiles.ihe.net/ENDO/index.html Endoscopy] |
|
| |
|
| * [PIR] [[Patient Information Reconciliation]] coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients. | | * [https://profiles.ihe.net/EYECARE/index.html Eye Care] |
|
| |
|
| * [CPI] [[Consistent Presentation of Images]] maintains consistent intensity and image transformations between different hardcopy and softcopy devices. | | * [https://profiles.ihe.net/ITI/index.html IT Infrastructure] |
|
| |
|
| | * [https://profiles.ihe.net/PaLM/index.html Pathology and Laboratory Medicine] |
|
| |
|
| * [XDS-I] [[Cross-enterprise Document Sharing for Imaging]] shares DICOM images, diagnostic reports and related information across a network of care sites. | | * [https://profiles.ihe.net/PCC/index.html Patient Care Coordination] |
|
| |
|
| * [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. | | * [https://profiles.ihe.net/PHARM/index.html Pharmacy] |
|
| |
|
| | * [https://profiles.ihe.net/QRPH/index.html Quality, Research and Public Health] |
|
| |
|
| * [IRWF] [[Import Reconciliation Workflow]] manages importing images from CDs, hardcopy, etc. and reconciling identifiers to match local values. | | * [https://profiles.ihe.net/RO/index.html Radiation Oncology] |
| * ...
| |
|
| |
|
| ==[[Cardiology| IHE Cardiology]] Profiles==
| | * [https://profiles.ihe.net/RAD/index.html Radiology] |
|
| |
|
| * [CATH] - [[Cardiac Cath Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for Cardiac Catheterization procedures
| |
| * [ECHO] - [[Echocardiography Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for digital echocardiography
| |
| * [ECG] - [[Retrieve ECG for Display]] provides a mechanism for broad access throughout the enterprise to electrocardiogram (ECG) documents for review purposes
| |
| * [ED] - [[Evidence Documents]] The addition of the Cardiology specific options to the Radiology ED profile
| |
| * [IDCO] - [[Implantable Device Cardiac Observation]] specifies a mechanism for the creation, transmission, and processing of discrete data elements and report attachments associated with cardiac device interrogations (observations).
| |
| * [STRESS] - [[Stress Testing Workflow]] provides the mechanism for ordering and collecting multi-modality data during diagnostic Stress testing procedures
| |
|
| |
|
| ==[[IT Infrastructure| IHE IT Infrastructure]] Profiles==
| |
|
| |
|
| * [<span ID='CT'>CT</span>] [[Consistent Time]] ensures system clocks and time stamps of computers in a network are well synchronized (median error less than 1 second).
| |
|
| |
|
| * [<span ID='ATNA'>ATNA</span>] [[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.
| | '''<span style="color:#D2691E; font-size: 14px;">Important Note: The content previously on this page has been archived and is no longer being updated. For historical purposes, it is available at https://wiki.ihe.net/index.php/Profiles/Archive_1. Always refer to [https://profiles.ihe.net/ profiles.ihe.net] for the current IHE Profiles.</span>''' |
| | |
| * [<span ID='RID'>RID</span>] [[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.
| |
| | |
| * [<span ID='EUA'>EUA</span>] [[Enterprise User Authentication]] enables single sign-on by facilitating one name per user for all devices and software that participate in this profile.
| |
| | |
| * [<span ID='PIX'>PIX</span>] [[Patient Identifier Cross Referencing]] cross-references patient identifiers between hospitals, sites, RHIOs, etc.
| |
| | |
| * [<span ID='PSA'>PSA</span>] [[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.
| |
| | |
| * [<span ID='PDQ'>PDQ</span>] [[Patient Demographics Query]] lets applications query a central patient information server and retrieve a patient’s demographic and visit information.
| |
| | |
| * [<span ID='XDS'>XDS</span>] [[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.
| |
| | |
| * [<span ID='PWP'>PWP</span>] [[Personnel White Pages]] provides basic directory information on human workforce members to other workforce members and applications.
| |
| | |
| ==[[Laboratory| IHE Laboratory]] Profiles==
| |
| | |
| | |
| ==[[Patient Care Coordination| IHE Patient Care Coordination]] Profiles==
| |
| | |
| * [<span ID='MS'><span ID='XDS-MS'>MS</span></span>] [[Medical Summaries]] defines the content and format of Discharge Summaries and Referral Notes.
| |
| | |
| * [<span ID="XPHR">XPHR</span>] [[Exchange of Personal Health Record Content]] describes the content and format of summary information extracted from a PHR system for import into an EHR system, and visa versa.
| |
| | |
| * [<span ID='EDR'>EDR</span>] [[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|medical summaries]] by adding structures to pass data specific for ED referrals such as the estimated time of arrival and method of transport.
| |
| | |
| * [<span ID='BPPC'>BPPC</span>] [[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.
| |
| | |
| * [<span ID='PPHP'>PPHP</span>] [[Pre-procedural History and Physical]] describes the content and format of an electronic Preprocedural History and Physicial document.
| |
| | |
| ==[[Patient Care Devices| IHE Patient Care Devices]] Profiles==
| |
| | |
| ==[[Eyecare| IHE Eyecare]] Profiles==
| |
| | |
| ==[[Radiation Oncology| IHE Radiation Oncology]] Profiles==
| |
IHE Profiles provide a standards-based framework for sharing information within care settings and across networks by addressing critical interoperability issues related to the following important key areas:
Information Access for Care Providers and Patients
Clinical Workflow
Privacy & Security
Administration
IT Infrastructure
Each IHE Profile describes a clinical requirement and solution for systems integration. It defines functional components, called IHE Actors, by specifying in careful detail the transactions each IHE Actor must perform, based on standards such as HL7FHIR, DICOM, HL7, and many others. This detail allows health IT professionals to implement IHE Profiles in health IT systems.
IHE Profiles are documented in IHE’s Technical Frameworks, detailed technical specifications that serve as implementation guides for effective systems integration.
Referencing IHE Profiles gives implementers and users a common language for solutions backed by detailed specifications to ensure interoperability.
IHE Technical Framework documents are available at profiles.ihe.net. Or, follow the links below for a specific IHE domain's Technical Framework documents.
Important Note: The content previously on this page has been archived and is no longer being updated. For historical purposes, it is available at https://wiki.ihe.net/index.php/Profiles/Archive_1. Always refer to profiles.ihe.net for the current IHE Profiles.