Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Overview

The goal OHDSI Study Design Assistant (SDA) is to provide an experience similar to working with a coding agent but for designing and executing observational retrospective studies using OHDSI tools. SDA is designed to organize and enable users to interact with a wide variety of agentic tools to suppor their study work. It does so by providing a clean separation between the agentic user experience and the generative AI tools. Check out the tag `first_agent_and_strategus` for the first version to assist with Strategus (not validated) as shown [in this video](https://pitt.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=f802b01f-9bce-4f38-a4c4-b3f800e6ebdd&start=254) or the [more recent video for the second version](https://pitt.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=34ed8cfe-2e4c-40b7-9efa-b40800b75bd5) (no sound). This demonstrates a possible way for the agent to help the user design, run, and interpret the results of an OHDSI incidence rate analysis using the [CohortIncidenceModule](https://raw.githubusercontent.com/OHDSI/Strategus/main/inst/doc/CreatingAnalysisSpecification.pdf) of [OHDSI Strategus](https://github.com/OHDSI/Strategus).
The goal OHDSI Study Design Assistant (SDA) is to provide an experience similar to working with a coding agent but for designing and executing observational retrospective studies using OHDSI tools. SDA is designed to organize and enable users to interact with a wide variety of agentic tools to suppor their study work. It does so by providing a clean separation between the agentic user experience and the generative AI tools. Check out the tag `first_agent_and_strategus` for the first version to assist with Strategus (not validated) as shown in the [more recent video for the second version](https://pitt.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=34ed8cfe-2e4c-40b7-9efa-b40800b75bd5) (no sound). This demonstrates a possible way for the agent to help the user design, run, and interpret the results of an OHDSI incidence rate analysis using the [CohortIncidenceModule](https://raw.githubusercontent.com/OHDSI/Strategus/main/inst/doc/CreatingAnalysisSpecification.pdf) of [OHDSI Strategus](https://github.com/OHDSI/Strategus). This older [ video](https://pitt.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=f802b01f-9bce-4f38-a4c4-b3f800e6ebdd&start=254) shows an prior test of this concept.

#### Want to contribute?

Expand All @@ -16,7 +16,9 @@ Here are some ways:

### Near term

Review with colleagues, test that scripts function, deploy to a different environment for portability testing, and plan. Extend the study agent so it uses results from Data Quality Dashboard, Achilles Heel data quality checks, and Achilles data source characterizations over one or more sources that a user intends to use within a study. In this mode, the study agent derive insights from those sources based on the user's study intent. This is important because it will make the information in the characterizations and QC reports more relevant and actionable to users than static and broad-scope reports (current state).
- `data_quality_interpretation` : study agent provides interpretation from Data Quality Dashboard, Achilles Heel data quality checks, and Achilles data source characterizations over one or more sources that a user intends to use within a study. In this mode, the study agent derive insights from those sources based on the user's study intent. This is important because it will make the information in the characterizations and QC reports more relevant and actionable to users than static and broad-scope reports (current state). Users will use this tool from R initially.

- `create_new_phenotype_definition` : Study agent will guide the user through the creation of a definition for an EHR phenotype for the target or outcome cohort relevant to their study intent. This workflow involves selection of concepts, organization of concepts into concept sets, and organization into cohort definition logic. Users will use this tool from R or Atlas initially.

### Long term

Expand Down
Loading