9:00 - 9:30 Opening

9:30 - 10:00 Andrew Crabb Johns Hopkins University / I Do Imaging Recent developments in free medical imaging software Medical imaging has a long history of free and open source software, benefiting from the ethos of sharing knowledge which is central to the software and academic worlds. Open source software consistently leads the adoption of new trends in medical imaging, software development, and computing practices. We will look at these changing trends, and the software projects that address them. Imaging itself evolves, with ever-increasing resolution and new modalities such as digital pathology. Software development changes much more rapidly and we see projects using new, or newly-popular, languages. Modern computing platforms - cloud, web services, containers - lead to new or repackaged projects. Yet there are top software projects that are decades old and have kept their lead through continued refinement. We will look at these and the wide world outside of clinical DICOM systems: research pipelines, image analysis, batch processing and lesser-served imaging modalities and formats.

10:00 - 10:30 Grégory Canivet and Christophe Gérard University Hospital of Liège Telemedecine using Orthanc: Two use cases at CHU Liège Teledermoscopy: Skin cancer has risen sharply in recent years. In 2015, it is the 4th most frequent among women. Having an appointment at the specialist for a consultation can take 8 to 12 weeks. This projet TeleSPOT (Teledermoscopy Smartphone-based Pigmented lesion diagnosis Online Taskforce) aims to propose a rapid and reliable diagnostic aid in the face of a suspicious pigment lesion, accelerate the care of very suspicious malignant lesions and revalorize the first line of care in screening and early diagnosis. Teleanapathology: CHU Liège has multiple remote sites where frozen sections (extemporanés) exams are realized and for which anapathologists give their diagnosis. Some of these sites are too far to be directly connected to the CHU network. Anapathologists have sometimes to drive several hours to give their diagnosis. The aims of this project are to make use of the new digital slide scanner and orthanc API to save time to the anapathologist and to make available the whole slide images to all laboratories.

10:30 - 11:00 Salim Kanoun et al. Institut Claudius Regaud GaelO: A free and open source imaging clinial trial management system We developed a free and open source (AGPLv3) web app for clinical trial imaging centralization including, DICOM deidentification, storage, quality control, expert's interpretation and clinical trial management. The web app using Orthanc as backend is built to manage multiple trials with users having one or multiple roles (Investigator, Controller, Monitor, Supervisor, Reviewer) in each trial. At the study creation the administrators define the number of imaging procedure in the trial, the expected patients and define the trial specific forms to be filled. Investigators are allowed to send DICOM through the web app after local deidentification. Reviewers can download DICOM from the web interface with the software of their choice and could also benefit from a direct viewer integration such as FIJI (using RestAPIs). Supervisor's dedicated interface shows the trial progress, reviews answers and integrates tools such as upload reminder, audit trail and images download interface.

11:00 - 11:30 Coffee break

11:30 - 12:00 Maxime Coevoet Cliniques universitaires St-Luc iTherapy Process [iTP]: Checklist workflow manager Improvement of radiation safety culture in medicine is a challenge as it is in other critical industrial fields. However, in order to ensure of a certain level of process quality achievement, checklists have only been introduced during the last two decades in hospitals, especially in the operating rooms (i.e. : WHO Surgical safety checklist). In the way to improve safety and efficiency in our Radiation Oncology department, we initiated an inhouse software development to help us on having an overview of the workload. iTP is a web-based open-source tool which is able to display the list of all the patients being supported in a department. Workload per role is displayed through a colour code. Entering the patient chart will bring you to a detailed checklist of the different items to be covered and finalized at a specific stage of the whole process. We have now an experience covering thousands of patients for which the treatment plans process preparation has been driven through this software.

