Loading...
Validates that values represent valid percentages. Supports both 0-100 scale (e.g., 75.5%) and 0.0-1.0 scale (e.g., 0.755). Catches data conversion errors between percentage representations.
Validates that W-2 Box 1 (Wages, tips, other compensation) is a numeric value greater than or equal to zero. Federal wages reported on Form W-2 must be non-negative. A negative value indicates a data entry error or system issue that would cause IRS e-file rejection.
Validates that financial amounts do not exceed a configurable limit. Catches data entry errors, currency conversion issues, and fraudulent transactions. Supports both upper and optional lower bounds.
Validates that age values fall within a reasonable human age range. Default range is 0-120, configurable for specific contexts such as working-age adults (18-65) or children (0-17).
Validates that the customer date of birth is a valid date, is not in the future, and that the customer is at least 18 years of age. CIP regulations require date of birth collection, and most financial products require the customer to be a legal adult.
Validates that stored card data has not exceeded its retention period. Card expiry dates older than the configured limit (default 10 years) should be flagged for deletion per PCI-DSS data retention policies.
Validates that personal data records do not exceed their retention period. Records older than the configured retention limit should be flagged for deletion to comply with GDPR storage limitation principle.
Validates that the fill number (refill count) on pharmacy claims is within the valid range of 0 to 99. A fill number of 0 indicates the original dispensing (first fill), while values 1-99 represent subsequent refills. This field is critical for tracking prescription utilization and detecting potential fraud or abuse.
Detects statistical outliers by checking if values fall within X standard deviations of the mean (z-score method). Values with |z-score| > threshold are flagged as potential outliers. Useful for detecting data entry errors, measurement anomalies, and distribution shifts.
Validates that PHI data records do not exceed the configured retention period. Records with a creation or effective date older than the allowed retention window should be flagged for review and disposal. HIPAA requires that covered entities retain certain documentation for at least 6 years, but organizational policies may impose shorter limits on active PHI storage.
Validates that the quantity dispensed on pharmacy claims is a positive value greater than zero and does not exceed 9999. Quantity dispensed represents the total units (tablets, capsules, mL, etc.) provided to the patient and must be a clinically reasonable positive number.
Validates that W-2 Box 3 (Social Security wages) does not exceed the annual Social Security wage base limit. For tax year 2025, the wage base is $168,600. Wages above this cap are not subject to Social Security tax and should not be reported in Box 3. Values must also be non-negative.
Validates that date values are not older than a configurable threshold. Catches default dates (1900-01-01, 1970-01-01), data migration artifacts, and stale records that may indicate data loading or conversion errors.
Validates that cash transaction amounts are non-negative and that transactions exceeding $10,000 are properly flagged for Currency Transaction Report (CTR) filing. Under the Bank Secrecy Act, financial institutions must report cash transactions over $10,000 to FinCEN.
Validates that the days supply field on pharmacy claims is within a plausible range. Days supply must be between 1 and 365 (inclusive). Values exceeding the warning threshold (default 90 days) are flagged as warnings, as they may indicate data entry errors or require clinical review. Zero or negative values are invalid.
Validates that all values in a numeric column fall within a specified minimum and maximum range (inclusive). Catches data entry errors, unit conversion issues, and out-of-bounds values.
Validates that process capability index (Cpk) values meet the minimum acceptable threshold. A Cpk of 1.33 or higher indicates a capable process where the spread of measured values falls well within specification limits. Values below 1.33 indicate the process may produce out-of-specification parts and should be flagged for investigation.
Validates that a date or timestamp column contains no values in the future. Catches data entry errors, timezone issues, and ETL bugs that produce future-dated records for columns like birth_date, transaction_date, or created_at.