Page History

1

SLPG meetings will be recorded and recordings will be accessible to SLPG members.Apologies from Alejandro and Brian

•  Check attendance details and apologies

•  Review agenda

A brief look at how we plan to use Expression Constraints and Expression Template in the MRCM.

Example attribute rule:

(<< 404684003 |Clinical finding (finding)| OR << 272379006 |Event (event)|):

[0..*] { [0..*] 255234002 |After (attribute)| = (<< 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)|) }

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

[[ [1..1] @findingWithExplicitContext ]]:
[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 ]] }

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. Cardinality - How to specify cardinality of (i) an attribute, (ii) an attribute group, (iii) a focus concept?
3. Do we need to be able to name the role groups to refer to them in the Mapping/Transformation code?
4. What will the mapping/Transformation code look like? What dependencies does it have on the Template

1. Template

Confirm date and time of next SLPG meeting

• Wednesday 22nd June 2016

•  Confirm date of next call