Goals
- Expand the use of the ECL language - discuss
- Make ECL expansion consistent on well known FHIR Terminology Servers
- Consider requirements for the maintenance of postcoordinated expressions
Attendees
- Chair: Kai Kewley
- Attendees: Jeremy Rogers, Roger Jane, Michael Lawley, Márk Czotter Unknown User (mgall), Rob Hausam
- Staff: Alejandro Lopez Osornio, Katharine Priest ,
- Apologies:
Next Time:
- URIs for postcoordinated expressions?
- A way for termionlogy servers to warn of a partial expression validation implementation?
Agenda and Meeting Notes
Description | Owner | Notes |
---|---|---|
Welcome and agenda | All | |
ECL 2.2 Check | ECL 2.2 - published Has anyone implemented this?
| |
Expanding the use of the ECL standard | All | A light topic to start! Previous discussion: How to make it easier to add an ECL capability to more tooling?
ECL Lite - MVP Scope:
|
ECL Maintenance Recommendations | All | Background: Unknown User (mgall) from EMIS is seeking guidance on best practises for ECL maintenance. We plan to add a "Maintenance Recommendations" page to the ECL guide. Jeremy Rogers has drafted some content on this topic. |
MRCM on FHIR | All | There is a growing desire to enable access to the SNOMED CT Machine Readable Concept Model via FHIR Terminology Servers. Use cases:
How could this work? ConceptMap / ValueSet. New implicit URIs? |
Expression Repository Maintenance | All | - Aim to round off the guidance - make expression repositories feasible - Potential issues when upgrading the substrate of an expression repository
|
ECL Results - TS consistency | Testing consistency between Snowray (Snow Owl), Ontoserver, Snowstorm. Also using custom made NHS Subset maintenance tool, would like to migrate to a standardised solution. Questions:
ML: Some observations: it is interesting to see the number of examples that are querying against terms – the results are not surprising since 1., this is a relatively new part of the spec, and 2., it steps outside the original conception of ECL as a query language that only used defining aspects of concepts as supported by the Concept and Relationship tables. | |
Other Topics | All |
|
The items below are currently on hold | ||
Meds ECL Requirement | RequirementRequirement to select a substance or a modification of that substance .... use case: during authoring to prompt the user with all the active ingredient options. Author/modeller chooses a drug and wants to refine the selection using modification-of substances.
BackgroundThe modification-of attribute is a transitive property in OWL. Transitive properties have a similar characteristic to an is-a relationships but without stating a subtype relationship. In SNOMED CT an OWL property chains are used to help organise the hierarchy, allowing products with modified substance to be subsumed into concept groupers defined using the base substance. However in this case the base substance should not be inherited into the product with the modified substance. The base (not modified) version of the substance is found as redundant and removed during NNF calculation. See OWL Guide: 2.5. Generating Necessary Normal Form Relationships from the OWL Refsets Example property chain: "|Has active ingredient| o |Is modification of|" is a sub-property of "|Has active ingredient|". Example hierarchy: Parent Child Because And Property Chain:
.. which results in OWL seeing the non modified ingredient as a property of the concept for the purpose of subsumption. Finally
This could be used by the ECL engines. Solution Options:
| |
SNOMED OWL Query Engine | Jeremy and all |
|
ECL EOF marker | Kai | Suggestion from Martin Gall (EMIS Health) https://github.com/IHTSDO/snomed-expression-constraint-language/issues/6 Answer - all known TS implementations call Antlr in a way that doesn't require EOF. |