|
|
| 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] |
| === Final Text ===
| |
| * [<span ID='CT'>CT</span>] [[Concistent Time]]
| |
| The Consistent Time Integration Profile (CT) provides a means to ensure that the system clocks and time stamps of the many computers in a network are well synchronized. This profile specifies synchronization with a median error less than 1 second. This is sufficient for most purposes.
| |
| * [<span ID='ATNA'>ATNA</span>] [[Audit Trail and Node Authentication]]
| |
| The Audit Trail and Node Authentication (ATNA) Integration Profile establishes security measures which, together with the Security Policy and Procedures of the enterprise, provide patient information confidentiality, data integrity and user accountability. The Audit Trail and Node Authentication Integration Profile requires the use of bi-directional certificate-based node authentication for connections to and from each node, and requires that events concerning PHI use are recorded and transmitted to a repository where they can be monitored to detect indications of inappropriate activity.
| |
| * [<span ID='RID'>RID</span>] [[Request Information for Display]]
| |
| The Retrieve Information for Display Integration Profile (RID) provides simple and rapid read-only access to patient-centric clinical information that is located outside the user’s current application but is important for better patient care (for example, access to lab reports from radiology department). It supports access to existing persistent documents in well-known presentation formats such as CDA (Level 1), PDF, JPEG, etc. It also supports access to specific key patient-centric information such as allergies, current medications, summary of reports, etc. for presentation to a clinician. It complements workflows with access from within the users’ on-screen workspace or application to a broad range of information.
| |
| * [<span ID='EUA'>EUA</span>] [[Enterprise User Authentication]]
| |
| Enterprise User Authentication Profile (EUA) – This defines a means to establish one name per user that can then be used on all of the devices and software that participate in this integration profile. It greatly facilitates centralized user authentication management and provides users with the convenience and speed of a single sign-on. This profile leverages Kerberos (RFC 1510) and the HL7 CCOW standard (user subject).
| |
| * [<span ID='PIX'>PIX</span>] [[Patient Identifier Cross Referencing]] | |
| The Patient Identifier Cross-referencing Integration Profile (PIX) is targeted at healthcare enterprises of a broad range of sizes (hospital, a clinic, a physician office, etc.). It supports the cross-referencing of patient identifiers from multiple Patient Identifier Domains.
| |
| * [<span ID='PSA'>PSA</span>] [[Patient Synchronized Application]]
| |
| The Patient Synchronized Applications Profile (PSA) 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]]
| |
| The Patient Demographics Query Profile (PDQ) provides ways for multiple distributed applications to query a central patient information server for a list of patients, based on user-defined search criteria, and retrieve a patient’s demographic (and, optionally, visit or visit-related) information directly into the application.
| |
| * [<span ID='XDS'>XDS</span>] [[Cross Enterprise Document Sharing]]
| |
| The Cross-Enterprise Document Sharing IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
| |
| * [<span ID='PWP'>PWP</span>] [[Personell White Pages]]
| |
| The Personnel White Pages (PWP) Profile provides access to basic directory information on human workforce members to other workforce members within the enterprise. This information has broad use among many clinical and non-clinical applications across the healthcare enterprise.
| |
|
| |
|
| ==[[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 ===
| |
| * [<span ID='MS'><span ID='XDS-MS'>MS</span></span>] [[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] |
| * [<span ID="XPHR">XPHR</span>] [[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.
| |
|
| |
|
| * [<span ID='EDR'>EDR</span>] [[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.
| |
|
| |
|
| * [<span ID='BPPC'>BPPC</span>] [[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.
| |
|
| |
|
| * [<span ID='PPHP'>PPHP</span>] [[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.