ECL 2.0 Proposal

• The approach agreed at last week's SLPG meeting, and supported by SNOMED International is as follows:
  1. To select and/or filter columns of a reference set, reference set field names will be used
  2. Field names will come directly from the international RF2 specification (http://snomed.org/rfs), if the associated reference
  set pattern
  1. set type is defined there. In all other cases, the field names will either come from another specification (e.g. a national specification) or directly from the RF2 files themselves.
     E.g.
  ^ 
  1. • ^ 447562003 |ICD-10 complex map reference set|  {{ M mapGroup = #2, mapPriority = #1, mapTarget = "J45.9" }}
     • ^ [referencedComponentId, mapTarget]  816210007 |SNOMED CT to MedDRA simple map reference set|
  2. The reference set
  pattern
  1. type concepts
  defined
  1. in the international RFS, will always be a < 900000000000455006 |Reference set| that has a refset descriptor and has no ancestor with a refset descriptor.
  Only
  1. • Note: All other reference set
  grouper concepts
  1. • concepts above the refset types are refset grouper concepts (which do not themselves have refset descriptors)
  the highest subtypes of < |Reference set| that have a refset descriptor pattern.
• A computable representation of these international reference set patterns will be shared. Effective ways of distributing this computable representation can be raised in the MAGdiscussed.

Expression Constraint Language 2.0 WIP

Please review updates to the following pages:

• 1. Introduction (History)
• 3.2 Expression Constraint and Query Requirements
• 4. Logical Model
• 4.1 Details
• 5.1 Brief Syntax (Normative)
• 5.2 Long Syntax (Informative)
• 5.3 Informative Comments
• 5.4 Order of Operation
• 6.1 Simple Expression Constraints (Member Of) **
• 6.8 Description Filters (Module, Effective Time, Active Filters)
• 6.10 Member Filters **
• 6.11 History Supplements
• Appendix D - ECL Quick Reference