> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metriport.com/llms.txt
> Use this file to discover all available pages before exploring further.
# General
> Transform your data for analytics and pipe it into warehouses like Snowflake, Redshift, BigQuery, and more
Metriport provides tools to transform your data for analytics and pipe it into warehouses like Snowflake, Redshift,
BigQuery, and more - enabling you to do population level analytics on your patient data.
There are two primary ways to perform analytics on your patient population data: Managed and Manual.
## Managed: Snowflake Data Warehouse
Metriport offers direct integration with Snowflake, allowing you to analyze your patient data in a
powerful, scalable cloud data warehouse. This approach provides:
* **Managed data transformation**: Metriport does the heavy lifting to get your data into an analytics
ready data warehouse 🎉
* **Near Real-time Analytics**: Query your patient data right after it's processed
* **Scalable Performance**: Leverage Snowflake's elastic compute resources for complex analytics
* **Secure Data Sharing**: Use Snowflake's `Secure Data Sharing` feature for secure data collaboration
### Setting Up Snowflake Integration
1. **Create a Snowflake Account**: Sign up for a
Business Critical Edition
Snowflake account and share your account identification with us:
* View account details:
* Copy these fields and share them with your Metriport account manager:
* Organization Name
* Account Name
* Account Locator
* Cloud Provider (AWS, Azure, GCP)
* Region
2. **Access the data**: Metriport will share your patients' medical data with your Snowflake instance:
* It uses Snowflake's Secure Data Sharing
for secure, compliant, and zero-copy data sharing between Metriport and your Snowflake account.
* Data will be visible through Secure Views, one for each resource type.
## Manual: Tuva Data Model
To accomplish this, we standardize our data into the [Tuva data model](https://thetuvaproject.com/) -
another open source project that focuses on making healthcare data more standardized for analytics.
The Tuva approach provides:
* **Open Source**: Transparent, community-driven data modeling
* **Healthcare-Specific Metrics**: Built-in calculations for common healthcare KPIs
* **Multi-Warehouse Support**: Works with Snowflake, BigQuery, Redshift, and other warehouses
To get started with Tuva, check out our
[data warehouse connector documentation](https://thetuvaproject.com/connectors/pre-built-connectors#metriport) on the Tuva site.
## Schema Documentation
The Metriport data model consists of a normalzied FHIR schema along with computed columns to ease querying complexity. Each table is designed to capture specific information in a standardized format for analytics.
**See [Core tables by resource](/medical-api/handling-data/schema-v100/README)** for an index of all core tables grouped by main resource type.
### Core Tables
* **[AllergyIntolerance](/medical-api/handling-data/schema-v100/allergyintolerance/base)** - Patient allergies and intolerances, with reaction and manifestation detail tables
* **[Binary](/medical-api/handling-data/schema-v100/binary)** - Binary content (e.g., documents, images) referenced by the system
* **[CarePlan](/medical-api/handling-data/schema-v100/careplan/base)** - Patient care plans and activities
* **[Communication](/medical-api/handling-data/schema-v100/communication/base)** - Communications (e.g., messages, notifications) associated with the patient
* **[Composition](/medical-api/handling-data/schema-v100/composition/base)** - Clinical documents (e.g., discharge summary) with sections, attestation, and events
* **[Condition](/medical-api/handling-data/schema-v100/condition/base)** - Symptoms, problems, complaints, and diagnoses reported during encounters
* **[Consent](/medical-api/handling-data/schema-v100/consent/base)** - Patient consent and provision/category codings
* **[Coverage](/medical-api/handling-data/schema-v100/coverage/base)** - Insurance and payment coverage
* **[Device](/medical-api/handling-data/schema-v100/device/base)** - Devices (e.g., implants, equipment) with optional version detail
* **[DiagnosticReport](/medical-api/handling-data/schema-v100/diagnosticreport/base)** - Diagnostic reports containing test results and clinical findings
* **[DocumentReference](/medical-api/handling-data/schema-v100/documentreference/base)** - References to clinical documents and their content/attachments
* **[Encounter](/medical-api/handling-data/schema-v100/encounter/base)** - Unique patient interactions with the healthcare system
* **[FamilyMemberHistory](/medical-api/handling-data/schema-v100/familymemberhistory/base)** - Family member history and conditions
* **[Goal](/medical-api/handling-data/schema-v100/goal/base)** - Patient goals and targets
* **[Immunization](/medical-api/handling-data/schema-v100/immunization/base)** - Vaccines administered to patients
* **[Location](/medical-api/handling-data/schema-v100/location/base)** - Practice and facility locations where care is provided
* **[Medication](/medical-api/handling-data/schema-v100/medication/base)** - Medications ordered or administered during encounters
* **[MedicationAdministration](/medical-api/handling-data/schema-v100/medicationadministration/base)** - Records of medications actually administered to patients
* **[MedicationDispense](/medical-api/handling-data/schema-v100/medicationdispense/base)** - Records of medications dispensed to patients
* **[MedicationRequest](/medical-api/handling-data/schema-v100/medicationrequest/base)** - Medication orders and prescriptions
* **[MedicationStatement](/medical-api/handling-data/schema-v100/medicationstatement/base)** - Patient-reported medication information (with dosage table)
* **[Observation](/medical-api/handling-data/schema-v100/observation/base)** - Clinical measurements like blood pressure, height, and weight (with reference range table)
* **[Organization](/medical-api/handling-data/schema-v100/organization/base)** - Healthcare organizations and facilities
* **[Patient](/medical-api/handling-data/schema-v100/patient/base)** - Patient demographic information and core patient data
* **[Practitioner](/medical-api/handling-data/schema-v100/practitioner/base)** - Healthcare providers who deliver care
* **[Procedure](/medical-api/handling-data/schema-v100/procedure/base)** - Procedures performed on patients
* **[ServiceRequest](/medical-api/handling-data/schema-v100/servicerequest/base)** - Orders and referrals for procedures, labs, or other services