Difference between revisions of "IHE Domain Coordination Committee 2008-08-19 Teleconference"

Revision as of 12:14, 19 August 2008

Agenda

General Committee Business

1. Roll Call

2. Approval of Minutes

August 04 Minutes

3. Schedule Future Agenda Topics for upcoming meetings, as appropriate.

4. Review previous action items

Domain Coordination Checkpoints

RAD
- Call for Proposals
  - Due: Sept 2
  - Profile Selection expected late October

LAB
- Publication as Final Text - <some list of profiles>

Domain Coordination Issues

1. Domain Timeline Coordination

Review 2008-2009 timelines

2. Committee Quorums

Discussion prior to potentially bumping to IHE Board
Confirm secretariat responsibility for monitoring/recording quorum
Is it an issue if a committee consistently fails to reach quorum
Is there a mimimum acceptable quorum for a committee? 1? 2? 3? 4?

3. R2 definition document review.

Documentation, Websites and Public Information

1. Implementation support material

How to make it easily available for developers
Specialized part of the wiki ordered by domain and profile? (e.g. the Implementation section of the Wiki)
Suggestion from ITI Tech to facilitate access to support material for developers (WSDLs, schemas, examples). Example at ftp:/ftp.ihe.net/TF_Support_Material
Review updated implementation templates and domain implementation guide links under Implementation Guidance

2. Review domain tool kits links.

3. Recruitment message for clinicians to participate in Domain Committees

4. Process refinements to encourage and facilitate clinical participation

Governance Implementation

1) Vote on proposal to change the way the pluses are used in rosters for voting purposes.

Example http://wiki.ihe.net/index.php?title=ITI_Technical_Committee_Roster

2) IHE Membership Requirements

Review of requirements
Schedule update of rosters
- All members of rosters should now be representing an IHE Member Organization
- IHE Membership went live in January. We've allowed a 6 month grace period.
- Suggested Action: Each Committee Secretary to update roster for next meeting and work with cochairs to remind/encourage laggard members.

Next steps and New Actions Items

September 2, 2008

Domain Coordination Committee

@@ Line 5: / Line 5: @@
 . Approval of Minutes
-:* [[IHE Domain Coordination Committee 2008-08-04 Teleconference Minutes| 2008-08-04 Minutes]]
+:* [[IHE Domain Coordination Committee 2008-08-04 Teleconference Minutes| August 04 Minutes]]
-. Schedule [[Domain Coord - Future Agenda Topics| Future Agenda Topics]] for upcoming meetings.
+. Schedule [[Domain Coord - Future Agenda Topics| Future Agenda Topics]] for upcoming meetings, as appropriate.
 . Review [[Domain Coordination Committee Action Item List|previous action items]]
@@ Line 19: / Line 19: @@
 * LAB
-** Publication as Final Text (rev. 2.1)
+** Publication as Final Text - ''<some list of profiles>''
-** Laboratory Testing Workflow (LTW), Laboratory Device Automation (LDA), Laboratory Point Of Care Testing (LPOCT), Laboratory Code Set Distribution (LCSD), Laboratory Specimen Barcode Labeling (LBL) and Sharing Laboratory Reports (XD-LAB)
-* ITI
-** Call for proposals issued in July; due by Sept. 26
-** Next meeting in Paris, Oct. 16-17
-** Webinars Sept. 29 - Oct. 10 to cover each profile proposal and streamline meeting in discussion
-* QRPH
-** Off-cycle profile (Drug Safety for Reporting of Adverse Events) to be published for public comment; comments due Sept. 30: to be included in current Connectathon Cycle (in New Directions area?)
 ===Domain Coordination Issues===
 . Domain Timeline Coordination
 :* Review [[Domain Milestones|2008-2009 timelines]]
-::* '''Action Item:''' Secretariat to send reminder to outstanding domains to enter their milestone dates
-::* '''Action Item:''' Add column to table for estimated number of supplements
 . Committee Quorums
@@ Line 41: / Line 30: @@
 :* Is it an issue if a committee consistently fails to reach quorum
 :* Is there a mimimum acceptable quorum for a committee?  1? 2? 3? 4?
-::* Action Item: Set floor of five voting members for committee to be active (quorum minimum is 3)
-::* Action Item: (Committee Secretaries) Establish procedure for when committees fall below minimum
-::* Action Item: Committee Secretary Update Meeting
-. R2 optionality definition document review
-:* ITI, PCC, Rad and Lab definitions of R2 are all similar to HL7 RE (required, empty)
-:: * ITI, Rad: R2=Required if know, must be able to capture and transmit
-:: * PCC: R2=Required if known, not required to capture (system-by-system differences)
-:: * Lab: RE=R2, similar to interpretation used by ITI, Rad; harmonize on single designation?
-:: * PCC will align its definition of R2 with usage by ITI, Rad
-:: * PCC will develop separate optionality designation (R3?): if you capture, you must send, but you are not required to capture
-:: * R2 derived from DICOM Type 2, but coinage of IHE; continue to use for DICOM designation
-:: * RE to be used for 2.x HL7 message profiling
-:: * General principle: document requirements in syntax of underlying standard
-:: * '''Action Item:''' Keith Boone to draft definition of RE as possible replacement for R2; based on Lab definition of RE?
-:: * '''Action Item:''' Lab, Rad, PCD, ITI and PCC Tech Cmtes to review definition and agree on how and when to use
-. PCC APR Profile Dependencies and Content Profile Compliance
-. TF Publication Process Guidelines
-::* [[Technical Framework Publication Process|Charles Parisot's proposed guidelines]]
-::* [[Writing Technical Frameworks|Current Guidelines on Publishing Technical Framework Documents]]
-. HL7 Review Task Force
+. R2 definition document review.
 ===Documentation, Websites and Public Information===
@@ Line 93: / Line 60: @@
 ===Next steps and New Actions Items===
-* Next Tcon: 2008-09-02
+*September 2, 2008
 [[Domain Coordination Committee]]
-[[Category: Agenda]]