Loading...
Validates that consumer deletion requests have been fully propagated to all downstream systems. When a consumer exercises their right to delete, the business must ensure deletion is carried out across all systems and service providers that hold the consumer's personal information.
Validates that feature columns do not exceed the configured null rate threshold. Excessive missing values in feature columns degrade model training quality and can introduce bias. Under EU AI Act Article 10, training data must be complete in view of the intended purpose of the AI system.
Asserts that when a status column has a specific value (e.g., 'active'), a set of required fields must all be populated (non-null). Enforces lifecycle-based data completeness rules where later stages demand richer data.
Validates that the Politically Exposed Person (PEP) flag is non-null for all customer records. The PEP flag must be explicitly set to true or false; a null value indicates the PEP screening was not performed, which is a compliance gap for enhanced due diligence requirements.
Validates that CVV/CVC/CID security codes are never stored post-authorization. The column must be NULL or empty for all rows. Storing CVV is explicitly prohibited by PCI-DSS even if encrypted.
Validates that sensitive authentication data (full magnetic stripe, PIN blocks, CVV2) is not stored after authorization. These columns must be NULL or empty in all post-authorization records.
Validates that FHIR Patient resources have a non-null, non-empty identifier. Per the HL7 FHIR R4 specification, Patient.identifier is used to carry official patient identifiers such as MRN, SSN, or national IDs. While FHIR marks this field as 0..*, most implementations require at least one identifier for patient matching and record linkage.
Validates that the customer legal name field is non-null and non-empty. A complete legal name is required for all customer records under CIP regulations to establish and verify customer identity during account opening.
Validates that the sanctions_screened flag is non-null and contains a valid boolean value (true or false) for all active customers. OFAC sanctions screening is a mandatory BSA/AML compliance requirement, and every active customer must have a documented screening status.
Asserts that a target column is not null whenever a condition column has a specific value. For example, 'shipping_date must not be null when order_status is shipped'. Enforces business rules where field population depends on another field's state.
Validates that each record has provenance fields populated: source_system, ingestion_date, and data_version. Under EU AI Act Article 10, providers must maintain data governance practices that ensure traceability of training data origin and lineage. Provenance tracking is essential for auditing, debugging model behavior, and demonstrating regulatory compliance.
Validates that SAR records contain all required documentation fields: narrative (non-empty with minimum 100 characters), activity_type, amount, and subject_name. Complete SAR documentation is essential for law enforcement utility and FinCEN regulatory compliance.
Validates that access audit trail records exist for all PHI data access events. Every record of PHI access must include non-null values for accessed_by (who accessed the data), accessed_at (when it was accessed), and access_reason (justification for access). Missing audit trail fields indicate a gap in access logging that violates HIPAA audit control requirements.
Asserts that a table contains all expected columns by name. Catches schema drift, missing columns after migrations, or upstream schema changes before downstream logic breaks.
Asserts that no row has all null values across a specified set of columns. Catches ghost rows or placeholder records that carry no meaningful data.
Asserts that a specified column contains no null values. This is the most fundamental completeness check — every row must have a value present in the target column.
Validates that records containing personal data have pii_flag set to true and anonymization_method populated. Under EU AI Act Article 10, training data containing personal data requires appropriate data governance measures including privacy-preserving techniques. Proper PII annotation ensures transparency and supports GDPR compliance alongside AI Act requirements.
Validates that every consumer privacy request is fully logged with all required fields. CCPA/CPRA requires businesses to maintain records of consumer requests (access, delete, correct, opt-out) for at least 24 months. Each request must include the request type, submission date, consumer identifier, and current processing status.