This wiki has undergone a migration to Confluence found Here
Difference between revisions of "RIMBAA Mission and Charter"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 10: | Line 10: | ||
The RIMBAA Work Group will: | The RIMBAA Work Group will: | ||
| − | *provide a joint forum for HL7 members who are interested in, planning to create, RIM based applications and/or messaging interfaces. | + | *provide a joint forum for HL7 members who are interested in, planning to create, RIM based applications and/or messaging interfaces. This forum will allow for the exchange of the various approaches that have already been implemented though out the world. |
*create a best practices document which describes the approaches to take when one designs a new RIM based application, as well as the situation in which one or more of the layers of an application are legacy and can not be re-designed. | *create a best practices document which describes the approaches to take when one designs a new RIM based application, as well as the situation in which one or more of the layers of an application are legacy and can not be re-designed. | ||
| − | *support third parties in the creation of, and maintenance of, software toolkits that support the development of RIM based applications. | + | *support third parties in the creation of, and maintenance of, software toolkits that support the development of RIM based applications. |
| + | *provide feedback from the implementation community into the standards development process, especially in areas where the standard lacks functionality or clarity of documentation. | ||
==Formal Relationships With Other HL7 Groups== | ==Formal Relationships With Other HL7 Groups== | ||
Revision as of 17:29, 13 May 2010
RIMBAA WG
Contents
Mission
The mission of the RIM Based Application Architecture (RIMBAA) Work Group is to facilitate the adoption and implementation of the HL7 version 3 RIM. The focus lies particularly on the use of the RIM for application and database design; and to a lesser degree on the implementation of messaging interfaces.
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 and databases. This has the advantage that it saves time and resources by not having to design new one-off application frameworks and databases.
Charter
The RIMBAA Work Group will:
- provide a joint forum for HL7 members who are interested in, planning to create, RIM based applications and/or messaging interfaces. This forum will allow for the exchange of the various approaches that have already been implemented though out the world.
- create a best practices document which describes the approaches to take when one designs a new RIM based application, as well as the situation in which one or more of the layers of an application are legacy and can not be re-designed.
- support third parties in the creation of, and maintenance of, software toolkits that support the development of RIM based applications.
- provide feedback from the implementation community into the standards development process, especially in areas where the standard lacks functionality or clarity of documentation.
Formal Relationships With Other HL7 Groups
- The RIMBAA Work Group will work with the Tooling Work Group to share experiences and best practices in those areas where the Tooling Roadmap overlaps with the scope of RIMBAA.
Decision Making Practices
Date of Last Revision
June 12, 2008
