Difference between revisions of "Enhanced SOLE for AI"

From IHE Wiki
Jump to navigation Jump to search
Line 48: Line 48:
 
==5. Discussion==
 
==5. Discussion==
  
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
+
#This proposal is a result of an ad hoc committee formed within IHE/ACR to address “CP-458 SOLE: Add events to support AIR and AIW-I”.    #Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem.
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
+
#With many proprietary methods available today and W3C developing the common standard, the timing is good for IHE to converge on promoting a single industry-wide method that benefits community at large.
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
+
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.
:''<What are some of the risks or open issues to be addressed?>''
+
'''Risks, Open Issues'''
 
+
#What to do about non-http transports. (out-of-scope?)
 
 
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''
 
 
 
 
 
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]
 

Revision as of 11:24, 24 June 2022


1. Proposed Workitem: Enhanced SOLE for AI

  • Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: <Domain name Radiology

2. The Problem

Healthcare providers have a strong desire to increase throughput and efficiency, both to improve the quality and timeliness of care and to control costs which include:

  • Workflow restructuring/optimization (existing in SOLE)
  • Disaster support/readiness (existing in SOLE)
  • Performance tracking and bottleneck identification (extended)
  • Resource allocation for new machines, upgrades (new)
  • Software/Network Fault isolation/troubleshooting (new)


The SOLE profile currently lacks the capability to address the complexity introduced by AI and distributed cloud-native applications. This profile extends SOLE to address these gaps.

3. Key Use Case

A study is acquired. An Orchestrator/Task Manager invokes one or more applications. I need to know:

  • Right-size the resources for an AI Application
  • Allocate the resource allocation to optimize the algorithm performance
  • How much CPU, what kind of accelerator, memory, bandwidth storage
  • What is the uptime, latency, requests/algorithm utilization
  • How to troubleshoot a problem
  • Licensing deployment model assessment


'Should I pay for a machine running 24 hours or on-demand running?'

4. Standards and Systems

SOLE, Standardize Operational Logging of Events

/ IHE_RAD_Suppl_SOLE.pdf

W3C Trace Context

/ www.w3.org/TR/trace-context-1 (V1, status: recommendation)
/ w3c.github.io/trace-context (v2, status: draft)

5. Discussion

  1. This proposal is a result of an ad hoc committee formed within IHE/ACR to address “CP-458 SOLE: Add events to support AIR and AIW-I”. #Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem.
  2. With many proprietary methods available today and W3C developing the common standard, the timing is good for IHE to converge on promoting a single industry-wide method that benefits community at large.
  3. Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.

Risks, Open Issues

  1. What to do about non-http transports. (out-of-scope?)