> For the complete documentation index, see [llms.txt](https://docs.gradienthealth.io/gradient-atlas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gradienthealth.io/gradient-atlas/gradient-atlas-is....md). # Gradient Atlas is... Gradient Atlas is the one step tool to create medical cohorts. Welcome to Gradient Health, Inc's Atlas, a searchable medical repository. With Atlas, you can * Create cohorts * Search by **any** * body part * DICOM tag * Any text within medical report * Any pathology * Request help if you can’t find what you are looking for Atlas was designed to help researchers and data engineers find their next training set for any medical application you can imagine. Search our 14M studies from the United States and Brazil and build a cohort for your next project. We have a white glove service to export your DICOM cohorts to you after you look through it. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gradienthealth.io/gradient-atlas/gradient-atlas-is....md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.