> For the complete documentation index, see [llms.txt](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/gci-help/evidence-collection-genetic-evidence/curating-case-control-information.md).

# Curating Case-Control Information

The top section of the curation interface shows the publication currently being curated.&#x20;

Case-control studies are those in which statistical analysis is used to evaluate enrichment of variants in cases compared to controls. Each case-control study should be independently assessed based on the criteria outlined in the [SOP](https://clinicalgenome.org/docs/gene-disease-validity-standard-operating-procedure-version-8/) (Case-Control Data section) to evaluate the quality of the study design. The score status of case-control studies can now also be selected as "Review" or "Contradicts".

All required fields (marked with a star) must be filled in before the curated record for an individual can be saved. The required fields are:

* **Case-Control Label**, **Case Cohort Label** and **Control Cohort Label** are free-text identifiers assigned by the curator. They should be used to uniquely identify the cohorts described in a publication. If possible, use the identifiers given in the publication.&#x20;
* **Disease(s) in Common** -- usually select “Copy disease term from Gene-Disease Record”.
* **Number of Cases with variant(s) in the gene in question** -- fill in the number given in the publication
* **Number of Controls with variant(s) in the gene in question** -- fill in the number given in the publication
* **Number of all Cases genotyped/sequenced** -- fill in the number given in the publication
* **Number of all Controls genotyped/sequenced** -- fill in the number given in the publication

For the sections sections following the Case-Control Label, there is a split screen where Case Cohort information is entered in the left panel and Control Cohort information is entered in the right panel.

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FYjMVlMtzi47hrK4jINtM%2FScreen%20Shot%202022-06-01%20at%209.57.35%20AM.png?alt=media\&token=e84da8e2-6e33-4a7a-92c6-0cf64d4c7bed)

In the case cohort "Disease(s) & Phenotype(s)" section, you must enter either disease or phenotype information. Generally, you can simply copy the disease from the gene-disease record. In the "Demographics" and "Methods" subsections, enter as much information as is given in the publication.

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FCwYUkBqQVBI6L5ha9nyR%2FScreen%20Shot%202022-07-15%20at%2010.29.42%20AM.png?alt=media\&token=8ad6e23a-a765-490f-8260-0241909757b7)

Additional required information for both cases and controls must be entered in the "Power" section. Additional information can be entered for both cases and controls in the "Additional Information" section below.

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FykQYGBfdc6Joh2oSnNtC%2FScreen%20Shot%202022-06-01%20at%2010.07.02%20AM.png?alt=media\&token=efcaa4b7-ff4d-4a5d-b068-23d67fea47d2)

The "Case-Control Evaluation" section enables you to enter information that is used by the GCEP to determine whether the study can be scored. A "Study type" must be entered in order to score the study. The following "Statistics", "Bias Category" and "Comments" subsections facilitate evaluation of the quality of the case-control study.

![](https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2FfVSszoGwB1v8q26YQaYO%2FScreen%20Shot%202022-06-01%20at%205.19.59%20PM.png?alt=media\&token=ed471151-16ce-4b3d-bd0b-c8aecd944347)

Case-control studies are evaluated and points are assigned at the discretion of experts. The "Case-Control Score" section now allows the selection of a scoring status that includes the "Review" and "Contradicts" options. To score a study, select "Score" and the appropriate numerical value from the "Score" drop-down menu.

<figure><img src="https://453646021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzjRMfxI6chghHwy4VhQv%2Fuploads%2F6gt26VKNI2e7eRaCukIG%2FScreen%20Shot%202023-02-27%20at%2010.45.09%20AM.png?alt=media&amp;token=cec7e4e0-b9b9-4b2a-9afc-517e515c5314" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Remember to click the "Save" button at the bottom of the page. If you click "Cancel" or navigate away from the page without saving, all entered data will be lost.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vci-gci-docs.clinicalgenome.org/vci-gci-docs/gci-help/evidence-collection-genetic-evidence/curating-case-control-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
