|
412
|
360X
|
360 Exchange Closed Loop Referral (360X)
|
The goal of this profile is to enable improved care coordination between providers utilizing different Electronic Health Record technology (EHRT) / Health Information technology (HIT) when a patient is referred from one provider to another, and when the expectation is that the patient will eventually return to the referring provider for continued care. In particular, the 360X Profile seeks to enable providers — using existing health data exchange standards and technologies — to exchange:
• referral requests containing relevant patient clinical information
• result of referral containing relevant patient clinical information
from within their EHRT workflow, regardless of the EHRT used. This will allow providers to communicate electronically the related patient information even if utilizing different EHRT/HIT. This scope indicates that the 360X Project includes defining the transport and content of:
• the Referral Request
• the Result of Referral
• additional information to facilitate the referral process workflow, and the closing of the loop
|
Trial Implementation
| |
|
|
440
|
360X / Direct
|
360X / Direct
|
360X is the PCC Integration Profile. Direct is described below.
The 360X / Direct entry is created to indicate that IHE USA testing is only performed in the context of 360X. IHE USA does not perform Direct certification / conformance assessment.
Direct is a technical standard for exchanging health information between health care entities (e.g. primary care physicians, specialists, hospitals, clinical labs) in a trusted network. It is secure, easy-to-use, inexpensive, and approved for use by nationally-recognized experts and organizations. Direct functions like regular e-mail with additional security measures to ensure that messages are only accessible to the intended recipient, per the protection regulations of the Health Insurance Portability and Accountability Act (HIPAA).
https://www.healthit.gov/sites/default/files/directbasicsforprovidersqa_05092014.pdf
|
Final Text
| |
|
|
441
|
ACDC
|
Assessment Curation and Data Collection
|
The Assessment Curation and Data Collection (ACDC) supports the selection of assessment instruments from a repository and the integration of those instruments into a provider workflow for the capture of the assessment data.
|
Trial Implementation
| |
|
|
274
|
ACM
|
Alert Communication Management
|
This profile defines the communication of alerts from alert source systems to alert manager systems and from alert manager systems to alert communicator systems.
This profile provides for alert dissemination between alert source devices and systems, from the connector to and within the communication services to the required abstract semantics, in a manner that, if complied with, enables multi-vendor multi-modality interoperation.
|
Final Text
| |
|
|
83
|
ACM2010
|
DEPRECATED: 2010 Alarm Communication Management
|
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.
|
Deprecated
| |
|
|
371
|
ADX
|
Aggregate Data Exchange
|
The Aggregate Data Exchange (ADX) profile defines the structure of ADX/XML messages to be exchanged between a Content Creator and a Content Consumer. . ADX introduces a new actor: the Content Data Structure Creator. The Content Data Structure Creator defines the structural metadata (eg code lists for dataelements) to be used in the message exchange. The message structure definition files created by the Content Data Structure Creator may be employed by a Content Creator to construct and exchange interoperable, ADX-conformant messages with a Content Consumer.
|
Trial Implementation
| |
|
|
435
|
ADX-HIV
|
Aggregate Data Exchange-HIV
|
The Aggregate Data Exchange-HIV Profile (ADX-HIV) specifies how to create and consume ADX messages for core HIV care and treatment indicators. ADX-HIV leverages the actors and transactions defined in the ADX Profile to enable interoperable reporting of routine HIV indicator data.
ADX-HIV is a Content Profile that defines a common Data Structure Definition (DSD) with structural metadata (codelists with data elements and associated disaggregation) to represent HIV core indicators that could be readily used in existing systems for reporting. Additionally, it specifies how to create and extend HIV care and treatment normative schema and XML messages. These are used for producing, validating and processing aggregate data by diverse Content Creators and Content Consumers of these core HIV indicators.
|
Trial Implementation
| |
|
|
446
|
AIR
|
AI Results
|
The AI Results Profile addresses the capture, distribution, and display of medical imaging analysis results. The central use case involves results generated by artificial intelligence (AI Model) algorithms.
|
Trial Implementation
| |
|
|
448
|
AIW-I
|
AI Workflow for Imaging
|
The AI Workflow for Imaging Profile addresses use cases to request, manage, perform, and monitor AI Inference on digital image data. AI Inference is the process of using trained AI Models or machine learning algorithms to make a prediction.
|
Trial Implementation
| |
|
|
99
|
APE
|
Antepartum Education
|
Antepartum Education
|
Trial Implementation
| |
|
|
98
|
APHP
|
Antepartum History and Physical
|
Antepartum History and Physical
|
Trial Implementation
| |
|
|
100
|
APL
|
Antepartum Laboratory
|
Antepartum Laboratory
|
Trial Implementation
| |
|
|
393
|
APPC
|
Advanced Patient Privacy Consents
|
https://profiles.ihe.net/ITI/TF/Volume1/ch-43.html
The Advanced Patient Privacy Consents (APPC) Profile defines a structural representation of a privacy consent policy. The definition allows for privacy consent policies that can include individualized parts, based on the patient’s choices.
|
Trial Implementation
| |
|
|
97
|
APS
|
Antepartum Summary
|
Antepartum Summary
|
Trial Implementation
| |
|
|
297
|
APSR
|
Anatomic Pathology Structured Reports
|
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.
|
Trial Implementation
| |
|
|
86
|
APW
|
Pathology Workflow
|
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
|
Trial Implementation
| |
|
|
16
|
ARI
|
Access to Radiology Information
|
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.
|
Final Text
| TF |
|
|
115
|
ARPH
|
Anatomic Pathology Reporting to Public Health
|
Anatomic Pathology Reporting to Public Health
|
Trial Implementation
| |
|
|
317
|
ARTI
|
Advanced Radiation Therapy Integration
|
This integration profile involves the exchange of RT Plan information between treatment planning systems and between treatment planning systems and treatment management systems. The emphasis for this profile is on reducing ambiguity involved in re-planning and incorporation of the planning information in to the treatment management system in anticipation of transfer to a treatment delivery system. The transactions revolve around content rather than workflow.
|
Trial Implementation
| |
|
|
48
|
ATNA
|
Audit Trail and Node Authentication
|
https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html
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.
|
Final Text
| |
|