Birger, you are in the right path. We do something similar to your proposal in LinkEHR, when working with transformations of data. we developed several functions to gain access to the archetype ontology and metadata while processing data instances, such as getText(atNNNN, LANG), getDescription( atNNNN, LANG), getTermBinding(atNNNN)... Sometimes they are useful while working with data instances. And the same is applied to AQL.
In my opinion, it would be interesting to study adding add a set of such functions to AQL, to be available in any implementation. They would help to interact with the archetype structure and metadata properly. El jue., 6 sept. 2018 a las 11:43, Birger Haarbrandt (< birger.haarbra...@plri.de>) escribió: > Hi Ian, > > it's likely I am just plainly wrong here (or just only a little bit), so > let me elaborate and find out :) > > My understanding is: there are some archetypes with terminology bindings > on element level, for example the blood pressure archetype. When I am > creating a composition based on the definition described in the archetype, > I store the measured values, e.g. for the element systolic blood pressure. > This systolic blood pressure Element has a terminology binding to SNOMED > ([SNOMED-CT(2003)::163030003). However, I think in reality there is hardly > an implementation that explicitly puts this SNOMED code into the name field > of this element within a composition for every single measurement (what is > the added information?). However, if you want to retrieve data, you might > like to use SNOMED codes (or any other terminology) to *identify the > paths* that match your code (this is how I understood the question of > Georg). > > Even when you had all the codes put into your compositions, AQL would > still not be able to find out to which path this belongs, you need to be > explicit about the technical path. > > To my knowledge, there is no way to use the terminology bindings defined > on the archetype or template (say "metadata") level to retrieve data from > compositions using AQL, if they are not explicitly stored in the particular > instances of elements (e.g. the name attribute) within a composition (which > I feel would be sort of a redundant information as the semantics of the > element in the path should be invariant and are already defined in the > archetype). > > > Hence, what I have in mind is a look-up of all elements with a matching > terminology binding that provides the candiate paths which will then allow > to build your AQL query. > > Best, > > -- > > > > *Birger Haarbrandt, M. Sc. Peter L. Reichertz Institut for Medical > Informatics (PLRI) Technical University Braunschweig and Hannover Medical > School Software Architect HiGHmed Project * > Tel: +49 176 640 94 640, Fax: +49 531/391-9502 > birger.haarbra...@plri.de > www.plri.de > > > > Am 06.09.2018 um 10:43 schrieb Ian McNicoll: > > Hi Georg, > > I'm about to slightly disagree with Birger (or at least clarify!!) but it > is taking me longer and I need to be offline for a bit!! Watch this space! > > It is definitely possible to search on SNOMED terms both on the name and > value attributes of the Element. What is more tricky is using the > subsumption capablities of a terminology like SNOMED *(which is what I > think Birger was saying). - that requires coordination between AQL and the > underlying terminology server. This has been done by individual > implementers but not in a generic way to date. > > Back soon with more details!! > > > Ian > > > Dr Ian McNicoll > mobile +44 (0)775 209 7859 > office +44 (0)1536 414994 > skype: ianmcnicoll > email: i...@freshehr.com > twitter: @ianmcnicoll > > > Co-Chair, openEHR Foundation ian.mcnic...@openehr.org > Director, freshEHR Clinical Informatics Ltd. > Director, HANDIHealth CIC > Hon. Senior Research Associate, CHIME, UCL > > > On Thu, 6 Sep 2018 at 09:21, Georg Fette <georg.fe...@uni-wuerzburg.de> > wrote: > >> Hello, >> In AQL it is possible to constrain the value of a node to one of the >> codes that are allowed for that value (as specified in the respective >> archetype). >> To find patients with gender (snomed-ct:248153007) male >> (snomed-ct:248153007) I could write something like this: >> >> SELECT e FROM EHR e CONTAINS DEMOGRAPHICS d >> >> WHERE d.items[at0017].value = 'snomed-ct:248153007' >> >> >> Is it possible to identify the node of an archetype instead of its path >> parts (e.g. d.gender or d.items[at0017]) also with a terminology code, so >> the query would rather look like something like that: >> >> SELECT e FROM EHR e CONTAINS DEMOGRAPHICS d >> >> WHERE d.items['snomed-ct:263495000'].value = 'snomed-ct:248153007' >> >> >> I am not very experienced with AQL so the queries are probably already >> syntactically wrong. >> Greetings >> Georg >> >> -- >> --------------------------------------------------------------------- >> Dipl.-Inf. Georg Fette Raum: B001 >> Universität Würzburg Tel.: +49-(0)931-31-85516 >> Am Hubland Fax.: +49-(0)931-31-86732 >> 97074 Würzburg mail: georg.fe...@uni-wuerzburg.de >> --------------------------------------------------------------------- >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical@lists.openehr.org >> >> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >> > > > _______________________________________________ > openEHR-technical mailing > listopenEHR-technical@lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- David Moner Cano Web: http://www.linkedin.com/in/davidmoner Twitter: @davidmoner Skype: davidmoner
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
