2016-04-27 - SLPG Meeting

1

Welcome, introductions and apologies

@Former user (Deleted)

SLPG meetings will be recorded and recordings will be accessible to SLPG members

2

Agenda review

@Former user (Deleted)

Review agenda for today's meeting

3

SNOMED CT Expression Constraint Language

@Former user (Deleted)

Discuss proposed updates to the SNOMED CT Expression Constraint Language

5

SNOMED CT Template Syntax

@Former user (Deleted)

Review discussion on optionality and populating attribute groups:

1. Scope and purpose of syntax

   1. Extract/disentangle SNOMED CT (and SNOMED CT-relevant) content from a FHIR Condition resource (i) into a free-standing and ‘recognisable’ SNOMED CT expression, whilst (ii) ‘leaving nothing behind’ which may be of relevance to further processing

   2. Specify mappings from FHIR value sets (e.g. Condition.clinicalStatus) into SNOMED CT

   3. Transform the extracted expression into an ‘optimally-processable’ SNOMED CT expression (in particular grouping body site values with morphology)

   4. Specify constraints on what the extracted/disentangled SNOMED CT expression could or couldn’t contain (by e.g. cardinality instructions).

2. (From a(ii) and b above) Simplify |finding context| refinement to either:

   • 408729009 |finding context| = [[ @findingContext ]]

   • 408729009 |finding context| = [[ findingContextTable ($clinicalStatus, $verificationStatus) ]]

3. (From d above) How to specify cardinality in terminology binding when restricting valid values in an information model data element:

   •  

     • 62014003 |Adverse reaction to drug (disorder)|: 246075003 |Causative agent| = [[ [0..1] ^ 111115 | AMP reference set | ]]

     • 62014003 |Adverse reaction to drug (disorder)|: !! [0..1] !! 246075003 |Causative agent| = [[ ^ 111115 | AMP reference set | ]]

4. (From c above) To indicate how the following data structure can be used to populate a template:

   • Data Structure A

     • Condition

       • Code: CodeableConcept [0..1]

       • MorphologyBS [0..*]

     •  

       •  

         • BodySite: CodeableConcept [0..1]

         • Morphology: CodeableConcept [0..1]

   • Possible template syntax examples:

     • [[ $code ]]: { 363698007 |finding site| = [[ $BodySite ]], 116676008 |associated morphology| = [[ $Morphology ]] }

     • [[ $code ]]: { 363698007 |finding site| = [[ $MorphologyBS.BodySite ]], 116676008 |associated morphology| = [[ $MorphologyBS.Morphology ]] }

     • [[ $code ]]: !! For each M = $MorphologyBS !! { 363698007 |finding site| = [[ M.BodySite ]], 116676008 |associated morphology| = [[ M.Morphology ]] }
       
       

   • Data Structure B

     • Condition

       • Code: CodeableConcept [0..1]

       • BodySite: CodeableConcept [0..*]

       • Morphology: CodeableConcept [0..1]

   • Possible template syntax examples:

     • To include the different finding sites within the same attribute group:
       
       

       • [[ $code ]]: { 363698007 |finding site| = [[ $BodySite ]], 116676008 |associated morphology| = [[ $Morphology ]] }

     • To include an attribute group for each different finding site (with the same associated morphology):
       
       

       • [[ $code ]]: !! For each BS = $BodySite !! { 363698007 |finding site| = [[ BS ]], 116676008 |associated morphology| = [[ $Morphology ]] }

   • Other examples discussed by email (double scope):

     • |finding| : [[ {    [0..*] |findingSite| = $bodySite << 48566001 | Bone structure of extremity (body structure) |,
           [[ [0..1] |assocMorph| = $morphology < 72704001 | Fracture (morphologic abnormality) |]] } ]]
       
       

6

Confirm next meeting date/time

@Former user (Deleted)

Confirm date and time of next SLPG meeting - Wednesday 25th May