Domain Coord - Future Agenda Topics

Feel free to add proposed agenda items here.

Urgent: For Next Meeting

Try to indicate why it's urgent

• The process for building CDA-based content profiles crosses multiple domains (ITI, PCC, Lab for now) and requires coordination among the domains. CDA-based content profiles should have common building blocks and references across domains where common content is desired. The domains need a mechanism to support this coordination effort.

Near Term

• Request from ITI committee member that since we are using the urn:ihe:iti... namespace URN: IHE should really register its URN namespace usage with IANA.

• 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.

• How to make support material for developers easily available
  • Specialized part of the wiki ordered by domain and profile? (e.g. the Implementation section of the Wiki)
  • Suggestion from ITI Technical Committee to facilitating access to support material for developers (WSDLs, schemas, examples). Example at ftp:/ftp.ihe.net/TF_Support_Material

• Non-participating Domains - need action plan to pull missing co-chairs into this Cmte
  • May be able to springboard from Domain Applications
  • E.g. "Welcome to IHE" email to cochairs of Approved domains outlining responsibilities, linkups

• Template for Domain Reports to the Board
  • What should the board hear about each domain
  • Draft a template and an example.
  • Short, informative

• New Committee Member Welcoming Process
  • 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

• Updated Email Ballots explanation page at Email_Ballots

"Parking Lot"

Review these from time to time for activation

• IHE Review Committees - Revisit after "HL7 Review Taskforce" pilot has made some progress
  • Previously tried to do a single Review Cmte and the volume is intractable
  • Consider Standard oriented cross-domain review committees
  • E.g. IHE HL7 Review Cmte, IHE DICOM Review Cmte, IHE WebServices Review Cmte, IHE CDA Review Cmte
  • Basically for any standard that is used across more than one domain
  • Any transaction created in any Domain using a certain standard, must be sent to the relevant Review Cmte.
  • Transaction authors must participate in the review

Completed

If you think we've covered it, but aren't comfortable deleting it yet (it remains in History), then move it here

• Board Representative Selection for Domains
  • Deadlines in March
  • Learnings from domain representative elections:
    • Lack of update-to-date roster (see 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
  • ...