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

Difference between revisions of "AID Action Items"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
This page contains a mixture of action items of the RIMBAA WG and the Dutch RIMBAA SIG (part of HL7 Netherlands).
 
This page contains a mixture of action items of the RIMBAA WG and the Dutch RIMBAA SIG (part of HL7 Netherlands).
 +
 +
===Implementation FAQ===
 +
*The [[Implementation FAQ]] page is one of the most visited pages on the Wiki. It does contain some basic information created in 2006. It needs updating, merging, and references to RIMBAA issue pages.
  
 
===GForge update===
 
===GForge update===

Revision as of 15:30, 11 February 2010

This page contains a mixture of action items of the RIMBAA WG and the Dutch RIMBAA SIG (part of HL7 Netherlands).

Implementation FAQ

  • The Implementation FAQ page is one of the most visited pages on the Wiki. It does contain some basic information created in 2006. It needs updating, merging, and references to RIMBAA issue pages.

GForge update

  • 201002 Rene: Aproach HQ to change contents of RIMBAA/JavaSIG project page on GForge to be a reference to the latest sources of the Java SIG RIMBAA reference implementation

Get TSC apporval for September/November out-of-cycle meetings

  • 201001 Rene: to fill in the forms, and get approval of out-of-cycle meetings via Lynn at HQ.

RIMBAA in SAEAF

  • 200912 Michael vd Zel to create a SAEAF matrix showing the areas covered/addressed by the RIMBAA WG. The resulting matrix is to be published on the wiki.

HIST datatype as a UDT

  • Willem Dijkstra: have not implemented this (HXIT/HIST) as a UDT - Willem to research the option to see if this would be feasable.

Communication Plan

  • 20091027 create a communications plan, akin to the one created by the ArB

SQL for datatypes spec

  • 20091027 would be nice to have a standard SQL definition for use of HL7 datatypes. Could attempt to standardize SQL across the board.

Whitepaper RIM approach

  • 20090203 Rene: to create (to act as editor) whitepaper to show benefits (to "market") of RIM-approach vs. one-off model solutions for individual issues. Target audience: developers, OR physicians (would lead to use of different arguments). Physicians: re-use of componets, research uses the samen samentic models as used anywhere.
  • See Reasons for RIMBAA

AP to RP cell transition