This wiki has undergone a migration to Confluence found Here
Difference between revisions of "PIC:BCSM"
Jump to navigation
Jump to search
m (→Instructions:) |
|||
(4 intermediate revisions by one other user not shown) | |||
Line 11: | Line 11: | ||
'''Project Timeline''' | '''Project Timeline''' | ||
− | :*Project Launch: | + | :*Project Launch: Not yet scheduled |
− | :*Gather Requirements: | + | :*Gather Requirements: Ongoing |
− | :*Update Template: | + | :*Update Template: Not yet scheduled |
− | :*Release/Publication: | + | :*Release/Publication: Not yet scheduled |
==Project Working Documents== | ==Project Working Documents== | ||
− | : The [[Media: | + | : The [[Media:Ballotcomments_template_2014JAN_140408_0416(Siew_Meyer).xlsx |Ballot Common spreadsheet Template]] is used by all workgroups and members that ballot documents through the ballot desktop. PIC will be updating/improving the template. |
==Project Requirements Gathering== | ==Project Requirements Gathering== | ||
Line 29: | Line 29: | ||
#* Committee Comments: leave blank | #* Committee Comments: leave blank | ||
#* Status: Entered | #* Status: Entered | ||
− | + | # Add "handy hints" for co-chairs based on WGs best practice, for example, 1) OO typically has motion to delegate Affirmative-Typos resolution to Editor to apply, unless Editor has question will bring back to WG 2) Recommendations on how to execute block votes 3) Recommendation from last ANSI Audit to: assign disposition to person or small group, schedule a call to review the dispositions, then vote to approve the package. Items that need further discussion can be pulled out. Simple majority of members present and voting 4) Recommend how to break up large ballot for processing, then later, recombine. Might be used to divide large project into smller sections. | |
− | + | #* Source: Freida Hall freida.x.hall@questdiagnostics.com | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | # Add "handy hints" for co-chairs based on WGs best practice, for example, 1) OO typically has motion to delegate Affirmative-Typos resolution to Editor to apply, unless Editor has question will bring back to WG 2) Recommendations on how to execute block votes 3) Recommendation from last ANSI Audit to: assign disposition to person or small group, schedule a call to review the dispositions, then vote to approve the package. Items that need further discussion can be pulled out. Simple majority of members present and voting 4) Recommend how to break up large ballot for processing, then later, | ||
− | #* Source: Freida Hall | ||
#* Submitted on: 2014-01-20 | #* Submitted on: 2014-01-20 | ||
#* Committee Comments: pending identification of source documents (best practices, etc.) NOTE: some topics mentioned do not relate to WG co-chairs (how to execute block vote,for example). Could be separate project to build Q&A and capture best practices. | #* Committee Comments: pending identification of source documents (best practices, etc.) NOTE: some topics mentioned do not relate to WG co-chairs (how to execute block vote,for example). Could be separate project to build Q&A and capture best practices. |
Latest revision as of 22:31, 9 March 2017
Return to the >> Process Improvement Committee
Contents
Ballot Comment Spreadsheet Maintenance
Project Information
- Insert project description here
- The Project Scope Statement status is: In Development
Project Lead(s)
- Sandra Stuart (Sandra.Stuart@Kp.org)
Project Timeline
- Project Launch: Not yet scheduled
- Gather Requirements: Ongoing
- Update Template: Not yet scheduled
- Release/Publication: Not yet scheduled
Project Working Documents
- The Ballot Common spreadsheet Template is used by all workgroups and members that ballot documents through the ballot desktop. PIC will be updating/improving the template.
Project Requirements Gathering
Instructions:
To add a requirement for consideration by the committee edit the WIKI directly yourself following the template provided or email the PIC List Service (pic@lists.hl7.org)
- Requirement Template:
- enter requirement
- Source: enter your name and email address
- Submitted on: enter the date of your submission
- Committee Comments: leave blank
- Status: Entered
- Add "handy hints" for co-chairs based on WGs best practice, for example, 1) OO typically has motion to delegate Affirmative-Typos resolution to Editor to apply, unless Editor has question will bring back to WG 2) Recommendations on how to execute block votes 3) Recommendation from last ANSI Audit to: assign disposition to person or small group, schedule a call to review the dispositions, then vote to approve the package. Items that need further discussion can be pulled out. Simple majority of members present and voting 4) Recommend how to break up large ballot for processing, then later, recombine. Might be used to divide large project into smller sections.
- Source: Freida Hall freida.x.hall@questdiagnostics.com
- Submitted on: 2014-01-20
- Committee Comments: pending identification of source documents (best practices, etc.) NOTE: some topics mentioned do not relate to WG co-chairs (how to execute block vote,for example). Could be separate project to build Q&A and capture best practices.
- Status: Deferred