You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to avoid as many joins and just pull data from query. This may require updating the interface to not pull from valuesets or to reflect the JSON we create for query_data.
This should allow us to also in the case of superadmins get rid of any WHEREs. which only exist now to speed up processing. The limiting factor should be done based on user permissions, which we may need to add here or could potentially be accomplished in an alternative method.
Acceptance Criteria:
Fetches valuesets / concepts for conditions pulls from the query_data column
My Queries table pulls from the query table rather than hardcoded
Constants that tie the demo query options to labels / values / etc aren't so duplicative
The text was updated successfully, but these errors were encountered:
Description:
Once work is complete to add
query_data
andconditions_list
to thequery
table in the database, we will need to refactor this section of code: https://github.com/CDCgov/dibbs-query-connector/blob/main/query-connector/src/app/database-service.ts#L622We should be able to avoid as many joins and just pull data from
query
. This may require updating the interface to not pull from valuesets or to reflect the JSON we create forquery_data
.This should allow us to also in the case of superadmins get rid of any WHEREs. which only exist now to speed up processing. The limiting factor should be done based on user permissions, which we may need to add here or could potentially be accomplished in an alternative method.
Acceptance Criteria:
query_data
columnquery
table rather than hardcodedThe text was updated successfully, but these errors were encountered: