Stream: hapi
Topic: ReferenceAndListParam
Keith Boone (Mar 30 2018 at 21:14):
I'm seeing some troublesome behavior in ReferenceAndListParam.parseValuesAsQueryTokens() when passed a value like encounter:AuditEvent=Encounter/1234567
Clearly this query won't match because the resource is an Encounter, but the query is looking for AuditEvent. Ignore the use of AuditEvent, this was my test harness and I knew it was a good test case. There are other cases where even though the query is obviously wrong, automated software might not get that.
So, what happens to this is that the parsed reference parameter uses the value of Encounter from the specified Reference, rather than the value associated with the qualifier. While the query may be messed up, it seems also that the HAPI server behavior would also be not what is desired in this situation. The query parameters might be set by one software component, the values by another (or perhaps even bad input from an unrelated component -- which is what my test was checking). Thoughts? @James Agnew
Łukasz Dywicki (Apr 16 2018 at 15:49):
I'm seeing some troublesome behavior in ReferenceAndListParam.parseValuesAsQueryTokens() when passed a value like encounter:AuditEvent=Encounter/1234567
If I'm not mistaken in such case syntax is slightly different - ie. encounter:AuditEvent.id=<id-of-audit-id>. I was patching this part of SearchMap implementation for my own use because I had to rewrite search from hapi to format accepted by system I was interfacing with.
Last updated: Apr 12 2022 at 19:14 UTC
