Skip to content

RadioLogicCreator for Mac

Jump to bottom
Marco BARNIG edited this page Nov 29, 2019 · 4 revisions

The RadioLogicCreator tool for Mac was developed in the second half of 2016 to automate the creation process of clinical cases. The programming was done with the Swift 3 programming language.

The tool created a clinical case in four steps.

radiologiccreator-for-mac

First the collection of all related DICOM file was done recursively from a folder. The files were anonymized, cleaned, compressed and scaled. In the second step the patient name was replaced with the name of the clinical case and a description was added. In the third step the Observation and Answer pictures were read, the possible diagnoses were entered and the radio-button for the correct diagnosis was selected. After the validation of all text entries two DICOM files were created, embedding the pictures as DICOM images and the text as private tags. In the last step the modified and new created DICOM files were uploaded to the DICOM archive.

A first stable version was available at the end of 2016. The following code snippets of the project were shared on GitHub with other Swift developers :

From the beginning the RadioLogicCreator tool running on Mac was a continuous source of frustration for the users and the developer, for the following reasons:

  • Due to the severe security restrictions of Apple, the deployment of the RadioLogicCreator application on a Mac was difficult, despite the fact that the developer was identified and that the app was signed.
  • At each change of the OS X, it was necessary to adapt the application to new rules. The initial OS X was Yosemite, followed by El Capitan (end 2015), Sierra (end 2016), High-Sierra (end 2017), Mojave (end 2018) and now Catalina (2019).
  • The processing of DICOM files in four steps was synchronous and it took some waiting time before the creation of a clinical case was finished.
  • The connection between the Mac computer running the RadioLogicCreator tool and the Orthanc server working as a DICOM archive with an integrated reversed nginx proxy in a local network was recurrently the source of failures.
Clone this wiki locally