2019-03-27 - SLPG Meeting

Welcome and apologies

@Former user (Deleted)

Actions from last week

@Former user (Deleted)

• Actions from last week:

  • Consider new syntax to support proposed expression template use case

    • Add examples with 2-levels of nesting

    • Revise notation based on last meeting's discussion

  • Consider new syntax to support proposed map use case

Template Syntax

@Former user (Deleted)

Use cases: New concept development, querying based on template matching, and template-based modeling transformation

New requirements

Executing maps

@Former user (Deleted)

Proposed extension to ECL to support the execution of maps

• Example use cases

  • Mapping from international substance concepts to AMT substance concepts

  • Anatomy structure and part association reference set - e.g. find the anatomical parts of a given structure

• Potential syntax to consider

  • Functional

    • mapTarget (|Anatomy structure and part association refset|, << |Upper abdomen structure|)

    • mapSource (|Anatomy structure and part association refset|, << |Liver part|)

  • Dot notation

    • |Anatomy structure and part association refset| . |mapTarget|
      
      

    • |Anatomy structure and part association refset| . |referencedComponent| (Same as ^ |Anatomy structure and part association refset|)

    • ( |Anatomy structure and part association refset|: |ReferencedComponent| = << |Upper abdomen structure ) . |mapTarget|

    • ( |Anatomy structure and part association refset|: |mapTarget| = << |Upper abdomen structure ) . |referencedComponent|
      
      

  • Filters
    
    

    • ( |Anatomy structure and part association refset| {{ |referencedComponent| = << |Upper abdomen structure| }} ). |mapTarget|
      
      

    • ( |Anatomy structure and part association refset| {{ mapTarget = << |Upper abdomen structure| }} ) . |referencedComponent|
      
      

      • ^ ( |Anatomy structure and part association refset| {{ mapTarget = << |Upper abdomen structure| }} )
        
        

  • Specify value to be returned

    • ?|mapTarget|? |Anatomy structure and part association refset|

    • ?|mapTarget|? |Anatomy structure and part association refset| {{ |referencedComponent| = << |Upper abdomen structure| }}

    • ?|mapTarget|? |Anatomy structure and part association refset| : |referencedComponent| = << |Upper abdomen structure|

Returning attributes

@michael lawley

Proposal from Michael:

• Currently ECL expressions can match (return) concepts that are either the source or the target of a relationship triple (target is accessed via the 'reverse' notation or 'dot notation', but not the relationship type (ie attribute name) itself. 

For example, I can write: 

<< 404684003|Clinical finding| : 363698007|Finding site| = <<66019005|Limb structure| 

<< 404684003|Clinical finding| . 363698007|Finding site| 

But I can't get all the attribute names that are used by << 404684003|Clinical finding| 

URI Standard

@Former user (Deleted)

• Finalize and publish language and language instance URIs

Query Language
- Summary from previous meetings

@Former user (Deleted)

Examples: version and language

Notes

Examples: where

Notes

Keywords for Term-based searching:

• 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 = * LANGUAGE X)

Language preferences using multiple language reference sets

• 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|

Other topics

@Former user (Deleted)

• Any other topics?

Confirm next meeting date/time

@Former user (Deleted)

The next SLPG meeting will be held in 6 weeks at 20:00 UTC on Wednesday 8th May.