Introduction
2.1. Overview
The Integrating the Healthcare Enterprise (IHE) Integration Statement specifies the Integration Profiles, its Actors, and Options Philips Healthcare has chosen for implementing in this product. This document helps the reader to investigate whether and to what extent interoperability with other products might be supported.
The IHE Technical Framework identifies a subset of the functional components of the healthcare enterprise and specifies their interactions in terms of a set of coordinated transactions. The actors and transactions described in the IHE Technical Framework are abstractions of the real-world healthcare in-formation system environment. While some of the transactions are traditionally performed by specific product categories (e.g. HIS, RIS, PACS, or modalities), the IHE Technical Framework intentionally avoids associating functions or actors with such product categories. For each actor, the IHE Technical Framework defines only those functions associated with integrating information systems. The IHE definition of an actor should therefore not be taken as the complete definition of any product that might implement it, nor should the framework itself be taken as the complete definition of a healthcare information system architecture.
This IHE Integration Statement provides the reader with a high-level view of supported IHE integration profiles. For further investigations, additional information can be found in the DICOM Conformance Statement of this product and in the IHE Technical Framework.
2.2. Important Note to the Reader
This IHE Integration Statement by itself does not guarantee successful interoperability of this Philips product with other products. The user (or user's agent) should be aware of the following issues:
Interoperability
Interoperability refers to the ability of application functions, distributed over two or more systems, to work successfully together. It is the user's responsibility to analyze thoroughly the application requirements and to specify a solution that integrates Philips equipment with non-Philips equipment.
Verification
Philips equipment has been carefully tested to ensure that the actual implementation of the IHE Integration Profiles corresponds with this Integration Statement. Where Philips equipment is linked to other equipment, the first step is to compare the relevant Integration Statement. If the Integration Statement indicates that successful information exchange should be possible, additional verification tests will be necessary to ensure the functionality, performance, accuracy and stability of image and image related data. It is the responsibility of the user (or user's agent) to specify the appropriate test suite and to carry out the additional verification tests.
New versions of the IHE Technical Framework
The IHE Technical Framework will evolve in future to meet the user's growing requirements and to incorporate new features and technologies. Philips is actively involved in this evolution and plans to adapt its equipment to future versions of the IHE Technical Framework. In order to do so, Philips reserves the right to make changes to its products or to discontinue its delivery. The user should ensure that any non-Philips provider linking to Philips equipment also adapts to future versions of the IHE Technical Framework. If not, the incorporation of IHE enhancements into Philips equipment may lead to loss of connectivity (in case of networking).
2.3. General Acronyms and Abbreviations
The following acronyms and abbreviations are used in the document.
- Actor: An entity within a use case that performs an action
- ATNA: Audit Trail and Node Authentication
- CPI: Consistent Presentation of Images
- CT: Consistent Time
- DMS: Document Management System
- DICOM: Digital Imaging and Communication in Medicine
- HIS: Hospital Information System
- IHE: Integrating the Healthcare Enterprise
- MR: Magnetic Resonance
- NTP: Network Time Protocol
- PACS: Picture Archiving and Communication System
- RIS: Radiology Information System
- SWF.b: Scheduled Workflow.b
- TLS: Transport Layer Security
- UDP: User Datagram Protocol
3. IHE Integration Statement
Version history:
| Version | Date of issue | Description of change |
|---|---|---|
| 1.0 | 01-Apr-2025 | Initial Release of MR Systems |
Product Information:
| Vendor | Product Name | Version |
|---|---|---|
| Philips Medical Systems |
| MR R12.3 |
This product implements all the transactions required in the IHE Technical Framework to support the IHE Integration Profiles, Actors and Options listed below.
IHE Integration Details:
| Integration Profiles Implemented | Actors Implemented | Options Implemented |
|---|---|---|
| Scheduled Workflow.b (SWF.b) | Acquisition Modality | Broad Worklist Query Patient Based Worklist Query Assisted Acquisition Protocol Setting PPS Exception management |
| Consistent Presentation of Images (CPI) | Acquisition Modality | No options defined |
| Consistent Time (CT) | Time Client | SNTP (Simple NTP) |
| Audit Trail and Node Authentication (ATNA) | Secure Node | Radiology Audit Trail STX: No Secure Transport STX: TLS 1.2 Floor using BCP195 ATX: TLS Syslog ATX: UDP Syslog |
Conformance and Information Links
- IHE Conformance Statements: Philips IHE (www.philips.com/IHE)
- DICOM Conformance Statements: Philips DICOM (www.philips.com/DICOM)
- More about products from Philips Healthcare: Philips Healthcare Support
- General information on IHE: IHE International and North America, IHE Europe, IHE Japan
Issued by:
Philips Medical Systems Nederland B.V.
Veenpluis 6
5684 PC Best
The Netherlands
Internet: www.philips.com/IHE
Doc Id: 1943575
Date: 01-Apr-2025
