Roger, The web site www.veriquant.com gives a few more details, but not the low-level design information you are probably interested in. We can talk more about this privately if you are that interested and I can let you see what we currently have in action along with some low-level detail. There are a lot of ways to get it wrong. EAV frameworks are not easy to build from scratch. In my case I am overhauling our entire metadata system, going to version 2.0, as it were, not so much to improve performance as to improve the tooling and capacity to customize a single site and mix and merge different standard domains, independently developed, within a single system. One problem one can hit is how to maintain the metadata itself, let alone what it points to! But the rewards are real.
Searching on EAV/CR will yield a number of results by the authority Prakash Nadkarni I mentioned earlier. He does get down into some of the nitty gritty details. I've worked with him on editing and critiquing his latest manuscript and have differed with him at times. His manuscript and his JAMIA articles basically relate to two EAV databases he has been involved with, one involving clinical studies management, and the other a scientific neurological database (SenseLab) widely used by neuroscientists worldwide. Neither, however, involves EMR/EHR directly, and I would not simply adopt those designs whole for EMR/EHR. But you may still find him useful. I can put you directly in touch with him if you are interested. Thanks, Randy On Wed, Jun 8, 2011 at 6:03 AM, Roger Erens <roger.erens at e-s-c.biz> wrote: > On Wed, Jun 8, 2011 at 04:54, Randolph Neall <randy.neall at veriquant.com> > wrote: > > ... > > Some EAV designs are > > foolish and unusable. But others aren't. > > Thanks for your interesting explanation, Randy. Do you have some > examples or links available that may teach us unusable/usable designs? > > Roger > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110608/e0d922b7/attachment.html>
