2018-06-06 - SLPG Meeting

Date & Time

20:00 UTC Wednesday 6th June 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
- Discuss use of multiple language reference sets
URI standard
- URI for canonical normal form
- URI for necessary (long/short) normal form
Future goals:
- Transitive relationships in ECL
- Ability to execute maps from within ECL

Attendees

Chair: @Former user (Deleted)
Project Group: @michael lawley, @Ed Cheetham, @Rob Hausam

Apologies

@Anne Randorff Højen

Agenda and Meeting Notes

Description	Owner	Notes

Description	Owner	Notes
Welcome and apologies	@Former user (Deleted)
Query Language - Recap from previous meetings	@Former user (Deleted)	Examples: version and language << 64572001 \|Disease\| {{ term = "heart" }} VERSION http://snomed.info/sct/900000000000207008/version/20180131 << 64572001 \|Disease\| {{ synonym = "heart" }} VERSION http://snomed.info/sct/900000000000207008/version/20180131 << 64572001 \|Disease\| {{ FSN = "heart" }} VERSION http://snomed.info/sct/900000000000207008/version/20180131 << 64572001 \|Disease\| {{ FSN = "heart" }} VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE W << 64572001 \|Disease\| {{ preferredTerm = “heart”}} VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE Y << 64572001 \|Disease\| {{ acceptableTerm = “heart”}} VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE Y (* {{ term = "heart" }} VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE Z) MINUS (* {{ term = "heart" }} VERSION http://snomed.info/sct/900000000000207008 /version /20170731, LANGUAGE W) X MINUS Y WHERE X = * , Y = (* {{ term = "heart" }}) VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE W Notes Allow nested where, version, language Scope of variables is inner query
Query Language - Recap from previous meetings		Examples: where X MINUS >! X WHERE X = (<< 1234 : 5678 = << 6547) X MINUS >! X WHERE X = (<< 1234 : 5678 = << 6547) VERSION http://snomed.info/sct/900000000000207008/version/20180131 X MINUS >! Y WHERE X = (<< 1234 : 5678 = << 6547), Y = (<< 1456) VERSION http://snomed.info/sct/900000000000207008/version/20180131 X MINUS >! X WHERE X = (<< 1234 : 5678 = << 6547) VERSION http://snomed.info/sct/900000000000207008/version/20180131 , LANGUAGE 900000000000508004 \|GB English\| X MINUS >! X WHERE X = (<< 1234 : 5678 = << 6547) VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE 999001881000000108\|GB clinical extension LRS\|, 900000000000508004 \|GB English\| X minus >! X WHERE X = ( < M WHERE M = (< 1234))) VERSION http://snomed.info/sct/900000000000207008/version/20180131, LANGUAGE 999001881000000108\|GB clinical extension LRS\|, 900000000000508004 \|GB English\| Notes Allow nested variable definitions, but recommend that people don't due to readability Scope of variables is the inner query No recursion e.g X WHERE X = 1234 MINUS X ie can't use a variable in its own definition ie X is only known on the left of the corresponding WHERE, and not on the right of the WHERE
Query Language - Recap from previous meetings	@Former user (Deleted)	What filter keywords will we introduce for Term-based searching, and what are their exact meanings? D.term D.term = "heart" D.term = wild:"heart" D.term = regex:".heart." D.term = match:"hear att" D.term = (sv) wild: "heart" D.languageCode D.languageCode = "en" D.languageCode = "es" D.caseSignificanceId D.caseSignificanceId = 900000000000448009 \|entire term case insensitive\| D.caseSignificanceId = 900000000000017005 \|entire term case sensitive\| D.caseSignificanceId = 900000000000020002 \|only initial character case insensitive\| D.caseSignificance D.caseSignificance = "insensitive" D.caseSignificance = "sensitive" D.caseSignificance = "initialCharInsensitive" D.typeId D.typeId = 900000000000003001 \|fully specified name\| D.typeId = 900000000000013009 \|synonym\| D.typeId = 900000000000550004 \|definition\| D.type D.type = "FSN" D.type = "fullySpecifiedName" D.type = "synonym" D.type = "textDefinition" D.acceptabilityId D.acceptabilityId = 900000000000549004 \|acceptable\| D.acceptabilityId = 900000000000548007 \|preferred\| D.acceptability D.acceptability = "acceptable" D.acceptability = "preferred" Additional Syntactic Sugar FSN FSN = "heart" D.term = "heart", D.type = "FSN" D.term = "heart", D.typeId = 900000000000003001 \|fully specified name\| FSN = "heart" LANGUAGE X D.term = "heart", D.type = "FSN", D.acceptability = LANGUAGE X D.term = "heart", D.typeId = 900000000000003001 \|fully specified name\|, acceptabilityId = LANGUAGE X synonym synonym = "heart" D.term = "heart", D.type = "synonym" D.term = "heart", D.typeId = 900000000000013009 \|synonym\| synonym = "heart" LANGUAGE X D.term = "heart", D.type = "synonym", D.acceptability = LANGUAGE X D.term = "heart", D.typeId = 900000000000013009 \|synonym\|, (D.acceptabilityId = 900000000000549004 \|acceptable\| OR D.acceptabilityId = 900000000000548007 \|preferred\|) LANGUAGE* X synonymOrFSN synonymOrFSN = "heart" synonym = "heart" OR FSN = "heart" D.term = "heart", (D.type = "synonym" OR D.type = "fullySpecifiedName") synonymOrFSN = "heart" LANGUAGE* X synonym = "heart" OR FSN = "heart" LANGUAGE X D.term = "heart", (D.type = "synonym" OR D.type = "fullySpecifiedName"), D.acceptability = LANGUAGE X textDefinition textDefinition = "heart" D.term = "heart", D.type = "definition" D.term = "heart", D.typeId = 900000000000550004 \|definition\| textDefinition = "heart" LANGUAGE X D.term = "heart", D.type = "definition", D.acceptability = LANGUAGE X D.term = "heart", D.typeId = 900000000000550004 \|definition\|, D.acceptabilityId = LANGUAGE X Unacceptable Terms (D.term = "heart") MINUS (D.term = "heart", (D.acceptability = "acceptable" OR D.acceptability = "preferred") LANGUAGE X)
Query Language - Combining language reference sets	@Former user (Deleted)	How do we support language preferences, which are defined over multiple language reference sets? For example: LRSs that use the same Language tend to use 'Addition' - i.e. child LRS only includes additional acceptable terms, but can override the preferred term E.g. Regional LRS that adds local dialect to a National LRS E.g. Specialty-specific LRS E.g. Irish LRS that adds local preferences to the en-GB LRS 99999900 \|Irish language reference set\| PLUS \|GB English reference set\| LRSs that define a translation to a different language tend to use 'Replacement' - i.e. child LRS replaces set of acceptable and preferred terms for any associated concept E.g. Danish LRS that does a partial translation of the International Release 999999 \|Danish language reference set\| ELSE \|GB English reference set\|
URI Specification	@Former user (Deleted)	Status update URLs for canonical necessary normal form and necessary (long/short) normal form Necessary normal form (short) - http://snomed.org/snf, http://snomed.org/snform Necessary normal form (long) - http://snomed.org/lnf, http://snomed.org/lnform Canonical normal form (short) - http://snomed.org/cnf, http://snomed.org/cnform Close to user form - http://snomed.org/ctuf, http://snomed.org/ctuform Next Meeting: Recap on purpose of SNOMED CT computable language URIs? Recap on language instance URIs (e.g. URIs for expressions and expression constraints)
Other topics	@Former user (Deleted)	Other topics for discussion. For example: Query language - Can we de-scope relationship filters? ECL suggestions - Ability to execute maps in ECL The specific use-case here comes initially from Jeremy and relates to being able to work with inactive concepts via the historical association maps. For example, given an ECL expression, e, that identifies a set of concepts to be used for retrieving patient records, you probably also want to retrieve records for sameAs(e) and replacedWith(e)
Confirm next meeting date/time	@Former user (Deleted)	The next SLPG meeting will be held in 2 weeks at 20:00 UTC on Wednesday 4th July.

	File	Modified

No files shared here yet.