http://wiki.ihe.net/api.php?action=feedcontributions&user=Lindop&feedformat=atomIHE Wiki - User contributions [en]2024-03-19T06:11:07ZUser contributionsMediaWiki 1.35.5http://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128849SOLE for ITI2022-09-02T16:39:32Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki<br />
:: ACR DSI Model API Standardization Effort<br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization Effort submitted the proposal [[Enhanced SOLE for AI]] with the goal to address the complexity introduced by AI and distributed, cloud-native applications.<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)<br />
* add the Context Tracing in this proposal<br />
<br />
* Does Radiology separate out a Radiology Option?</div>Lindophttp://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128848SOLE for ITI2022-09-02T15:22:03Z<p>Lindop: /* 1. Summary */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki<br />
:: ACR DSI Model API Standardization Effort<br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization Effort submitted the proposal [[Enhanced SOLE for AI]] with the goal to address the complexity introduced by AI and distributed, cloud-native applications.<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)</div>Lindophttp://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128847SOLE for ITI2022-09-02T15:18:25Z<p>Lindop: /* 1. Proposed Workitem: New Domain Host for SOLE: ITI */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki<br />
:: ACR DSI Model API Standardization Effort<br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization group submitted the proposal [[Enhanced SOLE for AI]].<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)</div>Lindophttp://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128846SOLE for ITI2022-09-02T15:17:32Z<p>Lindop: /* 1. Proposed Workitem: New Domain Host for SOLE: ITI */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki<br />
* ACR DSI Model API Standardization Effort<br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization group submitted the proposal [[Enhanced SOLE for AI]].<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)</div>Lindophttp://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128845SOLE for ITI2022-09-02T15:16:13Z<p>Lindop: /* 1. Proposed Workitem: New Domain Host for SOLE: ITI */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki<br />
*<br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization group submitted the proposal [[Enhanced SOLE for AI]].<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)</div>Lindophttp://wiki.ihe.net/index.php?title=SOLE_for_ITI&diff=128844SOLE for ITI2022-09-02T15:15:07Z<p>Lindop: Created page with "__NOTOC__ ==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''== * Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki ==1. Summary== SOLE was p..."</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''New Domain Host for SOLE: ITI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
<br />
==1. Summary==<br />
<br />
SOLE was profiled by IHE Radiology for trial implementation as part of the [https://wiki.ihe.net/index.php/Radiology_2016-2017_Development_Cycle Radiology 2016-2017 Development Cycle]. <br />
For the Radiology 2022-2023 Development Cycle, the ACR DSI Model API Standardization group submitted the proposal [[Enhanced SOLE for AI]].<br />
<br />
==3. Use Cases beyond Imaging==<br />
<br />
While the SOLE use case development focused on Imaging workflow and performance analytics, SOLE is useful throughout the healthcare enterprise as these references suggest: <br />
<br />
* Departmental Healthcare Event and Activity Logging: [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6175513/}<br />
* Business process mining and analytics: https://www.researchgate.net/publication/344176824_Event_Log_Generation_in_a_Health_System_A_Case_Study<br />
<br />
* Data logging to support closed loop healthcare<br />
:* [https://mdpnp.org/MD_PnP_Program_DataLogger.html https://mdpnp.org/MD_PnP_Program_DataLogger.html]<br />
:* [https://smartamerica.org/teams/closed-loop-healthcare/ https://smartamerica.org/teams/closed-loop-healthcare/]<br />
<br />
*Service-oriented Device Point-of-Care Interoperability (PCD whitepaper)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_Rev1-1_Pub_2019-11-01.pdf] (section 8.5)<br />
:* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_WP_SDPi_UseCases_Rev1-1_Pub_2019-11-01.pdf] (see UC.186 and UC.190)<br />
:* [https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf https://www.stahq.org/files/2813/9171/8106/60_Abstract_Goldman.pdf]<br />
: Note: PCD uses the term “logging” for capturing parameters from devices via HL7 observations<br />
<br />
<br />
== Discussion Notes==<br />
* need powerful filtering<br />
* attributes such as ‘purpose of use’ can aid with event differentiation (Security, Operational Workflow, System Performance)</div>Lindophttp://wiki.ihe.net/index.php?title=Radiology_Proposals_2022-2023&diff=128843Radiology Proposals 2022-20232022-09-02T13:27:00Z<p>Lindop: /* Short List/ Detailed Proposals */</p>
<hr />
<div>{{TOCright}}<br />
<br />
===Final Selection===<br />
Final selection by the '''[[Rad_Plan_Minutes_2022-09-26|Planning Committee on Sept 26, 2022]]''' <br />
:* A. Maintenance (25%)<br />
<br />
===Effort Evaluations===<br />
The Technical Committee [[Proposal Effort Evaluation|evaluated the required effort]] of the Detailed Proposals as follows in tcons on [[Rad_Tech_Minutes_2022-08-29 | Aug 29]], [[Rad_Tech_Minutes_2022-08-31 | Aug 31]], & [[Rad_Tech_Minutes_2022-09-01 | Sept 1]].<br />
<br />
Assessments were captured in the new spreadsheet form. <br />
<br />
:* A. [[RAD TF Maintenance 2022-2023]]<br />
<br />
See [[Proposal Effort Evaluation#TC Review & Effort Estimation]] for evaluation guidance.<br />
<br />
===Short List/ Detailed Proposals===<br />
The Tech Cmte agreed to evaluate TBD number of proposals. The following Proposals were shortlisted by the [[Rad Plan Minutes 2022-08-10| Planning Committee on Aug 10, 2022]].<br />
<br />
:* A. Maintenance<br />
:* B. [[Realtime Bidirectional Communication for Interactive Multimedia Reporting - Detailed]]<br />
:* C. [[Reporting Worklist Prioritization - Proposal]]<br />
:* D. [https://docs.google.com/document/d/1DeFr0oB6ZA-SBAk2BSgZ_mjNtydQwULh/edit?usp=sharing&ouid=102612276002431976750&rtpof=true&sd=true Management of Sensitive Images (MOSI)] - Withdrawn<br />
:* E. [[Imaging Diagnostic Report - Proposal]]<br />
<br />
[[SOLE for ITI]]<br />
<br />
<br />
'''Editors''': by COB '''Aug 24''', 2022<br />
* '''Complete the Breakdown of Tasks''' with a strawman estimate of story points:<br />
:* [https://docs.google.com/spreadsheets/d/1IoRwFz1xxORCwYIJat-Yn2trfkhiT5OKbU8toEpKb5k/edit?usp=sharing BoD & Estimation - Google Sheet (Tab for each proposal)]<br />
* '''Expand your Brief Proposal''' to include Detailed Proposal elements<br />
:* Copy the [[Delta Proposal Template]] into the bottom of your proposal page<br />
:* Update as described in the Delta Template (adds Summary, Technical Details, Evaluation, etc.)<br />
:* Breakdown of Tasks is now covered in the Google Sheet (above)<br />
* Your goal is to give sufficient detail for the Tech Cmte to be able to evaluate the technical feasibility, specification tasks and effort required.<br />
<br />
'''Reviewers''': Feel free to enter comments under Risks and Decisions/Topics/Uncertainties section of the proposal<br />
<br />
Tech Cmte evaluations will be recorded at the bottom of each detailed proposal. The "Breakdown of Tasks" and "Story Point" refinements to the '''[[Proposal Effort Evaluation]]''' are in the Google Sheet.<br />
<br />
===Brief Proposals===<br />
:* A. Maintenance<br />
:* B. [[Enhanced SOLE for AI]]<br />
:* C. [[SWF on FHIR]]<br />
:* D. [[Realtime Bidirectional Communication]]<br />
:* E. [https://docs.google.com/document/d/1DeFr0oB6ZA-SBAk2BSgZ_mjNtydQwULh/edit?usp=sharing&ouid=102612276002431976750&rtpof=true&sd=true Management of Sensitive Images (MOSI)] <br />
:* F. [[Reporting Worklist Prioritization - Proposal]]<br />
:* G. [[Imaging Diagnostic Report - Proposal]]<br />
<br />
Submission DEADLINE is '''August 5''', 2022, 11:59pm CT<br />
<br />
===Call for Proposals===<br />
Interested parties are invited to submit proposal pages based on the '''[[Brief Proposal Template]]'''.<br />
<br />
You are also welcome to update and resubmit proposals from '''[[Radiology Proposals 2021-2022|last year]]''' or earlier.<br />
<br />
Contact radiology@ihe.net with any questions.<br />
<br />
===Committee Links===<br />
<br />
[[Radiology Planning Committee]]<br />
<br />
[[Radiology Technical Committee]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128729Enhanced SOLE for AI2022-08-12T16:33:57Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==1. Summary==<br />
<br />
Applications, in particular AI Algorithms, are increasingly moving to distributed architectures. Right-sizing the resources for these applications is vital to provide cost-effective offerings. In the presence of system failures, it is also essential to understand the root cause. However, we currently lack the ability to effectively log, in a unified fashion, actions and interactions between these distributed architectures, significantly impeding our ability to understand their behaviors<br />
<br />
Standardized Operational Logging of Events (SOLE) offers an existing framework for logging events related to patients, equipment, staff, and facilities. When logging events communicated by computer systems though, this standard currently lacks a mechanism to link related events (i.e.,tracing).<br />
<br />
The W3C Trace Context provides a standard for identifying and communicating such interactions. This proposed extension to SOLE will include W3C Context Trace elements in SOLE messages to improve our understanding of the relationships <br />
<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#With many proprietary methods available today and W3C developing the common standard, it is appropriate for IHE to converge on a single, industry-wide method that benefits community at large.<br />
#This approach will leverage the existing actors/transactions in SOLE with enhancements that address the AI workflow and use cases outlined above.<br />
'''Risks and Open Issues'''<br />
#What to do about traced transactions using protocols that W3C has not specified (e.g. DICOM DIMSE, HL7 v2)? (out-of-scope?)<br />
<br />
==6. Technical Approach==<br />
Describe the new use case elaborating on the W3C approach and what this means for patient workflows in a hospital:<br />
* Early traces allow for greater understanding of the patient experience but if any system doesn’t carry the trace id forward the link is broken and the connection can no longer be made<br />
* Administrators may be more concerned with unifying traces in their department, in computer workflows (e.g., algorithm inference), etc in which case the initial trace id should be set later<br />
* Regardless, any system should adhere to the rule of carrying forward any valid trace id and setting a new one if one is not set<br />
For example, what this means for the patient experience how the new fields are used.<br />
<br />
<This section describes the technical scope of the work and the proposed approach to solve the problems in the Use Cases. The Technical Committee will be responsible for the full design and may choose to take a different approach, but a sample design is a good indication of feasibility. The Technical Committee may revise/expand this section when doing the effort estimation.><br />
<If any context or "big picture" is needed to understand the transaction, actor and profile discussion below, that can be put here><br />
<If a phased approach would make sense indicate some logical phases. This may be because standards are evolving, because the problem is too big to solve at once, or because there are unknowns that won’t be resolved soon.><br />
<The material below also serves as the breakdown of tasks that the technical committee will use to estimate the effort required to design, review and implement the profile. It helps a lot if it is reasonably complete/realistic.><br />
<br />
<READ PROPOSER HOMEWORK IN Proposal Effort Evaluation FOR GUIDANCE ON POPULATING THE FOLLOWING SECTIONS ><br />
<br />
'''Actors'''<br />
*(NEW) No New Actors<br />
* <List existing actors that may be given requirements in the Profile.><br />
'''Transactions'''<br />
* (NEW) No New Transactions.<br />
* <List existing transactions that may be used and which might need modification/extension.><br />
* Adding new fields to the Event Object mapped from the W3C Trace Context fields.<br />
<br />
'''Profile'''<br />
* <Describe the main new profile chunks that will need to be written.><br />
* <List existing profiles that may need to be modified.><br />
'''Decisions/Topics/Uncertainties'''<br />
* <List key decisions that will need to be made, open issues, design problems, topics to discuss, and other potential areas of uncertainty><br />
* <Credibility point: A proposal for a profile with any degree of novelty should have items listed here. If there is nothing here, it is usually a sign that the proposal analysis and discussion has been incomplete.><br />
==6. Support & Resources==<br />
<List groups that have expressed support for the proposal and resources that would be available to accomplish the tasks listed above.><br />
<Identify anyone who has indicated an interest in implementing/prototyping the Profile if it is published this cycle.><br />
==7. Risks==<br />
<List real-world practical or political risks that could impede successfully fielding the profile.><br />
<Technical risks should be noted above under Uncertainties.><br />
==8. Tech Cmte Evaluation==<br />
<The technical committee will use this area to record details of the effort estimation, etc.><br />
Effort Evaluation (as a % of Tech Cmte Bandwidth):<br />
* xx% for MUE<br />
* yy% for MUE + optional<br />
Editor:<br />
TBA<br />
SME/Champion:<br />
TBA <typically with a technical editor, the Subject Matter Expert will bring clinical expertise; in the (unusual) case of a clinical editor, the SME will bring technical expertise></div>Lindophttp://wiki.ihe.net/index.php?title=SWF_on_FHIR&diff=128663SWF on FHIR2022-08-03T15:13:20Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
==1. Proposed Workitem: SWF on FHIR==<br />
<br />
* '''Proposal Editor:''' Chris Lindop, Jonathan Whitby<br />
* '''Editor:''' ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* '''Domain:''' Radiology <br />
<br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
FHIR is the emerging clinical information standard that industry has adopted world-wide. Scheduled Workflow is the most widely adopted IHE profile throughout the world. However, it provides no guidance on implementing FHIR. HL7 provides minimal guidance with regards to implementing FHIR for Imaging. <br />
<br />
This leaves vendors and users to develop their own implementations for deploying FHIR-based imaging workflows. The result is apparent. Each deployed site will be unique. Vendors will need to adopt and implement a unique configuration for every clinical site's deployed environment.<br />
==3. Key Use Case==<br />
The key use cases are documented in the IHE Radiology Technical Framework Volume 1 Section 3.3 Scheduled Workflow Process flow. ''No changes are proposed.''<br />
<br />
For this workitem, the proposed scope is to be limited. The patient Management transactions will be ignored. Primary focus should be on Orders Management and The FHIR resource ServiceRequest and Procedure. DICOM messaging will not be addressed with the exception of mapping of DICOM to FHIR.<br />
<br />
==4. Standards and Systems==<br />
'''Relevant Systems'''<br />
<br />
:Relevant systems are the same as those systems implementing Scheduled workflow. ''No change is proposed to the existing relevant systems.''<br />
<br />
'''Relevant Standards'''<br />
* IHE Scheduled Workflow<br />
* HL7 FHIR <br />
* DICOM<br />
==5. Discussion==<br />
A comprehensive inclusion of FHIR with the existing SWF is a major effort. This level of effort should not inhibit IHE Radiology from starting this project. This project proposal scope needs to limited to a focused component of the overall transformation to a FHIR-based workflow. The initial proposed scope is to focus on the Imaging Orders to FHIR Data Model.<br />
<br />
This project needs to leverage and collaborate with existing profiling work that is either in progress or completed by other IHE domains and HL7. <br />
<br />
HL7 Orders and Observations currently has an IG in progress for v2 to FHIR mapping which includes a General Order Message. This work can be leveraged and can help O&O with usage of the implementation guide.<br />
<br />
The joint DICOM WG20/HL7 Imaging Integration Working group has a workitem to address gaps with the HL7 v2/FHIR mapping relevant to imaging. <br />
<br />
IHE PCC has a profile QEDm which utilized FHIR for query of existing Data. While the profile does have an option for procedures, it is missing an option for ServiceRequests. This project could utilize the Procedures option to be refined for imaging and add a Query for Imaging ServiceRequests.<br />
<br />
An initial draft of the Imaging Orders mapping to FHIR is in the HL7 Confluence page [https://confluence.hl7.org/display/IMIN/FHIR+ServiceRequest+Mapping+to+Imaging+Order "FHIR ServiceRequest Mapping to Imaging Order"]<br />
<br />
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile. IHE has the most expertise on this subject. <br />
<br />
Realizing that this is an extensive and most significant update requested of SWF, the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions. This will ensure backward compatibility and support of mixed environments. <br />
<br />
No new Actors are proposed. The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.<br />
<br />
For transactions, propose to leverage existing QEDm transactions with refinements to imaging.</div>Lindophttp://wiki.ihe.net/index.php?title=SWF_on_FHIR&diff=128661SWF on FHIR2022-08-02T16:08:39Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
==1. Proposed Workitem: SWF on FHIR==<br />
<br />
* '''Proposal Editor:''' Chris Lindop, Jonathan Whitby<br />
* '''Editor:''' ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* '''Domain:''' Radiology <br />
<br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
FHIR is the emerging clinical information standard that industry has adopted world-wide. Scheduled Workflow is the most widely adopted IHE profile throughout the world. However, it provides no guidance on implementing FHIR. HL7 provides minimal guidance with regards to implementing FHIR for Imaging. <br />
<br />
This leaves vendors and users to develop their own implementations for deploying FHIR-based imaging workflows. The result is apparent. Each deployed site will be unique. Vendors will need to adopt and implement a unique configuration for every clinical site's deployed environment.<br />
==3. Key Use Case==<br />
The key use cases are documented in the IHE Radiology Technical Framework Volume 1 Section 3.3 Scheduled Workflow Process flow. ''No changes are proposed.''<br />
==4. Standards and Systems==<br />
'''Relevant Systems'''<br />
<br />
:Relevant systems are the same as those systems implementing Scheduled workflow. ''No change is proposed to the existing relevant systems.''<br />
<br />
'''Relevant Standards'''<br />
* IHE Scheduled Workflow<br />
* HL7 FHIR <br />
* DICOM<br />
==5. Discussion==<br />
A comprehensive inclusion of FHIR with the existing SWF is a major effort. This level of effort should not inhibit IHE Radiology from starting this project. This project proposal scope needs to limited to a focused component of the overall transformation to a FHIR-based workflow. The initial proposed scope is to focus on the Imaging Orders to FHIR Data Model.<br />
<br />
This project needs to leverage and collaborate with existing profiling work that is either in progress or completed by other IHE domains and HL7. <br />
<br />
HL7 Orders and Observations currently has an IG in progress for v2 to FHIR mapping which includes a General Order Message. This work can be leveraged and can help O&O with usage of the implementation guide.<br />
<br />
The joint DICOM WG20/HL7 Imaging Integration Working group has a workitem to address gaps with the HL7 v2/FHIR mapping relevant to imaging. <br />
<br />
IHE PCC has a profile QEDm which utilized FHIR for query of existing Data. While the profile does have an option for procedures, it is missing an option for ServiceRequests. This project could utilize the Procedures option to be refined for imaging and add a Query for Imaging ServiceRequests.<br />
<br />
An initial draft of the Imaging Orders mapping to FHIR is in the HL7 Confluence page [https://confluence.hl7.org/display/IMIN/FHIR+ServiceRequest+Mapping+to+Imaging+Order "FHIR ServiceRequest Mapping to Imaging Order"]<br />
<br />
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile. IHE has the most expertise on this subject. <br />
<br />
Realizing that this is an extensive and most significant update requested of SWF, the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions. This will ensure backward compatibility and support of mixed environments. <br />
<br />
No new Actors are proposed. The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.<br />
<br />
For transactions, propose to leverage existing QEDm transactions with refinements to imaging.</div>Lindophttp://wiki.ihe.net/index.php?title=SWF_on_FHIR&diff=128582SWF on FHIR2022-07-14T15:11:14Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
==1. Proposed Workitem: SWF on FHIR==<br />
<br />
* '''Proposal Editor:''' Chris Lindop, Jonathan Whitby<br />
* '''Editor:''' ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* '''Domain:''' Radiology <br />
<br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
FHIR is the emerging clinical information standard that industry has adopted world-wide. Scheduled Workflow is the most widely adopted IHE profile throughout the world. However, it provides no guidance on implementing FHIR. HL7 provides minimal guidance with regards to implementing FHIR for Imaging. <br />
<br />
This leaves vendors and users to develop their own implementations for deploying FHIR-based imaging workflows. The result is apparent. Each deployed site will be unique. Vendors will need to adopt and implement a unique configuration for every clinical site's deployed environment.<br />
==3. Key Use Case==<br />
The key use cases are documented in the IHE Radiology Technical Framework Volume 1 Section 3.3 Scheduled Workflow Process flow. ''No changes are proposed.''<br />
==4. Standards and Systems==<br />
'''Relevant Systems'''<br />
<br />
:Relevant systems are the same as those systems implementing Scheduled workflow. ''No change is proposed to the existing relevant systems.''<br />
<br />
'''Relevant Standards'''<br />
* IHE Scheduled Workflow<br />
* HL7 FHIR <br />
==5. Discussion==<br />
Currently, the joint HL7/DICOM Imaging Integration Working group is planning to address gaps with the HL7 v2/FHIR mapping relevant to imaging. This will be key input.<br />
<br />
The RSNA IAIP demonstration is currently defining FHIR resources relative to SWF that will be accessed during the demonstration. <br />
<br />
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile. IHE has the most expertise on this subject. <br />
<br />
Realizing that this is an extensive and most significant update requested of SWF, the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions. This will ensure backward compatibility and support of mixed environments. <br />
<br />
No new Transactions or Actors are proposed. The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.<br />
:'''Proposed FHIR Resources:''' ImagingStudy, ServiceRequest, Procedure, Patient, Visit</div>Lindophttp://wiki.ihe.net/index.php?title=SWF_on_FHIR&diff=128581SWF on FHIR2022-07-14T14:57:14Z<p>Lindop: Created page with "__NOTOC__ ==1. Proposed Workitem: SWF on FHIR== * '''Proposal Editor:''' Chris Lindop, Jonathan Whitby * '''Editor:''' ''<Name of candidate Lead Editor for the Profile, if kn..."</p>
<hr />
<div>__NOTOC__<br />
==1. Proposed Workitem: SWF on FHIR==<br />
<br />
* '''Proposal Editor:''' Chris Lindop, Jonathan Whitby<br />
* '''Editor:''' ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* '''Domain:''' Radiology <br />
<br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
FHIR is the emerging clinical information standard that industry has adopted world-wide. Scheduled Workflow is the most widely adopted IHE profile throughout the world. However, it provides no guidance on implementing FHIR. HL7 provides minimal guidance with regards to implementing FHIR for Imaging. This leaves vendors and users to develop their own implementations for deploying FHIR-based imaging workflows. The result is apparent. Each deployed site is unique. Vendors will need to implement a unique configuration for every clinical site's deployed environment.<br />
<br />
==3. Key Use Case==<br />
The key use cases are documented in the IHE Radiology Technical Framework Volume 1 Section 3.3 Scheduled Workflow Process flow. No change is proposed.<br />
==4. Standards and Systems==<br />
'''Relevant Systems'''<br />
Relevant systems are the same as those systems implementing Scheduled workflow. No change is proposed.<br />
'''Relevant Standards'''<br />
* IHE Scheduled Workflow<br />
* HL7 FHIR <br />
<br />
==5. Discussion==<br />
<br />
Currently, the joint HL7/DICOM Imaging Integration Working group is planning to address gaps with the HL7 v2/FHIR mapping relevant to imaging. This will be key input.<br />
<br />
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile. IHE has the most expertise on this subject. <br />
<br />
Realizing that this is an extensive and most significant update requested of SWF, the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions. This will ensure backward compatibility and support of mixed environments. <br />
<br />
No new Transactions or Actors are proposed. The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.<br />
:'''Proposed Resources for SWF''' ImagingStudy, ServiceRequest, Procedure, Patient, Visit</div>Lindophttp://wiki.ihe.net/index.php?title=Radiology_Proposals_2022-2023&diff=128576Radiology Proposals 2022-20232022-07-13T14:51:21Z<p>Lindop: </p>
<hr />
<div>{{TOCright}}<br />
<br />
===Final Selection===<br />
Final selection by the '''[[Rad_Plan_Minutes_2022-09-26|Planning Committee on Sept 26, 2022]]''' <br />
:* A. Maintenance (25%)<br />
<br />
===Effort Evaluations===<br />
The Technical Committee [[Proposal Effort Evaluation|evaluated the required effort]] of the Detailed Proposals as follows in tcons on [[Rad_Tech_Minutes_2022-08-29 | Aug 29]], [[Rad_Tech_Minutes_2022-08-31 | Aug 31]], & [[Rad_Tech_Minutes_2022-09-01 | Sept 1]].<br />
<br />
Assessments were captured in the new spreadsheet form. <br />
<br />
:* A. [[RAD TF Maintenance 2022-2023]]<br />
<br />
See [[Proposal Effort Evaluation#TC Review & Effort Estimation]] for evaluation guidance.<br />
<br />
===Short List/ Detailed Proposals===<br />
The Tech Cmte agreed to evaluate TBD number of proposals. The following Proposals were shortlisted by the [[Rad Plan Minutes 2022-08-10| Planning Committee on Aug 10, 2022]].<br />
<br />
:* A. Maintenance<br />
<br />
'''Editors''': by COB '''Aug 24''', 2022<br />
* '''Complete the Breakdown of Tasks''' with a strawman estimate of story points:<br />
:* [https://docs.google.com/spreadsheets/d/18wETLZhLYcXq5pOMfAhH8-Q4M5cKztj6QNUEOAcOnng/edit#gid=1166925166 BoD & Estimation - Google Sheet (Tab for each proposal)]<br />
* '''Expand your Brief Proposal''' to include Detailed Proposal elements<br />
:* Copy the [[Delta Proposal Template]] into the bottom of your proposal page<br />
:* Update as described in the Delta Template (adds Summary, Technical Details, Evaluation, etc.)<br />
:* Breakdown of Tasks is now covered in the Google Sheet (above)<br />
* Your goal is to give sufficient detail for the Tech Cmte to be able to evaluate the technical feasibility, specification tasks and effort required.<br />
<br />
'''Reviewers''': Feel free to enter comments under Risks and Decisions/Topics/Uncertainties section of the proposal<br />
<br />
Tech Cmte evaluations will be recorded at the bottom of each detailed proposal. The "Breakdown of Tasks" and "Story Point" refinements to the '''[[Proposal Effort Evaluation]]''' are in the Google Sheet.<br />
<br />
===Brief Proposals===<br />
:* A. Maintenance<br />
:* B. [[Enhanced SOLE for AI]]<br />
:* C. [[SWF on FHIR]]<br />
<br />
Submission DEADLINE is '''August 5''', 2022, 11:59pm CT<br />
<br />
===Call for Proposals===<br />
Interested parties are invited to submit proposal pages based on the '''[[Brief Proposal Template]]'''.<br />
<br />
You are also welcome to update and resubmit proposals from '''[[Radiology Proposals 2021-2022|last year]]''' or earlier.<br />
<br />
Contact radiology@ihe.net with any questions.<br />
<br />
===Committee Links===<br />
<br />
[[Radiology Planning Committee]]<br />
<br />
[[Radiology Technical Committee]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128479Enhanced SOLE for AI2022-07-01T17:13:14Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#With many proprietary methods available today and W3C developing the common standard, it is appropriate for IHE to converge on a single, industry-wide method that benefits community at large.<br />
#This approach will leverage the existing actors/transactions in SOLE with enhancements that address the AI workflow and use cases outlined above.<br />
'''Risks and Open Issues'''<br />
#What to do about traced transactions using protocols that W3C has not specified (e.g. DICOM DIMSE, HL7 v2)? (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128478Enhanced SOLE for AI2022-07-01T17:10:14Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#With many proprietary methods available today and W3C developing the common standard, it is appropriate for IHE to converge on a single, industry-wide method that benefits community at large.<br />
#This approach will leverage the existing actors/transactions in SOLE with enhancements that address the AI workflow and use cases outlined above.<br />
'''Risks and Open Issues'''<br />
#What to do about traced transactions using protocols that W3C has not specified (e.g. DICOM DIMSE, HL7 v2)? (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128477Enhanced SOLE for AI2022-07-01T17:09:48Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#With many proprietary methods available today and W3C developing the common standard, it is appropriate for IHE to converge on a single, industry-wide method that benefits community at large.<br />
#This approach will leverage the existing actors/transactions in SOLE with enhancements that address the AI workflow and use cases outlined above.<br />
'''Risks and Open Issues'''<br />
#What to do about traced transactions using protocols that W3C has not specified (e.g. DICOM DIMSE, HL7 v2)? (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128476Enhanced SOLE for AI2022-07-01T16:46:59Z<p>Lindop: /* 5. Discussion */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#With many proprietary methods available today and W3C developing the common standard, it is appropriate for IHE to converge on a single, industry-wide method that benefits community at large.<br />
#This approach will leverage the existing actors/transactions in SOLE with enhancements that address the AI workflow and use cases outlined above.<br />
'''Risks and Open Issues'''<br />
#What to do about traced transactions using protocols that W3C has not specified (e.g. DICOM DIMSE, HL7 v2)? (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128475Enhanced SOLE for AI2022-07-01T16:33:47Z<p>Lindop: /* 5. Discussion */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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”. <br />
#Detailed proposed changes were initially discussed as part of the IHE Maintenance and to be included in this workitem. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128474Enhanced SOLE for AI2022-07-01T16:29:19Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resources to optimize the algorithm performance<br />
*Decide how much CPU, accelerator capacity, memory, bandwidth, and storage are needed<br />
*Determine the current uptime, response latency, request volume, and algorithm utilization <br />
*Troubleshoot a problem<br />
*Assess model licensing<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128473Enhanced SOLE for AI2022-07-01T16:24:22Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring and optimization ''('''existing''' in SOLE)''<br />
* Disaster support and readiness ''('''existing''' in SOLE)''<br />
* Resource utilization and bottleneck identification ''('''extended''')''<br />
* Resource allocation for algorithms and workflows ''('''new''')''<br />
* Fault identification and troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128472Enhanced SOLE for AI2022-07-01T16:13:19Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Clinical workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128466Enhanced SOLE for AI2022-06-24T17:49:16Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ Enhanced SOLE for AI Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128465Enhanced SOLE for AI2022-06-24T17:48:29Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing/ / Enhanced SOLE for IA Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128464Enhanced SOLE for AI2022-06-24T17:47:30Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing / Enhanced SOLE for IA Power Point presentation]<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128463Enhanced SOLE for AI2022-06-24T17:46:46Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing \ Enhanced SOLE for IA Power Point presentation}<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128462Enhanced SOLE for AI2022-06-24T17:46:19Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing / Enhanced SOLE for IA Power Point presentation}<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128461Enhanced SOLE for AI2022-06-24T17:45:38Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
<br />
[https://drive.google.com/drive/folders/11JOH1OgMcSKC9dxrlw5I3YZb2TqcEGO-?usp=sharing \ Enhanced SOLE for IA Power Point presentation}<br />
<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128460Enhanced SOLE for AI2022-06-24T17:24:05Z<p>Lindop: /* 5. Discussion */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
#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. <br />
#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.<br />
#Technical Approach is to include the existing actors/transactions in SOLE with enhancements that address the AI workflow and used case outlined earlier.<br />
'''Risks, Open Issues'''<br />
#What to do about non-http transports. (out-of-scope?)</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128459Enhanced SOLE for AI2022-06-24T17:18:08Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1 / www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context / w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128458Enhanced SOLE for AI2022-06-24T17:17:07Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf / IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1/ www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context/ w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128457Enhanced SOLE for AI2022-06-24T17:16:12Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf/IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1/www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context/w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128456Enhanced SOLE for AI2022-06-24T17:13:46Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
SOLE, Standardize Operational Logging of Events<br />
:[https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_SOLE.pdf]<br />
<br />
W3C Trace Context <br />
:[https://www.w3.org/TR/trace-context-1] (V1, status: recommendation)<br />
<br />
:[https://w3c.github.io/trace-context] (v2, status: draft)<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128455Enhanced SOLE for AI2022-06-24T17:11:07Z<p>Lindop: /* 1. Proposed Workitem: */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''Enhanced SOLE for AI''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128454Enhanced SOLE for AI2022-06-24T17:10:14Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128453Enhanced SOLE for AI2022-06-24T17:09:52Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''('''existing''' in SOLE)''<br />
* Disaster support/readiness ''('''existing''' in SOLE)''<br />
* Performance tracking and bottleneck identification ''('''extended''')''<br />
* Resource allocation for new machines, upgrades ''('''new''')''<br />
* Software/Network Fault isolation/troubleshooting ''('''new''')''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128452Enhanced SOLE for AI2022-06-24T17:07:59Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''(existing in SOLE)''<br />
* Disaster support/readiness ''(existing in SOLE)''<br />
* Performance tracking and bottleneck identification ''(extended)''<br />
* Resource allocation for new machines, upgrades ''(new)''<br />
* Software/Network Fault isolation/troubleshooting ''(new)''<br />
<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128451Enhanced SOLE for AI2022-06-24T17:07:35Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization ''(existing in SOLE)''<br />
* Disaster support/readiness ''(existing in SOLE)''<br />
* Performance tracking and bottleneck identification ''(extended)''<br />
* Resource allocation for new machines, upgrades ''(new)''<br />
* Software/Network Fault isolation/troubleshooting ''(new)''<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">'''''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.'''''</div><br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Enhanced_SOLE_for_AI&diff=128450Enhanced SOLE for AI2022-06-24T17:03:59Z<p>Lindop: Created page with "__NOTOC__ ==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''== * Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki * Edito..."</p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: Chris Lindop, Neil Tenenholtz, Rob Horn, Brian Bialecki <br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''<Domain name Radiology <br />
[[Category:RAD]]<br />
<br />
==2. The Problem==<br />
<br />
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:<br />
* Workflow restructuring/optimization (existing in SOLE)<br />
* Disaster support/readiness (existing in SOLE)<br />
* Performance tracking and bottleneck identification (extended)<br />
* Resource allocation for new machines, upgrades (new)<br />
* Software/Network Fault isolation/troubleshooting (new)<br />
<br />
'''''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.'''''<br />
<br />
==3. Key Use Case==<br />
<br />
A study is acquired. An Orchestrator/Task Manager invokes one or more applications.<br />
I need to know:<br />
*Right-size the resources for an AI Application<br />
*Allocate the resource allocation to optimize the algorithm performance<br />
*How much CPU, what kind of accelerator, memory, bandwidth storage <br />
*What is the uptime, latency, requests/algorithm utilization<br />
*How to troubleshoot a problem<br />
*Licensing deployment model assessment<br />
<br />
<div class="center" style="width: auto; margin-left: auto; margin-right: auto;">''''Should I pay for a machine running 24 hours or on-demand running?''''</div><br />
<br />
<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=Radiology_Proposals_2022-2023&diff=128449Radiology Proposals 2022-20232022-06-24T16:40:25Z<p>Lindop: </p>
<hr />
<div>{{TOCright}}<br />
<br />
===Final Selection===<br />
Final selection by the '''[[Rad_Plan_Minutes_2022-09-26|Planning Committee on Sept 26, 2022]]''' <br />
:* A. Maintenance (25%)<br />
<br />
===Effort Evaluations===<br />
The Technical Committee [[Proposal Effort Evaluation|evaluated the required effort]] of the Detailed Proposals as follows in tcons on [[Rad_Tech_Minutes_2022-08-29 | Aug 29]], [[Rad_Tech_Minutes_2022-08-31 | Aug 31]], & [[Rad_Tech_Minutes_2022-09-01 | Sept 1]].<br />
<br />
Assessments were captured in the new spreadsheet form. <br />
<br />
:* A. [[RAD TF Maintenance 2022-2023]]<br />
<br />
See [[Proposal Effort Evaluation#TC Review & Effort Estimation]] for evaluation guidance.<br />
<br />
===Short List/ Detailed Proposals===<br />
The Tech Cmte agreed to evaluate TBD number of proposals. The following Proposals were shortlisted by the [[Rad Plan Minutes 2022-08-10| Planning Committee on Aug 10, 2022]].<br />
<br />
:* A. Maintenance<br />
<br />
'''Editors''': by COB '''Aug 24''', 2022<br />
* '''Complete the Breakdown of Tasks''' with a strawman estimate of story points:<br />
:* [https://docs.google.com/spreadsheets/d/18wETLZhLYcXq5pOMfAhH8-Q4M5cKztj6QNUEOAcOnng/edit#gid=1166925166 BoD & Estimation - Google Sheet (Tab for each proposal)]<br />
* '''Expand your Brief Proposal''' to include Detailed Proposal elements<br />
:* Copy the [[Delta Proposal Template]] into the bottom of your proposal page<br />
:* Update as described in the Delta Template (adds Summary, Technical Details, Evaluation, etc.)<br />
:* Breakdown of Tasks is now covered in the Google Sheet (above)<br />
* Your goal is to give sufficient detail for the Tech Cmte to be able to evaluate the technical feasibility, specification tasks and effort required.<br />
<br />
'''Reviewers''': Feel free to enter comments under Risks and Decisions/Topics/Uncertainties section of the proposal<br />
<br />
Tech Cmte evaluations will be recorded at the bottom of each detailed proposal. The "Breakdown of Tasks" and "Story Point" refinements to the '''[[Proposal Effort Evaluation]]''' are in the Google Sheet.<br />
<br />
===Brief Proposals===<br />
:* A. Maintenance<br />
:* B. [[Enhanced SOLE for AI]]<br />
<br />
Submission DEADLINE is '''August 5''', 2022, 11:59pm CT<br />
<br />
===Call for Proposals===<br />
Interested parties are invited to submit proposal pages based on the '''[[Brief Proposal Template]]'''.<br />
<br />
You are also welcome to update and resubmit proposals from '''[[Radiology Proposals 2021-2022|last year]]''' or earlier.<br />
<br />
Contact radiology@ihe.net with any questions.<br />
<br />
===Committee Links===<br />
<br />
[[Radiology Planning Committee]]<br />
<br />
[[Radiology Technical Committee]]</div>Lindophttp://wiki.ihe.net/index.php?title=Radiology_Proposals_2022-2023&diff=128448Radiology Proposals 2022-20232022-06-24T16:33:28Z<p>Lindop: /* Brief Proposals */</p>
<hr />
<div>{{TOCright}}<br />
<br />
===Final Selection===<br />
Final selection by the '''[[Rad_Plan_Minutes_2022-09-26|Planning Committee on Sept 26, 2022]]''' <br />
:* A. Maintenance (25%)<br />
<br />
===Effort Evaluations===<br />
The Technical Committee [[Proposal Effort Evaluation|evaluated the required effort]] of the Detailed Proposals as follows in tcons on [[Rad_Tech_Minutes_2022-08-29 | Aug 29]], [[Rad_Tech_Minutes_2022-08-31 | Aug 31]], & [[Rad_Tech_Minutes_2022-09-01 | Sept 1]].<br />
<br />
Assessments were captured in the new spreadsheet form. <br />
<br />
:* A. [[RAD TF Maintenance 2022-2023]]<br />
<br />
See [[Proposal Effort Evaluation#TC Review & Effort Estimation]] for evaluation guidance.<br />
<br />
===Short List/ Detailed Proposals===<br />
The Tech Cmte agreed to evaluate TBD number of proposals. The following Proposals were shortlisted by the [[Rad Plan Minutes 2022-08-10| Planning Committee on Aug 10, 2022]].<br />
<br />
:* A. Maintenance<br />
<br />
'''Editors''': by COB '''Aug 24''', 2022<br />
* '''Complete the Breakdown of Tasks''' with a strawman estimate of story points:<br />
:* [https://docs.google.com/spreadsheets/d/18wETLZhLYcXq5pOMfAhH8-Q4M5cKztj6QNUEOAcOnng/edit#gid=1166925166 BoD & Estimation - Google Sheet (Tab for each proposal)]<br />
* '''Expand your Brief Proposal''' to include Detailed Proposal elements<br />
:* Copy the [[Delta Proposal Template]] into the bottom of your proposal page<br />
:* Update as described in the Delta Template (adds Summary, Technical Details, Evaluation, etc.)<br />
:* Breakdown of Tasks is now covered in the Google Sheet (above)<br />
* Your goal is to give sufficient detail for the Tech Cmte to be able to evaluate the technical feasibility, specification tasks and effort required.<br />
<br />
'''Reviewers''': Feel free to enter comments under Risks and Decisions/Topics/Uncertainties section of the proposal<br />
<br />
Tech Cmte evaluations will be recorded at the bottom of each detailed proposal. The "Breakdown of Tasks" and "Story Point" refinements to the '''[[Proposal Effort Evaluation]]''' are in the Google Sheet.<br />
<br />
===Brief Proposals===<br />
:* A. Maintenance<br />
:* B. Enhanced SOLE for AI<br />
<br />
Submission DEADLINE is '''August 5''', 2022, 11:59pm CT<br />
<br />
===Call for Proposals===<br />
Interested parties are invited to submit proposal pages based on the '''[[Brief Proposal Template]]'''.<br />
<br />
You are also welcome to update and resubmit proposals from '''[[Radiology Proposals 2021-2022|last year]]''' or earlier.<br />
<br />
Contact radiology@ihe.net with any questions.<br />
<br />
===Committee Links===<br />
<br />
[[Radiology Planning Committee]]<br />
<br />
[[Radiology Technical Committee]]</div>Lindophttp://wiki.ihe.net/index.php?title=Simple_Image_and_Numeric_Report&diff=126017Simple Image and Numeric Report2021-09-07T12:08:31Z<p>Lindop: /* Specification */</p>
<hr />
<div>'''Simple Image and Numeric Report (SINR)''' specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.<br />
<br />
__TOC__<br />
<br />
==Summary==<br />
<br />
Simple Image and Numeric Report (SINR) specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.<br />
<br />
<br />
<br />
[[Image:SINR_diag_1.png]]<br />
<br />
==Benefits==<br />
<br />
The key benefits of Simple Image Numeric Report profile are as follows:<br />
<br />
* DICOM SR, enables maximum interoperability in Imaging Departments<br />
* Export to Clinical Data Repositories with HL-7 V.2 defined mapping<br />
* Non-transcription based information capture systems support, including; <br />
:* Numerical measurements from image processing applications<br />
:* Links to images stored in the image repository<br />
:* machine searchable structured content<br />
:* Integrated with the Reporting Workflow<br />
:* Adaptable to CDA and XML interfacing<br />
<br />
==Details==<br />
<br />
The Simple Image and Numeric Report (SINR) Integration Profile facilitates the creation, management, distribution, storage, and viewing of reports created in imaging facilities. <br />
<br />
<br />
The content structure uses the DICOM Structured Report for a simple imaging report. The content structure is simple: a title, an observation context, and one or more sections, each with a heading, observation context, text, image references, and optionally coded measurements. The Report complexity is extensible, limited only to the constraints of DICOM.<br />
<br />
<br />
In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report. The created report is submitted for management, distribution and storage by departmental information system. <br />
<br />
<br />
Once the initial report is submitted, the reports are processed until the report is final. This may involve adding and changing report data as well as verifying the draft reports. Previous draft versions are maintained. Once final, the report may be amended with updates.<br />
<br />
<br />
Permanent storage of the reports is maintained through the use of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by known DICOM queries. <br />
<br />
<br />
Viewing reports internal and external to the department requires a DICOM Structured Report-capable viewer. <br />
<br />
<br />
The Integration Profile allows for the flexibility of distributing the report external to the department at any time. But at a minimum, the final report will be made available for distribution. The report may be distributed outside the department by an HL7 format. The DICOM Structured Report may be queried and retrieved by an any DICOM SR-capable system.<br />
<br />
==Systems Affected==<br />
Systems which are expected to have implemented actors from this profile include:<br />
:* Digital Dictation Systems, with the ability to create and modify reports<br />
:* Voice Recognition Systems, with the ability to create and modify reports<br />
:* specialized reporting packages, with the ability to create and modify reports<br />
:* Enterprise-wide information systems that manage the Electronic Medical Record for recieving reports <br />
:* Radiology departmental information systems that manage Radiology Reports (i.e., radiology information system (RIS)) <br />
:* Radiology image & Report management/archiving systems that manage Radiology Reports (i.e., picture archiving and communication system (PACS)) <br />
<br />
'''Actors & Transactions:'''<br />
<br />
[[Image:SINR.PNG]]<br />
<br />
==Specification==<br />
<br />
'''Profile Status:''' [[Comments| Final Text]] <br />
<br />
'''Documents:''' <br />
<br />
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]<br />
:* [http://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol1.pdf Vol. 1] - Section 6 documents the profile<br />
:* [https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol2.pdf Vol. 2] - Sections 4.24 to 4.28 document specific transactions<br />
<br />
'''Underlying Standards:'''<br />
:* [http://dicom.nema.org DICOM]<br />
:* [http://www.hl7.org HL7]<br />
<br />
==See Also==<br />
<br />
'''Related Profiles'''<br />
<br />
* [[Reporting Workflow]] [RWF] uses Simple Image & Numeric Reports as inputs to the reporting process.<br />
<br />
* [[Patient Information Reconciliation]] [PIR] is expected to reconcile Simple Image & Numeric Reports along with the rest of the patient data record.<br />
<br />
* [[Evidence Documents]] [ED] may be used as inputs for Simple Image and Numeric Reports.<br />
<br />
* [[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Simple Image & Numeric Reports between sites over a network.<br />
<br />
* [[Portable Data for Imaging]] [PDI] can store Simple Image & Numeric Reports on media such as CDs.<br />
<br />
* [[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Simple Image & Numeric Reports when importing.<br />
<br />
<br />
[[Category:Profiles]]<br />
[[Category:RAD Profile]]<br />
[[Category:DICOM]]<br />
[[Category:HL7v2]]<br />
[[Category:CDA]]</div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125859SWF.b Assisted Protocol Option Extension2021-08-13T21:44:47Z<p>Lindop: </p>
<hr />
<div>__NOTOC__<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
An imaging service request is typically created by and EMR and transferred as an imaging order to a Radiology Department Information System.<br />
<br />
The order received by the Radiology Information System (EMR), initiates two tasks, Scheduling and Protocolling. These tasks happen independently. In this use case, these tasks are performed on two separate systems, a RIS performing the scheduling and a Protocol Management System performing the protocoling.<br />
<br />
When the Order is received by the Protocol Management System, the order is associated with a number of radiology-specific procedures that have to be performed to satisfy the order. Each procedure prescribes a number of actions that are to be performed by Acquisition Modalities. Actions are grouped into procedure steps.<br />
<br />
A Radiologist determines the procedure assignment and will recommend the protocols to be performed by the acquisition modalities to fill the order. This includes the acquisition protocol which identifies the settings and conditions to be used by the technologist to perform the acquisition. The Radiologist reviews the patient’s medical history, typically hosted on an EMR, to assist in this assignment. This task is performed on a Protocol Management System.<br />
<br />
A Department Scheduler will assign the time slots and performing resource (modality) for the procedure steps. The procedure steps includes the protocol assignments by the Radiologist.<br />
<br />
==4. Standards and Systems==<br />
<br />
'''Systems'''<br />
<br />
:# Protocol Management System<br />
:# Electronic Medical Record Order Management System<br />
:# Radiology Information System<br />
:# Protocol Management System<br />
:# Acquisition Modality<br />
'''Standards'''<br />
:# DICOM<br />
:# HL7 v2<br />
:# HL7 FHIR<br />
:# IHE Scheduled Workflow, Assisted Protocol Option<br />
:# IHE Management of Acquisition Protocols<br />
<br />
==5. Discussion==<br />
<br />
This proposal is to bridge two existing IHE profiles, IHE SWF.b, Assisted Protocol Option with the IHE MAP. The Protocol Manager defined in MAP will require the Order created in SWF.b by the Order Placer. This is an existing transaction [RAD-2]. The protocol assigned by the protocol Manager needs to be communicated to the Order Filler in SWF.b. This transaction is not defined in IHE. RSNA is demonstrating this capability at the RSNA 2021 IAIP demonstration and could serve as a model on how this can be achieved.<br />
<br />
The Protocol Manager may need to know what protocol is performed by the Modality. This feedback is provided by the existing Modality in the MPPS transaction. A Protocol Manager could receive the MPPS directly from the Modality. While access to the Patient’s medical record is important to the protocoling, IHE IT has defined several profiles which should be considered as a cross profile consideration.<br />
<br />
The Protocol Management system will require access to the list of local procedures for the department. This need can be supported by IHE ITI Shared Value Set profile as a cross profile consideration. <br />
<br />
[[File:RIS-writeback graphic.jpg]]</div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125858SWF.b Assisted Protocol Option Extension2021-08-13T21:42:15Z<p>Lindop: /* 5. Discussion */</p>
<hr />
<div>__NOTOC__<br />
<br />
<br />
''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''<br />
<br />
<br />
''<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>''<br />
<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
An imaging service request is typically created by and EMR and transferred as an imaging order to a Radiology Department Information System.<br />
<br />
The order received by the Radiology Information System (EMR), initiates two tasks, Scheduling and Protocolling. These tasks happen independently. In this use case, these tasks are performed on two separate systems, a RIS performing the scheduling and a Protocol Management System performing the protocoling.<br />
<br />
When the Order is received by the Protocol Management System, the order is associated with a number of radiology-specific procedures that have to be performed to satisfy the order. Each procedure prescribes a number of actions that are to be performed by Acquisition Modalities. Actions are grouped into procedure steps.<br />
<br />
A Radiologist determines the procedure assignment and will recommend the protocols to be performed by the acquisition modalities to fill the order. This includes the acquisition protocol which identifies the settings and conditions to be used by the technologist to perform the acquisition. The Radiologist reviews the patient’s medical history, typically hosted on an EMR, to assist in this assignment. This task is performed on a Protocol Management System.<br />
<br />
A Department Scheduler will assign the time slots and performing resource (modality) for the procedure steps. The procedure steps includes the protocol assignments by the Radiologist.<br />
<br />
==4. Standards and Systems==<br />
<br />
'''Systems'''<br />
<br />
:# Protocol Management System<br />
:# Electronic Medical Record Order Management System<br />
:# Radiology Information System<br />
:# Protocol Management System<br />
:# Acquisition Modality<br />
'''Standards'''<br />
:# DICOM<br />
:# HL7 v2<br />
:# HL7 FHIR<br />
:# IHE Scheduled Workflow, Assisted Protocol Option<br />
:# IHE Management of Acquisition Protocols<br />
<br />
==5. Discussion==<br />
<br />
This proposal is to bridge two existing IHE profiles, IHE SWF.b, Assisted Protocol Option with the IHE MAP. The Protocol Manager defined in MAP will require the Order created in SWF.b by the Order Placer. This is an existing transaction [RAD-2]. The protocol assigned by the protocol Manager needs to be communicated to the Order Filler in SWF.b. This transaction is not defined in IHE. RSNA is demonstrating this capability at the RSNA 2021 IAIP demonstration and could serve as a model on how this can be achieved.<br />
<br />
The Protocol Manager may need to know what protocol is performed by the Modality. This feedback is provided by the existing Modality in the MPPS transaction. A Protocol Manager could receive the MPPS directly from the Modality. While access to the Patient’s medical record is important to the protocoling, IHE IT has defined several profiles which should be considered as a cross profile consideration.<br />
<br />
The Protocol Management system will require access to the list of local procedures for the department. This need can be supported by IHE ITI Shared Value Set profile as a cross profile consideration. <br />
<br />
[[File:RIS-writeback graphic.jpg]]</div>Lindophttp://wiki.ihe.net/index.php?title=File:RIS-writeback_graphic.jpg&diff=125857File:RIS-writeback graphic.jpg2021-08-13T21:41:08Z<p>Lindop: </p>
<hr />
<div></div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125856SWF.b Assisted Protocol Option Extension2021-08-13T21:36:58Z<p>Lindop: /* 5. Discussion */</p>
<hr />
<div>__NOTOC__<br />
<br />
<br />
''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''<br />
<br />
<br />
''<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>''<br />
<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
An imaging service request is typically created by and EMR and transferred as an imaging order to a Radiology Department Information System.<br />
<br />
The order received by the Radiology Information System (EMR), initiates two tasks, Scheduling and Protocolling. These tasks happen independently. In this use case, these tasks are performed on two separate systems, a RIS performing the scheduling and a Protocol Management System performing the protocoling.<br />
<br />
When the Order is received by the Protocol Management System, the order is associated with a number of radiology-specific procedures that have to be performed to satisfy the order. Each procedure prescribes a number of actions that are to be performed by Acquisition Modalities. Actions are grouped into procedure steps.<br />
<br />
A Radiologist determines the procedure assignment and will recommend the protocols to be performed by the acquisition modalities to fill the order. This includes the acquisition protocol which identifies the settings and conditions to be used by the technologist to perform the acquisition. The Radiologist reviews the patient’s medical history, typically hosted on an EMR, to assist in this assignment. This task is performed on a Protocol Management System.<br />
<br />
A Department Scheduler will assign the time slots and performing resource (modality) for the procedure steps. The procedure steps includes the protocol assignments by the Radiologist.<br />
<br />
==4. Standards and Systems==<br />
<br />
'''Systems'''<br />
<br />
:# Protocol Management System<br />
:# Electronic Medical Record Order Management System<br />
:# Radiology Information System<br />
:# Protocol Management System<br />
:# Acquisition Modality<br />
'''Standards'''<br />
:# DICOM<br />
:# HL7 v2<br />
:# HL7 FHIR<br />
:# IHE Scheduled Workflow, Assisted Protocol Option<br />
:# IHE Management of Acquisition Protocols<br />
<br />
==5. Discussion==<br />
<br />
This proposal is to bridge two existing IHE profiles, IHE SWF.b, Assisted Protocol Option with the IHE MAP. The Protocol Manager defined in MAP will require the Order created in SWF.b by the Order Placer. This is an existing transaction [RAD-2]. The protocol assigned by the protocol Manager needs to be communicated to the Order Filler in SWF.b. This transaction is not defined in IHE. RSNA is demonstrating this capability at the RSNA 2021 IAIP demonstration and could serve as a model on how this can be achieved.<br />
<br />
The Protocol Manager may need to know what protocol is performed by the Modality. This feedback is provided by the existing Modality in the MPPS transaction. A Protocol Manager could receive the MPPS directly from the Modality. While access to the Patient’s medical record is important to the protocoling, IHE IT has defined several profiles which should be considered as a cross profile consideration.<br />
<br />
The Protocol Management system will require access to the list of local procedures for the department. This need can be supported by IHE ITI Shared Value Set profile as a cross profile consideration. <br />
<br />
[[File:Diagram 1.jpg]]</div>Lindophttp://wiki.ihe.net/index.php?title=File:Diagram_1.jpg&diff=125855File:Diagram 1.jpg2021-08-13T21:35:22Z<p>Lindop: Lindop uploaded a new version of File:Diagram 1.jpg</p>
<hr />
<div></div>Lindophttp://wiki.ihe.net/index.php?title=File:Diagram_1.jpg&diff=125854File:Diagram 1.jpg2021-08-13T21:15:07Z<p>Lindop: </p>
<hr />
<div></div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125853SWF.b Assisted Protocol Option Extension2021-08-13T21:11:27Z<p>Lindop: /* 4. Standards and Systems */</p>
<hr />
<div>__NOTOC__<br />
<br />
<br />
''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''<br />
<br />
<br />
''<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>''<br />
<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
An imaging service request is typically created by and EMR and transferred as an imaging order to a Radiology Department Information System.<br />
<br />
The order received by the Radiology Information System (EMR), initiates two tasks, Scheduling and Protocolling. These tasks happen independently. In this use case, these tasks are performed on two separate systems, a RIS performing the scheduling and a Protocol Management System performing the protocoling.<br />
<br />
When the Order is received by the Protocol Management System, the order is associated with a number of radiology-specific procedures that have to be performed to satisfy the order. Each procedure prescribes a number of actions that are to be performed by Acquisition Modalities. Actions are grouped into procedure steps.<br />
<br />
A Radiologist determines the procedure assignment and will recommend the protocols to be performed by the acquisition modalities to fill the order. This includes the acquisition protocol which identifies the settings and conditions to be used by the technologist to perform the acquisition. The Radiologist reviews the patient’s medical history, typically hosted on an EMR, to assist in this assignment. This task is performed on a Protocol Management System.<br />
<br />
A Department Scheduler will assign the time slots and performing resource (modality) for the procedure steps. The procedure steps includes the protocol assignments by the Radiologist.<br />
<br />
==4. Standards and Systems==<br />
<br />
'''Systems'''<br />
<br />
:# Protocol Management System<br />
:# Electronic Medical Record Order Management System<br />
:# Radiology Information System<br />
:# Protocol Management System<br />
:# Acquisition Modality<br />
'''Standards'''<br />
:# DICOM<br />
:# HL7 v2<br />
:# HL7 FHIR<br />
:# IHE Scheduled Workflow, Assisted Protocol Option<br />
:# IHE Management of Acquisition Protocols<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125852SWF.b Assisted Protocol Option Extension2021-08-13T21:07:50Z<p>Lindop: /* 3. Key Use Case */</p>
<hr />
<div>__NOTOC__<br />
<br />
<br />
''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''<br />
<br />
<br />
''<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>''<br />
<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
An imaging service request is typically created by and EMR and transferred as an imaging order to a Radiology Department Information System.<br />
<br />
The order received by the Radiology Information System (EMR), initiates two tasks, Scheduling and Protocolling. These tasks happen independently. In this use case, these tasks are performed on two separate systems, a RIS performing the scheduling and a Protocol Management System performing the protocoling.<br />
<br />
When the Order is received by the Protocol Management System, the order is associated with a number of radiology-specific procedures that have to be performed to satisfy the order. Each procedure prescribes a number of actions that are to be performed by Acquisition Modalities. Actions are grouped into procedure steps.<br />
<br />
A Radiologist determines the procedure assignment and will recommend the protocols to be performed by the acquisition modalities to fill the order. This includes the acquisition protocol which identifies the settings and conditions to be used by the technologist to perform the acquisition. The Radiologist reviews the patient’s medical history, typically hosted on an EMR, to assist in this assignment. This task is performed on a Protocol Management System.<br />
<br />
A Department Scheduler will assign the time slots and performing resource (modality) for the procedure steps. The procedure steps includes the protocol assignments by the Radiologist.<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindophttp://wiki.ihe.net/index.php?title=SWF.b_Assisted_Protocol_Option_Extension&diff=125851SWF.b Assisted Protocol Option Extension2021-08-13T21:06:45Z<p>Lindop: /* 2. The Problem */</p>
<hr />
<div>__NOTOC__<br />
<br />
<br />
''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''<br />
<br />
<br />
''<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>''<br />
<br />
<br />
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==<br />
<br />
* Proposal Editor: ''Chris Lindop''<br />
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>'' <br />
* Date: N/A (Wiki keeps history)<br />
* Version: N/A (Wiki keeps history)<br />
* Domain: ''Radiology'' <br />
<br />
[[Category:RAD]]<br />
<br />
<br />
==2. The Problem==<br />
<br />
<br />
IHE has defined two profiles regarding how acquisition protocoling is performed and managed. They are Management of Acquisition Protocols and Scheduled Workflow, Assisted Protocol Option. IHE has not defined how these profiles interact.<br />
<br />
Management of Acquisition Protocols defines actors, and a centralized process for managing Protocols across modalities, and the SWF.b Assisted Protocol Option provides for the capability to communicate to the acquisition modality, the recommended protocols for the acquisition.<br />
<br />
There is a natural grouping of Protocol Management and Protocol Prescription functionalities within the Protocol Manager Actor. Such systems are being developed as standalone systems apart from the traditional Radiology Information System. The RIS typically incorporates this Protocol Prescription capability along with resource (Modality) scheduling, however, the RIS may lack equipment specific knowledge to assign the correct protocol based on the manufacturer and model of the scheduled resource. These new systems include the incorporation of EMR clinical data (such as patient history and allergies) and AI algorithms, to improve the efficiencies of radiologists in prescribing acquisition protocols necessary to fulfill an order. <br />
<br />
This proposal is to address how a Protocol Management System communicates to a Radiology Information System the prescription of the acquisition protocols that are known by the performing modality to be scheduled.<br />
<br />
==3. Key Use Case==<br />
<br />
''<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>''<br />
<br />
''<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>''<br />
<br />
<br />
==4. Standards and Systems==<br />
<br />
''<List existing systems that are/could be involved in the problem/solution.>''<br />
<br />
''<If known, list standards which might be relevant to the solution>''<br />
<br />
==5. Discussion==<br />
<br />
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''<br />
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''<br />
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''<br />
:''<What are some of the risks or open issues to be addressed?>''<br />
<br />
<br />
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''<br />
<br />
<br />
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]</div>Lindop