---
title: Flume Data Model & Consolidated Data Store
slug: flume-data-model-and-consolidated-data-store
docTags:
createdAt: 2024-05-16T21:07:19.015Z
---
# Flume Data Model
Flume uses a canonical approach to data interoperability. Rather than integrating point-to-point redundantly, systems connect to Flume one time and then trade data with each other on a directed basis.
We call our canonical data model format the **Flume Data Model (****FDM****)**
- **Source data** is transformed from its native format -> to the FDM format
- **Destination data** is transformed from the FDM format -> to the destination system's native format
All mapping and transformation operations happen in Flume with little to no pre-processing required.
### Data Types
Supported data types include:
- Eligibility
- Medical Claim Service Lines
- Rx Claims
- Accumulators
- Authorizations
- Providers
- Groups
See the specification of the [Flume Data Model](docId\:Sq2D0I5tR_hQk2dnilPJR)
# Consolidated Data Store (CDS)
Data transformed into the FDM format is stored in the **Consolidated Data Store (****CDS****)**. **CDS** is hosted in your environment either on-cloud or on-premises with support for most major providers (AWS, GCP, MS Azure, etc...).
Each source Endpoint maintains its own, segregated data store within the **CDS**. Records are updated with subsequent files from source Endpoints. Flume supports both whole and incremental file delivery for both sources and destinations.
