/
2020-11-04 - SLPG Meeting

2020-11-04 - SLPG Meeting

2025-Sep-05

Date & Time

20:00 to 21:00 UTC Wednesday 4th November 2020

Location

Zoom meeting link (password: 764978)

Goals

  • Start development of postcoordination guidance

Attendees 

  • Chair: @Former user (Deleted)

  • Project Group: @michael lawley, @Peter Jordan (Unlicensed), @Anne Randorff Højen, @Kai Kewley, @Rob Hausam

Apologies

@Daniel Karlsson (Unlicensed) , @Ed Cheetham

Agenda and Meeting Notes

Description

Owner

Notes

Description

Owner

Notes

Welcome and agenda

@Former user (Deleted)

NOTE: Next meeting to be held on Wednesday 18th November

Postcoordination Guidance

@Former user (Deleted) , @Anne Randorff Højen , @Kai Kewley

Practical Guide to Postcoordination

  • Discuss use cases for postcoordination

    • Mapping local codes to postcoordinated expressions

    • Natural language processing – e.g. ""

    • Semantic interoperability (e.g. between FHIR resource instances)

    • Comparing 2 clinical meanings for equivalence and subsumption

      • E.g. Extemporaneous drug formulations

  • Comments

    • Should there be a syntactic distinction between refinement and constructive addition (ie adding a new role group)

  • Agree on approach and next steps - potentially including:

    • Agree on list of expression forms that need defining - 3.4 Transforming Expressions

    • Discuss different types of transformations required

    • Explain transformation steps

 

 

 

Other Options for Future Progress

 

  1. Postcoordination and close-to-user transformations

  2. URIs for draft editions

  3. ECL extensions

    1. Primitive/Defined filters → concept filter

    2. Concept+Description filters (e.g. effectiveTime, module, active)

    3. Accessing Refset attributes → (e.g. historical association refsets) → historical ECL

    4. OR use full syntax to be able to query any table (e.g. Relationship table) - ie expand ECL into something more verbose (e.g. SNOMED query language)

  4. Template extensions

URIs for Extended Editions

 

How to refer to an 'extended edition' using a URI - e.g. "International Edition plus the following 2 nursing modules: 733983009  |IHTSDO Nursing Health Issues module|and 733984003 |IHTSDO Nursing Activities module|

Use Case - Need to execute an ECL, that refers to "^ 733991000 | Nursing Health Issues Reference Set (foundation metadata concept) |" and/or "^ 733990004 | Nursing Activities Reference Set (foundation metadata concept) |", where the substrate includes the international edition, plus the modules that include these reference sets

July 2020 International Edition URI: http://snomed.info/sct/900000000000207008/version/20200731

July 2020 International Edition + nursing modules URI ?? - For example:

  • http://snomed.info/sct/900000000000207008/version/20200731/module/733983009/time/20200131/module/733984003/time/20200131

  • http://snomed.info/sct/900000000000207008/version/20200731/modules/733983009:733984003

  • http://snomed.info/sct/900000000000207008:733983009:733984003/version/20200731:20190731:20200131

  • Canonical order? Or order doesn't matter?

  • Constraints on what can go in the additional packages (only refsets and their metadata)

Querying Refset Attributes

@Former user (Deleted)

Proposed syntax to support querying and return of alternative refset attributes (To be included in the SNOMED Query Language)

  • Example use cases

    • Execution of maps from international substance concepts to AMT substance concepts

    • Find the anatomical parts of a given anatomy structure concept (in |Anatomy structure and part association reference set)

    • Find potential replacement concepts for an inactive concept in record

    • Find the order of a given concept in an Ordered component reference set

    • Find a concept with a given order in an Ordered component reference set

  • Potential syntax to consider (brainstorming ideas)

    • SELECT ??

      • SELECT 123 |referenced component|, 456 |target component|
        FROM 799 |Anatomy structure and part association refset|
        WHERE 123 |referenced component| = (< 888 |Upper abdomen structure| {{ term = "*heart*" }} )

      • SELECT id, moduleId
        FROM concept
        WHERE id IN (< |Clinical finding|)
        AND definitionStatus = |primitive|

      • SELECT id, moduleId
        FROM concept, ECL("< |Clinical finding") CF
        WHERE concept.id = CF.sctid
        AND definitionStatus = |primitive|

      • SELECT ??? |id|, ??? |moduleId|
        FROM concept ( < |Clinical finding| {{ term = "*heart*" }} {{ definitionStatus = |primitive| }} )

      • Question - Can we assume some table joins - e.g. Concept.id = Description.conceptId etc ??

      • Examples

        • Try to recast relationships table as a Refset table → + graph-based extension

        • Find primitive concepts in a hierarchy

    • ROW ... ?

      • ROWOF (|Anatomy structure and part association refset|) ? (|referenced component| , |target component|)

        • same as: ^ |Anatomy structure and part association refset|

      • ROWOF (|Anatomy structure and part association refset|) . |referenced component|

        • same as: ^ |Anatomy structure and part association refset|

      • ROWOF (|Anatomy structure and part association refset|) {{ |referenced component| = << |Upper abdomen structure|}} ? |targetComponentId|

      • ROWOF (< 900000000000496009|Simple map type reference set| {{ term = "*My hospital*"}}) {{ 449608002|Referenced component| = 80581009 |Upper abdomen structure|}} ? 900000000000505001 |Map target|

        • (ROW (< 900000000000496009|Simple map type reference set| {{ term = "*My hospital*"}}) : 449608002|Referenced component| = 80581009 |Upper abdomen structure| ).900000000000505001 |Map target|

    • # ... ?

      • # |Anatomy structure and part association refset| ? |referenced component\

      • # (|Anatomy struture and part association refset| {{|referenced component| = << |Upper abdomen structure|) ? |targetComponentid|

Copyright © 2025, SNOMED International