Stream: conformance
Topic: Coding search control parameters into conformance statement
Eeva Turkka (Jan 04 2017 at 14:43):
I see fields for searchInclude and searchRevInclude in the conformance statement, but how does one give information for example about _sort or _elements?
Is _sort something that has to be implemented or could we declare that we only support sorting by this and that search parameter?
Grahame Grieve (Jan 04 2017 at 19:47):
which version of FHIR are you asking about?
Eeva Turkka (Jan 05 2017 at 06:58):
Currently DSTU2 but if it has been changed in STU3 that would be interesting as well
Grahame Grieve (Jan 05 2017 at 10:58):
actually it doesn't make any difference. There's no way to document them
Eeva Turkka (Jan 09 2017 at 06:57):
Thanks, at least I know why I didn't find any way to put them into the conformance statement :). Should there be a way to document these? I guess we can put them into the implementation guide text.
Grahame Grieve (Nov 26 2019 at 15:00):
@Eeva Turkka asked me about this today. No one took it up then. Does anyone else think it would be useful to have a computible format for what sorts are supported?
Lloyd McKenzie (Nov 26 2019 at 17:38):
It doesn't really make sense to expose capabilities for some bits of search and not others, though CapabilityStatement is already overloaded
Last updated: Apr 12 2022 at 19:14 UTC
