IHE Testing and Tools Committee 2009-03-30 Teleconference Minutes

From IHE Wiki
Jump to navigation Jump to search


  • Lisa Carnahan, NIST
  • Steve Moore, MIR
  • Charles Parisot, GE
  • Eric Poiseau, INRIA
  • Rob Snelick, NIST
  • Joan McMillen, RSNA
  • Chris Carr, RSNA


1) Tools Development Planning with NIST

  • January 2010 Connectathon to use Gazelle
  • Eric's group (INRIA) to devote focused attention to test engine over the next few months
  • Porting 600+ existing tests into test management framework will require time
  • Critical task is to refine the test engine first to make population with test scripts possible (need to be defined in BPEL)
  • Refactoring of Kudu tests will improve organization and efficiency, but again requires effort
  • MIR has two engineer FTEs working on Gazelle (also performs Connectathon management and domain committee work/test plan development)
  • INRIA has three FTEs working on Gazelle
  • Eric currently applying for renewal of team's funding
  • MIR contract renewal with HIMSS/RSNA under discussion: likely equivalent or slightly reduced support
  • Plus management oversight by Eric and Steve (one FTE total)
  • Delays have made it difficult for NIST to link up its simulation tools
  • NIST Plans
  • NIST likely to get specified funds for Test Tools Development
  • Designed to be used up over next 2 years
  • Most of the funding to be contracted out
  • Increase of 2-3 FTEs internally
  • Need to develop tools with ability to support NHIN, CCHIT testing (as well as IHE)
  • Need to coordinate timelines and development plans to avoid redundancy and conflict
  • Willing to undertake connections to test services other gaps in development work: focus on external validation services (EVS), eg, CDA validator and linking of simulation tools
  • IHE Europe in discussion with EC about funding for development of platform for tools (Mandate 403)
  • Charles will forward report
  • Important to highlight international aspect of development effort
  • CCHIT and Cypress
  • NIST to convene a kickoff meeting among groups sometime around mid-April

2) Connectathon Process Guidelines

  • Review updated draft of Connectathon QC guidelines and Sponsor requirements
  • Place responsibility for test plan development on national deployment committees holding Connectathons
  • Chris Carr to develop matrix of technical project managers, domains and funding groups

3) Product Registry Development and Rollout [Deferred to next tcon]

  • Vendor input pilot
  • User review pilot

4) Connectathon Monitor/Project Manager Training Event [Deferred to next tcon]

  • Date
  • Location
  • Cost
  • Target Audience
  • Eric and Steve to develop a proposal for event

Testing and Tools Committee