Roadmap

This is a list of long term ideas (in addition to short term issues):

• Improve Dicom Support: RT STRUCT #306, DICOM Seg #932, overlays #585, waveforms?
• Switch to es6 #399
• more cloud integrations: Microsoft Azure (dicom-services-overview), Google cloud (dicom), cozy, owncloud, Microsoft onedrive (picker)
• Add DICOM series filter #646
• Improve parsing and display speed...
• Better quantification / labelling tools
• 3D segmentation tools
• Support high resolution data: OpenLayers (as 3dicom)?
• 3D rendering: WebGL (caniuse:webgl)?
• Follow BIR requirements

(app info on AppCircus or AppsFuel)

Open source medical

• Distribution related: debian-med (imaging and imaging packages), fedora-med (imaging), ubuntu-med, opensuse-med (last update 2010)
• Hospital Information systems / Patient record:
  • OpenEMR: open source electronic health records and medical practice management solution
  • GNUmed: open patient record
  • GNU Health: free health and hospital information system. Uses viewers like Ginkgo or Aeskulap (ref)
  • OpenMRS: has a radiology module using dcm4chee + weasis/ovyiam. Looking at Open Web Apps integration...
  • LibreHealth: code on gitlab
  • HospitalRun: code on github
• Lists: medfloss, wikipedia, openhub (dwv)
• Cenatic (for Spain, not only medical)

Some refs:

• Open innovation will be the winning strategy for digital sovereignty and human progress in the new decade , with a ref to dwv!! (04/2021)
• The Evolving Role of Open Source Software in Medicine and Health Services, a bit long... (01/2013)
• Lawyer demands software source (01/2012)
• Open Source Software: A Primer for Health Care Leaders (US, 2006)
• About licenses: License_compatibility (on wikipedia)

Funding

• Challenges from health2con (US) (as done in this presentation)
• Wayra (Spain)
• NGO
• Society for Imaging Informatics in Medicine: SIIM
• International Medical Informatics Association: IMIA
• European Federation for Medical Informatics: EFMI
• Association française d'informatique médicale: AIM
• Raising platforms: Kickstarter, Indiegogo, Fundly, Crowdfunder

Epics

Following are requirements relevant to the usage of DICOM data produced by an image acquisition machine.

Patient access/share DICOM

As a patient, I want to have access to my DICOM files and share them.

Examples:

• patient shares DICOM with doctor for (second) opinion
• patient shares DICOM anonymously with hospital/group/company for clinical trial, AI training...

Doctor access/share DICOM

As a doctor, I want to have access to a patient DICOM files (with his agreement), have the possibility to annotate them and optionally share them.

Examples:

• doctor views and annotates DICOM to give opinion
• doctor shares DICOM with other doctor for (second) opinion
• doctor shares DICOM anonymously with hospital/group/company for image analysis
• doctor shares annotated DICOM anonymously with hospital/group/company for clinical trial, AI training...
• doctor shares (annotated) DICOM anonymously with public for educational purposes (web, blog, special app...)

Solution

The DICOM data could be uploaded to a private cloud storage with the patient owning it. The storage could be a generic one (for example Google Drive) or a specific medical one (for example a hospital HIS with external access). A storage system that wants to meet the previous requirements would need to implement the following:

• a DICOM Web Viewer to view data
• a DICOM Web Annotator to add annotations to data
• a DICOM Web Anonymiser to view/download anonymous data

Each functionality being accessible via access rights such as view, annotate and download decided at the moment of sharing the data. View and annotate could be done live between multiple users. Download can only be done anonymously to avoid a data breach.