Difference between revisions of "Public Comment Process"

From QIBA Wiki
Jump to: navigation, search
Line 9: Line 9:
* Tidy up PC draft (e.g. "accept all changes" in Word)
* Tidy up PC draft (e.g. "accept all changes" in Word)
* [[Publication Process|Post PC draft of Document on the Wiki]] ('''editor/secretariat''')
* [[Publication Process|Post PC draft of Document on the Wiki]] ('''editor/secretariat''')
* The Profile has now reached the [[QIBA Profile Stages|Public Comment Stage]].
* The Profile has now reached the [[QIBA Profile Stages|Public Comment Stage]]. Start working on [[QIBA Profile Stages|Consensus]].

Revision as of 05:24, 7 March 2018

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)

  • Send announcement to mailing lists (secretariat)
    • 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
  • Email comments to secretariat (Commenters)
    • commenters include committee members, other QIBA people, external bodies
    • this is the key point for asynchronous engagement
    • please use the provided comment form, it saves the editor having to transcribe your comments

  • Collate all comments into a resolution spreadsheet (see Google template or Word table (secretariat/editor)
    • 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"
  • Resolve comments with priority Low (editor)
    • 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
  • Review Med & High comments (Biomarker Committee)
    • 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
    • you may want a 3-person sub-committee to take a first pass at this and focus the full committee on items needing discussion
  • Record decision and explanation (as needed) in the Resolution column of the resolution table/spreadsheet (editor)
  • The Google template includes a status column with codewords to track completion progress.

  • Post resolution spreadsheet and change-tracked Profile Document on the Wiki (editor/secretariat)
    • This helps people review the resolution of their comments and the changes that resulted from the Public Comment process
  • Approve as Consensus (Biomarker & Modality Committees)
  • Tidy up Consensus draft (e.g. "accept all changes" in Word)
  • Post Consensus Document on the Wiki (editor/secretariat)
  • The Profile has now reached the Consensus Stage.