conceptSet included concepts

[bviernes]

I may be wrong, but I don't see anyway to review descendant or mapped concepts from a created concept set in Capr. It seems like it could be possible to add that functionality to the getConceptSetDetails() function. When creating concept sets in Atlas, you have the functionality to search for concept, add it to your concept set, and then see all the included concepts.

If getConceptSetDetails() currently queries the CONCEPT table to get back related info from a given CDM, it could just add a join to CONCEPT_ANCESTOR and CONCEPT_RELATIONSHIP tables for descendant and mapped concepts.

[ob325]

I agree it would be nice to be able to show in a research notebook (before even generating a cohort) what the descendants are for a given ancestor concept. Since getConceptSetDetails returns a modified copy of a concept set with additional details, and gets used downstream in cohort generation, we might not want to mess with that S4 class and break something. Could we instead add a getDescendants function as part of the Capr vocabulary queries we are developing?

[mdlavallee92]

hey all,

currently the goal is to just build the circe equivalent structure of the concept set to serialize into standardized ohdsi sql. The mapping result is not available. For example:

cs(desecendents(201826), name = "t2d)

this really creates the structure as S4 which serializes to a circe json which can be serialized to standardized ohdsi-sql. The UI to check what individual concepts make up the set would be great for the user. The decision to omit this one was a practical one. First-level Capr can build a circe equivalent object. Second level would add all the aesthetics and user experience pieces to compliment "building the circe".

Adding this feature is possible....you can either add it as part of the print or you could create a function to preview all the standard terms used in the set as you outlined. Feel free to make a pr of this feature