Here is the dcm4chee install at an uber-quick-and-simple pace…

Download the latest version, and unpack it.



Rename the folder to dcm4chee and move it to your “Applications” folder.



Set up your JAVA_HOME in your environment.



Plant yourself in the /Applications/dcm4chee/sql directory, and run the following commands to set up the mysql database.



Next you want to edit the ds-mysql.xml file located in the /Applications/dcm4chee/server/deploy folder to reflect the database connectivity information you supplied in the last step.



Next stop is to adjust the run.conf file in /Applications/dcm4chee/bin folder to the settings in the screenshot below.



Now let’s fire it up! Get yourself in the bin directory at /Applications/dcm4chee/bin in a terminal and execute `sh run.sh`



Alright, now that its running lets logon to it and poke around…the first thing we want to logon to is the jmx-console at http://0.0.0.0:8080/jmx-console (default user/pass is admin/admin)...



If everything is ok, you will see the configuration screen for JBoss…



Now lets check the main web interface for dcm4chee, point your browser to http://0.0.0.0:8080/dcm4che-web and logon with admin/admin…



Once logged in, the interface looks like the screenshot below.

Hmmm… no patients in the archive, Lets fire up OsiriX and quickly send one in, the default AE Title is DCM4CHEE on port 11112.



After the send is complete, refresh the patient list and see if the study you sent in made it… worked like a champ in the screenshot below.



Whoa! slick eh? Drill down on the patient and click the image icon, lets make sure WADO and the conversion libraries are all in order.



There you have it, zero to enterprise IHE image management with a quickness, thanks to the efforts of the folks at dcm4chee.