-
Notifications
You must be signed in to change notification settings - Fork 81
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
FHIR API $lookup - query response with normalForm property #571
Comments
Raised internal ticket INFRA-12101 for this, which I expect to move to the MAINT project. |
There are a couple of small things in this area. The normalFormTerse has the same issue with missing definition status. The normalFormTerse should also have any whitespace removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When including the normalForm property in the $lookup operation, the response includes the expression, however the expression does not include the symbols for equivalent === or subtype <<<.
For example the SNOMED CT browser indicates the expression for 233604007 |Pneumonia| as "=== 95436008 |Lung consolidation (disorder)| + 205237003 |Pneumonitis (disorder)| : { 363698007 |Finding site (attribute)| = 39607008 |Lung structure (body structure)|, 116676008 |Associated morphology (attribute)| = 707496003 |Inflammation and consolidation (morphologic abnormality)| }".
But observe the query response for:
https://snowstorm.snomedtools.org/fhir/CodeSystem/$lookup?system=http://snomed.info/sct&code=233604007&property=normalForm
normalForm valueString is indicated as "95436008|Lung consolidation (disorder)| + 205237003|Pneumonitis (disorder)| : { 363698007|Finding site (attribute)| = 39607008|Lung structure (body structure)|, 116676008|Associated morphology (attribute)| = 707496003|Inflammation and consolidation (morphologic abnormality)| }"
The text was updated successfully, but these errors were encountered: