Stream: implementers
Topic: Search Parameter without fhirpath
Ken Sinn (Aug 25 2020 at 14:04):
We're looking at defining a custom Search Parameter for a Query.
The Search Parameter does not map to any element within the FHIR resource being searched. Consider that Search Parameter to be a status flag on that resource (metadata), but is not clinically relevant to that FHIR resource and would never be exposed externally.
Are we breaking any rules around custom definitions of search params? Based on existing SearchParam definition constraints, this seems to be allowed.
Thoughts? Thank you!
Ken Sinn (Aug 25 2020 at 14:21):
Specifically, we're looking at using the Async Restful Message (https://www.hl7.org/fhir/messaging.html#rest). We're looking for a way to track the "acknowledgement" status for each of the Message Bundles, so that the receiver can query by "all message bundles with acknowledgement status = false".
Lloyd McKenzie (Aug 25 2020 at 15:21):
Yes, that's allowed
Ken Sinn (Aug 25 2020 at 15:41):
Is there a recommended way to handle this? Would it be preferable to use a chained search based the corresponding message responses, eg "Query all MessageHeaders where MessageHeader.id!=MessageHeader.response.id and MessageHeader.response.code!="OK"? Seems a lot simpler to use the previous approach with a separate custome search param instead of a convoluted search condition.
Lloyd McKenzie (Aug 25 2020 at 17:39):
You don't have to have a FHIRPath at all
Last updated: Apr 12 2022 at 19:14 UTC