2017-08-30 - SLPG Meeting

2017-08-30 - SLPG Meeting

Date & Time

20:00 UTC Wednesday 30th August 2017

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

  • Review proposed format for results sets of ECL examples

  • Discuss further requirements for update to URI standard

  • Discuss implications of potential DL enhancements and other outstanding questions

  • Review proposed Query language examples

Attendees 

  • Chair: @Former user (Deleted)

  • Project Group: @Ed Cheetham@Former user (Deleted)@Former user (Deleted)@Andrew Perry@Brian Carlsen@Former user (Deleted), @Rob Hausam@Daniel Karlsson@Anne Randorff Højen

Apologies

@michael lawley

Agenda and Meeting Notes



Description

Owner

Notes

Description

Owner

Notes

Welcome and apologies

@Former user (Deleted)

  • Business meeting in Bratislava

  • Comments in Compositional Grammar

Result sets for ECL examples

@Former user (Deleted)

  • Review proposed format for result sets of ECL examples

    • Agree on file naming scheme for each file type

      • xres2_ECL(v1.3)_6.1.3.1-ExpresionConstraint_INT_20170817.ecl

      • xres2_ECL(v1.3)_6.1.3.1-Result(INT-20170731)_INT_20170817.txt

      • xres2_ECL(v1.3)_6.1.3.1-SQLScript_INT_20170817.sql

    • Master Metadata Index with the following information

    • Include only the concept identifier

    • Using alphabetical ordering of concept identifiers

URI standard updates

@Former user (Deleted)

Implications of enhanced DL

All

  • Discuss any implications to computable languages of potential enhancements to DL - for example:

    • GCIs

    • Role chains

    • Universal restriction

    • ?Concepts as numbers

Questions from Daniel

All

Discuss questions from Daniel

  1. to support expression repositories (i.e. where the substrate is dynamic in that expressions could be added), do we need to add the ability to use the ECL to apply constraint operators to post-coordinated expressions, i.e. where a piece of the ECL string is to be interpreted as a SCG expression, e.g. << [ 404684003 | Clinical finding (finding) |: 363698007 |Finding site (attribute)| = 10200004 | Liver structure (body structure) | ]? This would correspond to a DL query.

  2. to support potential expansion of the SNOMED CT logic profile, do we need to extend SCG to support axioms as opposed to only expressions, for example to allow (non-hidden) GCAs to be stated in SCG?

  3. we need an SNOMED CT OWL specification, i.e. how is SNOMED CT (concepts and descriptions) represented in OWL. Is this within the scope of this group?

Query Language

@Former user (Deleted)

  • Review proposed Query Language examples

  • Additional requirements from SLPG members?

Confirm next meeting date/time

@Former user (Deleted)

Next meeting to be held at 20:00 UTC on Wednesday 13th September 2017



Copyright © 2025, SNOMED International