All Rules

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 the subscriber relationship code is one of the allowed values defined in the X12 270/271 eligibility transaction standard. Valid codes include 18 (Self), 01 (Spouse), 19 (Child), 20 (Employee), 21 (Unknown), 39 (Organ Donor), 40 (Cadaver Donor), 53 (Life Partner), and G8 (Other Relationship).

Validates that HumanName.use values conform to the HL7 FHIR R4 NameUse value set. Only the defined codes are permitted: usual, official, temp, nickname, anonymous, old, and maiden.

Validates that values conform to the FDA National Drug Code (NDC) 10-digit format with hyphens. The NDC uniquely identifies a drug product and supports three segment patterns: 4-4-2 (labeler-product-package), 5-3-2, and 5-4-1. All three formats are accepted by the FDA NDC Directory.

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 values conform to the HL7 FHIR R4 date data type format. FHIR dates follow ISO 8601 and allow partial precision: YYYY (year only), YYYY-MM (year and month), or YYYY-MM-DD (full date). This flexibility supports clinical scenarios where only partial date information is known.

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 Claim Adjustment Reason Codes (CARCs) are 1 to 3 digits in the range 1-999. CARCs are used in X12 835 remittance advice transactions to communicate why a claim or service line was adjusted. Each code must be a numeric value maintained by the X12 Code Maintenance Committee and published by the Washington Publishing Company (WPC).

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.

Validates that smart meter reading intervals are one of the standard values: 5, 15, 30, or 60 minutes. These intervals represent the industry-standard data collection frequencies for Advanced Metering Infrastructure (AMI) and are critical for accurate load profiling, billing, and demand response programs.

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 position 1 of the VIN contains a recognized World Manufacturer Identifier (WMI) country code per ISO 3780. Position 1 indicates the country or region of manufacture: 1-5 = North America, 6-7 = Oceania, 8-9 = South America, A-H = Africa, J-R = Asia, S-Z = Europe.

Validates the NPI check digit using the Luhn algorithm as specified in 45 CFR 162.406. The algorithm prefixes '80840' to the first 9 digits of the NPI, then applies the Luhn mod-10 formula. The 10th digit of the NPI must equal the computed check digit. This ensures the NPI is not just well-formed but mathematically valid.