Two remarks, just some thoughts that occur to me in this discussion. First, datamodel re-use like in inheritance is a technical approach, it is not proven that it will always be good from a medical-informatics point of view. So it should not be a leading principle in design. It is just handy for developers if it can be used. A user of a system is not aware of these principles, but may have requirements which do not necessarily fit inside a closed technical approach.
Second, designing for real practice on a global base sounds megalomaniac. It sounds like carrying the world on ones shoulder, which is quite some weight. I think it is better to accept that there are other good ways too, and one should find solutions to cooperate instead of thinking that ones system is good for every purpose. I think that this is a weakness in as well OpenEHR as also MLHIM. I like the Chinese saying: Let thousand flowers bloom. Bert Verstuurd vanaf mijn iPad Op 7 apr. 2013 om 00:50 heeft Thomas Beale <thomas.beale at oceaninformatics.com> het volgende geschreven: > > [This is Tim again, initially bounced] > >> And that is the issue, and what is at the root of this dispute. Tim does not >> see the point of specialization or redefinition, which, in my opinion, is >> why he can hold forth so strongly for XML. >> >> Randy Neall > You are mostly correct. It isn't that I don't think that re-use is a > good idea. The knowledge modellers and developers are telling us by > their actions that do not want to participate in the top-down, maximal > data model approach. As I have said many times, for many years; it is > a wonderfully engineered eco-system. Now we know, it just doesn't work > in real practice on a global basis. > > So that had to change. Add in some other simplifications in the RM and > openEHR turns into MLHIM. My goal is to encourage multi-level > modelling to solve the semantic interoperability issue. Whatever > acronym you want to tie to it. > > I know that MLHIM isn't perfect, but it is designed with agility and > data durability in mind. > > --Tim > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130407/e90f9e49/attachment.html>
