FDG-PETCT Technical Committee Subcommittees Progress to Date (summary version) Software Version Tracking – Ling Shao Team: Ling Shao, Mike Casey, Steve.

Slides:



Advertisements
Similar presentations
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Post-Processing Workflow Sanjay Jain Co-Chair, Radiology Planning.
Advertisements

IHE Radiology Integration Profiles: ▪ Post-Processing Workflow ▪ Reporting Workflow IHE Educational Workshop – June 11-13, 2007 Nikolaus Wirsz, PhD Manager.
UPDATE ON GROCERSMART 4.0 RESEARCH PLAN Regional Technical Forum May 3, 2011.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
1 Physics Testing for Performance Based Protocol version 3.0 (Now based on ACRIN 6678) QIBA Group 1C.
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
QIBA FDG-PET ROI subgroup Goals Determine current basic ROI capabilities common to all (or large subset of commercial workstations) –Prepare survey –Make.
SE 555 Software Requirements & Specification Requirements Management.
Software Configuration Management (SCM)
Adjusting EPLC to your Project Colleen Robinson & Teresa Kinley Friday, February 6, 2009.
Configuration Management
MICS Survey Design Workshop Multiple Indicator Cluster Surveys Survey Design Workshop Overview of MICS Tools, Templates, Resources, Technical Assistance.
Configuration Management Supplement 67 Robert Horn, Agfa Healthcare.
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Feb , 2005IHE Europe Workshop 1 Integrating the Healthcare Enterprise – Radiology – Established IHE Integration Profiles: Dr. Nikolaus Wirsz –Siemens.
Project Proposal: Academic Job Market and Application Tracker Website Project designed by: Cengiz Gunay Client: Cengiz Gunay Audience: PhD candidates and.
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
FDG-PET/CT Technical Committee
Managing Projects using Oracle Project Management (PJT) & SPREADSHEETS Neeraj Garg Vice President, Client Services.
Software Configuration Management
Travel Website Enhancement Project Project Update First Name Last Name.
1 Technical & Business Writing (ENG-315) Muhammad Bilal Bashir UIIT, Rawalpindi.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
May 19-20, Quantitation, both single point and longitudinal*, of tumor metabolism via FDG-PET/CT that can be used practically and efficiently as.
Overview of recent ORNL progress in restraint free laboratory animal imaging Bethesda May 20, 2005.
Project Status Report Presenter Name Presentation Date.
1 NUOPC National Unified Operational Prediction Capability 1 Review Committee for Operational Processing Centers National Unified Operational Prediction.
Update: Grocery Refrigeration Provisional Standard Protocol for Site Specific Savings RTF Meeting June 28,
Software Quality Assurance
I Power Higher Computing Software Development The Software Development Process.
APEC-TEL Broadband Study TEL03/2009A – status report Bangkok, May 20 th.
Scanner Validation via the SNM Clinical Trials Network Phantom Program Paul E. Christian Molecular Imaging Program Huntsman Cancer Institute University.
Integration Issues for RTF Guidelines: Savings, Lifetimes and Cost/Benefit October 24, 2012 Regional Technical Forum Presented by: Michael Baker, SBW.
Develop Project Charter
Implementation Strategy July 2002 STANDARDS DEVELOPMENT LIFECYCLE PROCESS ORP Publishes & Maintains 8 Standing Committee Recommends Approval / Disapproval.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
FDG-PET/CT Technical Committee Purpose: to foster adoption of practical [I deleted cost-effective because I do not see us doing any cost-effective analyses.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
IHE Update IT Infrastructure, Radiology, Laboratory and Cardiology IHE Update to December 2003 DICOM Committee Charles Parisot, GE Medical Systems Information.
Network design Topic 6 Testing and documentation.
Digital Reference Object Subcommittee Goals 1.Build a common reference DICOM test object (digital reference object or DRO) that can be generated by each.
EMI INFSO-RI Guidelines and SQA Process Maria Alandes Pradillo (CERN) SA2.2 Task Leader.
IHE Workshop – June 2006What IHE Delivers 1 Todd Kantchev, Siemens Molecular Imaging Jerold Wallis, Mallinckrodt Institute of Radiology Kevin O’Donnell,
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Software Configuration Management SEII-Lecture 21
| imodules.com Bringing It All Together – Planning for Success with iModules Presented by Jennifer McGee, Engagement Manager.
1 Physics Testing for Performance Based Protocol version 2.1 QIBA Group 1C.
November 29, 2007 TAC Meeting Texas Nodal Program Update Jerry Sullivan, Executive Director.
2014 CalCom Activity Plan based on last year’s work and open discussion: Periodic meetings with detector groups to discuss algorithms, discuss software.
Protocol Revision Subcommittee Report to ERCOT Technical Advisory Committee September 4, 2003.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
QIBA DCE-MRI Analysis Algorithm Validation Specification and Testing Daniel Barboriak M.D. Duke University Medical Center
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Standard Design Process Overview
Introduction to CMIS, an Electronic Design Change Process Presented by: Mark Gillis (FirstEnergy) and Brad Diggans (Rolls-Royce)
WONIX: Training and Scanner Harmonization
Software Configuration Management
School of Business Administration
2011 Prioritization Update to Market Subcommittees
Implementation Strategy July 2002
Physics Testing for ACRIN 6678 Protocol version 3.0 QIBA Group 1C
WONIX: Training and Scanner Harmonization
Change Assurance Dashboard
FDG-PET/CT Technical Committee
Digital Reference Object Subcommittee
PSS verification and validation
FDG-PET/CT Technical Committee
Presentation transcript:

FDG-PETCT Technical Committee Subcommittees Progress to Date (summary version) Software Version Tracking – Ling Shao Team: Ling Shao, Mike Casey, Steve Kohlmyer 1.Objective: To track the traceability of SW version of a PET/CT system to ensure the consistency of quantitative output through out the trial Rational: Due to the continuous improvements of current PET/CT systems, vendors will upgrade software in different part of sub-systems from time to time for the same system. Some of upgrades will include quantitation improvements Essential SW Version to be tracked: Three major SW in the quantitative imaging chain should be tracked: Acquisition (include detector), Reconstruction (may combined with acquisition) and Quantitation Tool Approach: Short team: Manual Tracking (available now) Long Term (TBD): 5-8 Years: Fully DICOM Tracking (New DICOM attributes needed); 8 Years Beyond: One-button SW Tracking Function (Industry guideline - vendors to do it) Note: * Some sites use third party Display/Quantitative Tools, which further complicate the tracking

FDG-PETCT Technical Committee Software Version Tracking 1.Short term: Manual Tracking Status: Currently, every vendor should have the ability of obtaining the version info each software installed. Action: Send out a survey to vendors for instructions to check the SW version (Acquisition, Reconstruction, Quantitative Tool. Some vendors provide multiple reconstruction methods) 2.Fully DICOM Tracking (5-8 Years) - TBD Status: Currently only the attribute for acquisition SW version may exist Action: Work with other committees to define a global recommended list of DICOM attributes needed for quantitation purpose Working with DICOM committee to define the timeline for implementing the list 3.One-button SW Tracking Function (8 Year beyond) -TBD Status: Currently, vendors provide tools to view all/most DICOM Info, but, most info which impact quantitation are missing (No DICOM Attributes): The goal is for vendors to provide a one-button function in the quantitative tool to display all quantitative related info. Action: I.Define what are the quantitative info to be recorded (DICOM) II.Develop guidelines (working with NEMA ??) III.Compliance Steps

FDG-PETCT Technical Committee Software Version Tracking 2.Current status Subcommittee formed Draft of Survey circulated in Subcommittee 3.Specific tasks planned Subcommittee meeting scheduled for reviewing survey Send survey to vendor for info Subcommittee Review 4.Resources needed TBD

Appendix

Discussion points SW Version Tracking Specifics 1.Scanner to be surveyed Every scanner in the market for the last 5 years 2.Who knows these information best Application specialist/Customer support engineer 3.For workstation side, only the display tool which is used for SUV calculation or for quantitation needs to be tracked 4.Third party display tool: Does this belong to this subcommittee? Other issues that the QIBA need to consider 1.Should we define a standard phantom (known structure) – Used to align the protocols from different vendors by adjusting different recon parameters to matching the same/close image quality Repeat QI phantom (Quantitative criteria) every time there is change to the scanner Site physicist task or vendors task IEC NEMA could be a good 2.Record Recon Method and parameters used (MLEM, OSEM, FBP, iteration, filtering, etc) 3.What about Count-rate dependence on quantitation (SUV)? 4.List all new DICOM attributes request Discussion for the next week Review the survey Clarify the requirements for Stage II and Stage III SW version control requirement List the DICOM attributes required for SW version tracking

Draft of Survey (updated 3/9/09) Vendor Name: (Create one survey for every scanner in the market for the last 5 years Scanner Name: SW Type Step-by-Step instruction for obtaining version NumberVersion Number New Phantom Calibration Required (Y/N)Comments Acquisition SW ( In DICOM Header)1. XXXXX Y/N 2. XXXXX 3. XXX Reconstruction SW (Not in DICOM)1. XXX 2. XXX 3. XXX Display/Quantitation tool: Workstation Name :____________ SW Package Name :____________ (Not in DICOM, May be third parity SW)1. XXX 2. XXX 3. XXX

Draft of Survey Vendor Name: Scanner Name SW Type Step-by-Step instruction for obtaining version Number Version Number Repeat QI phantom (Quantitative criteria) –site physicist task, Vendor do the test (IEC NEMA is good) Comments Count-rate dependence Recon Method (iteration, filtering, - standard for future Acquisition SW1. XXX 2. XXX 3. XXX Reconstruction SW1. XXX 2. XXX 3. XXX Display/Quantitation tool (non-DICOM)1. XXX 2. XXX 3. XXX