Rationale: My physicist has the job of recording the radiation dose of all the patients that we scanned. Previously, this was done by hand (i.e. pulling up the Dose Protocol from PACS, writing down the patient details and Total DLP, and calculating the estimated Effective Dose for each TDLP). Needless to say, my physicist had better things to do with her time (like chasing down us radiologists to change our film badges every month... :P).

Current Status: Active. As of May 2016, 20,000 dose protocols over 3 years

Publications:

Malaysian Congress of Radiology 2015

mcdcmReporter
Rapid Reporting System

Rationale:

There's this bus that goes around the rural areas in the state of Sarawak doing tuberculosis screening via chest radiographs. Although it uses computed radiography, there is no radiology information system installed. My job was to create a systematic way for radiologists in the state hospital to report the CXRs, and to disseminate the reports & images back to the peripheral hospitals / clinics.

Current Status: Active. As of May 2016, 3,000 CXRs in Orthanc, a few hundred reports

mcdcmViewer
HTML5/Javascript DICOM Viewer

Rationale: An offshoot of my experimentation with DICOM. Initially this was a PHP script relying on Orthanc to supply the relevant DICOM tags and pixel data, but has moved on to a pure client-based environment. In a nutshell: It's a single 2000-line HTML file that displays DICOM images (inefficiently :P). It's placed under Orthanc Projects because it can load studies directly from Orthanc. View the online version here.

Rationale: As mentioned multiple times by Sebastien, Orthanc Explorer was designed as low-level front-end. I wanted a front-end that allowed me to search the Orthanc database using more options, as well as perform QueryRetrieves from other DICOM nodes. This is also the front-end I encourage my colleagues to use to present radiology images at hospital meetings held in rooms without PACS stations.

Screenshots:

Remote Q/R and Local Search all in one interface.
Loadable by Patient / Study / Series either into the webViewer plug-in or into mcdcmViewer.

Rationale: Our hospital PACS system is, um... [CENSORED]. As StorageCommitment was never set-up, there was always a risk that patient images were deleted from the CT scanner before they arrived at the PACS. I designed a system to allow the technician to quickly compare the studies in the CT scanner with those in the PACS server just prior to manual deletion on the CT scanner.

Screenshots:

Colour codes try to guess the number of expected instances based on Study Description