2016-05-25 - SLPG Meeting

2016-05-25 - SLPG Meeting

 Date & Time

Wednesday 25th May 2016, 20:00 UTC

GoToMeeting Details

Click here to see GoToMeeting joining information

Click here to see GoToMeeting recordings

Goals

  • To finalize the ECL v1.1 updates

  • To reflect on discussions at the HL7 WG meeting in Montreal

  • To continue work on SNOMED CT Templates

Attendees 

  • Chair: @Former user (Deleted)

  • Project Group: @Daniel Karlsson@Former user (Deleted)@michael lawley@Rob Hausam

Apologies

@Brian Carlsen@Ed Cheetham@Alejandro Lopez Osornio

Observers

Agenda and Meeting Notes

Item

Description

Owner

Notes

Action

Item

Description

Owner

Notes

Action

1

Welcome, introductions and apologies

@Former user (Deleted)

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

Check attendance details and apologies

2

Agenda review

@Former user (Deleted)

Review agenda for today's meeting

Review agenda

3

Expression Constraint Language v1.1

@Former user (Deleted)

  • Discuss any remaining feedback on updates

  • Propose timeline for publication of updates

 

4

Discuss outcomes of HL7 WG meeting

@Former user (Deleted)

Condition

[[ [1..1] @findingWithExplicitContext ]]:
[1..2] @RG1 { 246090004 |Associated finding| = ([[ [0..1] @associatedFinding ]]:
[0..1] @RG2 { 246112005 |Severity| = [[ [0..1] @severity]],
363698007 |Finding site| = [[ [0..1] @findingSite]] })
408732007 |Subject relationship context| = 410604004 |Subject of record|,
408731000 |Temporal context| = [[ [1..1] @temporalContext ]],
408729009 |Finding context| = [[ [1..1] @findingContext ]] }

AllergyIntolerance

  • IF ($code = < 373572006 |Clinical finding absent|) THEN

[[ $code ]]

  •  IF ($code = (< 105590001 |Substance| OR < 373873005 |Pharmaceutical / biologic product|)  THEN

413350009 |Finding with explicit context|:
[0..2] @RG1 { 246090004 |Associated finding| = ([[ [1..1] @associatedFinding ]]:
   370135005  |Pathological process| = [[ [0..1] @pathologicalProcess ]],
[0..1] @RG2 { 255234002 |After| = [[ [0..1] @after ]],
246075003 |Causative agent| = [[ [1..1] @causativeAgent ]]})
408732007 |Subject relationship context| = 410604004 |Subject of record|,
  408731000 |Temporal context| = [[ [1..1] @temporalContext ]],
408729009 |Finding context| = [[ [1..1] @findingContext ]] }

Procedure

129125009 |Procedure with explicit context|:
[1..1] @RG1 { 363589002 |Associated procedure| = ( [[ @associatedProcedure ]] :
  [0..1] @RG2 { 363704007 |Procedure site| = [[ [0..1] @procedureSite ]],
  363699004 |Direct device| =  [[ [0..1] @directDevice ]],
  424361007 |Using substance| = [[ [0..1] < 105590001 |Substance| @usingSubstance ]]),
  424226004 |Using device| = [[ [0..1] < 49062001 |Device|) @usingDevice]]),
  408732007 |Subject relationship context| =  410604004 |Subject of record|,
  408731000 |Temporal context| =  410512000 |Current or specified time|,
  408730004 |Procedure context| = [[ [0..1] @procedureContext ]] }

 

5

SNOMED CT Template syntax development

@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:

    • HL7 FHIR Mapping Syntax

      • Explore ....

    • 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 8th June 20:00 UTC

Confirm date of next call

Meeting Files

  File Modified
No files shared here yet.

Copyright © 2025, SNOMED International