PIC:BCSM

Return to the >> Process Improvement Committee

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: Sept 2013
• Gather Requirements: Sept-Nov 2013
• Update Template: Jan 2014

• Release/Publication: May 2014 WGM

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:

1. enter requirement
   • Source: enter your name and email address
   • Submitted on: enter the date of your submission
   • Committee Comments: leave blank
   • Status: Entered
2. Vote/Type Column - consider combining Neg-Mg, Neg-Mi. Since GOM and ANSI have some requirements for 'Negative' is there really any value in further categorizing Major/Minor.
   • Source: freda.x.hall@questdiagnostics.com
   • Submitted on: 2014-01-18
   • Committee Comments: to be taken under discussion
   • Status: Referred to PIC, beyond the scope of project
3. Clarify Instructions,which line items require vote, for example: Negatives line items require vote on all ballot types, Affirmative line items do not require vote (or onlyif changing standard/IG/model etc.)
   • Source: Freida Hall freda.x.hall@questdiagnostics.com
   • Submitted on: 2014-01-20
   • Committee Comments: assigned to Meyer, in process
   • Status: IN process
4. Would be nice to have process to post reconciliation spreadsheet after the ballot comment spreadsheets are amalgamated. FHIR used Google Docs but OO WG did not think it had worked well, e.g. not all organizations can access and changes hard to track. GForge SVN might be possibility (requires login); want co-chairs only to have edit rights but allow others to download/view.
   • Source: Freida Hall freda.x.hall@questdiagnostics.com
   • Submitted on: 2014-01-20
   • Committee Comments: to be taken under discussion
   • Status: referred to PIC, beyond project scope
5. 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, recobine. Might be used to divide large project into smller sections.
   • Source: Freida Hall freda.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