12:00 - 12:30 Arnaud Pin et al. IBA Captain: An interface between the clinics and automation tool Purpose: To describe the open-source software platform CAPTAIN dedicated to research in radiation oncology and more specifically in proton therapy. The software provides online QA and decisionmaking tools and serve as a platform for the development of automatic adaptive re-planning tools. It offers the possibility to recompute proton doses maps with an independent Monte-Carlo dose-engine (MC-square), estimate clinical goals, DVH and gamma analysis and normal tissue complication probability (NTCP) model computation using the MATLAB library OPEN-REGGUI and python script. The architecture of the tool is very modular to allow researchers to use each piece independently. Orthanc is one of the most important building blocks in the development of these workflows. It’s the DICOM interface between the CAPTAIN platform and the external medical software: treatment planning system, the imaging system, Oncology Information System,…. For each new DICOM object received by Orthanc, it notifies CAPTAIN, which then triggers the appropriate worklow among those implemented. The results are accessible to the researchers, physician and physicist remotely via a web-browser on any device. Available workflows are (1) indications for adaptive therapy, machine log QA, and NTCP computation. Results: Daily anatomical changes are evaluated using the in-room CT or virtual CT (vCT) computed by deforming the pCT onto the daily CBCT. The estimated fractional dose expected to be delivered by the plan on the daily image is computed and used to determine the need for adaptive replanning. The same kind of indicators could also be evaluated by performing a dose reconstruction on the CT image using information recorded in the irradiation logs, i.e. using information about the actually delivered beam instead of the planned beam. in order to accelerate the process of patient specific QA. This last workflow in the CAPTAIN platform was used as the research prototype for the development of the medical software myQAion. A third workflow automatically computes the NTCP when CT, structure set, treatment plan and dose map are available on Orthanc. The computation is repeated for every new dose map. It provides a demonstrator of implementation of the model-based approach of patient selection. Orthanc also offer the possibility of 3D dose map visualization, overlaid onto the CT scan and the RTstructure within stone-of-Orthanc web-viewer to support the user in his research. Conclusion: CAPTAIN is an open source platform for translational research research in PT and RT, facilitating the development and evaluation of algorithms for clinical research studies. The application is of interest for clinical research in adaptive proton-therapy and it helps the clinical user to test, validate and evaluate the workflows developed by other researchers in proton therapy. Several workflows are already implemented, and the modularity of the tool offers possibility to anyone to implement his own application. In that platform Orthanc is a major piece of the architecture. The open-source approach allows research groups to develop their own workflow to share with the community to speed up research in PT.

12:30 - 13:00 Kim-Ann Git Selayang Hospital Orthanc as PACS: A Malaysian experience of deployment without funding Hospital Taiping is a 608-bed hospital in Malaysia which was established in 1880. Prior to the deployment of Orthanc, radiology images and reports were printed on film to be distributed to the wards and clinics. We introduced Orthanc supported with PostgreSQL in August 2017 with a custom front-end for search and reporting, on a desktop computer (Intel Core i5 with 4Gb RAM), which functioned as a mini-PACS for the radiology department. Multiple Orthanc instances were connected to the same PostgreSQL database to improve performance. In addition, Orthanc also serves as the backend for a custom mobile app for remote image viewing. Through negotiations, we managed to integrate all available modalities to Orthanc. Clinician acceptance was high, and problems were centered around our custom front-end. With a successful proof-of-concept, we obtained funding and in July 2019, migrated to a small server (Intel Xeon with 8Gb RAM) for expansion of PACS services to the entire hospital. Our database is currently at 2.2Tb, consisting of approximately 80,000 studies. Future plans include load-balancing and an improved disaster recovery solution.

13:00 - 14:00 Lunch

14:00 - 14:30 Andrew Crabb Johns Hopkins University / I Do Imaging Image management using Orthanc in a multi-centre research PET study We present a case study of a long-term research imaging study involving multiple academic PET imaging centres. A cloud-based Orthanc installation is used to provide a central image repository to receive and store PET, CT, and MR images. We use the DIMSE, REST API, and graphical interfaces of Orthanc as appropriate for image collection and management. A range of cloud services provide for easy data archiving and provide secure and validated access. Research imaging studies pose different challenges than clinical practice, especially in the variability of scanners, imaging protocols, and image header contents between centres and over time. We describe how the Orthanc API allows us to query the database of image metadata to monitor the study and assist in designing a flexible analysis workflow to accommodate differences between scans. A future expansion of the system will be built upon the API to allow study-wide image processing, accommodate errors in subject names, and study-specific image de-identification.

