Picture Archiving and Communication Systems (PACS) have been widely deployed in healthcare institutions, and they constitute now a normal commodity for practitioners. However, its installation, maintenance and utilization are still a burden due to their heavy structures, typically supported by centralized computational solutions. Dicoogle is a PACS archive supported by a document-based indexing system and by distributed engines. Replacing the traditional database storage (RDBMS) by a documental organization permits gathering and indexing data from file-based repositories, which allows searching the archive through free text queries. As a direct result of this strategy, more information can be extracted from medical imaging repositories, which clearly increases flexibility when compared with current query and retrieval DICOM services. Moreover, Dicoogle is easy to install, manage and use, and it maintains full interoperability with standard DICOM services.
Dicoogle is a platform easy to extend and if you need an extensible platform to develop new DICOM repositories with specific features, like Content-Image Based Retrieval, DICOM Data mining or any other feature, Dicoogle will allow to develop your own extensions.
To support software developers, Dicoogle provides a architecture with a “big picture”, where it specify several blocks, each of them with specific goals.
There are many abstractions, in different layers in Dicoogle architecture. Hence, we are exposing these modules, and show how they interact with the engine application.
Dicoogle PACS offers a full set of robust APIs, and even full integrated environments, suitable for a wide variety of pursuits, e.g. web, mobile devices, peer-to-peer, etc.
Are you interested in writing applications with Dicoogle? Dicoogle SDK is aimed at those completely new to Dicoogle programming. Dicoogle SDK is a package containing all abstractions interfaces to: Local, LAN and WAN access.(development)
Dicoogle RMI Communication
Dicoogle GUI (Graphical User Interface) can run separated from Engine. For instance, we can run more than one GUI, connecting just one Dicoogle Engine. The communication between those components use RMI (Remote Method Invocation).
Datasource Controller (API)
The datasource bus is strongly related with Dicoogle SDK. The key idea is create an abstraction for all modules (Local, LAN, WAN, CBIR). All those modules will use the datasource bus to communicate with Dicoogle engine. (development)
Dicoogle Mobile is a webservices Client. (development)
It is a webinterface of Dicoogle to the platform (development)
Provides an API to access search and download files indexed by Dicoogle.