2018-02-14 - SLPG Meeting
Date & Time
20:00 UTC Wednesday 14th February 2018
Teleconference Details
To join the meeting please go to https://snomed.zoom.us/j/471420169.
Further information can be found at SLPG meeting information
Goals
Progress SNOMED Query language
Attendees
Chair: Former user (Deleted)
Project Group: michael lawley, Rob Hausam
Apologies
Ed Cheetham, Daniel Karlsson
Agenda and Meeting Notes
Description | Owner | Notes |
|---|---|---|
Welcome and apologies | Former user (Deleted) |
|
Query Language | Former user (Deleted) | Examples of using LET ... IN ...
Examples of using ... FROM ...
|
| Q: What attributes are used by this set of concepts? | |
Former user (Deleted) | Using Language Reference Sets
| |
Confirm next meeting date/time | Former user (Deleted) | There will be NO meeting in 2 weeks, due to travel commitments Next meeting to be held at 20:00 UTC on Wednesday 14th March 2018 |
Comments
Thanks for letting us know Ed! Enjoy your evening!
Kind regards,
Linda.
The following shows how I've prototyped extending the ECL syntax to support simple filters.
Original ECL grammar rule
conjunctionExpressionConstraint = subExpressionConstraint 1*(ws conjunction ws subExpressionConstraint)
Updated and additional grammar rules:
conjunctionExpressionConstraint = subExpressionConstraint 1*(ws conjunction ws (subExpressionConstraint / filterExpression))
filterExpression = "{{" ws filter 1*(ws "," ws filter) ws "}}")
filter = filter_name filter_op filter_val
...
For filter_name, I've implemented "term", "moduleId", "effectiveTime", and both "definitionStatus" and "definitionStatusId".
Thanks Michael! Very useful.
Have you used "C" and "D" prefixes for the filter names, or just assumed that moduleId and effectiveTime refer to the concept?
I suggest that we should focus on language refsets next, in terms of defining searches over preferred and acceptable terms in a given language/dialect.
Kind regards,
Linda.
At the moment the only things my filters act on are concepts, so no need for "C" etc. and "term" for us means "all known label for the concept". This includes things like the conceptId itself as well as descriptionIds.
Apologies Linda, all
I shall not be able to attend this call.
Kind regards
Ed