Stream: fhir/infrastructure-wg
Topic: FHIR-30631
Yunwei Wang (Mar 26 2021 at 20:50):
In last conference call, we discussed FHIR-30631. The resolution states that:
If the 'base' SearchParameter defined by HL7 or an implementation guide is referenced, then all listed modifiers, comparators, etc. are expected to be supported. If an implementation wishes to restrict which modifiers they support, they must define their own SearchParameter instance based on the 'official' SearchParameter.
How do I say that my implementation does NOT support any modifiers? For example, for string search, my implementation does not support :contains nor :exact
@Lloyd McKenzie
Lloyd McKenzie (Mar 26 2021 at 20:51):
You have to define a custom search parameter based on the 'official' search parameter that constrains out the modifiers you don't support.
Yunwei Wang (Mar 26 2021 at 20:52):
So I would say something like
"modifier": []
Lloyd McKenzie (Mar 26 2021 at 21:07):
I don't think that's legal. I think you'd omit "modifier" entirely.
Gino Canessa (Mar 29 2021 at 15:05):
But if you leave it off, won't it inherit from the parent?
Lloyd McKenzie (Mar 29 2021 at 15:06):
@Grahame Grieve
Eric Haas (Mar 29 2021 at 23:45):
I think that akin to conformance-expectation extension on each for a requirements CapStatement , would need some modifier extension like is-supported boolean for each comparator/modifier for an instance CapStatement. yucky and heavy but computable. More reason to test out CapStatement2.
Last updated: Apr 12 2022 at 19:14 UTC
