308
|
Acute Zorg
|
Acute Zorg
| |
Final Text
| |
|
301
|
Appeltaart
|
Appeltaart
|
Recept voor appeltaart
|
Trial Implementation
| |
|
256
|
ATNA
|
Audit Trail and Node Authentication
|
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
| TF |
|
310
|
BGZ_2017
|
Basisgegevensset Zorg
|
De Basisgegevensset Zorg (afgekort BgZ) is de minimale set van patiëntgegevens die specialisme-, ziektebeeld- en beroepsgroepoverstijgend relevant is en van belang voor de continuïteit van zorg. Dit betreft vooral situaties waarbij overdracht van zorg tussen zorgaanbieders plaatsvindt en/of behoefte bestaat aan een patiëntsamenvatting met eerdere behandelingen die in andere instellingen hebben plaatsgevonden.
|
Final Text
| |
|
280
|
BK2020-SE
|
Screening Eenheid
|
Afwijkende workflow voor de mobile unit gebaseerd op SWF.B
|
Trial Implementation
| |
|
307
|
BMHK
|
Baarmoederhalskanker
|
Baarmoederhalskanker
|
Final Text
| |
|
252
|
BPPC
|
Basic Patient Privacy Consents
|
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.
|
Final Text
| TF |
|
311
|
BVO BMHK
|
BVO BMHK
| |
Final Text
| |
|
259
|
CATH
|
Cardiac Catheterization Workflow
|
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.
|
Final Text
| |
|
302
|
CLBPS
|
CLBPS
| |
Trial Implementation
| |
|
304
|
Counseling
|
Counseling
| |
Final Text
| |
|
275
|
CT
|
Consistent Time
|
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.
|
Final Text
| TF |
|
264
|
DEPRECATED:A-EYECARE2015
|
DEPRECATED:Advanced Eye Care Workflow2015
|
The Eye Care Workflow Integration Profile establishes the continuity and integrity of basic patient and procedure data in the context of an eye clinic and/or an integrated hospital workflow scenario. This profile deals specifically with consistent handling of patient identifiers and demographic data. It also specifies the scheduling and coordination of procedure data to a wide variety of diagnostic imaging and testing equipment, and its reliable storage in an image management system from where it is available to support subsequent workflow steps, such as reporting. It also provides the ability for the acquisition devices to identify the actual procedure(s) that were performed. This enables further workflow steps such as automated billing.
|
Deprecated
| |
|
267
|
DEPRECATED:B-EYECARE2015
|
DEPRECATED:Basic Eye Care Workflow2015
|
Basic Eye Care Workflow Integration Profile establishes the continuity and integrity of basic patient and procedure data in the context of an eye clinic and/or an integrated hospital workflow scenario. This profile is a subset of the features defined in the Advanced Eye Care Workflow Integration profile.
|
Deprecated
| |
|
268
|
DEPRECATED:C-EYECARE2015
|
DEPRECATEC:Core Eye Care Workflow2015
|
This Core Eye Care Workflow (C-Workflow) profile addresses a scenario where organizations have a Practice Management System (PMS), Electronic Health Record System (EHR) and eye care diagnostic imaging and testing equipment (fundus cameras, slit lamps, refractive measurement devices, visual fields etc.).
This profile enables the consistent handling of patient identifiers and demographic data among the above types of systems. It includes support for features such as patient registration, appointment scheduling, eye care orders and equipment modality worklist. It reduces the implementation requirements of the other eye care workflows by not integrating an Image Archive (i.e. PACS system). Therefore, users of this profile must understand that acquisition devices and users are responsible for the safe keeping of the images and/or measurements created upon their system. It is important for users to understand how this is accomplished so that patient data is protected. How this is accomplished is outside the scope of IHE.
|
Deprecated
| |
|
261
|
DEPRECATED:ECAS2015
|
DEPRECATED:Eye Care Appointment Scheduling2015
|
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.
|
Deprecated
| |
|
283
|
DIFF
|
MR Diffusion Imaging
|
The MR Diffusion Imaging Integration Profile leverages enhanced MR diffusion images containing standard attributes for Diffusion B value, Diffusion gradient orientation and Diffusion image type. These objects are exchanged in an interoperable way allowing correct and convenient display. Applications using older single-frame DICOM image objects depended on knowledge of private attributes for this information.
|
Trial Implementation
| |
|
287
|
ECED
|
Eye Care Evidence Documents
|
The Eye Care Evidence Documents Profile defines information such as observations, measurements, and results (i.e., evidence documents), to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented or used by display and reporting systems.
|
Final Text
| |
|
260
|
ECHO
|
Echocardiography Workflow
|
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.
|
Final Text
| |
|
284
|
ED
|
Evidence Documents
|
The Evidence Documents Profile defines interoperable ways for observations, measurements, results and other procedure details recorded in the course of carrying out a procedure step to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented by display and reporting systems. This allows detailed non-image information, such as measurements, CAD results, procedure logs, etc. to be made available as input to the process of generating a diagnostic report. The Evidence Documents may be used either as additional evidence for the reporting physician or in some cases for selected items in the Evidence Document to be included in the diagnostic report.
|
Final Text
| TF |
|