Product: Mercury Archive Engine™
Key Features
- Rapid OEMing of custom archive and DICOM PACS backend solutions.
- Pluggable and modular architecture with easy configuration.
- Support for standard DICOM archive functions built-in.
- Rule-based DICOM tag filtering and change tracking.
- Configurable DICOM transaction monitoring.
- HIPAA compliant logging.
Pricing Info
The Mercury Archive Engine from Laurel Bridge Software provides the core for a custom OEM medical image archive or PACS. It is a robust, fully functional DICOM store archive which serves as the foundation for a rich set of pluggable, interchangeable modules, which allow an OEM to very rapidly deploy a custom archive that can leverage their existing databases, persistence mechanisms, and look-and-feel.
Selecting or switching between various pluggable
modules is simple: a single line in a configuration file is
all that needs to be changed; no code modifications or
recompilations are necessary. The Mercury Archive
Engine itself is configurable: OEM's can specify which
DICOM tags should be stored in the database module and
which DICOM tags should be available for
Query/Retrieve searching; changing a configuration file
is all it takes.
The Mercury Archive Engine capitalizes on the worldclass performance of the DICOM Connectivity Framework (DCF). It takes full advantage of the rich set of logging and configuration features available for support and management of DICOM services.
Mercury Archive Engine Features:
- Modularity - Pluggable module architecture allows easy swapping of engine modules; predefined module implementations allow you to get started immediately.
- Configurable schema - Configurable database engine schema allows easy DICOM tag additions/deletions/modifications.
- Standard archive functionality - DICOM support for standard archive functions is built-in: Store SCP, Query/Retrieve SCP, Storage Commitment SCP, and Verification SCP/SCU.
- Non-image SOP classes - Full support for non-image sop classes, such as storage of Structured Reports, Radio Therapy, and GSPS objects.
- Transfer syntax handling - Configurable transfer syntax support allows datasets to be converted to and stored in any specified transfer syntax; optionally datasets can be stored in the transfer syntax that they were received, e.g. ILE, ELE, JPEG Lossless, JPEG 2000, etc.
- DICOM tag filtering - Powerful rule-based DICOM tag filtering (add/replace/modify) with optional change tracking in DICOM header.
- Chapter 10 support - Datasets can optionally be stored in DICOM Chapter 10 media exchange format.
- Control of session settings - Configurable session settings allow fine-grained control of associations, AE titles, filters, and logging.
- Easy logging and monitoring - Logging or monitoring of all DICOM transactions in a user-friendly, human-readable format.
- HIPAA logging - Includes HIPAA compliant logging for tracking access to the archive.
- High performance - Fully multi-threaded implementation assures high-performance of the engine.
- Event triggering - Supports triggers to allow scheduled events, including automatic or scheduled forwarding of datasets.
The Mercury Archive Engine provides OEMs or medical service providers the opportunity to rapidly implement their own custom archive solution or DICOM PACS backend that supports their business model and exhibits their own look-and-feel. The responsibility for managing compliance with the DICOM standard is off-loaded to the archive engine, greatly simplifying on-going support issues.

Mercury Product Description