Mercury™ is a robust, fully functional mini-archive, and is the first DICOM archive which indexes exactly the information you want. It can work out of the box as a temporary archive, store and forward cache, or small departmental archive. Its configurable database indexes and retrieves the DICOM tags and workflow fields that you specify. Mercury can also become an instant archive for any persistent datasets you have or receive - just specify their location, and instruct Mercury to import all of the DICOM datasets it finds at that location.

Mercury's configurability extends to the DBMS, persistent storage, and the administrative interfaces allowing you to leverage your existing infrastructure. You can use Mercury's preconfigured database, or you can configure Mercury to use your existing DBMS. Likewise, you can use Mercury's provided GUIs, or use Mercury's public APIs in order to quickly deliver a look and feel consistent with your organization. You can even specify multiple persistence locations for the DICOM datasets being archived.

Selecting or switching Mercury between the various pluggable modules is simple: a configuration change is all that is needed and no code modifications or recompilations are necessary.

Mercury capitalizes on the world class 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 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.

Mercury 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.