Difference between revisions of "IHE Domain Coordination Committee 2008-09-30 Teleconference"

From IHE Wiki
Jump to navigation Jump to search
Line 19: Line 19:
 
[ftp://ftp.ihe.net/Document_templates/IHE%20Supplement%20Template-V7.1.doc Updated Supplement Template]
 
[ftp://ftp.ihe.net/Document_templates/IHE%20Supplement%20Template-V7.1.doc Updated Supplement Template]
  
−
3. Review of definitions of R2 and RE (see discussion in 2008-08-18 minutes)
+
2. Review of definitions of R2 and RE (see discussion in 2008-08-18 minutes)
−
:* There is no clear distinction between the [ftp://ftp.ihe.net/CoChairs/IHE_Optionality_Codes_R2_RE.doc definitions provided of R2 and RE in Technical Framework documents]
+
:* Progress toward consolidated optionality definitions
−
:* Perception of PCC, per Keith Boone, has been that RE is stricter than R2
 
−
:* No distinction has been made in testing of R2 vs. RE elements per Steve Moore
 
−
:* ITI uses both R2 and RE in PAM profile
 
−
:* IHE Radiology created R2 designation based on Type 2 requirement definition in DICOM; however, R2 is only applied to HL7 elements in Rad TF; Rad would be amenable to adopting RE definition
 
−
:* HL7 is working on refining RE definition for release of HL7 2.7 (timeline unknown)
 
−
::* '''Action Item: Chris Carr''' to coordinate a meeting of interested parties during HL7 meeting in Vancouver to resolve disagreement and confusion and develop consistent definitions to be used in all TF documents
 
−
::* Participants to include: Todd Cooper, John Moerhke, Rob Horn, Keith Boone, Francois Macary, Kevin O'Donnell
 
−
:* Remaining questions:
 
−
::* Is a "send if known" designation (R2 or RE) appropriate at all or should these elements simply be optional?
 
−
::* Is there any meaningful distinction to be made between R2 and RE?
 
−
::* Would it be useful to be more precise in defining behaviors of sending and receiving actors; perhaps including behavior of human actors?
 
  
−
4. HL7 Task Force Update
+
3. HL7 Task Force Update
−
:* Call took place on 2008-09-28
+
:* Progress toward updated Appendix C with HL7 version compatibility info
 +
:* HL7 CDA schemas on forge to be organized by HL7 versions and include version guidance
  
 
===Documentation, Websites and Public Information===
 
===Documentation, Websites and Public Information===

Revision as of 13:29, 29 September 2008

Agenda

General Committee Business

1. Roll Call

2. Approval of Minutes

3. Schedule Future Agenda Topics for upcoming meetings

4. Review previous action items

Domain Coordination Checkpoint Announcements

Domain Coordination Issues

1. Domain Timeline Coordination

Updated Supplement Template

2. Review of definitions of R2 and RE (see discussion in 2008-08-18 minutes)

  • Progress toward consolidated optionality definitions

3. HL7 Task Force Update

  • Progress toward updated Appendix C with HL7 version compatibility info
  • HL7 CDA schemas on forge to be organized by HL7 versions and include version guidance

Documentation, Websites and Public Information

1. Implementation support material

  • Review updated implementation templates and domain implementation guide links under Implementation Guidance
  • Use of INRIA Forge for Distributing WSDLs and Schema Rules in Controlled Environment

2. Technical Framework Publication Page

  • Revew sample ITI TF Wiki page

3. pdated Supplement Template

  • Plan for soliciting participation in DCC from non-participating domains
  • Implementation Support Material:

4. Recruitment message for clinicians to participate in Domain Committees [Defer to 2008-09-30]

  • Action Item: Chris Carr will distribute recruiting message for review and comment by committee

Governance Implementation

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

2. ITI notes on implementing governance in domain committees

  • Review and consider for adoption across domain committee process for presentation and evaluation of profile proposals

3. Roadmap Development

  • Discuss method for strategic planning exercise to develop Roadmap
  • How to reflect strategic direction of Board
  • Have well-defined process and reference document for 2008-2009 publication cycle
  • Include coordination among domain (eg, for ITI, QRPH)
  • Action Item: Mike Nusbaum will circulate generalized approach for brainstorming strategic issues

4. IHE Membership Requirements

  • Action Item: Each Committee Secretary to update roster for next meeting and work with cochairs to remind/encourage laggard members.

Next Tcon

  • October 14, 10:00am - 11:30am CDT

Domain Coordination Committee

Retrieved from "http://wiki.ihe.net/index.php?title=IHE_Domain_Coordination_Committee_2008-09-30_Teleconference&oldid=23957"