Profiles: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
WjhLqn (talk | contribs)
mNo edit summary
removed bold
 
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 implementers 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 implementers 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.


Profiles available for implementation (i.e. released as Final Text or for Trial Implementation) are listed below.
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.


Alternatively, see the '''[[:Category:Profiles| alphabetized index of Profiles]]'''.
* [https://profiles.ihe.net/CARD/index.html Cardiology]


* [https://profiles.ihe.net/DENT/index.html Dental]


__TOC__
* [https://profiles.ihe.net/DEV/index.html Devices]


* [https://profiles.ihe.net/ENDO/index.html Endoscopy]


==[[Cardiology| IHE Cardiology]] Profiles==
* [https://profiles.ihe.net/EYECARE/index.html Eye Care]


* [CATH] - [[Cardiac Cath Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for Cardiac Catheterization procedures
* [https://profiles.ihe.net/ITI/index.html IT Infrastructure]


* [ECHO] - [[Echocardiography Workflow]] integrates ordering, scheduling, imaging acquisition, storage and viewing for digital echocardiography
* [https://profiles.ihe.net/PaLM/index.html Pathology and Laboratory Medicine]


* [ECG] - [[Retrieve ECG for Display]] provides access throughout the enterprise to electrocardiogram (ECG) documents for review purposes
* [https://profiles.ihe.net/PCC/index.html Patient Care Coordination]


* [ED] - [[Evidence Documents]] adds Cardiology-specific options to the Radiology ED profile
* [https://profiles.ihe.net/PHARM/index.html Pharmacy]


* [IDCO] - [[Implantable Device Cardiac Observation]] specifies the creation, transmission, and processing of discrete data elements and report attachments associated with cardiac device interrogations (observations) or messages.
* [https://profiles.ihe.net/QRPH/index.html Quality, Research and Public Health]


* [STRESS] - [[Stress Testing Workflow]] provides ordering and collecting multi-modality data during diagnostic Stress testing procedures
* [https://profiles.ihe.net/RO/index.html Radiation Oncology]


* [DRPT] - [[Displayable Reports]] distributes “display ready” (PDF) cardiology clinical reports from the department to the enterprise.
* [https://profiles.ihe.net/RAD/index.html Radiology]


==[[Eyecare| IHE Eyecare]] Profiles==


* [EYECARE] - [[Eye Care Workflow]] manages eye care workflow.


* [ECED] - [[Eye Care Evidence Document]] creates, stores, retrieves
 
'''<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>'''

Latest revision as of 14:04, 10 September 2026

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.