Difference between revisions of "Reasons for RIMBAA"

From HL7Wiki
Jump to navigation Jump to search
(New page: category:RIMBAA IssueWhat are the (business) reasons as to why one should embrace RIMBAA? *As a starter: see [http://www.theenterprisearchitect.eu/archive/2009/11/25/15-reasons-w...)
 
Line 1: Line 1:
 
[[category:RIMBAA Issue]]What are the (business) reasons as to why one should embrace [[RIMBAA]]?
 
[[category:RIMBAA Issue]]What are the (business) reasons as to why one should embrace [[RIMBAA]]?
  
 
+
#RIMBAA results in software being less sensitive to changes in terms of scope: if one adds new functionality, or new domains - the RIM is a uniform model accross all healthcare domains.
*As a starter: see [http://www.theenterprisearchitect.eu/archive/2009/11/25/15-reasons-why-you-should-start-using-model-driven-development this MDD whitepaper] and replace '[[MDD]]' with 'RIMBAA'.
+
#RIMBAA enables enhanced, granular decision support (and: Business Intelligence).
*In addition to those reasons: "RIMBAA enables enhanced, granular decision support" and "RIMBAA decreases the cost of implementing decision support" and for each of these you can substitute "Business Intelligence" for "decision support".
+
#RIMBAA decreases the cost of implementing decision support (and: Business Intelligence).
 +
#RIMBAA preserves the full semantics (no translations) if one uses [[MDD]] based on constrained RIM-based models (e.g. CDA, or an R-MIM)
 +
#RIMBAA results in software being less sensitive to technology changes. Given the model, it would be easier to port an application to a new language or platform.

Revision as of 11:05, 31 July 2011

What are the (business) reasons as to why one should embrace RIMBAA?

  1. RIMBAA results in software being less sensitive to changes in terms of scope: if one adds new functionality, or new domains - the RIM is a uniform model accross all healthcare domains.
  2. RIMBAA enables enhanced, granular decision support (and: Business Intelligence).
  3. RIMBAA decreases the cost of implementing decision support (and: Business Intelligence).
  4. RIMBAA preserves the full semantics (no translations) if one uses MDD based on constrained RIM-based models (e.g. CDA, or an R-MIM)
  5. RIMBAA results in software being less sensitive to technology changes. Given the model, it would be easier to port an application to a new language or platform.