| Product Sheet 
Rapid Application Development The Native Java 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 Software Development Kit (SDK) provides simple, high-level abstraction of DICOM messaging details, and comprehensive sample applications that are a straightforward demonstration of programming concepts. For many medical imaging applications, slight customization of the sample applications is the only development required.
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 Native Java 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 Native Java 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 Native Java 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
Portability and Performance The Native Java Toolkit is an object-oriented class library modeled after objects contained in the DICOM standard. A modern design maximizes performance on a wide array of platforms supported by Java. Use of Java minimizes the development learning curve and simplifies application portability across a wide variety of platforms. The Toolkit utilizes XML files for its data dictionary and configuration.
Platform Optimization The Native Java 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 rather than set through configuration files.
- Tools are included to limit the XML data dictionary to only the DICOM services required by the application.
- Integrated Network Capture supports field connectivity troubleshooting with the MergeDPM™.
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 Java types
- DICOMDIR/DICOM File
- File to Message Conversion
- Message to File Conversion
- DICOMDIR population and reading routines
|
 |
- Network Transfer
- Send Message
- Receive Message
- Secure Connections through Java JSSETM (AES and 3DES based encryption supported)
- Compression Support
- Supports encoding and decoding of all approved DICOM transfer syntaxes
- Future releases will support compression and decompression of common DICOM transfer
syntaxes.
- Debug/Logging
- Configurable
- Integrated Network Capture
|
Message Object Database and Supporting Data
- Dictionary included describing DICOM objects and tags in XML format.
- Used by the class library to construct, maintain, and validate DICOM message objects.
- Can be extended by developers to include private services and tags.
Example Storage, Storage Commitment, Query/Retrieve, Modality Worklist and Media Applications
- Java 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.
Product Sheet PDF 789K
