Some search parameters support not indicated in CapabilityStatement #4672
Labels
Bug
Bug bug bug.
Up for grabs
The issue require minimal context and is well-suited for new contributors.
VSTS-Backlog
On VSTS Backlog
Describe the bug
A consumer of our FHIR server refuses to use the
_summary
search result parameter, as they (reasonably) determine whether they can use it based on its presence in the server'sCapabilityStatement
. The only items inCapabilityStatement.rest.searchParam
are_type
and_count
(this is on release 4.0.198):The server does accept a
_summary=count
and returns aBundle
in the expected form, e.g.So it seems reasonable that this should be reflected in the
CapabilityStatement
, probably along with all other supported parameters. See e.g. the lists of Common search parameters and Search result parameters.FHIR Version?
Stu3
Data provider?
SQL Server
To Reproduce
Steps to reproduce the behavior:
/metadata
endpoint.Expected behavior
All supported search/search result parameters will be returned in the
CapabilityStatement
.Actual behavior
Not all supported search parameters were returned; in particular
_summary
is missing.The text was updated successfully, but these errors were encountered: