|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 2:40 AM
Points: 191,
Visits: 97
|
|
Though wary of re-igniting the discussion (informative and lively though it has been), I wonder how this relates to the HL7 RIM model (look up RIMBAA) - as I (only partially) understand it this is using the RIM approach, EAV-like, for the data persistence as well as message definition. Have people used the RIM approach and if so, how did it work in practice? I have a system to design that won't directly be using healthcare data (so no HL7 use as such) - would anyone recommend for or against using a RIMBAA approach?
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 7:23 AM
Points: 1,164,
Visits: 3,334
|
|
keith.fearnley (2/20/2013) Though wary of re-igniting the discussion (informative and lively though it has been), I wonder how this relates to the HL7 RIM model (look up RIMBAA) - as I (only partially) understand it this is using the RIM approach, EAV-like, for the data persistence as well as message definition. Have people used the RIM approach and if so, how did it work in practice? I have a system to design that won't directly be using healthcare data (so no HL7 use as such) - would anyone recommend for or against using a RIMBAA approach? RIMBAA, is that just a proposal for how to model a healthcare related data warehouse, or an operational database?
"Wise people understand the 10,000 things without going to each one. They know them without having to look at each one, and they transform all without acting on each one." - The Tao Te Ching: Verse 47
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: 2 days ago @ 2:40 AM
Points: 191,
Visits: 97
|
|
| I might be getting the wrong end of the stick, but I interpret it as an approach using the RIM design as a working database design - expressing it in SQL Server.
|
|
|
|