See below.
Gerard Freriks +31 620347088 [email protected] Kattensingel 20 2801 CA Gouda the Netherlands > On 6 Sep 2018, at 10:42, Thomas Beale <[email protected]> wrote: > > > In openEHR as it stands now, the answer would be no, because the > snomed-ct:263495000 code is just one binding to at0017. What is reliable in > the data is the at0017 internal code. > Exactly. For the data inside an EHR system the at0017 code is essential, the key thing. But in terms of what it means for interpretation by humans and ‘intelligent’ services the SNOMED code is the key thing. In essence OpenEHR/13606 binds Codes from Reference Terminologies to archetype/template structures inside EHR systems and messages or documents. > In future, it is not out of the question that different types of OPTs would > be generated that would treat bound terminology codes as if they were the > structural ones, but this is probably a long way off. Some further ideas > about this in the ADL2 spec > <https://www.openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_terminology_integration>, > and also the OPT2 spec > <https://www.openehr.org/releases/AM/latest/OPT2.html>. > > It also might not be hard to preprocess AQL queries written like this into > the standard form, but that would require that the code snomed-ct:263495000 > be bound uniquely to at0017, and no other node code e.g. at0015. So doing > this would require stricter binding rules than we currently have, and which I > think are not semantically justifiable. > > - thomas > >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
