|
|
| Line 1: |
Line 1: |
| '''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. | | '''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. |
|
| |
|
| Each [[Domains| domain]] manages a collection of Profiles shown below. Alternatively, there is an [[:Category:Profiles| alphabetized index of Profiles]].
| | '''IHE Profiles are documented in IHE’s Technical Frameworks''', detailed technical specifications that serve as implementation guides for effective systems integration. |
|
| |
|
| __TOC__
| | Referencing IHE Profiles gives implementers and users a common language for solutions backed by detailed specifications to ensure interoperability. |
|
| |
|
| ==[[Radiology| IHE Radiology]] Profiles==
| |
|
| |
|
| * [SWF] - [[Scheduled Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.
| | 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. |
| * [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]] supports sharing DICOM images, diagnostic reports and related information across a network of care sites. | | * [https://profiles.ihe.net/CARD/index.html Cardiology] |
| * [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/DENT/index.html Dental] |
|
| |
|
| ==[[Cardiology| IHE Cardiology]] Profiles==
| | * [https://profiles.ihe.net/DEV/index.html Devices] |
|
| |
|
| * [CATH] - [[Cardiac Cath Workflow]] ... | | * [https://profiles.ihe.net/ENDO/index.html Endoscopy] |
| * [ECHO] - [[Echocardiography Workflow]] ...
| |
| * ...
| |
|
| |
|
| ==[[IT Infrastructure| IHE IT Infrastructure]] Profiles==
| | * [https://profiles.ihe.net/EYECARE/index.html Eye Care] |
|
| |
|
| ==[[Laboratory| IHE Laboratory]] Profiles==
| | * [https://profiles.ihe.net/ITI/index.html IT Infrastructure] |
|
| |
|
| ==[[Patient Care Coordination| IHE Patient Care Coordination]] Profiles==
| | * [https://profiles.ihe.net/PaLM/index.html Pathology and Laboratory Medicine] |
| === Final Text ===
| |
| * [MS] [[Medical Summaries]] [http://www.ihe.net/technical_framework/upload/ihe_pcc_tf_rev1.1_ti_2006-06-20.pdf pdf] | |
| This profile defines the content sections for Discharge Summaries and Referral Notes. It uses HL7 Clinical Document Architecture (CDA) Release 2 and Care Record Summary as its base standard and constrains this to level 3 encoding for medications, allergies and problem lists.
| |
|
| |
|
| === Trial Implementation ===
| | * [https://profiles.ihe.net/PCC/index.html Patient Care Coordination] |
| * [XPHR] [[Exchange of Patient Health Record Data]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_XPHR_Exchanging_PHR_Content_20060812.pdf pdf] | |
| This profile describes the content and format of summary information extracted from a phr system for import into an ehr system, and visa versa. The purpose of this profile is to support interoperability between phr systems used by patients and ehr systems used by healthcare providers.
| |
|
| |
|
| * [EDR] [[Emergency Department Referral]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_EDR_ED_Referral_PC_20060812.pdf pdf] | | * [https://profiles.ihe.net/PHARM/index.html Pharmacy] |
| This profile 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 onmedical summary adding structures to pass data specific for ed referral such as estimated time of arrival and transport method.
| |
|
| |
|
| * [BPPC] [[Basic Patient Privacy Consent]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_BPPC_Basic_Patient_Privacy_Consents_20060810.pdf pdf] | | * [https://profiles.ihe.net/QRPH/index.html Quality, Research and Public Health] |
| This profile allows affinity domains to create a vocabulary of codes that identify policies with respect to information sharing. Each policy should identify which functional roles may access a document.
| |
|
| |
|
| * [PPHP] [[Preprocedural History and Physical]][http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_PPHP_Preprocedure_History_and_Physical_TI_2006_08_15.pdf pdf] | | * [https://profiles.ihe.net/RO/index.html Radiation Oncology] |
| This profile allows clincians to prepare an electronic representation of a Preprocedural History and Physicial document. It is similar to a Medical Summary document and shares methods for conveying structured data for medications, allergies and problem, but additionally provides mechanisms to represent more specific detail needed for preprocedural care.
| |
|
| |
|
| ==[[Patient Care Devices| IHE Patient Care Devices]] Profiles==
| | * [https://profiles.ihe.net/RAD/index.html Radiology] |
|
| |
|
| ==[[Eyecare| IHE Eyecare]] Profiles==
| |
|
| |
|
| ==[[Radiation Oncology| IHE Radiation Oncology]] Profiles== | | |
| | |
| | '''<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>''' |
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.