Difference between revisions of "IHE Testing and Tools Committee Teleconference Minutes 2009-01-05"
Jump to navigation
Jump to search
Chrisdcarr (talk | contribs) |
Chrisdcarr (talk | contribs) |
||
Line 12: | Line 12: | ||
==Minutes== | ==Minutes== | ||
− | 1. Connectathon Results Proposal - Charles Parisot/Geert Claeys | + | 1. [ftp://ftp.ihe.net/Testing_and_Tools/ihe_testing_tools_xathon_results_reporting_2008-11-18%20-gc-CP-1.doc Connectathon Results Proposal] - Charles Parisot/Geert Claeys |
+ | * Reviewed Geert Claeys' draft proposal for results reporting | ||
+ | ** Current draft would report failed results also | ||
+ | *** Consensus of committee is that we should not report failed testing results | ||
+ | ** Current draft would distinguish prototype results from product results | ||
+ | *** Consensus of the committee is that IHE is not able to verify this information for publication | ||
+ | ** Original intent was to distinguish Trial Implementation from Final Text | ||
+ | *** Make that designation simply: Trial Implementation or Final Text; no way to convey Trial Implementation Profiles that are moved to Final Text without changes | ||
+ | * '''Action Item:''' Geert will redraft simplified version of the proposal | ||
+ | * '''Action Item:''' Committee will provide feedback to Eric's group on design of product registry and linkage to Connectathon results matrix | ||
− | 2. Connectathon Quality | + | 2. [ftp://ftp.ihe.net/Testing_and_Tools/Quality_Assurance_IHE_Connectathon_v1.doc Connectathon Quality Assurance Guidelines] - Cor Loef |
+ | * Cor Loef's draft address processes as they are currently carried out | ||
+ | * Next draft should incorporate language about: | ||
+ | ** Bureaucratic rules around Connectathon (eg, must be national deployment committee) | ||
+ | ** Use of IHE tools | ||
+ | ** Training/qualification requirements for Connectathon project managers | ||
+ | ** Recognition of results reporting in main database | ||
+ | * Action Item: Chris Carr will develop new draft incorporating these elements prior to next committee tcon | ||
3. Committee Charter - Chris Carr | 3. Committee Charter - Chris Carr | ||
+ | * '''Action Item:''' Chris Carr will contact David Monteau offline to schedule a review of final document | ||
4. Licensing Terms - Chris Carr/Steve Moore | 4. Licensing Terms - Chris Carr/Steve Moore | ||
+ | * '''Action Item:''' | ||
5. Product Registry - Eric Poiseau | 5. Product Registry - Eric Poiseau | ||
Line 25: | Line 43: | ||
7. Use of Kudu by Malaysian Connectathon | 7. Use of Kudu by Malaysian Connectathon | ||
+ | * Incorporate formal rules for recognition of Connectathon | ||
+ | * Set training dates for use of Kudu | ||
+ | |||
+ | 8. Next Meeting: | ||
+ | * Jan. 19 is a holiday in US; move next call to Monday, Jan. 26 and resume normal schedule on Monday, Feb. 2 | ||
+ | * | ||
[[Testing and Tools Committee]] | [[Testing and Tools Committee]] | ||
[[Category: Minutes]] | [[Category: Minutes]] |
Revision as of 12:47, 5 January 2009
Attendees
- Geert Claeys - Agfa
- Didi Davis - HIMSS
- Chris Lindop - GE
- Cor Loef - Philips
- Bill Majurski - NIST
- Steve Moore - MIR
- Eric Poiseau - INRIA
- Nichole Drye-Mayo - RSNA
- Chris Carr - RSNA
Minutes
1. Connectathon Results Proposal - Charles Parisot/Geert Claeys
- Reviewed Geert Claeys' draft proposal for results reporting
- Current draft would report failed results also
- Consensus of committee is that we should not report failed testing results
- Current draft would distinguish prototype results from product results
- Consensus of the committee is that IHE is not able to verify this information for publication
- Original intent was to distinguish Trial Implementation from Final Text
- Make that designation simply: Trial Implementation or Final Text; no way to convey Trial Implementation Profiles that are moved to Final Text without changes
- Current draft would report failed results also
- Action Item: Geert will redraft simplified version of the proposal
- Action Item: Committee will provide feedback to Eric's group on design of product registry and linkage to Connectathon results matrix
2. Connectathon Quality Assurance Guidelines - Cor Loef
- Cor Loef's draft address processes as they are currently carried out
- Next draft should incorporate language about:
- Bureaucratic rules around Connectathon (eg, must be national deployment committee)
- Use of IHE tools
- Training/qualification requirements for Connectathon project managers
- Recognition of results reporting in main database
- Action Item: Chris Carr will develop new draft incorporating these elements prior to next committee tcon
3. Committee Charter - Chris Carr
- Action Item: Chris Carr will contact David Monteau offline to schedule a review of final document
4. Licensing Terms - Chris Carr/Steve Moore
- Action Item:
5. Product Registry - Eric Poiseau
6. Cypress Project - Chris Carr/Steve Moore
7. Use of Kudu by Malaysian Connectathon
- Incorporate formal rules for recognition of Connectathon
- Set training dates for use of Kudu
8. Next Meeting:
- Jan. 19 is a holiday in US; move next call to Monday, Jan. 26 and resume normal schedule on Monday, Feb. 2