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) (Version as approved on June 12, 2008) |
Rene spronk (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
==Mission== | ==Mission== | ||
| − | The mission of the RIM Based Application Architecture (RIMBAA) Work Group is to | + | 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 serializations for the purpose of interoperability (e.g. messages, services, documents). |
| − | 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 | + | 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 advantages of: |
| + | #it saves time and resources by not having to design new one-off data models for applications and databases. | ||
| + | #not having to develop and support different databases and interfaces between systems for different healthcare domains - all healthcare domains can be represented and integrated using one single ISO standard information model. | ||
==Charter== | ==Charter== | ||
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 | + | *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 through 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. | ||
| − | * | + | *identify and support third parties in the design, development and maintenance of software toolkits that support the development of RIM based applications and databases. |
| + | *provide feedback from the implementation community into the standards development process, especially in areas where the standard lacks functionality or clarity of documentation. | ||
| − | == | + | ==Relationships With Other HL7 Groups== |
| − | The RIMBAA Work Group will work with the | + | The RIMBAA Work Group will work with the Tooling, SOA and Vocabulary Work Group to share experiences and best practices where the scope of these groups overlaps with the scope of RIMBAA. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Decision Making Practices== | ==Decision Making Practices== | ||
| − | [http://www.hl7.org/ | + | [http://www.hl7.org/library/committees/java/RIMBAA%20WG%20DMP%20v20.doc Decision Making Practices] |
==Date of Last Revision== | ==Date of Last Revision== | ||
| − | + | May 17, 2010 | |
Revision as of 17:43, 18 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 serializations for the purpose of interoperability (e.g. messages, services, documents).
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 advantages of:
- it saves time and resources by not having to design new one-off data models for applications and databases.
- not having to develop and support different databases and interfaces between systems for different healthcare domains - all healthcare domains can be represented and integrated using one single ISO standard information model.
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 through 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.
- identify and support third parties in the design, development and maintenance of software toolkits that support the development of RIM based applications and databases.
- provide feedback from the implementation community into the standards development process, especially in areas where the standard lacks functionality or clarity of documentation.
Relationships With Other HL7 Groups
The RIMBAA Work Group will work with the Tooling, SOA and Vocabulary Work Group to share experiences and best practices where the scope of these groups overlaps with the scope of RIMBAA.
Decision Making Practices
Date of Last Revision
May 17, 2010
