> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Datasets & Document Sources

> Numbers and dates are illustrative. For your own build, connect your data sources and run the same steps. Set connectors at the start of a session; credentials are managed in co…

## Example datasets used in this workshop

<table>
  <tr><th>Dataset</th><th>What it is</th><th>Used for</th></tr>
  <tr><td>**Clinical + claims (Tuva model)**</td><td>A synthetic, patient-level Medicare claims + clinical dataset (the open Tuva data model): patients, encounters, conditions, procedures, claims, eligibility, member-months.</td><td>Track A — rich entities for metrics like readmission rate and cost PMPM.</td></tr>
  <tr><td>**Medicare Part D + demographics**</td><td>Public CMS Part D landscape data — plans, formulary, costs, prescribers — plus county-level socioeconomic reference data.</td><td>Cross-source analysis and the role-based-access examples.</td></tr>
</table>

<Note>
  **Demo data** —

  Numbers and dates are illustrative. For your own build, connect **your** data sources and run the same steps. Set connectors at the start of a session; credentials are managed in connector settings — never stored in the ontology repo.
</Note>

## Bringing your documents to Ana

<table>
  <tr><th>Method</th><th>How it works</th><th>Best for</th></tr>
  <tr><td>**Upload to a session**</td><td>Add files directly (PDF, DOCX, PPTX, XLSX, CSV, Markdown).</td><td>A handful of documents, or adding "one more".</td></tr>
  <tr><td>**Cloud document store**</td><td>Connect a shared drive and point Ana at a folder.</td><td>Teams whose documents live in a managed drive.</td></tr>
  <tr><td>**Enterprise document systems**</td><td>SharePoint / OneDrive, Confluence, or internal object storage (S3 / Azure Blob / GCS).</td><td>Larger or regulated organizations.</td></tr>
  <tr><td>**Git repository**</td><td>Keep the distilled ontology (Markdown + .tql) in your own git repo.</td><td>The governed ontology itself.</td></tr>
</table>

<Warning>
  **For regulated organizations** —

  Keep documents and data **inside your own boundary**. With a single-tenant / in-VPC deployment, sensitive content never leaves your environment, and Ana ingests from your **sanctioned** stores rather than a consumer drive. A common pattern is a **watched location** — a designated folder or bucket Ana monitors, so a newly dropped document is distilled into the ontology as a reviewable change.
</Warning>

The flow: raw documents are **inputs**; the ontology is the **governed output** they become. You don't upload raw binaries into the ontology repo — you feed them to Ana, and she distills them into the governed Markdown/`.tql` that lives there.