> I just care about getting one model.... In the case of 13606 one good model that describes a generic interface for EHR communication, also, for communication with other proprietary EHR solutions. In the case of openEHR one good model that describes one particular implementation of an EHR-system.
This difference is something the EN1366 Association cares about. Gerard Freriks EN13606 Association p/a Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands M: +31 620347088 E: gerard.freriks at EN13606.org W: http:www.en13606.org On 4 Oct 2012, at 00:02, Thomas Beale wrote: > On 13/09/2012 10:15, David Moner wrote: >> Hi, >> >> 2012/9/13 Erik Sundvall <erik.sundvall at liu.se> >> It would be great if e.g most of the future ISO 13606 version could be a >> true subset of openEHR instead of the current confusing situation. >> >> This is something I discussed with Thomas some time ago, it would be one of >> the best harmonisation solutions, but probably with a slightly different >> interpretation. Since 13606 has more generic classes (eg. the generic ENTRY >> can represent all of OBSERVATION, EVALUATION, INSTRUCTION, ACTION), instead >> of 13606 being a subset of openEHR I think that openEHR should be a >> specialized model of 13606. Obviously this would require a deep analysis and >> changes of the models, but that could be the idea. > > I don't care about the linguistics of subset / specialisation etc, I just > care about getting one model.... > > - thomas Gerard Freriks +31 620347088 gfrer at luna.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20121004/846345bc/attachment.html>
