Difference between revisions of "Public Comment Process"

From QIBA Wiki
Jump to navigation Jump to search
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Public Comment is intended to allow both regular participants in QIBA Activities and also those who don't have the time to dedicate to regular participation a chance to contribute their thoughts on proposed specifications before they are formally released.  It's also an excellent chance to engage relevant stakeholder individuals and organizations. Comments are accepted from all.
 
Public Comment is intended to allow both regular participants in QIBA Activities and also those who don't have the time to dedicate to regular participation a chance to contribute their thoughts on proposed specifications before they are formally released.  It's also an excellent chance to engage relevant stakeholder individuals and organizations. Comments are accepted from all.
  
Public comment should be considered the prelude to publicationA committee should be largely satisfied with the contents of a document before it is sent out for Public Comment.
+
NOTE: ''If you receive few or no public comments, that's a'' '''bad sign.'''  Presuming we didn't hit perfection on the first try, it means we didn't convince people it was important enough to read in any great detailThat bodes poorly for our ability to convince people it is important enough to read and conform to.  Good outreach is a significant part of Public Comment.  It's our first stage at marketing the Profile.
  
Note in the description below that the "secretariat" is understood to be the RSNA.  Specific tasks may be assigned to staff and/or contractors of RSNA in performance of the function.
 
  
 
Period: 30 days (may be longer at the discretion of the committee)
 
Period: 30 days (may be longer at the discretion of the committee)
  
* [[Review Process|Approve for public comment]] ('''Biomarker & Modality Committees''')
+
* ''Biomarker Committee'' '''[[Review Process|reviews and approves for public comment]]'''
* Tidy up PC draft (e.g. "accept all changes" in Word)
+
* ''Editor'' tidies up PC draft (e.g. "accept all changes" in Word) and submits to RSNA Staff
* [[Publication Process|Post PC draft of Document on the Wiki]] ('''editor/secretariat''')
+
* ''RSNA Staff'' '''[[Publication Process|publishes PC draft]]'''
* The Profile has now reached the [[QIBA Profile Stages|Public Comment Stage]].
+
* The Profile has now reached the [[QIBA Profile Stages|Public Comment Stage]]. Work toward [[QIBA Profile Stages|Consensus]] begins.
* Send announcement to mailing lists ('''secretariat''')
+
 
 +
 
 +
* ''RSNA Staff'' sends PC announcement to mailing lists
 
** detail location of document to be reviewed, deadline for comment submission, method of submission
 
** detail location of document to be reviewed, deadline for comment submission, method of submission
** provide a link to the [[:Media:QIBA_Public_Comment_Template-2011.01.doc | QIBA Public Comment Template]]
+
** provide a link to the [http://tinyurl.com/QIBA-Public-Comment-Form QIBA Public Comment Form]
 
** reach out to any organizations and individuals that might have and interest or expertise to contribute
 
** reach out to any organizations and individuals that might have and interest or expertise to contribute
* Email comments to secretariat ('''Commenters''')
+
* ''Commenters'' submit comments to RSNA Staff (via web form or emailed comment form)
 
** commenters include committee members, other QIBA people, external bodies
 
** commenters include committee members, other QIBA people, external bodies
 
** this is the key point for asynchronous engagement
 
** this is the key point for asynchronous engagement
** please use the provided comment form, it saves the editor having to transcribe your comments
+
** please use the comment forms; it saves the Editor having to transcribe your comments
* Collate all comments into a spreadsheet or Word table ('''secretariat/editor''')
+
 
 +
 
 +
* ''RSNA Staff/editor'' collate all comments into a resolution spreadsheet (see [https://docs.google.com/spreadsheets/d/1o3_ssHHIABGKNesUJ_-jL5RYqSx9Eq4o6C2dlIsHQo4/edit?usp=sharing Google Sheet template] or '''[[:Media:QIBA_Public_Comment_Template-2011.01.doc | Word table]]'''
 
** sort by line number and priority (Low/Med/High)
 
** sort by line number and priority (Low/Med/High)
 
** re-title the leftmost column from "Leave Blank" to "#"
 
** re-title the leftmost column from "Leave Blank" to "#"
 
** fill the leftmost column with incrementing numbers.  Now you can refer to "Comment #43", or re-sort the table if you like
 
** fill the leftmost column with incrementing numbers.  Now you can refer to "Comment #43", or re-sort the table if you like
 
** re-title the rightmost column from "Leave Blank" to "Resolution"
 
** re-title the rightmost column from "Leave Blank" to "Resolution"
* Resolve comments with priority Low ('''editor''')
+
* ''Editor'' resolves comments with priority Low
 
** turn on Change Tracking in Word
 
** turn on Change Tracking in Word
** for most Low comments (typos), fix it in the document and enter "Done" in the Resolution column
+
** for most Low comments (typos), fix it in the Profile document and enter "Done" in the Resolution column of the resolution table
 
** if any Low comments prove problematic, elevate to Med
 
** if any Low comments prove problematic, elevate to Med
* Review Med & High comments ('''Biomarker Committee''')
+
* ''Biomarker Committee'' reviews Med & High comments
** walk through document
+
** step through the resolution table
 
** each comment may be:
 
** each comment may be:
 
*** accepted = proposed text accepted as is
 
*** accepted = proposed text accepted as is
 
*** rejected = committee does not agree with issue (document reason, e.g. out of scope, )
 
*** rejected = committee does not agree with issue (document reason, e.g. out of scope, )
 
*** resolved = issue accepted but resolved differently than proposed
 
*** resolved = issue accepted but resolved differently than proposed
* Record decision and explanation (as needed) in the Resolution column of the table/spreadsheet ('''editor''')
+
** consider getting a 3-person sub-committee to take a first pass at this and focus the full committee on items needing discussion
** editor may find it useful to color code comment rows or resolution cells, e.g.
+
* ''Editor'' records decision and explanation (as needed) in the Resolution column of the resolution table/spreadsheet
*** grey - resolved, document update done (if needed).
+
** The Google template includes a status column with codewords to track completion progress.
*** green - resolution decided, document still needs to be updated
 
*** yellow - currently under debate/discussion
 
* Post resolution spreadsheet and updated Document on the Wiki ('''editor/secretariat''')
 
* [[Review Process|Approve as Consensus]] ('''Biomarker & Modality Committees''')
 
* Tidy up Consensus draft (e.g. "accept all changes" in Word)
 
* [[Publication Process|Post Consensus Document on the Wiki]] ('''editor/secretariat''')
 
* The Profile has now reached the [[QIBA Profile Stages|Consensus Stage]].
 
  
NOTE: If you receive few or no public comments, that's a bad sign.  Presuming we didn't hit perfection on the first try, it means we didn't convince people it was important enough to read in any great detail.  That bodes poorly for our ability to convince people it is important enough to read and conform to.  Good outreach is a significant part of Public Comment.  It's our first stage at marketing the Profile.
 
  
The final resolution draft with all the comments resolved with change tracking still visible should be posted to the Wiki, along with the resolution spreadsheet.  This helps people review the resolution of their comments and the changes that resulted from the Public Comment process
+
* ''RSNA Staff'' posts resolution spreadsheet and change-tracked Profile Document on the Wiki
 
+
** This helps people review the resolution of their comments and the changes that resulted from the Public Comment process
After that, you can "accept all changes" and once it has been '''[[Review Process|approved by the Committee]]''', post it as the "Publicly Reviewed Version".
+
* ''Biomarker Committee'' [[Review Process|reviews and approves as Consensus]]
 +
* ''Modality Coordination Committee'' [[Review Process|reviews and approves as Consensus]]
 +
* ''Editor'' tidies up Consensus draft (e.g. "accept all changes" in Word) and submits to RSNA Staff
 +
* ''RSNA Staff'' '''[[Publication Process|publishes Consensus draft]]'''
 +
* The Profile has now reached the [[QIBA Profile Stages|Consensus Stage]].

Revision as of 16:43, 9 July 2019

Public Comment is intended to allow both regular participants in QIBA Activities and also those who don't have the time to dedicate to regular participation a chance to contribute their thoughts on proposed specifications before they are formally released. It's also an excellent chance to engage relevant stakeholder individuals and organizations. Comments are accepted from all.

NOTE: If you receive few or no public comments, that's a bad sign. Presuming we didn't hit perfection on the first try, it means we didn't convince people it was important enough to read in any great detail. That bodes poorly for our ability to convince people it is important enough to read and conform to. Good outreach is a significant part of Public Comment. It's our first stage at marketing the Profile.


Period: 30 days (may be longer at the discretion of the committee)


  • RSNA Staff sends PC announcement to mailing lists
    • detail location of document to be reviewed, deadline for comment submission, method of submission
    • provide a link to the QIBA Public Comment Form
    • reach out to any organizations and individuals that might have and interest or expertise to contribute
  • Commenters submit comments to RSNA Staff (via web form or emailed comment form)
    • commenters include committee members, other QIBA people, external bodies
    • this is the key point for asynchronous engagement
    • please use the comment forms; it saves the Editor having to transcribe your comments


  • RSNA Staff/editor collate all comments into a resolution spreadsheet (see Google Sheet template or Word table
    • sort by line number and priority (Low/Med/High)
    • re-title the leftmost column from "Leave Blank" to "#"
    • fill the leftmost column with incrementing numbers. Now you can refer to "Comment #43", or re-sort the table if you like
    • re-title the rightmost column from "Leave Blank" to "Resolution"
  • Editor resolves comments with priority Low
    • turn on Change Tracking in Word
    • for most Low comments (typos), fix it in the Profile document and enter "Done" in the Resolution column of the resolution table
    • if any Low comments prove problematic, elevate to Med
  • Biomarker Committee reviews Med & High comments
    • step through the resolution table
    • each comment may be:
      • accepted = proposed text accepted as is
      • rejected = committee does not agree with issue (document reason, e.g. out of scope, )
      • resolved = issue accepted but resolved differently than proposed
    • consider getting a 3-person sub-committee to take a first pass at this and focus the full committee on items needing discussion
  • Editor records decision and explanation (as needed) in the Resolution column of the resolution table/spreadsheet
    • The Google template includes a status column with codewords to track completion progress.