Public Comment Process: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
Kevino (talk | contribs)
editor
4,951 edits
No edit summary
Line 3: Line 3:
''This article is a component of the [[Technical Framework Publication Process]].''
''This article is a component of the [[Technical Framework Publication Process]].''


All IHE technical documents (Technical Framework supplements and white papers)are published for public comment to ensure stakeholder representation, transparency and quality review. All documents are published via the www.ihe.net Website and announced to the broadest email distribution list available. IHE Technical Framework supplements are published for formal public review for a minimum period of 30 days before being republished for Trial Implementation (ie, Connectathon testing).


All IHE Technical Framework supplements and white papers are published for public comment to ensure stakeholder representation, transparency and quality review.  This is a chance for both regular participants in IHE Activities and those who don't have the time to dedicate to regular participation to contribute thoughts on proposed specifications before they are formally released.


===Announce Publication to ihenews list====
Public comment should be considered the prelude to publication.  A committee should be largely satisfied with the contents of a document before it is sent out for Public Comment.


====Posting Thread Text====
The typical steps are shown below.  The '''entity responsible''' for each step needs to make sure it happens, but they may do so by delegating the action.
''The following text (or equivalent language) is used when creating a forum at forums.rsna.org for gathering public comment.''


The document is available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm. Submit comments by starting or replying to a thread below. For extensive comments please use the comment form provided below.


====Comment Form Post====
Period: 30 days (minimum)
''The following text (or equivalent language) is used when posting to a forum for gathering public comment.''


Please use the attached (MS-Excel) comment form to make extensive comments. To submit you can post a reply with the completed form attached or email the form to cardio@ihe.net.
* Approve document for public comment ('''Domain Technical Committee''')
* Notify [[Domain Coordination Committee]] document is going out for public comment ('''Domain TC Cochair''')




''<How comments can/should be submitted (e.g. IHE Forum, IHE Wiki, Email, etc.)>''
* Prepare PC draft of document ('''Editor''')
** Turn on line numbers
** Prepare PDF (to steer people away from inline comments and towards comment form)
* Copy PC draft of document to ftp.ihe.net/DocumentPublication/CommitteeSubmitted/<Domain> ('''Editor''')
* Notify Domain Secretariat by email that document is ready ('''Editor''')
* Post PC draft of document on [http://www.ihe.net/Technical_Framework/public_comment.cfm www.ihe.net Public Comment Page] ('''Domain Secretariat''')
* Announce PC to IHE News ('''Domain Secretariat''')
** [[Public Comment Announcement Template]]
** detail location of document to be reviewed, deadline for comment submission, method of comment submission
** provide a link to the Public Comment Form
* (Optional) Announce PC to associated stakeholder organizations ('''Domain TC Cochairs''')




''<How long should there be between announcement and closing comments (e.g. 30 days)>''
* Submit comments to secretariat ('''Commenters''')
** commenters include committee members, other IHE 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 spreadsheet ('''Secretariat/Editor''')
** sort by line number and priority (Low/Med/High)
* Resolve comments with priority Low ('''Editor''')
** if any Low comments prove problematic, elevate to Med
* Distribute comment spreadsheet and updated draft with Low resolutions to Technical Committee ('''Editor''')
* Review Med & High comments ('''Technical Committee''')
** walk through document
** 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
* Record resolution in comment spreadsheet ('''Editor''')
* Update document to reflect resolutions ('''Editor''')
 
 
* Post comment spreadsheet (either to ftp.ihe.net or to Google Docs) ('''Editor''')
* Link spreadsheet to the [[Public Comment Resolutions]] wiki page for the domain ('''Editor''')




==See Also==
==See Also==
[[Comments| Public Instructions for Public Comments]]
[[Comments| Public Instructions for Public Comments]]

Revision as of 15:05, 1 September 2011


This article is a component of the Technical Framework Publication Process.


All IHE Technical Framework supplements and white papers are published for public comment to ensure stakeholder representation, transparency and quality review. This is a chance for both regular participants in IHE Activities and those who don't have the time to dedicate to regular participation to contribute thoughts on proposed specifications before they are formally released.

Public comment should be considered the prelude to publication. A committee should be largely satisfied with the contents of a document before it is sent out for Public Comment.

The typical steps are shown below. The entity responsible for each step needs to make sure it happens, but they may do so by delegating the action.


Period: 30 days (minimum)

  • Approve document for public comment (Domain Technical Committee)
  • Notify Domain Coordination Committee document is going out for public comment (Domain TC Cochair)


  • Prepare PC draft of document (Editor)
    • Turn on line numbers
    • Prepare PDF (to steer people away from inline comments and towards comment form)
  • Copy PC draft of document to ftp.ihe.net/DocumentPublication/CommitteeSubmitted/<Domain> (Editor)
  • Notify Domain Secretariat by email that document is ready (Editor)
  • Post PC draft of document on www.ihe.net Public Comment Page (Domain Secretariat)
  • Announce PC to IHE News (Domain Secretariat)
    • Public Comment Announcement Template
    • detail location of document to be reviewed, deadline for comment submission, method of comment submission
    • provide a link to the Public Comment Form
  • (Optional) Announce PC to associated stakeholder organizations (Domain TC Cochairs)


  • Submit comments to secretariat (Commenters)
    • commenters include committee members, other IHE 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 spreadsheet (Secretariat/Editor)
    • sort by line number and priority (Low/Med/High)
  • Resolve comments with priority Low (Editor)
    • if any Low comments prove problematic, elevate to Med
  • Distribute comment spreadsheet and updated draft with Low resolutions to Technical Committee (Editor)
  • Review Med & High comments (Technical Committee)
    • walk through document
    • 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
  • Record resolution in comment spreadsheet (Editor)
  • Update document to reflect resolutions (Editor)


  • Post comment spreadsheet (either to ftp.ihe.net or to Google Docs) (Editor)
  • Link spreadsheet to the Public Comment Resolutions wiki page for the domain (Editor)


See Also

Public Instructions for Public Comments

Retrieved from "http://wiki.ihe.net/index.php?title=Public_Comment_Process&oldid=53665"