Graham, There can not be one model (or model of systems) that does it all in a perfect way. We must agree that it is best to leave every domain with its own problems and models that help solve it. We must have a standard way to deal with it.
About what is needed for EN13606 (a formal European standard and Nationale one in all Member States) I do not know for certain. On one hand everything in the EHRcom extract traveling between systems will be resolved completely. No dependence on services somewhere (or not) in between. But this holds for legacy systems, as we know them. What we want, and expect to happen, is that those old legacy systems are replaced by OpenEHR conformant (EN13606 conformant) systems. Then the rules will be different, because without several standardised services used by EHR-systems of the future we can not build the systems of the future.. Provided that those services are based on (European) Standards, no doubt. Gerard -- <private> -- Gerard Freriks, MD Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252544896 M: +31 620347088 E: gfrer at luna.nl Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 On 7-mrt-2007, at 0:03, Grahame Grieve wrote: > I have some sympathy for this. I have been tempted to toast the > qualifier > and push everything into code as you guys have done, for the same > reasons. > But I haven't found any case where the existing qualifier syntax is a > problem, and there is accepted requirements for originalText on the > qualifiers (at least, HL7 has accepted them). SO I didn't toast it, > but > I did say in the openEHR mapping that you'd collapse the qualifiers > into > the code phrase. I don't have a strong feeling for whether this > would be > necessary or appropriate for 13606 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070307/2ca08552/attachment.html> -------------- next part -------------- _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
