For large value sets where each value has multiple properties, when doing an expansion with a filter on what the user has typed in a field, it is useful to be able to specify:

1) Which properties are searched (matched against what the user types)

2) Which properties are displayed to the user in a multi-column selection list

3) Which properties are returned but not displayed (to be used for other purposes, e.g. population of other fields after a selection, or skip-logic).

If #3 is too controversial, I can submit a separate tracker item for that. However, I think (1) and (2) are both important.

For example, if you have a form field for an ICD-10-CM code lookup, the form designer might want to show both the code and display string, but only match the user's typing against the code. Or, there might be a synonyms column for the lookup which is searched but not displayed.