Shared software implementationl aspects of OpenEHR/HL7 RIMBAA implementations

Like Laura, Ed, and others I do believe there are things that can be
learned by looking at the experiences of OpenEHR/HL7v3 implementations,
and by listening to the best practices of those implementers. So allow
me to interject the following invitation into the fray:

The RIMBAA HL7 Workgroup (see
http://wiki.hl7.org/index.php?title=RIMBAA) is effectively the HL7
Software Implementers community; and one with a special interest: the
use of the HL7 v3 reference model as a data model for in memory object
processing (business/service layer) and as a persistence model. RIMBAA
has the aim to document existing implementations, and not to discuss
theoretical issues.

Some of the implementers of RIMBAA style applications are also
implementers of CEN 13606 and/or OpenEHR, and they suggested that it
could be fruitful (given the location of the upcoming international HL7
meeting in Australia) to have a discussion on "shared challenges", in
order to re-use some of the implementation best practices discovered in
one community within the other community.

Software implementers have to deal with issues such as model driven
application development with templates/archetypes/DCMs, reference
model based persistence, GUI generation based on archetypes/templates
etc. If an HL7 RIMBAA software implementer reads something like
http://www.serefarikan.com/?p=97 there appear to be a lot of common
issues faced by both implementer communities.

*Note:* any discussion related to "modeling aspects" are explicitely out
of scope of the meeting. The intent is to soley focus on those issues
faced by software programmers and software architects that are faced
with the issue of having to support a complex reference model based
standard. However good or bad, they have to make it work.

The draft agenda of the Sydney meeting can be found here:
http://wiki.hl7.org/index.php?title=RIMBAA_201101_Agenda. It does
contain a list of suggested agenda items; I'm open to suggestions as to
other software implementation topics that are of interest to both
implementer communities, as well as to links to OpenEHR materials (wiki
or otherwise) that already exist which are related to the topics
mentioned on the agenda.

TTYL,

-Rene