You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When expanding a valueset with LOINC codes, the filter only works for single terms, multiple terms always returns no results. example :
Works
curl --location 'http:///fhir/ValueSet/$expand?filter=blood&url=http%3A%2F%2Floinc.org%3Ffhir_vs'
Doesn't work
curl --location 'http:///fhir/ValueSet/$expand?filter=blood%20pressure&url=http%3A%2F%2Floinc.org%3Ffhir_vs'
The issue is also reproducible on the POST endpoint.
None of the filter features as specified in the FHIR spec seems to be working as intended. Is this an issue with the way we are using the API or is this an issue with snowstorm?
The text was updated successfully, but these errors were encountered:
Thank you for raising this issue. This was reported this morning by someone from the Open Healthcare Network.
I have confirmed the bug and started working on a fix.
This fixes a bug when filtering FHIR ValueSets that are not using SNOMED CT. The bug fix enables searching with multiple words or prefixes. Before the fix only searching with one word or prefix was working.
This fixes a bug when filtering FHIR ValueSets that are not using SNOMED CT. The bug fix enables searching with multiple words or prefixes. Before the fix only searching with one word or prefix was working.
When expanding a valueset with LOINC codes, the filter only works for single terms, multiple terms always returns no results. example :
Works
curl --location 'http:///fhir/ValueSet/$expand?filter=blood&url=http%3A%2F%2Floinc.org%3Ffhir_vs'
Doesn't work
curl --location 'http:///fhir/ValueSet/$expand?filter=blood%20pressure&url=http%3A%2F%2Floinc.org%3Ffhir_vs'
The issue is also reproducible on the POST endpoint.
None of the filter features as specified in the FHIR spec seems to be working as intended. Is this an issue with the way we are using the API or is this an issue with snowstorm?
The text was updated successfully, but these errors were encountered: