Press Room Investor Relations Careers
 
 
 
 
Cedara Software

Speak With A Cedara Software Technology Representative
Development Platforms and Toolkits
Decrease Font Size Increase Font Size Add to Favorites Print Send To A Friend

MergeCOM-3™ .NET DICOM Toolkit | Product Sheet

A Microsoft .NET 2.0 based, Scalable DICOM® v3.0 Class Library for Medical Imaging Application Developers The MergeCOM-3 Advanced Integrator's .NET DICOM Toolkit is a comprehensive Software Development Kit (SDK) that greatly reduces the time required to bring DICOM conformant products to market in any area of medical technology. The SDK enables developers to focus on their application rather than the specific details of the DICOM protocol.

Key Benefits

Rapid Application Development The .NET MergeCOM-3 Toolkit greatly reduces the time to bring DICOM conformant products to the medical imaging market by enabling developers to focus on their product application rather than the low level details of the DICOM protocol.

The MergeCOM-3 Software Development Kit (SDK) provides a simple, high-level abstraction of DICOM messaging details, as well as a comprehensive collection of sample applications written in C# to demonstrate programming concepts that can serve as a starting point to accelerate development.

The use of Microsoft’s .NET environment enables medical application developers to take advantage of the latest software development tools and APIs to aide in application development.

Broad Market Assurance Representatives of Merge Healthcare have led or actively participated on numerous ACR/NEMA, DICOM Standards, and IHE Image Integration/HL7 Committee panels since their inception. Merge Healthcare is widely acknowledged as the leader in DICOM Toolkit development with more than 150 commercial MergeCOM-3 licensees. The .NET Toolkit supports all additions to the DICOM Standard Data Dictionary within six months of Committee approval. Draft versions of Supplements to the Standard are supported in Beta releases when requested by Toolkit customers.

Outstanding Technical Support The average response time to technical support questions posed to the engineering team is less than 24 hours. When appropriate, the .NET Toolkit team includes DICOM background information in addition to the specific answer for the question posed, based on our belief that broader DICOM knowledge will better support industry interoperability.

The Interface and Common Language Runtime The .NET Toolkit is an object-oriented class library modeled after objects contained in the DICOM standard. The Toolkit can be utilized from any of the languages supported by Microsoft’s common language runtime. The use of Microsoft’s .NET Framework minimizes the development learning curve and aids in the rapid development of DICOM based applications.

Platform Optimization The .NET Toolkit is highly configurable to best support the needs of many different target systems. For example:

  • Large data attributes, such as Pixel Data Values, can either be stored automatically or forwarded directly to the application for customized handling.
  • Automatic storage is supported either in memory or in temporary files (configurable).
  • Objects for required DICOM services are loaded at runtime to optimize memory utilization.
  • Configuration can be updated at runtime or set through configuration files.
  • Integrated Network Capture supports field connectivity troubleshooting with the MergeDPM™.

Message Object Database and Supporting Data:

  • Dictionary included describing DICOM objects and tags in binary format.
  • Used by the class library to construct, maintain, and validate DICOM message objects.
  • Data dictionary can be extended by developers to include private services and tags.

Example Storage, Storage Commitment, Query/Retrieve, Modality Worklist and Media Applications:

  • C# source code supplied implementing each service.
  • Useful for testing purposes and as an aide in development.
  • Service Class User (SCU) and Service Class Provider (SCP) examples included.
  • The media exchange sample application receives storage service messages and stores them in DICOM part 10 format, including the creation of a DICOMDIR file.

Key Benefits

Class Library

  • Association Management
  • Automatic negotiation of associations
  • Static and Dynamic Service/Transfer Syntax Lists
  • Static and Dynamic Host Information
  • Support for DICOM Asynchronous Operations
  • Message Encode/Decode
  • Integrated Value Representation Conversion
  • Support for conversion to and from standard .NET data types
  • DICOMDIR/DICOM File
  • File to Message Conversion
  • Message to File Conversion
  • DICOMDIR population and reading routines
  • Network Transfer
  • Send Message
  • Receive Message
  • Compression Support
  • Supports encoding and decoding of all approved DICOM transfer syntaxes
  • JPEG Baseline, JPEG Extended, and JPEG Lossless support through the use of Pegasus Imaging libraries. JPEG 2000 support implemented with the library, but requires an additional license from Pegasus. RLE support implemented with our own algorithm.
  • Debug/Logging
  • Configurable
  • Integrated Network Capture

DICOM Service Classes Supported Custom classes to support Verification, Storage, Query/Retrieve, Print Management, Storage Commitment, Basic Worklist Management, Study Content Notification, Patient Management, Study Management, Results Management, and Media Exchange. Other service classes supported with generic interface.

Compression support is included through the use of Pegasus libraries. On 32-bit Windows, 64-bit Windows, 32-bit Linux, 64-bit Linux, and Solaris platforms, MergeCOM-3 includes Pegasus Imaging Corporation’s (www.jpg.com) PICTools™ MedX SDK to support compression and decompression. Licenses for compressing and decompressing at 3 frames per second are included for lossy and lossless JPEG. A separate license must be purchased from Pegasus to enable support for JPEG 2000 or to remove the performance limitation for lossy and lossless JPEG.

The RLE and the DICOM Deflate transfer syntaxes are internally supported by MergeCOM-3.

Message Object Database and Supporting Data

  • Dictionary included describing DICOM objects and tags in binary format.
  • Used by the class library to construct, maintain, and validate DICOM message objects.
  • Data dictionary can be extended by developers to include private services and tags.

Example Storage, Storage Commitment, Query/Retrieve, Modality Worklist and Media Applications

  • C# source code supplied implementing each service.
  • Useful for testing purposes and as an aide in development.
  • Service Class User (SCU) and Service Class Provider (SCP) examples included.
  • The media exchange sample application receives storage service messages and stores them in DICOM part 10 format, including the creation of a DICOMDIR file.

.NET Requirements

  • The .NET 2.0 Framework
 
     
 
Privacy Policy Terms & Conditions Send This Link To A Colleague E-Mail Sign-Up