Accessing Cohort elements programmatically

Business Requirements

Some of the temporary tables which are created in the result schema when Cohort statistics are calculated already contain information which may be interesting for its further usage by the other applications

Design Ideas and Functional Requirements

When a Cohort is generated there should be a way to specify that any sub-products of the Cohort statistics calculation should be available for its further usage. In addition there should be an endpoint which will respond if a particular Cohort has such sub-products available

For each domain (Drug Exposure, Condition Occurrence, etc.) there should be a way to define (on the application level, not on the Cohort level!) which attributes are of interest to use not to have all stored (whether in temporary tables or in a specific summary table to be exclusively created - https://github.com/OHDSI/Atlas/issues/2891)

Open Questions

• should there be a way to delete data being left / exclusively created for this feature?

@mrechkem @Sathyaraos

Start by mapping how Cohort generation creates temporary tables in the result schema and where Cohort-related endpoints are defined. Review the Drug Exposure and Condition Occurrence domains and determine how application-level attribute selection and sub-product availability would be represented. Done should include a defined way to request, query, and potentially delete the retained data.