SecretariatMedical Imaging & Technology Alliance (MITA)
Lisa Spellman, dicom@dicomstandard.org
ChairsLawrence Tarbox, PhD, University of Arkansas for Medical Sciences
Gianluca Paladini, Siemens Healthineers
wg23chairs@dicomstandard.org
Last strategy update2019-04-05
MinutesWG-23 minutes

Scope:

  • To identify or develop the DICOM mechanisms to support AI workflows, concentrating on the clinical context.  This includes the interfaces between application software and the back end DICOM infrastructure.

Current Supplements, Work and Objectives:

  • Sup 219 JSON Representation of DICOM Structured Reports [WI 2019-04-A]
  • Several suggested new use scenarios for a mechanism like Application Hosting.
  • Strong desire to use more modern, simpler technology in Application Hosting, leveraging work done in DICOMweb.
  • Desire to better support AI workflows
  • Work item for creating examples using existing mechanisms for Application Hosting

Challenges and Opportunities (Environment):

  • Mechanisms that are appropriate for one regulatory body are inappropriate for another.
  • Ensuring that Application Hosting is of sufficient interest to the potential contributors to maintain active participation by experts, champions, vendors and clinical users.
  • Requests for future work items will be dependent on the active participation of vendors and clinicians that perceive a need to expand the DICOM Standard in a specific area.
  • Some items may require cooperation from other working groups, including WG-11 (Display), WG-17 (3D), WG-18 (Clinical Trials and Education), WG-20/HL7 IIWG, WG-27 (DICOMweb), all of the modality-specific working groups, and the HL-7 FHIR working group.
  • Work may require shifts in the scope of the working group.
  • Staying focused on the task at hand.
  • The mechanisms utilized could become obsolete or broken.
  • The technological landscape is constantly shifting, with various tools falling in and out of favor
  • The use cases are continually shifting
  • Regulatory issues may limit the clinical utility of the Standard.
  • Specifying mechanisms that are easily incorporated and do not conflict with work done by other bodies.
  • Potential Intellectual Property issues.

Future Roadmap and Objectives (Committee Direction):

  • The working group has been creating examples of using DICOM web services, including the web-based Unified Procedure Step (UPS) to trigger a web-based analytic service, providing a list of DICOM objects to be analyzed, and leveraging Instance Availability Notification as well as the IHE Invoke Image Display profile.
  • The working group is considering, based on use examples, how to represent analytic results in DICOM in a machine-consumable and interoperable format.
  • An existing work item to create an abstract model for structured reports was reconsidered, with the intent with retiring it in favor of a json representation of analytic results.
  • Continued monitoring of potential use cases. There is concern that current DICOM mechanisms might not be adequate to cover some use cases, particularly bulk analysis of large repository data, e.g. for training deep learning neural networks.
  • The WG expects to leverage existing standards, insofar as possible. The WG has closely cooperated with HL7 in the past, and expects to continue to monitor what is happening in that space (e.g. FHIR).
  • Further flesh out use cases/scenarios where applications of Artificial Intelligence are a primary focus.

Past Work

  • Supplement 118 FT 2009
  • Application Hosting was included in the IHE Post Processing Work Flow (PPWF) profile.