Stream: committers
Topic: descendent-of
Michelle (Moseman) Miller (Apr 09 2020 at 18:09):
@Grahame Grieve I just did a local build and see a value set expansion of:
This value set could not be expanded by the publication tooling: Error from server: The filter "concept descendent-of 405533003" was not understood in the context of http://snomed.info/sct
The way I read http://build.fhir.org/valueset-filter-operator.html#expansion, descendent-of is very similar to is-a. Since is-a is supported for SNOMED, why wouldn't descendent-of be supported?
What do you recommend for next steps?
- Check in changes using descendent-of and log a JIRA for tooling to support expansion of descendent-of for SNOMED
- Change the value set compose logic to include "is-a" 405533003 and then exclude 405533003
Michelle (Moseman) Miller (Apr 09 2020 at 19:06):
Here is the value set I had for the local build: https://github.com/HL7/fhir/blob/michelle-miller-25556-25926-AdverseEvent-status-outcome/source/adverseevent/valueset-adverse-event-outcome.xml
Peter Jordan (Apr 09 2020 at 19:22):
One solution here is to filter SNOMED CT concepts by Expression Constraint. See http://build.fhir.org/snomedct.html ECL (Expression Constraint Language) enables you to request descendantOf or descendantOrSelfOf.
Michelle (Moseman) Miller (Apr 09 2020 at 19:28):
I've already confirmed that "include is-a 405533003 and then exclude 405533003" will work. It just looks overly verbose considering descendent-of should work.
Grahame Grieve (Apr 09 2020 at 20:17):
@Michelle (Moseman) Miller tx.fhir.org doesn't support descendent-of due to an oversight on my part - will srart doing so sometime in the next few days
Michelle (Moseman) Miller (Apr 09 2020 at 20:30):
OK, thanks -- I will create a PR for my changes that use descendent-of
Last updated: Apr 12 2022 at 19:14 UTC
