Difference between revisions of "QIBA Protocol/Profile Implementation Feedback Process"

From QIBA Wiki
Jump to navigation Jump to search
 
(96 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==<font color=red>Solicited Feedback during Field Tests of QIBA Documents</font>==
+
==<font color=red>Solicited Feedback during Implementation of QIBA Documents</font>==
 
This step collects feedback on use of the documents by users in the field, including clinical trialists, imaging scientists, pharma, CRO’s, etc.   
 
This step collects feedback on use of the documents by users in the field, including clinical trialists, imaging scientists, pharma, CRO’s, etc.   
  
Whereas the review and public comment steps prior to this focused on the document itself, this step now seeks feedback on how well it works in practice. As such, comments are solicited specifically from those that have used or are using it.
+
QIBA Technical Committees are interested in feedback on how well Protocols and Profiles work in practice. Therefore we solicit comments specifically from those that have used or are using them.
  
A procedure is outlined below listing what is done and by whom.
 
  
 +
'''A procedure is outlined below.'''
  
'''Period: 30 days'''
+
# Periodically, RSNA collects lists of people that may have used the document, and/or professional societies that may have a particular interest in the document. The goal is to include a full range of users of the document, e.g., vendors/suppliers, clinical trialists, imaging scientists, pharma, CRO's, etc.
 +
# RSNA sends an announcement to the relevant mailing lists, including a:
 +
#* Link to the document
 +
#* Link to the QIBA Protocol/Profile [[:Media:QIBA Document UserFeedbackForm-20SEPTEMBER2012.doc | User Feedback Form]].
 +
# Commenters email Implementation Feedback Form to ([mailto:jkoudelik@rsna.org Joe Koudelik]) at RSNA.
 +
# RSNA collates all comments into a spreadsheet for review by the Technical Committee.
 +
#* Technical Committee decides what changes to make (if any) to the document and records resolution in a spreadsheet.
 +
# Technical Committee votes on next step for the document, either:
 +
#* Refer the document to the Modality Committee for re-publication of an updated version
 +
#* Branch the document leaving the current version in place but spawning a derivative
 +
#* Place the document into inactive status
 +
#  All resolution will be documented and made available on the Wiki.
 +
 
 +
==<font color=red>Solicited Feedback during Field Test of QIBA Documents</font>==
 +
The purpose of this step is to actively seek feedback on use of published QIBA documents in a formally organized "Field Test."
 +
 
 +
 
 +
'''A procedure for Field Test feedback is outlined below.'''
  
# Collect from Field Test Leader a list of people who have participated in the field test.
+
# RSNA collects from Field Test Leader a list of people who participated in the field test.
# Technical Committee finalizes comment form (i.e.,standard form linked below, or modified standard form if necessary) that will be used in the survey.
+
# RSNA announces Call for Feedback to the list of people who participated in the field test. The announcement includes a:
# RSNA announces Call for Feedback to mailing lists, including:
+
#* Link to the document
#* Link to the document  
+
#* Link to the QIBA Protocol/Profile [[:Media:QIBA Document UserFeedbackForm-20SEPTEMBER2012.doc | User Feedback Form]]
#* Link to the QIBA Protocol/Profile Implementation [[:Media:QIBA_User_Feedback_Template-2011.01.doc | Feedback Form]] (Step #2 above).
+
# Field Test Leaders and/or Participants email completed User Feedback Form to ([mailto:jkoudelik@rsna.org Joe Koudelik]) at RSNA.
# Field Test Leader (Commenters) email completed Feedback Form to RSNA.
 
 
# RSNA collates all Feedback comments into a spreadsheet.
 
# RSNA collates all Feedback comments into a spreadsheet.
 
# Field Test Leader may additionally summarize feedback into a report.
 
# Field Test Leader may additionally summarize feedback into a report.
 
# Technical Committee reviews comments, making changes to the document as needed.
 
# Technical Committee reviews comments, making changes to the document as needed.
# Technical Committee records comment resolutions in spreadsheet.
+
# Technical Committee records comment resolution in spreadsheet.
 
# Technical Committee votes on next step for the document, either:
 
# Technical Committee votes on next step for the document, either:
 
#* Refer the document to the Modality Committee for Final Text publication
 
#* Refer the document to the Modality Committee for Final Text publication
Line 25: Line 41:
 
# RSNA posts comment spreadsheet and revised document to the Wiki.
 
# RSNA posts comment spreadsheet and revised document to the Wiki.
  
 +
==<font color=red>Current Protocol/Profile Documents:</font>==
  
==<font color=red>Solicited Feedback after Publication of QIBA Documents</font>==
+
'''<font color=red>Note to users - when referencing these QIBA Profile documents, please use the following format:</font>'''
The purpose of this process step is to actively seek and periodically respond to feedback on use of published QIBA documents.  It is important to put this into context with other activities that may seem similar at first. Whereas the review and public comment steps that are part of the Drafting phase focus on the document itself, prior to its use, and the Collect Feedback step as part of the Field Test phase collects feedback on the initial use of the document given that it has been placed into trial implementation, this step is where longer-term, extended use of the document allows for actual assessment of its performance in practice.  That is, over the course of time, clinical trials that had been designed with the QIBA document may close, and/or other results from field usage may become evident either with the user or supplier base.  Therefore, comments are solicited periodically for a wide range of the public that may connect with it in some way.
 
 
 
A procedure is outlined below listing what is done and by whom.
 
 
 
 
 
'''Period: 30 days'''
 
  
# Periodically, RSNA collects lists of people that may have used the document and/or professional societies that may have a particular relationship to the document.
+
''Specific QIBA Tech Ctte.'' * ''Specific Profile Title,'' * ''Quantitative Imaging Biomarkers Alliance.'' * ''Version.'' * ''Profile Stage.'' * ''QIBA,'' * ''Date.''
# Technical Committee finalizes comment form that will be used in the survey.
 
# RSNA sends announcement to mailing lists
 
#* Reminder copy of document that had been placed into field test
 
#* Provide a link to the QIBA User Feedback Form[[:Media:QIBA_Maintenance_Phase_Feedback_Template-2011.01.doc | QIBA User Feedback Form]]
 
# Commenters email comments to RSNA.
 
#* Include full range of users of the document, e.g., vendors/suppliers, clinical trialists, imaging scientists, pharma, CRO’s, etc.  However, only people who have used document are included.
 
#* Commenters are requested to use the provided comment form.
 
# RSNA collates all comments into a spreadsheet.
 
#* Summarize range of feedback to the questions into a report for review by the Technical Committee provided by the secretariat.
 
#* Technical Committee decides what changes to make (if any) to the document and whether to refer it to the Modality Committee for re-publication of an updated version, whether to branch the document leaving the current version in place but spawning a derivative, or to retire the document.
 
# Technical Committee records resolution in spreadsheet.
 
#* Regardless of recommended status for this document, ensure that the results are made available to related activities.
 
  
 +
<font color=red>Format example:</font>  DCE-MRI Technical Committee. DCE-MRI Quantification Profile, Quantitative Imaging Biomarkers Alliance. Version 1.0. Reviewed Draft. QIBA, July 1, 2012. Available from: [http://rsna.org/QIBA.aspx RSNA.ORG/QIBA]
  
==<font color=red>Protocol/Profile Implementation Feedback Process on the QIBA Wiki:</font>==
+
*[http://rsna.org/uploadedFiles/RSNA/Content/Science_and_Education/QIBA/DCE-MRI_Quantification_Profile_v1%200-ReviewedDraft%208-8-12.pdf QIBA Profile. DCE-MRI Quantification v1.0 Reviewed Draft (Publicly Reviewed Version)]
  
*[[Media:DCEMRI Quantification Profile v1.0-Implementation.pdf|Profile: <big><font color=red> DCE-MRI Quantification Version 1.0 </font></big>]]
+
*[http://rsna.org/uploadedFiles/RSNA/Content/Science_and_Education/QIBA/QIBA-CT%20Vol-TumorVolumeChangeProfile_v2.2_ReviewedDraft_08AUG2012.pdf QIBA Profile. CT Tumor Volume Change v2.2 Reviewed Draft (Publicly Reviewed Version)]
  
*[[Media:2011 07 28 Profile CT Advanced Disease V2 0f.pdf|Profile: <big><font color=red> QIBA Profile. Computed Tomography: Change Measurements in the Volumes of Solid Tumors </font></big>]]
+
*[http://www.rsna.org/uploadedFiles/RSNA/Content/Science_and_Education/QIBA/QIBA_FDG-PET_Profile_v105_Publicly_Reviewed_Version_FINAL_11Dec2013.pdf FDG-PET/CT as an Imaging Biomarker Measuring Response to Cancer Therapy (Publicly Reviewed Version)]
*[[Media:2011 07 28 QIBA Proffered UPICT Protocol-Vol Measurements in Solid Tumors.pdf|Protocol: <big><font color=red> QIBA UPICT CT Protocol: Change Measurements in the Volumes of Solid Tumors </font></big>]]
 

Latest revision as of 19:46, 2 April 2014

Solicited Feedback during Implementation of QIBA Documents

This step collects feedback on use of the documents by users in the field, including clinical trialists, imaging scientists, pharma, CRO’s, etc.

QIBA Technical Committees are interested in feedback on how well Protocols and Profiles work in practice. Therefore we solicit comments specifically from those that have used or are using them.


A procedure is outlined below.

  1. Periodically, RSNA collects lists of people that may have used the document, and/or professional societies that may have a particular interest in the document. The goal is to include a full range of users of the document, e.g., vendors/suppliers, clinical trialists, imaging scientists, pharma, CRO's, etc.
  2. RSNA sends an announcement to the relevant mailing lists, including a:
  3. Commenters email Implementation Feedback Form to (Joe Koudelik) at RSNA.
  4. RSNA collates all comments into a spreadsheet for review by the Technical Committee.
    • Technical Committee decides what changes to make (if any) to the document and records resolution in a spreadsheet.
  5. Technical Committee votes on next step for the document, either:
    • Refer the document to the Modality Committee for re-publication of an updated version
    • Branch the document leaving the current version in place but spawning a derivative
    • Place the document into inactive status
  6. All resolution will be documented and made available on the Wiki.

Solicited Feedback during Field Test of QIBA Documents

The purpose of this step is to actively seek feedback on use of published QIBA documents in a formally organized "Field Test."


A procedure for Field Test feedback is outlined below.

  1. RSNA collects from Field Test Leader a list of people who participated in the field test.
  2. RSNA announces Call for Feedback to the list of people who participated in the field test. The announcement includes a:
  3. Field Test Leaders and/or Participants email completed User Feedback Form to (Joe Koudelik) at RSNA.
  4. RSNA collates all Feedback comments into a spreadsheet.
  5. Field Test Leader may additionally summarize feedback into a report.
  6. Technical Committee reviews comments, making changes to the document as needed.
  7. Technical Committee records comment resolution in spreadsheet.
  8. Technical Committee votes on next step for the document, either:
    • Refer the document to the Modality Committee for Final Text publication
    • Conduct another round of field test on revised document
    • Place the document into inactive status
  9. RSNA posts comment spreadsheet and revised document to the Wiki.

Current Protocol/Profile Documents:

Note to users - when referencing these QIBA Profile documents, please use the following format:

Specific QIBA Tech Ctte. * Specific Profile Title, * Quantitative Imaging Biomarkers Alliance. * Version. * Profile Stage. * QIBA, * Date.

Format example: DCE-MRI Technical Committee. DCE-MRI Quantification Profile, Quantitative Imaging Biomarkers Alliance. Version 1.0. Reviewed Draft. QIBA, July 1, 2012. Available from: RSNA.ORG/QIBA