https://profiles.ihe.net/ITI/TF/Volume1/ch-19.html

The document sharing infrastructure provided by XD* allow for the publication and use of clinical documents associated with a patient. This profile allows for a Patient Privacy Policy Domain (e.g., an XDS Affinity Domain to have a number of Patient Privacy Policies that can be acknowledged (aka consent). This allows for more flexibility to support some patient concerns, while providing an important and useful dataset to the healthcare provider. Without BPPC, the XDS profile requires that the administrators of an XDS Affinity Domain creates and agrees to a single document publication and use policy (See ITI TF-1: Appendix L). Such a single XDS Affinity Domain Policy is enforced in a distributed way through the inherent access controls of the systems involved in the XDS Affinity Domain.
                        

The CA:Sec (Canadian Network Security) Implementation Guidance specifies the foundational elements needed to securely execute transactions between two systems.

CA:Sec is based on the ATNA profile and aims to bring improvements via loose coupling, and high cohesion, with focus on secure communication.
                        

The Canadian FHIR Exchange (CA:FeX) Specification seeks to promote RESTful FHIR exchange patterns, developed by industry-leading standards that can be applied on top of an existing non-FHIR infrastructure just as easily as it can be applied on top of FHIR servers. 

The current version of CA:FeX is focused on the RESTful exchange of documents, which FHIR offers multiple structures and patterns to achieve. CA:FeX aims to provide clarity to implementers by identifying some of the choices currently available, ranging from simple to a higher level of sophistication. As the development of CA:FeX continues, the Interoperability Specifications may evolve into a more formal Integration Profile (similar to existing international profiles reviewed below) that provides more comprehensive guidance on FHIR RESTful exchange patterns than what currently exists today.

It should be noted that the scope of CA:FeX may evolve beyond document-based exchange to explore a more atomic nature of health information exchange in the future. This will depend on the development of a multi-phased CA:FeX roadmap, the evolving needs of the Canadian healthcare market, and emerging trends within the international FHIR health information exchange community.
                        

The CA:Sec (Canadian Network Security) Implementation Guidance specifies the foundational elements needed to securely execute transactions between two systems.

CA:Sec is based on the ATNA profile and aims to bring improvements via loose coupling, and high cohesion, with focus on secure communication.
                        

The Cardiac Catheterization Workflow Integration Profile establishes the continuity and integrity of basic patient data in the context of the cardiac catheterization procedure. This profile deals specifically with consistent handling of patient identifiers and demographic data, including that of emergency patient presentation where the actual patient identity may not be established until after the beginning of the procedure, or even a significant time after the completion of the procedure. It also specifies the scheduling and coordination of procedure data across a variety of imaging, measurement, and analysis systems, and its reliable storage in an archive from where it is available to support subsequent workflow steps, such as reporting. It also provides central coordination of the completion status of steps of a potentially multi-phase (diagnostic and interventional) procedure.
                        

https://profiles.ihe.net/ITI/TF/Volume1/ch-7.html

Consistent Time Profile defines mechanisms to synchronize the time base between multiple actors and computers.  Various infrastructure, security, and acquisition profiles require use of a consistent time base on multiple computers.  The Consistent Time Profile provides median synchronization error of less than 1 second.  Configuration options can provide better synchronization. The Consistent Time profile specifies the use of the Network Time Protocol (NTP) defined in RFC 1305.
                        

Allows the creation of a scheduling information exchange between a master appointment schedule and a working provider, recognizing that often the master schedule and the personnel who operate it may not be readily available at the provider's location.
                        

The Patient Demographics for Mobile (PDQm) profile provides a transaction for mobile and lightweight browser based applications to query a patient demographics supplier for a list of patients based on user-defined search criteria and retrieve a patient’s demographic information into the application.

Deprecated in Aug 2017.  This was the DSTU2 version.
                        

https://profiles.ihe.net/ITI/TF/Volume1/ch-41.html

The Patient Identifier Cross-reference Mobile (PIXm) Integration Profile provides a transaction for mobile and lightweight browser based applications to query a Patient Identifier Cross-reference Manager for a list of patient identifiers based on the patient Identifier in a different domain and retrieve a patient’s cross-domain identifiers information into the application.
                        

https://profiles.ihe.net/ITI/TF/Volume1/ch-26.html

This profile describes the use of subscription and notification mechanism for use within an XDS Affinity Domain and across communities. The subscription allows for the matching of metadata during the publication of a new document for a given patient, and results in the delivery of a notification. 
                        

The Echocardiography Workflow Integration Profile describes the workflow associated with digital echocardiography, specifically that of transthoracic echo (TTE), transesophageal echo (TEE), and stress echo. As does the Cath Workflow Integration Profile, this profile deals with patient identifiers, orders, scheduling, status reporting, multi-stage exams (especially stress echo), and data storage. It also specifically addresses the issues of acquisition modality devices that are only intermittently connected to the network, such as portable echo machines, and addresses echo-specific data requirements.
                        

The Charge Posting Integration Profile describes mechanisms to transfer charge information to the clinic or enterprise Charge Processing System. This section corresponds to Transaction RAD-35 of the IHE Technical Framework. Transaction RAD-35 is used by the Department System Scheduler/Order Filler and Charge Processor actors. This section also refers to RAD-36 of the IHE technical framework that is used by the ADT Patient Registration and Charge Processor Actors. This section will correlate the activities that occur in the eye care clinic with these IHE defined transactions. The standards used are Health Level Seven, Version 2.3.1: Chapter 6 - Financial Management DICOM 2004 PS 3.4 Modality Performed Procedure Step SOP Class.
                        

The Guideline Appropriate Ordering profile supplies a mechanism by which EHR and departmental systems can evaluate orders to determine whether these orders conform to guidelines.  The profile enables the results of the evaluation (essentially an authorization) to be stored and transmitted, and the receiver of those results to verify that an order was evaluated with regard to appropriateness.

Supplement published for Public Trial Implementation: August 2015
                        

The IHE Radiology Import and Display of External Priors (IDEP) Profile specifies the trigger events, transactions, and data mappings necessary to automate the discovery of relevant prior imaging studies and reports and the transfer between different facilities, i.e., “external priors”.
IDEP is a workflow profile. The new requirements are concentrated in the Importer to minimize the impact on existing Image Managers and Report Managers. Specifically, IDEP provides a method for installed base systems to enable side-by-side display of relevant external priors studies for the same patient and to make those studies automatically appear “local”, including the ability to use the proper local display hanging protocols.
                        

This is not a real profile, but a way to create connectivity tests prior to an online event.
                        

The IPS profile uses the HL7’s IPS Implementation Guides that realize the CEN EN 17269 IPS dataset. Additional options pertaining to occupational Data for health and section constrains for complete IPS sections support are specified within this profile.
                        

The Import Reconciliation Workflow Integration Profile (IRWF.b) specifies how data Importers obtain local demographics, coerce patient and procedure attribute values in the imported data and report progress/status of the importation process. This Profile complements the Scheduled Workflow Profile by using the existing workflow mechanisms for notification and storage of imported Evidence Objects.

                        

https://profiles.ihe.net/ITI/TF/Volume1/ch-34.html

The IUA Profile adds authorization information to HTTP RESTful transactions. The IUA actors and behavior can be added to other profiles and transactions that need authorization.

The actors in the IUA Profile manage the access tokens used for authorization of access to HTTP RESTful services based on the flows and transactions defined in the OAuth 2.1 Authorization Framework [OAuth 2.1]. Authorization Clients interact with the Authorization Server to retrieve access tokens and incorporate them into HTTP RESTful transactions to authorize access to resources on the Resource Servers.