The Alarm Communication Management integration profile defines the communication of alarms from alarm source systems to alarm management systems and from alarm management systems to alarm historical systems.
                        

Integration profile per il sistema Amministrativo Contabile
                        

Profilo per integrazione con Anagrafe Zero Regionale
                        

Antepartum Education
                        

Antepartum History and Physical
                        

Antepartum Laboratory
                        

The Antepartum Record Profile (APR) extends the description of the content structures for the Antepartum Summary (APS), and is based on the data elements from prenatal records currently in common use.
                        

Antepartum Summary
                        

This content profile describes an anatomic pathology structured report (APSR) as a CDA r2 document to be published towards a document sharing resource such as a shared electronic health record used by a community of care providers, relying on one of the infrastructure 
document sharing/exchanging profiles defined in IHE ITI TF.
                        

The Pathology Workflow Integration Profile establishes the continuity and integrity of basic pathology data acquired for examinations being ordered for an identified inpatient or outpatient
                        

The Access to Radiology Information Integration Profile specifies a number of query transactions providing access to radiology information, including images and related reports, in a DICOM format as they were acquired or created. Such access is useful both to the radiology department and to other departments such as pathology, surgery and oncology. Non-radiology information (such as lab reports) may also be accessed if made available in DICOM format.
                        

Anatomic Pathology Reporting to Public Health
                        

The ITI Audit Trail and Node Authentication (ATNA) Profile establishes the characteristics of a Basic Secure Node: It describes the security environment (user identification, authentication, authorization, access control, etc.) assumed for the node so that security reviewers may decide whether this matches their environments. It defines basic security requirements for the communications of the node using TLS or equivalent functionality. It defines basic auditing requirements for the node. The profile also establishes the characteristics of the communication of audit messages between the Basic Secure Nodes and Audit Repository nodes that collect audit information. 
                        

Profilo relativo all'Attribute Provider
                        

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.
                        

This entry represents the actor/option structure of the BPPC profile prior to the publication of the ITI TF in August 2010.   In gazelle, the "BPPC" profile entry contains the updated structure for the profile with only 2 actors - Content Creator and Content Consumer.
                        

The HITSP Patient Level Quality Data Document Using HL7 Quality Reporting Document Architecture Component supports the communication of patient level quality data for quality measurement in a document sharing environment. Patient encounter data are compiled from both the local systems and from longitudinal data available through a Health Information Exchange (HIE) prior to communicating the retrieved data described in this construct for analysis. View the most current version as HTML here.
                        

This Component supports communication of a quality measure (aka an "eMeasure"). Clinical concepts (e.g. "atrial fibrillation", "coronary artery disease") and parameters (e.g. "numerator", "denominator") in an eMeasure are formally defined to support consistent and unambiguous interpretation. The eMeasure is standardized as a structured document, where one can capture the complete narrative of the measureand a formalized computable representation of statements. View the most current version as HTML here