Iteration 7

Expanding Query Sets Live

This rapid 3 week iteration is focused on implementing the base set of queries defined in IT6 as well as defining a deployment plan for release.

Question(s) Being Answered:

This iteration, we will be implementing a set of queries as a single batch or Query Set. These queries will be based on what was defined in IT6 and may expand on it.

For more details on these queries, see IT6 Queries

Rationale:

One of the elements needed for the overall design is the ability to run (and rerun) sets of queries. These can be related queries in the sense of multiple, related queries (e.g. data quality queries that support interpretation of the main query) or they may be a batch of queries that are run routinely (e.g. in the case of the AMCARE query set).

The main goal of this iteration is to develop the process and tools to manage routine query sets. This would allow for hQuery to run at regular intervals, query sets of commonly asked asked questions that would be needed to be tracked over time such as for AMCARE or for a time series study.

Secondary goals for this iteration includes:

• Map E2E sections / data element to the complete set of AMCARE's current queries data requirements.
• Develop a subset of the AMCARE queries inside of hQuery in preparation for an AMCARE Exporter.
• Develop a query scheduler inside of hQuery.

To contain the scope of the query set, the sub-set of AMCARE queries has been chosen that should cover data elements that are currently included in the OSCAR E2E exporter. Additional mapping will occur in this iteration in preparation for including the full query set, once it has been documented and shared by AMCARE.

Features:

See Features for Iteration 7