February 20, 2013 at 8:00 am
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?
February 20, 2013 at 9:08 am
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?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 20, 2013 at 9:12 am
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.
Viewing 3 posts - 61 through 62 (of 62 total)
You must be logged in to reply to this topic. Login to reply