-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$expand sorting is different (worse) than the full snowstorm version #4
Comments
Hi @ivank just looking at the "version" parameter in the response - does your instance of Snowstorm-lite have the January 2023 version loaded? |
Today I ran Ivan's query against my instance of snowstorm-lite which has the January 2024 edition loaded. My results were similar - 50 concepts in the expansion of this value set. I'm not sure how the concepts are ordered in the response, but I believe the difference in numbers can be explained because snowstorm-lite includes inactive concepts in the value set. These can be filtered as they are indicated as inactive, for e.g. {
"system": "http://snomed.info/sct",
"inactive": true,
"code": "366980001",
"display": "Suspected breast cancer"
} |
@ivank Thanks for reaching out. The relevance of the results can be improved by searching the specific area of the hierarchy you are interested in using ECL. Examples:
I hope that helps. Long Explanation |
There is a fix for this in the develop branch: to apply the same sorting as the main Snowstorm product, when within the first 100 results, without a loss of performance. |
This is fixed in the latest version 1.3.0-beta. |
Example:
responds with:
Whereas local snowstorm-lite server is returning
Where "Fear of breast cancer" is higher on the list than "Malignant tumor of breast" ... not the response we were expecting (and the full version was correctly returning).
Maybe we have to configure / reindex something to make it work the same as the full version?
Docker image version:
snomedinternational/snowstorm:9.2.0
The text was updated successfully, but these errors were encountered: