This wiki has undergone a migration to Confluence found Here

Difference between revisions of "RIMBAA Tooling Liaison"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
 
*#What types of tasks and roles would use tools to aid in standards adoption and implementation
 
*#What types of tasks and roles would use tools to aid in standards adoption and implementation
  
*From [[Implementation Tools]]:
+
*[[Tools for RIM based software development]]
**FWIW: Implementation tools that RIMBAA has identified include:
 
***MIF based class/code generators (e.g. MDHT. Everest)
 
***MIF based database schema generator (e.g. MGRID)
 
***MIF based UI component generators
 
***ISO Datatypes library (R1/RFH(FHIR)-datatypes)
 
***CTS products
 
***Mapping tools
 
***(Not a tool: MIF documentation, currently lacking)
 
**Tools that support implementation
 
***Testing tools (e.g. Instance Editor, MDHT)
 
 
*HL7 Tools list
 
*HL7 Tools list
 
**http://www.hl7.com.au/HL7-Tools.htm
 
**http://www.hl7.com.au/HL7-Tools.htm

Revision as of 17:31, 19 January 2012

From the San Diego WGM sept-2011

  • It passed a MOTION to have a joint RIMBAA/tooling meeting in San Antonio (Michael/Peter, 11-0-0) ;
  • Michael van der Zel is now the tooling liason to RIMBAA;
  • It passed a MOTION for RIMBAA to co-sponsor the "HL7 Tooling Strategy and Process Revision Project" created by the tooling WG (Peter/Ewout, 11-0-0)

Discussion Topics

  • Process to recommend use of certain tools
  • The Tooling Work Group asks for a couple more (14-oct-2011):
    1. Process to evaluate implementation oriented tools/toolkits
    2. Discuss the possible creation of a 'reference implementation’
    3. Criteria to use to determine quality/utility of implementation oriented tools – how do we know which tools to recommend/support/facilitate development
    4. What types of tasks and roles would use tools to aid in standards adoption and implementation