Stream: IG creation
Topic: Defining Query Support for an IG
Keith Boone (Jun 01 2020 at 15:10):
One of the things that seems to be missing from CapabilityStatement is a clearly computable definition of the combinations of Query Parameters a server supports. Not every server supports every parameter, and some combinations of parameters have different business requirements in different contexts. The important of having this be computable comes out when trying to create a test plan (as we did in the SANER Project).
To give an example:
A server is required to support queries by MeasureReport using _id, period, measure, and location, and _include=*.
-
MeasureReport?_id and _include=* must be supported by the server
-
MeasureReport? measure and period and location and _include=* must be supported by the server. The server may require that both measure and period be specified (e.g., min=1 for both parameters), and location and _include are both optional for the client.
One can express 1. and 2. above as an OperationDefinition (a named search), but there's nothing special about this named search other than the fact that it expresses some cardinality constrained for the client and for the server. The search behavior is otherwise as required by FHIR.
So, we have a way to describe the requirements, but no real way to express them without creating a named search, but no need for a named search other than to express capabilities.
If we put these named searches in a capability statement, it implies that they exist as a named search in the server.
I'll also point out that expect
Lloyd McKenzie (Jun 01 2020 at 15:56):
We've talked about this before. Expressing the full sophistication of what combinations are supported in a computable way introduces a very large degree of complexity. So far, we've landed on the side that says "CapabilityStatement is more than complex enough, thanks". That said, we're currently looking at refactoring CapabilityStatement (to the extent we can with a normative artifact), and it's possible we could introduce something like this with the new approach.
Keith Boone (Jun 01 2020 at 16:12):
I found what I needed in the http://hl7.org/fhir/extension-capabilitystatement-search-parameter-combination.html
Last updated: Apr 12 2022 at 19:14 UTC
