|
|
| Line 8: |
Line 8: |
|
| |
|
| == Completed == | | == Completed == |
|
| |
|
| |
| ''If you think we've covered it, but aren't comfortable deleting it yet (it remains in History), then move it here''
| |
|
| |
| * Publication of White Papers
| |
|
| |
| * Communication to purchasers about availability of compliant products - Monroe
| |
|
| |
| * CP communication process (see sample at http://wiki.ihe.net/index.php?title=RAD_Approved_CPs or
| |
|
| |
| * What to do about older documents that are still listed on the public comment page and for one reason or another have not been published for trial implementation [Jungers]:
| |
|
| |
| * Board Representative Selection for Domains
| |
| ** Deadlines in March
| |
| ** Learnings from domain representative elections:
| |
| *** Lack of update-to-date roster (see [[ITI_Planning_Committee#Roster | ITI Plan Roster]] which lists Keith Boone as a representative of Dictophone) means that it is not clear what organizations are eligible. Led to 40-50% ineligible votes in ITI, PCC, PCD and QRPH. All future votes should only be conducted with an up-to-date roster available to all participants. Roster should be referenced in every email ballot.
| |
| *** Should elections for board representative count toward maintaining or acquiring voting rights? Alternatively, is the fact that an organizations submitted a vote (not the contents of a vote, just the submission) be public or private? Should ineligible votes lead to eligible voting in the next meeting/vote? I propose that every email ballot explain the handling of ineligible votes.
| |
| *** When an organizations submits a vote that is not counted should that organization be notified?
| |
|
| |
| * HL7 2.x Versioning (delegated to HL7 Review Taskforce)
| |
| ** Strategies
| |
| ** Backward compatibilities or not
| |
| ** ...
| |
|
| |
| *Cross-Domain TF References
| |
| ** How to cross reference across domains given that PCC supports wiki management of their Technical Framework. How can other domains interact most effectively as they build off of the PCC framework. Effects ITI and Lab so far.
| |
| ** '''Completed:''' PCC now used MS-Word and PDF like other domains
| |
|
| |
| * Technical Framework section numbering (Karen Witting: 2009-11-10)
| |
| ** Some domains use static section numbering so that section numbers, at least the two or three top levels, don't change. i.e. a profile is always section x and a transaction is always section y. Some domains (ex. PCC) are not maintaining static section numbering so this has caused ITI has to update their section references each year as sections are moved. Should domains use consistent section numbering to support consistent cross-referencing.
| |
|
| |
| * Change Supplement Template title page to say "DRAFT in preparation for Public Comment". (2009-11-10)
| |
| ** Rationale: those outside IHE often find or are sent these documents prior to public comment and assume they are the public comment version. This leads to confusion. Sponsor would change title page when the supplement is released officially for public comment.
| |
|
| |
| * Discuss 2011 Webinar Series and begin planning to meet deadlines (March 15)
| |
|
| |
| * '''Steve Moore''': Change the process for entering public comments from RSNA Forums to Google Docs. We can publish a form that someone can fill in that will map directly to the columns in the spreadsheet we use for tracking. Nichole did a prototype of this. She can present that work or Steve can.
| |
| ** This is urgent because the F2F meetings for ITI/PCC/QRPH will need to reference some mechanism for entering comments. Default would be to fall back to the RSNA Forums. It would be helpful to use this mechanism.
| |
|
| |
| * New Committee Member Welcoming Process [2009-11-24; Teri Sippel to prepare for discussion on 2011-03-29 teleconference]
| |
| ** Form letter
| |
| ** How to get on the mailing list
| |
| ** How the Committee Page works
| |
| ** Pointer to Domain Timeline and current meeting schedule
| |
| ** Pointer to policies, procedures and processes
| |
| ** CONCLUSION: new letter and text being used by RSNA and IHE staff as of July 2011
| |
|
| |
| * Supplement Template - [Nov 2008]
| |
| ** Consider if it would help to add more explanatory material
| |
| ** See HITSP Templates for example
| |
| ** Consider copying in material from Process pages on editing Supplements
| |
| ** CONCLUSION: New Supplement Template August 2011
| |
Urgent: For Next Meeting
Try to indicate why it's urgent
Near Term
When the Committee has assigned an item to an upcoming call the [date is shown]
"Parking Lot"
Completed