Tools

The following proposal is organized by artifact/activity and is based on a presentation at the IHE International meeting Nov 2006. Each entry describes What is done Where by Whom. Hopefully this will provide some structure to the debate.

• Items in Bold text are proposed to be mandated by IHE
• Items in Normal text are proposed to be IHE conventions
• Items in Italic text are proposed as alternatives worth considering

The "Whom" listed is the default person responsible for it getting done. In different domains/regions/committees the "Whom" may delegate the responsibility to someone else. For example the Cochair and Secretariat might agree that the latter will maintain the roster.

Committee Activities

• Committee Roster
  • Maintained on Wiki by the Committee Co-chair

• Committee Meeting/T-Con Calendar
  • Maintained on IHE Calendar by Co-chair
  • Mirrored on Wiki by Cochair in Committee Timeline (for major events)

• Committee Discussions
  • Conducted on Google Groups by Members
  • Archived on Google Groups by Google
  • Linked-to on Committee Page

• Commitee Meeting Minutes
  • Archived on FTP site

Development Activities

• Domain Timeline / Development Activity Events
  • Authored on Wiki by Planning/Tech Cochairs
  • Announced (milestone headsup) on Domain Mailing List by Tech Cochair
    • Mirrored (cc’d) on Domain Coord Mailing List by Tech Cochair
    • Mirrored (cc’d) on Region Cochairs Mailing List by Tech Cochair
    • Mirrored on other Domain & Region Mailing Lists (as appropriate) by Domain/Region Cochairs
  • Presented on IHE.net by Secretariat?

• Draft Supplements
  • Authored in Word by Tech Cmte Members
  • Authored on Wiki by Tech Cmte Members

• Public Comment Supplements
  • Finalized in Word by Tech Cmte Editor
  • Archived on FTP by Tech Cmte Editor
  • Rendered in PDF by Secretariat
  • Published/Linked-to on Wiki by Secretariat
  • Published/Linked-to on IHE.net

• Public Comments
  • Submitted on Committee Mailing List (in Excel) by Members
  • Submitted on Public Comment List by Public

• Technical Framework, Final Text Supp, Trial Implementation Supp
  • Finalized in Word by Tech Cmte Editor
  • Archived on FTP by Tech Cmte Editor
  • Rendered in PDF by Secretariat
  • Published/Linked-to on IHE.net by Secretariat
  • Linked-to on Wiki

• CPs [see CP discussion or copy summary here]

Implementation Activities

• Profile Implementation Guidance/FAQs
  • Author on Wiki by domain and Implementer Community

• Integration Statements
  • Published on vendor sites by Vendors
  • Cataloged in Profile Registry by Vendors
  • Linked-to on IHE.net (IS Page) by Secretariat (at Vendor request)

• Region Activity & Timeline
  • Author on Wiki by region
  • Link to region web page?

Education Activities

• Profile Lists/One-line Descriptions
  • Author on Wiki (Profile List) by Planning Cmte
  • Illustrated on IHE.net by Secretariat (Marketing Cmte?)

• Profile FAQs (for Users)
  • Author on Wiki by Planning Cmte
  • Linked-to on IHE.net (Profiles Page) by Secretariat

• Regional Educational Events (including Demos)
  • Maintained on IHE Calendar by
  • Mirrored on Wiki (Region Page) by Region Cochair
  • List on Wiki Region and Domain pages?

• Educational Presentations
  • Author in Powerpoint by Committee Members
  • Archive on FTP by Committee Members
  • Linked-to on Wiki (Workshop Pages) by Committee Members
  • Linked-to on Wiki (relevant topic/Profile Page) by Committee Members

• Flyers and Brochures
  • Authored in (whatever) by Secretariat (based on raw materials in Wiki, etc)
  • Printed by Secretariat (and distributed wherever)\
  • Archived on FTP by Secretariat
  • Linked-to on Wiki and/or IHE.net (as appropriate)

• User Discussions

• Press Releases
  • Published on IHE.net by Secretariat
  • Mirrored to Mailing Lists (as appropriate) by each ML Moderator

Communication Tool Descriptions

These are the primary tools for persistent communications. Non-persistent tools like Webex, Skype, IM, T-Con are "unconstrained" for now. Secondary tools are listed below.

• IHE Website - www.ihe.net
  • Strengths: advanced presentation, strict publication process, stable
  • Primary Use: Professional/Glossy Presentation

• IHE Wiki - wiki.ihe.net
  • Strengths: easy edit, “live”, change tracking, “notification"
  • Primary Use: Authoring, Collaboration
  • Material that gets incrementally updated, multiple people contribute

• IHE Calendar - www.rsna.org/ihe/calendar
  • consider transitioning to a Google based calendar?
  • A calendar that could filter and also provide both a monthly event calendar view and a sequential list of events/timeline view might remove the need to mirror the calendar.

• IHE Mailing Lists - groups.google.com/group/IHE-group-name
  • Strengths: automatic, searchable archive/record of discussions
  • (all mailing lists are in the process of transitioning to Google Groups)
  • Some problems with delays in mailing?

• IHE FTP - ftp.rsna.org
  • should we rename to ftp.ihe.net?
  • Strength: Easy bulk download, file hierarchy
  • Primary Use: Document Archive

• IHE Forums - forums.rsna.org
  • transition to google mailing list?

• IHE Connectathon Website – www.connectathon.net

Secondary Communication Tools

• Regional IHE Websites
• wikipedia.org
• Brochures and Flyers

Wiki Conventions

Page Naming

<Some naming conventions are already listed in the relevant page templates>

Revision Reference Points

An plus & minus of Wiki pages is that they more dynamic than other modes of collaboration.

For certain pages, it may be useful to periodically benchmark a version that everyone has agreed to, but still not prevent further contributions and collaboration.

A "notary" (e.g. Chris or Didi) could edit the page and save it with a Summary comment or "OFFICIAL" or "CONCENSUS" or somthing.

This would allow people to continue to provisionally evolve the page contents, but if anyone wanted to see the last version that everyone officially agreed to, they could click on "history" and click the last version edited by a notary as "OFFICIAL". Further, you can use the comparison feature to see the delta of what has changed since.