From acquisition to archiving: how to integrate medical devices and software with a PACS without developing DICOM connectivity from scratch.
Integrating a medical device or acquisition software with a PACS (Picture Archiving and Communication System) is not always a straightforward process.
Many devices and applications produce JPEG, PNG or BMP images, PDF documents, videos or DICOM files, but lack the necessary functionality to transfer them directly to the hospital archive.
In such scenarios, developing a dedicated DICOM integration can be time-consuming and introduce further complexities: managing connections, creating DICOM objects, associating patient metadata, transmitting data and verifying successful delivery.
From the file to the PACS: the problem of DICOM integration
The DICOM (Digital Imaging and Communications in Medicine) standard defines how medical images and information are represented, exchanged and stored.
However, not all systems used in the healthcare sector are designed with a built-in DICOM interface.
Imaging software may export images in JPEG or BMP format. A device may generate PDF reports. A specialist application may save examination results to disc without having any functionality to communicate with a PACS.
To make this content available within the hospital’s infrastructure, three tasks generally need to be carried out:
- Creation or management of DICOM objects: converting content into objects compatible with the standard, where necessary.
- Metadata management: correctly associating information relating to the patient, study and series.
- Transmission to the PACS: establishing DICOM communication and managing the transmission, any errors and the confirmation of archiving.
These functions can be implemented directly within the device’s software, or delegated to an external component that handles interoperability.
The second solution is particularly useful when working with existing systems or third-party applications that cannot be easily modified.
What is a DICOM Folder Watcher and how does it work?
A DICOM Folder Watcher is an application that monitors a directory and automatically initiates operations on files placed within it.
In the context of medical imaging, it can be used to automate the transfer of images and documents to a PACS repository.
DicomPulse Watcher implements this approach via a configurable Windows service, based on the DicomPulse SDK.
The process involves four steps.
1. Folder monitoring
The acquisition software continues to operate as normal, exporting its files to a configured directory.
DicomPulse Watcher monitors this folder and intercepts the files to be processed, without requiring the development of a new integration within the source application.
2. Metadata conversion and association
When necessary, the Watcher converts the files into appropriate DICOM objects.
Patient and study information can be provided via sidecar files in JSON, CSV or TXT formats.
This makes it possible to separate content creation from its representation in accordance with the DICOM standard.
3. Transmission to the PACS
Once the objects have been prepared, the Watcher uses the DICOM C-STORE service to send them to the configured destination.
Routing can be configured to a single PACS or to multiple destinations, with retry and failover mechanisms.
4. Verification and traceability
The operation is recorded in the job history and audit logs.
When supported and configured, the DICOM Storage Commitment service also allows you to obtain confirmation from the destination that the transmitted objects have been archived.
The result is an automated workflow that connects the device’s file system to the hospital’s DICOM infrastructure.
Convert Images, PDFs, and Videos to DICOM
One of the main advantages of DicomPulse Watcher is the ability to integrate content that is not originally in DICOM format.
The system supports various input formats and display modes.
Da JPEG, PNG o BMP a DICOM Secondary Capture
JPEG, PNG, BMP or TIFF images can be converted into DICOM Secondary Capture objects.
This mode is useful for importing images into the PACS that have been produced by external systems, specialist workstations or applications that do not natively generate DICOM files.
From PDF to DICOM Encapsulated PDF
PDF documents, such as instrument reports or documentation associated with an examination, can be embedded in DICOM Encapsulated PDF objects.
This allows them to be managed via the DICOM infrastructure, whilst retaining the original document as encapsulated content.
The display of the PDF naturally depends on the features supported by the PACS and the viewer used.
H.264 video in DICOM objects
DicomPulse Watcher also supports H.264 video in MP4 format, which can be represented using appropriate DICOM video objects.
This is a useful feature for applications and devices that generate video sequences and need to transfer them to systems compatible with these classes of DICOM objects.
Support for video representation allows integration to be extended beyond static images, provided that the destination PACS supports the objects used.
Practical applications: when should DicomPulse Watcher be used?
Automation via a monitored folder is particularly useful when you wish to introduce DICOM connectivity without altering the existing software architecture.
Integration of medical devices without DICOM connectivity
An acquisition device generates images or documents on a Windows computer but is unable to transmit them directly to the PACS.
DicomPulse Watcher can be configured to capture these files, create the necessary DICOM objects and transmit them to the hospital archive.
Integration with third-party software
A specialist application exports processing results to a folder, but does not have the APIs required for DICOM communication.
The Watcher allows you to use the existing export function as an integration point, minimising the need to modify the original application.
Archiving reports and documents in the PACS
Some workflows produce images and documents that need to be stored alongside other imaging data.
The Watcher can automate the creation and transmission of DICOM objects from exported documents, simplifying integration with existing archives.
Distribution to multiple destinations
In certain scenarios, the same objects must be sent to multiple repositories, such as a production PACS and a secondary destination.
DicomPulse Watcher supports configurations with multiple destinations, broadcast or failover modes, and retries in the event of communication problems.
Security, Anonymization, and Transmission Control
In a healthcare infrastructure, automation cannot be separated from security management and the traceability of operations.
DicomPulse Watcher integrates the features of the SDK on which it is built, including:
- DICOM communication with TLS 1.3, to protect data during transfer when destinations are configured to use it.
- Encrypted configuration, for managing application parameters.
- Audit trail with chained hashes, to support the traceability of operations.
- Optional anonymisation, with the option to send de-identified copies to selected destinations.
- Storage Commitment, to verify storage confirmation from PACS systems that support the service.
Anonymisation complies with the Basic Application Level Confidentiality Profile of the DICOM PS3.15 standard, with consistent management of aliases and references between objects.
It is important to bear in mind that anonymising metadata does not automatically remove any identifying information embedded directly within the pixels: such situations must be assessed as part of the workflow.
DicomPulse Watcher or SDK integration?
DicomPulse offers two approaches for incorporating DICOM connectivity into a product.
DicomPulse SDK is a modular C++20 library designed for developers who wish to integrate DICOM functionality – including object creation, communication with PACS, anonymisation and auditing – directly into their software.
DicomPulse Watcher, on the other hand, is a ready-to-configure application built on the same SDK.
The main difference lies in the level of integration required.
When designing a new medical system and having full control over the source code, the SDK allows you to incorporate DICOM connectivity directly into the product’s architecture.
Where, on the other hand, an application that exports files already exists, the Watcher can offer a quicker way to integrate the system with the PACS without having to develop new functionality in the original application.
Both solutions are based on the same technological components and are designed to meet different integration requirements.
Automate the DICOM workflow without redesigning the software
Integrating a medical system with a PACS does not necessarily mean rewriting the application that generates images and documents.
In many cases, it is possible to maintain the existing acquisition workflow and introduce a component dedicated to conversion, DICOM communication, and transmission management.
DicomPulse Watcher was created precisely for this purpose: to connect software, devices, and medical archives through an automated, configurable, and traceable process.
D/Vision Lab develops software solutions for medical imaging and interoperability between devices, applications, and hospital infrastructure.
Do you need to connect a device or software to the PACS?
Discover DicomPulse Watcher and contact us to discuss how to integrate it into your medical imaging workflow.
Frequently Asked Questions
Is it possible to automatically send JPEG or PNG images to a PACS?
Yes. Using DicomPulse Watcher, images can be converted into DICOM Secondary Capture objects and transmitted to a compatible PACS via C-STORE.
How can I convert a PDF to DICOM?
A PDF can be embedded within a DICOM Encapsulated PDF object. DicomPulse Watcher allows you to automate the process using files and metadata stored in a monitored directory.
Do I need to modify the acquisition software?
Not necessarily. If the software is already capable of exporting the necessary files and metadata, the Watcher can handle the conversion and transmission to the PACS without requiring DICOM integration directly into the source code.
Does DicomPulse Watcher work on Windows?
Yes. It is available for Windows x64 and can be run as a Windows service or as a console process.
