Hi Mario,
The lack of direct access to metadata with WADO was indeed one of the major reasons MINT was created. You are correct that MINT does not provide image rendering of DICOM files. This was a design decision made for separation of concerns, as providing data access is a completely separate thing from rendering images.
The reference implementation of MINT is available on http://code.google.com/p/medical-imaging-network-transport/ . It uses DCM4CHE libraries internally, and creates a war file that could be deployed alongside DCM4CHEE’s war. True integration could be done by rewriting the database layer in the reference implementation to use DCM4CHEE’s structures. Unfortunately there is not a lot of additional documentation beyond what you have probably already found on the Google code site - once we proved the ideas of MINT in the reference implementation, many of the contributors to MINT shifted focus to commercial products development as well as getting the ideas submitted as DICOM standards such as WADO-RS, STOW, and QIDO (which make up the core of MINT 2.0).
Tim
________________________________________________________________________
This email has been scanned for all viruses and found to be virus free. If you have questions regarding this scanning please visit the Information Services area of http://home.vitalimages.com
________________________________________________________________________
java -jar DICOM2MINT.jar once xml /opt/DICOMDATA/MRBRAIN.DCM http://localhost:8080/MINTServer/ nodelete
DICOM2MINT.sh /opt/DICOMDATA/MRBRAIN.DCM localhost nodelete