My Orthanc Projects Some of my projects which are based on Orthanc. Most of the sources are available in the orthanc-users forum. isenDose | mcdcmReporter | mcdcmViewer | isenBrowser | Rapid CT Checker

isenDose CT Dose Database 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). System outline: Image Routing: [CT Scanner] --[fullStudy]--> [Routing Server] --[doseProtocol]--> [Dose Server (Orthanc)] In the Dose Server: [LUA Script] --[onStoredInstance, sends InstanceUID]--> [storeDoseData.php] In storeDoseData.php: [readsPatientData1 & readsDoseData2, stores in database] 1: Patient demographics retrieved via REST calls from PHP script to Orthanc 2: Depending on manufacturer, either OCR (Siemens, Toshiba) or read from DICOM tag (Philips) Screenshots: Hardware: CT: Siemens Sensation 64, Routing Server: Siemens Syngo.Via, Dose Server: HP Workstation (Xeon, 8Gb RAM, Windows 7 Pro) Software: Bitnami WAPP Stack, Orthanc 0.8.6 + PostGreSQL plug-in 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. System outline: Manual upload: [CR in Bus] --[CXR]--> [External HDD] --[upload CXR]--> [Reporting Server (Orthanc)] *contract details disallow direct network connection from the bus to the reporting server (facepalm) In the Reporting Server: [LUA Script] --[onStudyStable, sends InstanceUID]--> [mcdcmReporter] In mcdcmReporter: [readsPatientData1, creates new "order" in database] 1: Patient demographics retrieved via REST calls from PHP script to Orthanc To report in mcdcmReporter: [authenticate radiologist] --> [retrieve worklist] --> [report CXRs, generate keywords] --> [store report] To review reports in mcdcmReporter: [authenticate technician] --> [retrieve reported worklist] --> [generate PDFs with CXRs & reports] Screenshots: Dell Ultrasharp 24" Monitor Upload via Orthanc Explorer Worklist with patient details grabbed directly from DICOM tags in the CXRs Reporting interface. Features: - customizable user templates - AI keyword detection - automatically load next worklist item PDFs of Signed Reports & CXRs Hardware: CR: Carestream, Reporting Server: HP Workstation (Xeon, 8Gb RAM, Windows 10) Software: Bitnami WAPP Stack, Orthanc 1.0 + PostGreSQL & webViewer plug-ins 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. System outline: Loading from Orthanc1: [mviewer.html?study=orthancStudyUID]2 --> [instances list via REST] --> [async load instances] [mviewer.html?series=orthancSeriesUID] --> [instances list via REST] --> [async load instances] 1: works best with serveFolders plug-in, also works with reverse proxy 2: beta for loading studies is not yet available, pending final bug check Screenshots: Interface. Supports mouse, multi-touch and Leap Motion Running the MRI T2* Iron Quantification Tool Hardware: Orthanc Server: Consumer Desktop (Intel i5, 4Gb RAM, Windows 10) Software: Bitnami WAPP Stack, Orthanc 0.9.1 + PostGreSQL & serveFolders plug-in Current Status: Active. Publications: Viewer with T2* tool submitted for presentation at NASCI 2016

isenBrowser HTML5/Javascript Front-end for Orthanc 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. Hardware: Orthanc Server: Consumer Desktop (Intel i5, 4Gb RAM, Windows 10) Software: Bitnami WAPP Stack, Orthanc 0.9.1 + PostGreSQL & serveFolders plug-in Current Status: Active.

Rapid CT Checker Comparison of Q/Rs from Multiple Nodes 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 Hardware: Orthanc Server: HP Workstation (Xeon, 8Gb RAM, Windows 7 Pro) Software: Bitnami WAPP Stack, Orthanc 0.8.6 Current Status: Active.

© 2014 - 2016 the mcdcm Project