14:30 - 15:00 Marco Barnig Homepage and the RadioLogic project RadioLogic: A case-based learning and self-assessment tool for the Orthanc ecosystem for medical imaging Case-based learning (CBL) is an efficient method for radiologist education. RadioLogic is a system to create clinical cases from real DICOM files and provides a self-assessment tool to view the studies, submit a diagnosis and compare the performance with peers. The main components are a progressive web application and an Orthanc plugin to create and serve the teaching cases. The user selects a learning module, views the cases, submits his diagnosis and checks the results. The teacher selects a patient, study, series or instance inside an Orthanc server to start the creation of a clinical case in a webpage. He enters the name of the clinical case, the choices for a possible diagnosis, the answer and two images showing clinical data and explanations about the correct diagnosis. An asynchronous job is started in the Orthanc job engine to customize and compress the case and to generate two DICOM files from these images including private tags to hold the submitted data.

15:00 - 15:30 Christophe Phillips and Guillaume Flandin University of Liège (GIGA-CRC) and University College London (UK) Statistical parametric mapping, there and back again In 1988, the first brain activation studies, relying on Positron Emission Tomography, were reported. Back then, regional differences between brain images were simply characterised from hand-drawn regions of interest. The idea of producing a Statistical Parametric Map (SPM), i.e. providing valid inferences about signals across the entire brain, was subsequently formally introduced in 1990 by Friston et al. The SPM software, implementing these concepts in a complete analysis package, was first released in 1991 and made freely available to the neuroimaging community, to promote collaboration and a common analysis scheme across laboratories. Nowadays SPM remains the most used software for the analysis of neuroimaging data and has been extended over the years to handle functional and structural MRI, along with EEG/MEG data. An ecosystem of third-party extensions also flourished to address specific issues (over 60 at the time of writing). Some of them constitute toolboxes on their own, for example on the application on machine learning techniques in neuromaging or the processing of quantitative MRI.

15:30 - 16:00 Coffee break

16:00 - 16:30 Salim Kanoun et al. Institut Claudius Regaud Orthanc Tools, high level services built on the top of Orthanc Orthanc Tools is a standalone application written in Java to provide high level services using the power of Orthanc Rest APIs.This software could be described into 3 axes : An Orthanc GUI where most of the Rest APIs can be used through an user friendly GUI (display patients/studies/series, tag edition, deletion, Query/Retrieve/Send).

High level services built on the top of Orthanc such as : Automatic Query, to retrieve a batch of studies from a PACS with one predefined list of queries and a fully automatic retrieve Anonymize a batch of patient with management of different anonymization profile. CD/DVD burner management, automatically trigger CD/DVD burning from a simple DICOM transfer on Epson or Primera burning DiscProducer, with queue management, portable DICOM viewer, label printing Auto Fetch, retrieve automatically history from a PACS when a patient is received by Orthanc

Some Orthanc utils, such as Orthanc config json edition and generation through a GUI.

16:30 - 17:00 Luiz Eduardo Guida Valmont ALIS Soluções em Engenharia e Sistemas jOrthanc According to the TIOBE August 2019 index, Java is the most popular language, while C++ is fourth. Knowledge of the later is required to write Orthanc plugins. Therefore, the availability of an Orthanc Java API could prove to be a valuable asset in making Orthanc even more popular. The purpose of jOrthanc is to allow Java developers to extend Orthanc's capabilities. By harnessing the power of frameworks such as Spring Security, teams with no knowledge of C++ will be able to adopt Orthanc in their projects. This presentation aims to compare demo plugins written in both C++ and Java in regards to their total lines of code, testability and overall simplicity. It will follow that Java is a viable plugin technology just as C++ already is. It will also be shown that the cost of developing Java-enabled Orthanc plugins can be considerably smaller than that of their C++ counterparts. This makes jOrthanc an interesting proposition to further extend Orthanc's adoption.

17:00 - 17:30 Sébastien Jodogne Orthanc / Osimis The future of Orthanc, and announcement of new features

17:45 - 18:00 Closing and open discussions