Skip to main content

DataGuard: A Self-Hosted, AI-Accelerated Architecture for Multi-Source Regulatory Data Quality and Governance

Abstract

Regulated industries — banking, insurance, capital markets, life sciences, and supply chain — are subject to mandatory data submissions governed by frameworks such as the Basel Committee's BCBS 239 principles, the Federal Reserve's Comprehensive Capital Analysis and Review (CCAR), FinCEN anti-money-laundering (AML) obligations, HIPAA, and FDA 21 CFR Part 11. Existing tooling for validating data against these obligations falls into four inadequate categories: manual spreadsheet-based checks that do not scale, commercial data-quality suites that require multi-month implementations and dedicated engineering teams, brittle in-house scripts tied to individual engineers, and vendor-hosted SaaS platforms that raise data-residency concerns for regulated data. This paper presents the architecture of DataGuard, a self-hosted, AI-accelerated data quality and governance platform that integrates five technology domains — large language model (LLM) assisted rule authoring, an eight-database enterprise connectivity layer, cross-source column-level data lineage analysis, a library of seven regulatory rule packs spanning five industry sectors, and cloud-native, zero-infrastructure deployment — into a single deployable application. We describe the platform's layered-monolith architecture, its REST API surface, its four distinct Claude-API-based AI subsystems (including an automated metadata cataloging engine, DocuSmart), its three-tier column-matching algorithm for lineage inference, and its security and governance design, including an OAuth-based Git integration that establishes a version-controlled chain of custody for validation rules and results. We further situate the platform against alternative approaches, walk through an end-to-end validation session on the live application, and discuss the architecture's limitations and directions for future work. The platform is publicly accessible and its source is version-controlled, allowing independent verification of the claims described herein.

References

[1] Basel Committee on Banking Supervision. (2013). Principles for Effective Risk Data Aggregation and Risk Reporting (BCBS 239). Bank for International Settlements.
[2] Board of Governors of the Federal Reserve System. Comprehensive Capital Analysis and Review (CCAR): Program overview and FR Y-14 reporting instructions.
[3] Financial Crimes Enforcement Network (FinCEN). Anti-Money-Laundering (AML) program requirements, 31 U.S.C. § 5311 et seq.
[4] U.S. Department of Health and Human Services. Health Insurance Portability and Accountability Act of 1996 (HIPAA), Privacy and Security Rules.
[5] U.S. Food and Drug Administration. Title 21 CFR Part 11 — Electronic Records; Electronic Signatures.
[6] International Organization for Standardization. ISO 17442:2020 — Legal Entity Identifier (LEI) code.
[7] International Organization for Standardization. ISO 4217 — Currency codes.
[8] International Council for Harmonisation. ICH E2B(R3) — Electronic Transmission of Individual Case Safety Reports.
[9] MedDRA Maintenance and Support Services Organization / U.S. National Cancer Institute. MedDRA and CTCAE severity grading terminologies.
[10] Clinical Data Interchange Standards Consortium (CDISC). Study Data Tabulation Model (SDTM) Implementation Guide.