Data & source control

Get care flow data out for analysis, keep track of what a care flow collects, and version care flows as code in a Git repository.

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 of Awell. The strategies available.
Get access to BigQuery. BigQuery Studio, or a service account for external BI tools.
Data schema. The tables, and the definition-versus-instance distinction that everything else depends on.
Monthly active patients. What counts as active, and therefore what Awell bills on.

Knowing what a care flow collects

Data catalog. What it lists.
Configure and use your data catalog. PII flags, metadata, exports.

Care flows as code

Source Control. What it is and when to use it.
Set up Source Control. GitHub and GitLab.
How syncing works. One repository per care flow, and a one-way sync.
Protect care flows. Require a merge before publication.
Deploy care flows. From a CI/CD pipeline.
Care flow components as code. The JSON that lands in the repository.

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.