[Feature]: Implement NOT for search

[patrickskowronekdkfz]

General Summary

In upcoming projects, support for logical negation (NOT) will be required. While the AST already supports the NOT type, most other components in the system are not yet equipped to handle it.

A common request in the feasibility search is an explicit way to define exclusion criteria, i.e., fields whose inputs are logically negated to filter out matching subjects.

Design Question

A possible approach would be to provide a second search bar (or section) with an "Exclude criteria" option. However, it's unclear whether this is the most intuitive or scalable solution.

Initial Thoughts

Pros of separate “Exclude” bar:

Clear UI separation between inclusion and exclusion

Aligns with user expectations from medical or cohort query tools

Cons:

May add visual and cognitive complexity

Potential duplication of logic and UI handling

Alternative idea:

Add an “Exclude” toggle or tag at the field level within the existing search builder

Maintain a single UI, but clearly mark excluded filters visually (e.g., red tags, NOT badges)

Is this Breaking?

Yes

[timakro]

If we go for a dedicated "not" search bar we will have to decide how this interplays with the multi search bar. Actually we could also say you can either have "not" + regular search bar, or multi search bar (not both).