Difference between revisions of "Reasons for RIMBAA"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
[[category:RIMBAA Issue]]What are the (business) reasons as to why one should embrace [[RIMBAA]]?
+
[[category:Closed AID 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.
 
#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.

Latest revision as of 08:18, 25 March 2015

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.