It is a generic problem that impacts OpenEHR also. Present systems need a lot of implicit human knowledge in order to interpret the data safely and fully. SNOMED pre-corodination is one way to make this implicit knowledge explicit. It possibly is a solution. My point is that it is not the best solution. Not only do we need to make more of the implicit knowledge explicit but use archetype structures/patterns to define the full context/epistemology in a Standardised, shared way.
Existing systems use a myriad number of ways to store health and administrative data. This demands specific requirements to be met. Systems of the future have other additional requirements that impact archetype patterns and the standard way of using coding systems. Gerard Freriks +31 620347088 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 3 Apr 2018, at 10:06, Pablo Pazos <pablo.pa...@cabolabs.com> wrote: > > Check the initial messages on the thread. > > Basically how to use SNOMED in openEHR, and in a specific area: data > querying. AQL support for SNOMED codes and expressions was an initial part of > the topic. > > We are trying to solve a basic problem: how to get data out the systems in a > smart way. This is because archetypes are good but don't have context that > terminologies have, and AQL is good but only queries what is defined by > models. So we need something to query over terminologies in combination with > querying over models. Reasoning, interpretation and modeling approaches are > other orthogonal problems. > > This is a very specific problem for the openEHR specs and ITS, is not a > general problem to solve.
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
