This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 11: | Line 11: | ||
*[[:category:RIMBAA Issue|List of RIMBAA Issues]] | *[[:category:RIMBAA Issue|List of RIMBAA Issues]] | ||
*[[Template RIMBAA Issue|Template for creation of a new RIMBAA issue]] | *[[Template RIMBAA Issue|Template for creation of a new RIMBAA issue]] | ||
| + | *[[Implementation FAQ|HL7 v3 Implementation FAQ]] | ||
*[[RIMBAA: Java based Reference Implementation|Java based reference implementation]]: The RIMBAA working group creates and maintains a JAVA based reference implementation which serves as both a tool in aid of the development of RIM based applications, as well as an example of an application in which the internal as well as the persistence layers are completely RIM based. The implementation and documentation can be found at [http://aurora.regenstrief.org/javasig/wiki http://aurora.regenstrief.org/javasig/wiki] | *[[RIMBAA: Java based Reference Implementation|Java based reference implementation]]: The RIMBAA working group creates and maintains a JAVA based reference implementation which serves as both a tool in aid of the development of RIM based applications, as well as an example of an application in which the internal as well as the persistence layers are completely RIM based. The implementation and documentation can be found at [http://aurora.regenstrief.org/javasig/wiki http://aurora.regenstrief.org/javasig/wiki] | ||
Revision as of 19:41, 15 May 2010
The RIM Based Application Architecture working group (RIMBAA) serves as a focus for those who are interested in using RIM based information models for application and database design, and to promote the development of HL7 Version 3-compliant applications. The benefits of RIM based applications are not limited to accepting and creating ITS platform specific RIM based messages and documents. The RIM can be used as a universal model for designing both applications (Model Driven Software Development, MDD) and databases. This has the advantage that it saves time and resources by not having to design new one-off application frameworks and databases.
- See also: RIMBAA Mission and Charter, RIMBAA in the HL7 Roadmap, SWOT, and Goals & Three Year Plan, Java reference implementation in GForge. RIMBAA is part of the HL7 Foundation and Technology steering division.
Agendas / Action Items
- Action Items
- Agenda for the WGM in Rio (May 2010); out-of-cycle meeting in Rome, Italy (September 2010); WGM in Cambridge USA (October 2010); out-of-cycle meeting in London (November 2010), and WGM in Sydney, Australia (January 2011)
Talking points/issues
- List of RIMBAA Issues
- Template for creation of a new RIMBAA issue
- HL7 v3 Implementation FAQ
- Java based reference implementation: The RIMBAA working group creates and maintains a JAVA based reference implementation which serves as both a tool in aid of the development of RIM based applications, as well as an example of an application in which the internal as well as the persistence layers are completely RIM based. The implementation and documentation can be found at http://aurora.regenstrief.org/javasig/wiki
See also
- RIMBAA Technology Matrix
- List of RIMBAA based applications with detailed descriptions.
Minutes
- See list of RIMBAA Meeting Minutes for the wiki version of the minutes. The formal minutes can be found on the RIMBAA WG page on the HL7.org website.
- Minutes of the last 3 RIMBAA meetings:
- Minutes of the out-of-cycle RIMBAA meeting in Amsterdam (March 2010)
- Minutes of the Phoenix WGM (January 2010)
- Minutes of the out-of-cycle RIMBAA meeting in Amsterdam (Oct. 2009)
