Stream: fhir/infrastructure-wg
Topic: Search Requirement Clarification
Gino Canessa (Feb 25 2022 at 21:14):
Quick question on requirements for search. There has been a fair bit of discussion on GET and POST, which landed on text indicating that servers SHALL support both HTTP verbs, but MAY respond with a 405 to one of them (e.g., FHIR-31943).
It is not qualified anywhere today, but I assume that should only apply to where a server actually supports search, right? E.g., a server can still be fully compliant even if they support NO search at all, by not advertising support for it.
Thanks!
John Moehrke (Feb 25 2022 at 21:19):
I thought that was already clear as the requirement was on the search page.
Gino Canessa (Feb 25 2022 at 21:36):
Hmm.. I can't find anything there - the only Search Conformance / Capability mentions I can find are related to search parameter advertisement.
In a broader look, there is an implication on the http page - servers *that* support search SHALL also... (text needs to be updated per those tickets still, emphasis mine), and there is probably something that can be constructed via CapabilityStatement.rest.resource.interaction and CapabilityStatement.messaging.supportedMessage rules.
I was hoping that I was skipping over it (if anyone has a link to it, that would be nice =), but I am a bit less confident of that now. Next best is my hope that adding fluffy text about it to the search page is "harmless text" and doesn't require YAT (yet another ticket), but am not too confident about that either :-/.
Lloyd McKenzie (Feb 25 2022 at 21:40):
It's a normative page and it doesn't meet the criteria for technical correction (spelling/grammar/formatting/link), so I'm afraid it's a YAT scenario. But it should be a non-controversial ticket and you're fine to pre-apply.
Gino Canessa (Feb 25 2022 at 21:51):
FHIR-36126 . Filed under protest. ;-)
Last updated: Apr 12 2022 at 19:14 UTC
