Page tree

Status: All
Creators: All Creation period Categories: All
Topic Status Author Like View Replies Creation date Last Reply Contributors Category
Discussion Retrieving Primitive/Fully defined concepts In discussion 0 View 1390 Comment 2 1573744682000 Nov 14, 2019 15:18 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Nov 15, 2019 03:27 2 Undefined
Discussion Executing maps - ECL or QL In discussion 0 View 1424 Comment 2 1573643690000 Nov 13, 2019 11:14 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Nov 15, 2019 04:12 2 Undefined
Question Non-redundant attributes in cardinality count Resolved 0 View 2822 Comment 6 1573564213000 Nov 12, 2019 13:10 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Jul 8, 2020 03:52 6 Undefined
Discussion URIs for provisional releases In discussion 1 View 1529 Comment 1 1549107729000 Feb 2, 2019 11:42 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Feb 12, 2019 03:51 1 Undefined
Discussion ECL and grouped attributes In discussion 0 View 7214 Comment 20 1546432749000 Jan 2, 2019 12:39 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Feb 12, 2019 11:19 20 Undefined
Discussion MRCM In discussion 0 View 5765 Comment 15 1545044955000 Dec 17, 2018 11:09 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Feb 6, 2023 14:00 15 Undefined
Question How can I write an ECL expression to match attribute names In discussion 0 View 1905 Comment 1 1515385505000 Jan 8, 2018 04:25 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Feb 10, 2019 23:04 1 Undefined
Discussion Comments in expressions In discussion 0 View 4297 Comment 12 1503843960000 Aug 27, 2017 14:26 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Aug 30, 2017 13:14 12 Undefined
Discussion Interpretation of cardinality of reverse attributes In discussion 0 View 3694 Comment 8 1494834771000 May 15, 2017 07:52 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) May 17, 2017 05:55 8 Undefined
Discussion Nesting / Sub-expressions in the ECL In discussion 0 View 5137 Comment 11 1475195419000 Sep 30, 2016 00:30 $date.format('yyMMddHHmm', $lastComment.getCreationDate()) Feb 7, 2017 03:39 11 Undefined
1 2 ... Next Last

Discussion summary

Questions 2 Discussions 10 Replies 95 Contributors 12

Contributors (12)

  • No labels

3 Comments

  1. Kai Kewley Alejandro Lopez Osornio All I would like to start a discussion about how to find all the reference sets that contain a given SNOMED code, but I no longer have permissions for the "Add discussion" button (smile) hence this comment.

    We can almost get there with current syntax:

    • ^[refsetId] * {{ M referencedComponentId = 404684003 }}

    But "refsetId" is not a valid Field Name.

    On the other hand, this is pretty obscure syntax, may have inherent poor performance, and thus it would be nice to have a more direct syntax for this.

    I am thinking we could use the '@' symbol for "contains" similarly to how the '^' symbol is used for "memberOf".  So, the above would just be:

    • @404684003


    1. I would like to second Michael’s suggestion of adding an easy way to find the set of reference sets that contain a given concept, as this is a feature that I have often “wished for” during refset maintenance. Perhaps there are some additional use cases? A few comments on Michael’s proposed syntax:

      • I would be a bit cautious about using the “@” symbol for this, given that this is also used by the template syntax to prefix a slot name (this may cause confusion when both are used within an expression template for different purposes).
      • I would like to throw a few other possible options into the virtual "ring" -  “? 404684003” or “^? 404684003” or “^R 404684003” (note: The last one meaning “ReverseOf memberOf”).
      • Would this operator be intended to be applied only to a single concept, or could it be applied to a subexpression constraint? E.g. ^? <404684003
      • The other difference between the briefer and fuller syntax (although I prefer the shorter syntax too!) is that the fuller syntax allows you to find a set of reference sets that contain the given value in columns/attributes other than the referencedComponentId e.g. "^[refsetId] * {{ M targetComponentId = 404684003 }}" Perhaps that's a slippery slope ... but I think it's worth noting the differences in expressivity between the two approaches. 
      1. Ah, I always forget about the template syntax (sad)

        1. I had actually thought about ^R as an option
        2. concept vs expression - I haven't really contemplated this
        3. Agree it's a slippery slope – I think we need to get input from implementers on the implementation cost / overheads