Capabilities

multiple data formats flume supports both standardized data formats (edi, fhir, ncpdp, etc ) and custom formats for the data types listed below supported data types eligibility medical claim service lines rx claims accumulators authorizations providers groups other/customer defined multiple file types flume supports multiple file types including tabular formats (csv, tsv, psv) json fixed width archives/compressed files proprietary & custom format multiple protocols flume supports multiple data movement protocols including api, sftp, and event stream data mapping & transformation with flume, source data is transformed into the flume data model (fdm) format destination data is transformed from the fdm to the destination system's native format transformations are managed in flume with either sql or python mappings, depending on the complexity of the transformation flume supports both complete and incremental files for both sources and destinations this means a destination can choose to receive a change file or a complete file flume also supports metadata based updates such as term by omission (tbo) flume tracks file change history, such that it can recall files transacted to/from various sources and destinations at different points in time data quality flume has built in data quality processes to ensure accuracy and cleanliness for both source and destination systems validation flume enables anomaly detection on source transactions through control files or user defined validation logic rules can be written in either sql or python response files flume enables destination transactions to be validated against system generated response files routing & orchestration flume is direction agnostic any source can point to any destination as long as they are the same data type sources and destinations can be both within your organization or external trading partners transactions can be scheduled to sync to or from flume at any frequency, and down to every 15 m inutes flume can filter data to send data applicable to specific trading partners using business objects (see key concepts for more detail) business objects are configured based on customer's needs (examples include groups, blocks of business, plans, and products), empowering non technical users to add them directly within the platform and seamlessly share only applicable data with relevant parties user dashboard flume's dashboard provides you with real time insights into the overall health and status of your trading environment specific capabilities view transaction history and file change history monitoring alerts identify and allow rapid resolution of common errors such as file not found or validation rule errors transaction summaries over specific time intervals including success rate, transaction volume, data type, and record type furthermore, flume's interface allows you to setup integrations by configuring endpoints, connections, relays, and business objects data storage management data syncs with flume from source systems and is stored in the consolidated data store (cds) the cds is your portable data store hosted in your environment either in the cloud or on premises vendor management fully managed service is optionally provided including vendor communication, file configuration, testing, and troubleshooting & resolution