Flume Data Model & Consolidated Data Store

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