This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "RIMBAA Tooling Liaison"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
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]] (renamed from Implementation Tooling 17-jan-2012 San Antonio WGM)
**FWIW: Implementation tools that RIMBAA has identified include:
+
*HL7 Tools list
***MIF based class/code generators (e.g. MDHT. Everest)
+
**http://www.hl7.com.au/HL7-Tools.htm
***MIF based database schema generator (e.g. MGRID)
+
**''others?''
***MIF based UI component generators
+
*Should the Project Scope Statement (PSS) be adjusted
***ISO Datatypes library (R1/RFH(FHIR)-datatypes)
+
**Add category for tool:
***CTS products
+
***help develop standards (e.g. RMIM Designer, RMIMs)
***Mapping tools
+
***help use standards (EHR Profile Tool, EHR-S FM)
***(Not a tool: MIF documentation, currently lacking)
+
***implement standards (class library Marc-Hi Everest datatypes)
**Tools that support implementation
 
***Testing tools (e.g. Instance Editor, MDHT)
 

Latest revision as of 17:32, 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
  • Tools for RIM based software development (renamed from Implementation Tooling 17-jan-2012 San Antonio WGM)
  • HL7 Tools list
  • Should the Project Scope Statement (PSS) be adjusted
    • Add category for tool:
      • help develop standards (e.g. RMIM Designer, RMIMs)
      • help use standards (EHR Profile Tool, EHR-S FM)
      • implement standards (class library Marc-Hi Everest datatypes)