OHDSI / WebAPI

OHDSI WebAPI contains all OHDSI services that can be called from OHDSI applications
Apache License 2.0
130 stars 169 forks source link

`achilles_result_concept_count` build is not documented #2303

Closed anthonysena closed 1 year ago

anthonysena commented 1 year ago

We need to add to the wiki the step to build the Achilles result concept count. The script to run is here: https://github.com/OHDSI/WebAPI/blob/master/src/main/resources/ddl/achilles/achilles_result_concept_count.sql. If the achilles_result_concept_count table does not exist in the results schema this prevents users from obtaining record counts for a selected concept in the Atlas UI.

chrisknoll commented 1 year ago

This is accessible via ddl/achilles so that could be part of the instructions to set up the results schema. I am wondering if we should include this by default (ie ddl/results)

konstjar commented 1 year ago

It could not be merged with ddl/results. ddl/achilles requires Achilles to be executed. Here is a order of the steps:

  1. Apply ddl/results
  2. Run Achilles
  3. Apply ddl/achilles
chrisknoll commented 1 year ago

Actually. ddl/results does not depend on achilles. I would say the order is:

  1. ETL data into CDM
  2. Run Achilles (this will require a schema for results, but none of the tables that WebAPI uses is required to be created)
  3. Apply ddl/results (if this had achilles in it), or ddl/results and then ddl/achilles
  4. Add SOURCE to WebAPI to new CDM
  5. Do great science
anthonysena commented 1 year ago

Updated the wiki with this information: https://github.com/OHDSI/WebAPI/wiki/CDM-Configuration#concept-count-tables.