Add conditions_list. This is the condition.name of the condition(s) included in the query. This could be a comma delimited string, or if we want to ensure that if we end up displaying this differenntly in the future, we could make it a simple array that is then rendered on the My Queries page however we might need it.
Add query_name. This should be fine just being a JSON that holds a nested {condition: [valueset: [concept]]} for every included condition. I tend to think we want it to hold every valueset for a condition with an include/exclude flag and same for concepts. We can either hold all the data related to the query (name, author, etc. for each valueset) or just the IDs and an include flag. I lean toward maybe just having everything in query_data so that we can just take the JSON directly when a query is built.
linear[bot]
commented
15 hours ago
Description:
Necessary components:
conditions_list. This is thecondition.nameof the condition(s) included in the query. This could be a comma delimited string, or if we want to ensure that if we end up displaying this differenntly in the future, we could make it a simple array that is then rendered on the My Queries page however we might need it.query_name. This should be fine just being aJSONthat holds a nested{condition: [valueset: [concept]]}for every included condition. I tend to think we want it to hold every valueset for a condition with an include/exclude flag and same for concepts. We can either hold all the data related to the query (name, author, etc. for each valueset) or just the IDs and an include flag. I lean toward maybe just having everything inquery_dataso that we can just take the JSON directly when a query is built.Acceptance Criteria: