Hey there, We use tag across all resources pretty robustly. Now that we've set up our Medplum App with appropriate Project segmentation, we're exploring some data. We noticed that the tag filter is available, but it seems to expect an exact match (equals) on all tag values concatenated. We were hoping that we might be able to use FHIR search notation: https://www.hl7.org/fhir/search.html#_tag GET [base]/Observation?_tag=H Is this intentional behavior or could we look to update it?

Hi @brendankeeler , the intended behavior is to follow the same semantics for all

token

search parameters. If we're not doing that, then we can fix it ASAP

Here's what I see (test data). Tags are as shown.

Trailing white space and url encoding are my nemesis!

FWIW, it seems like a lot of the tags, are identifiers. Any reason you dont want to move them to the

identifiers

field?

If they represent an identifier, they are also in the identifiers array