# Data & source control
URL: https://docs.awellhealth.com/docs/data

> For the complete documentation index, see [llms.txt](https://docs.awellhealth.com/llms.txt).



This section covers knowing what data a care flow produces and getting it out, and treating the care
flows themselves as something to version and review.

## Getting data out [#getting-data-out]

* [Getting data out of Awell](/docs/data/getting-data-out-of-awell). The strategies available.
* [Get access to BigQuery](/docs/data/getting-access). BigQuery Studio, or a service account for
  external BI tools.
* [Data schema](/docs/data/data-schema). The tables, and the definition-versus-instance distinction
  that everything else depends on.
* [Monthly active patients](/docs/data/monthly-active-patients). What counts as active, and therefore
  what Awell bills on.

## Knowing what a care flow collects [#knowing-what-a-care-flow-collects]

* [Data catalog](/docs/data/data-catalog). What it lists.
* [Configure and use your data catalog](/docs/data/configure-use-your-data-catalog). PII flags,
  metadata, exports.

## Care flows as code [#care-flows-as-code]

* [Source Control](/docs/data/source-control). What it is and when to use it.
* [Set up Source Control](/docs/data/set-up-source-control). GitHub and GitLab.
* [How syncing works](/docs/data/syncing-to-scm). One repository per care flow, and a one-way sync.
* [Protect care flows](/docs/data/protect-care-flows). Require a merge before publication.
* [Deploy care flows](/docs/data/deploy-care-flows). From a CI/CD pipeline.
* [Care flow components as code](/docs/data/components). The JSON that lands in the repository.

## Who this is for [#who-this-is-for]

Engineers and analysts. The data catalog is worth a care flow author's time too: it's the one place
where the same value collected twice under two names becomes obvious.