Sources
Connect to claims feeds (837/835), flat files (CSV, TSV, fixed-width), databases (JDBC), and API endpoints. Configure connection credentials, schedules, and incremental loading.
B
AEGIS ISD DataBridge
Data loading to visualization without one-off ingestion work.
DataBridge connects claims feeds, flat files, and databases to structured datasets with visual field mapping, quality validation, pipeline execution with replay, and lakehouse publishing. It operates standalone — no AEGIS ISD Core or Detect required.
Capabilities
From raw data to analysis-ready datasets.
Datasets
Structured data containers with typed schemas, versioning, and lineage tracking. Datasets define the target shape for ingested data with validation rules applied at load time.
Mappings
Visual field mapping with transformations, type conversions, default values, and conditional logic. Map source fields to target dataset columns without writing code.
Quality Rules
Data validation and completeness checks applied at pipeline execution. Flag nulls, format violations, range violations, referential integrity failures, and custom business rules.
Runs & Replay
Pipeline execution with full run history, error logs, record counts, and timing. Replay any historical run against updated mappings or quality rules without re-ingesting source data.
Lakehouse Publishing
Publish validated datasets to the analytics layer for dashboards, reports, and downstream consumption. Data lands in a structured, query-optimized format ready for visualization.
Who it's for
Built for teams that move data into production.
DataBridge is a standalone product. It does not require AEGIS ISD Core or Detect to operate.
- Data Operations Teams
- Implementation and Onboarding Teams
- Customer Administrators
- Analytics and Reporting Teams
- IT Integration Engineers
What the demo covers
- Source and dataset creation workflow
- Visual field mapping with transformations
- Quality rule configuration and validation
- Pipeline run execution and monitoring
- Replay against updated mappings
- Lakehouse publishing and data verification
FAQ
Common questions about AEGIS ISD DataBridge.
Does DataBridge require Core or Detect?
No. DataBridge is a standalone product that operates independently. It connects data sources to datasets and publishes to a lakehouse without requiring any other AEGIS ISD product.
What data formats are supported?
DataBridge supports 837/835 claims feeds, CSV, TSV, fixed-width flat files, JDBC database connections, and REST API endpoints. Custom parsers can be configured for non-standard formats.
How does replay work?
Any completed pipeline run can be replayed against updated field mappings or quality rules. Replay uses the original source data snapshot, so you can iterate on transformations without re-ingesting from the source system.
What happens when quality rules fail?
Failed quality checks are logged per record with the specific rule violation, field name, and failing value. Records can be routed to a quarantine dataset for manual review or automatically excluded based on severity configuration.
How is data isolated between tenants?
DataBridge uses the same schema-per-tenant isolation as all AEGIS ISD products. Each tenant's sources, datasets, mappings, quality rules, and run history are completely isolated in dedicated database schemas.