680+ Data Quality Checks for ODCS Contract

Validate payment and remittance data — CARC/RARC codes, adjustment groups, paid vs billed consistency, and duplicate claim detection per X12 835 standards.

Validate federal spending data — UEI, CFDA, FIPS codes, congressional districts, and NIBRS crime reporting identifiers.

Monitor data pipeline health — row counts, freshness, schema changes, volume anomalies, and ingestion delays.

Validate financial messaging data — BIC/SWIFT codes, IBAN format with mod-97, monetary amounts per ISO 20022.

Validate transaction data — amounts, currencies, account references, dates, and reconciliation checks for payment processing.

Validate pharmacy claims — NDC codes, days supply, quantity dispensed, DEA schedules, prescriber NPI, and dispense date sequences per NCPDP standards.

Validate AI training data quality — label completeness, class balance, train/test leakage, feature null rates, data drift, bias coverage, and provenance tracking per EU AI Act Article 10.

Validate process capability, measurement systems, nonconformances, CAPA records, and BOM data for manufacturing quality.

Validate anti-money laundering data — SAR/CTR filing timeliness, customer due diligence, beneficial ownership, risk ratings, and sanctions screening per BSA/FinCEN requirements.

Data quality checks for critical infrastructure protection — asset inventory, timestamps, access controls, and safety reporting.

Validate claim records — numbers, statuses, dates, reserves, financial reconciliation, and policy linkage.

Validate HL7 FHIR R4 Patient resources — identifiers, names, gender, birth dates, addresses, marital status, contact points, and linked records.

Data quality rules for GDPR Article 5(1)(d) accuracy principle — validate personal data, consent records, and retention policies.

Essential data quality checks every team should have — null checks, format validation, uniqueness, freshness, and basic statistics.

Validate consumer privacy data — correction/deletion SLAs, opt-out enforcement, sensitive PI tagging, minor consent, and retention limits per CCPA/CPRA and US state privacy laws.

Validate drug codes, CDISC/SDTM clinical trial data, adverse events, and GMP batch records against FDA and ICH standards.

Validate call detail records, subscriber identifiers, SIM data — IMSI, IMEI, ICCID, E.164 phone numbers.

Validate Vehicle Identification Numbers against NHTSA and ISO 3779 standards — format, check digit, year code, and country of origin.

Validate regulatory reporting data for EU insurance — LEI, ISIN, CIC codes, SCR ratios, and asset classification.

Data quality controls for SOX Section 404 compliance — financial reporting accuracy, completeness, and auditability.

Validate payment card data — PAN Luhn check, masking compliance, expiration dates, and BIN format per PCI-DSS standards.

Data quality rules aligned to the 14 principles of BCBS 239 for risk data aggregation and reporting in banking.

Validate customer identity data — legal names, DOB, government IDs, address verification, KYC refresh, PEP flags, and duplicate detection per CIP/FATF/eIDAS requirements.

Extended GS1 validation — GTIN check digits, date formats, batch/lot numbers, and net weight fields for retail supply chain.

Validate W-2 tax form data — wages, Social Security caps, tax withholding consistency, EIN and SSN formats.

Validate clinical coding, patient records, and healthcare data against ICD-10 standards and HIPAA requirements.

Detect and validate removal of the 18 Safe Harbor identifiers — SSN, MRN, emails, phones, IPs, dates, ZIP codes, and biometric data in de-identified healthcare datasets.

Validate medical claims data — CPT, HCPCS, revenue codes, diagnosis pointers, amounts, date sequences, and timely filing per X12 837 standards.

Validate member enrollment data — member IDs, subscriber relationships, coverage dates, enrollment gaps, and plan types per X12 834/270/271 standards.

Clean customer data — validate emails, phones, addresses, deduplication, and completeness for CRM systems like Salesforce and HubSpot.

12 data-quality rules for National Notifiable Diseases Surveillance System (NNDSS) case notifications sent from states/jurisdictions to CDC, per the HL7 v2.5.1 Generic Message Mapping Guide (MMG) and PHIN Messaging Specification. Covers strictly-required ("R") data elements, PHIN VADS value sets (condition, case status, case class, sex, race, ethnicity, jurisdiction), date logic, timeliness, and duplicate suppression. HL7 messages missing required elements are rejected — clear these before transmission.

12 data-quality rules for the Home Mortgage Disclosure Act (HMDA) Loan/Application Register (LAR) submitted to the CFPB. Mirrors the edit categories in the Filing Instructions Guide (FIG, Section 5.3): syntactical, validity, and quality edits — record format, valid enumerations (action taken, loan type/purpose, lien status), LEI/ULI integrity, geography against the FFIEC census file, and reasonableness. Use it to clear the HMDA Platform edits before you file.

12 data-quality rules for XBRL financial reporting. Covers calculation linkbase footing, element sign correctness, context/period presence, taxonomy element validation, unit consistency, mandatory fact tagging, negative-value prohibitions, axis/member validation, decimals consistency, conflicting duplicates, ESEF block tagging, and full DQC ruleset compliance.

10 data-quality rules for Master Data Management (MDM). Covers duplicate detection, golden record uniqueness, cross-source linkage, orphan master detection, survivorship rules, match confidence, conflicting attributes, key standardization, merge/split audit trails, and golden record freshness.

10 data-quality rules for the FFIEC Consolidated Reports of Condition and Income (Call Report, FFIEC 031/041/051) filed by banks. Covers required schedules, the balance-sheet identity (Schedule RC: Total assets = Total liabilities and equity capital), income-statement consistency, MDRM item validity, RSSD identification, quarter-end period, and non-negative balances. Use it to clear validity edits before submitting to the agencies.

10 data-quality rules for automatic exchange of financial account information under the OECD Common Reporting Standard (CRS) and US FATCA (Form 8966), exchanged as XML to tax authorities. Covers required reporting elements, TIN presence/validity, ISO 4217 currency and ISO 3166 country codes, account-balance format, controlling persons for passive NFEs, and DocRefId uniqueness. Use it to pass schema/business-rule validation before transmission.

10 data-quality rules for CDC National Healthcare Safety Network (NHSN) healthcare-associated infection (HAI) reporting (CDA-based) from hospitals. Covers required event/summary elements, HAI event-type and pathogen value sets, NHSN location mapping, denominator (device-/patient-day) plausibility, date logic, and duplicate event suppression. Use it to validate HAI submissions before they reach NHSN (which feed CMS quality programs).

10 data-quality rules for immunization reporting to Immunization Information Systems (IIS) via HL7 v2.5.1 VXU messages. Covers required RXA (administration) elements, CVX vaccine and MVX manufacturer value sets, administration-date plausibility, lot number, dose volume, CVX/NDC consistency, and duplicate-dose suppression. Use it to validate VXU submissions before sending to the registry.

10 data-quality rules for EU transaction reporting under MiFID II / MiFIR (RTS 22) and EMIR derivatives reporting. Covers required fields, LEI and ISIN format, ISO 4217 currency and MIC venue codes, buy/sell indicator, price/quantity validity, UTC timestamps, and transaction-reference uniqueness. Use it to validate reports before submission to an ARM / trade repository.

10 data-quality rules for insurer statutory financial statements filed with the NAIC (Annual/Quarterly Statement). Covers required pages, the balance-sheet identity (assets = liabilities + capital and surplus), NAIC company-code validity, non-negative reserves, premium reconciliation, investment-schedule consistency, reporting period, and duplicate suppression. Use it to clear cross-checks before filing.

10 data-quality rules for SEC Form PF, filed by SEC-registered private fund advisers via the PFRD/IARD system. Covers required adviser/fund identifiers (CRD, CIK, fund ID/LEI), fund-type validity, non-negative gross/net assets, AUM consistency, reporting period, and duplicate suppression. Use it to validate Form PF data before filing.

10 data-quality rules for EPA Greenhouse Gas Reporting Program (GHGRP) submissions via e-GGRT under 40 CFR Part 98. Covers required facility identification and subparts, valid gas types and Global Warming Potentials, non-negative emissions, CO2e calculation consistency, reporting year, units, and duplicate suppression. Use it to validate the annual GHG report before e-GGRT submission.

10 data-quality rules for Drug Supply Chain Security Act (DSCSA) interoperable traceability, exchanged as GS1 EPCIS events. Covers required EPCIS event fields, GTIN/serial (SGTIN) format, lot and expiry, bizStep and disposition value sets, trading-partner GLNs, aggregation consistency, and duplicate-EPC suppression. Use it to validate EPCIS data before partner exchange or verification.

10 data-quality rules for the FERC Electric Quarterly Report (EQR) filed by jurisdictional sellers of wholesale electricity. Covers required seller/contract/transaction fields, product and rate-unit value sets, balancing-authority and point identifiers, non-negative price/quantity, quarter validity, and duplicate suppression. Use it to validate the EQR XML before submission to FERC.

10 data-quality rules for cancer-incidence reporting in the NAACCR (North American Association of Central Cancer Registries) fixed-format / XML standard, submitted by facilities to central/state registries. Covers required NAACCR items, ICD-O-3 primary-site and histology value sets, sex and date validity, age plausibility, geography, reportability, and duplicate tumor suppression. Use it to validate abstracts before registry submission.

10 data-quality rules for OECD BEPS Action 13 Country-by-Country Reporting (CbCR), exchanged as CbC XML to tax authorities. Covers required reporting entity and per-jurisdiction summary elements, ISO 3166 country and ISO 4217 currency codes, constituent-entity referential integrity, employee-count and summary validity, and DocRefId uniqueness. Use it to pass schema/business rules before transmission.

10 data-quality rules for the Medicare Hospital Cost Report (CMS-2552-10) filed by providers to their MAC via the MCReF / ECR format. Covers required worksheets, CMS Certification Number (CCN) validity, worksheet balancing and cost-to-charge consistency, non-negative beds/costs/charges, reporting period, and duplicate suppression. Use it to clear edits before submission.

10 data-quality rules for OSHA Form 300A injury and illness summary data submitted electronically to OSHA (ITA). Covers required establishment identification, valid NAICS, non-negative case and day counts, total-cases reconciliation, employee/hours plausibility, reporting year, and duplicate suppression. Use it to validate the 300A before ITA submission.

10 data-quality rules for the EPA National Emissions Inventory (NEI), reported by state/local/tribal agencies via the Emissions Inventory System (EIS). Covers required facility/unit/process identifiers, valid SCC and pollutant codes, non-negative emissions, units of measure, calculation method, reporting year, and duplicate suppression. Use it to validate EIS submissions before upload.

10 data-quality rules for EU Corporate Sustainability Reporting Directive (CSRD) disclosures prepared under the ESRS and tagged in the ESEF/ESRS XBRL taxonomy. Covers required datapoint identification, ESRS datapoint conformance, units of measure, GHG Scope 1+2+3 consistency, non-negative metrics, reporting period, and duplicate suppression. Use it to validate the sustainability statement before filing.

10 data-quality rules for the annual CMS-416 EPSDT (Early and Periodic Screening, Diagnostic and Treatment) report submitted by state Medicaid agencies to CMS. Covers required state/period identification, valid age groups, non-negative eligible and screened counts, screening-ratio bounds, population reconciliation, and duplicate suppression. Use it to validate the CMS-416 before submission.

10 data-quality rules for adverse-event reports submitted to the FDA Adverse Event Reporting System (FAERS) in the ICH E2B(R3) format. Covers required safety-report identifiers, MedDRA-coded reactions, seriousness and report- type validity, drug role and country codes, date logic, and duplicate safety-report suppression. Use it to validate ICSRs before gateway submission.

10 data-quality rules for the FINRA Consolidated Audit Trail (CAT) — order and trade event reporting by broker-dealers. Covers required event fields, event-type and side value sets, symbol and MPID validity, nanosecond timestamp format, non-negative price/quantity, event-time ordering, and duplicate suppression. Use it to validate CAT events before submission to avoid rejections and repairs.

10 data-quality rules for the EIA-923 Power Plant Operations Report (generation, fuel consumption, and stocks) filed by plant operators to the US Energy Information Administration. Covers required plant/prime-mover/fuel identifiers, value-set conformance, non-negative generation and fuel, heat-content plausibility, reporting period, and duplicate suppression. Use it to validate the EIA-923 before submission.

10 data-quality rules for EU bank supervisory reporting under the EBA Implementing Technical Standards — COREP (own funds / capital) and FINREP (financial reporting), submitted as XBRL. Covers required template identification, LEI, currency, capital-ratio bounds, own-funds and RWA consistency, reporting reference date, and duplicate suppression. Use it to clear EBA validation rules before filing.

10 data-quality rules for the CMS Minimum Data Set (MDS 3.0) resident assessments submitted by nursing homes to the iQIES/QIES ASAP system. Covers required RAI items, value-set conformance, assessment-type and reason-for-assessment validity, date logic, provider/resident identifiers, and duplicate assessment suppression. Use it to clear MDS edits before submission.

10 data-quality rules for prehospital EMS records reported under NEMSIS (National EMS Information System) from agencies to state and national EMS databases. Covers required event elements, value-set conformance (disposition, complaint), event time sequencing, agency/unit identifiers, and duplicate record suppression. Use it to validate NEMSIS XML before submission.

10 data-quality rules for property & casualty insurance data exchanged in the ACORD standard (policy, party, coverage, and claim messages) between carriers, agencies, and partners. Covers required policy/party elements, line-of-business and state value sets, non-negative premium/limit, policy date logic, currency, and duplicate suppression. Use it to validate ACORD messages before exchange.

12 data-quality rules for HL7 FHIR R4 clinical data (US Core), covering the core clinical resources exchanged across EHRs and APIs — Patient, Encounter, Condition, Observation, MedicationRequest, Procedure, AllergyIntolerance, and DiagnosticReport. Checks resource conformance, required US Core elements, subject-reference resolution, terminology bindings (LOINC, SNOMED CT, RxNorm, ICD-10-CM), status vocabularies, date plausibility, and duplicate suppression.

11 data-quality rules for the CMS Interoperability and Patient Access Final Rule (CMS-9115-F), which requires impacted payers (MA, Medicaid, CHIP, QHP) to expose a Patient Access API and a Provider Directory API over HL7 FHIR R4 (US Core / Da Vinci PDex & Plan-Net). Covers FHIR R4 conformance, required profile elements, NPI and terminology value sets, reference resolution, formulary drug codes, and provider-directory freshness. Use it to validate the API data before it goes live.

12 data-quality rules for CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F). Covers FHIR R4 conformance, US Core USCDI requirements, prior-authorization lifecycle, payer-to-payer exchange, provider attribution, Da Vinci PAS profiles, bulk export integrity, and terminology bindings. Effective dates align with Jan 1 2026 enforcement milestones.

10 data-quality rules for FDA clinical-trial data submitted as CDISC SDTM datasets (within an eCTD submission). Covers required identifier variables, USUBJID cross-domain referential integrity, CDISC Controlled Terminology conformance, ISO 8601 dates, DOMAIN consistency, sequence uniqueness, and visit referential checks. Use it to catch SDTM conformance issues before a define.xml / Pinnacle 21 validation run.

10 data-quality rules for source-to-target reconciliation. Covers row count matching, control totals, distinct key counts, missing/extra key detection, duplicate-on-load, row hash sampling, balance-to-zero, watermark gap detection, and partition completeness.

12 data-quality rules for mandated public-health disease reporting from hospitals and labs to state/local health departments and CDC. Covers the HL7 electronic Initial Case Report (eICR) and Electronic Laboratory Reporting (ELR, HL7 v2.5.1): required data elements, value-set conformance (LOINC, SNOMED CT, ICD-10-CM, and the Reportable Conditions Trigger Codes RCTC), reportability, timeliness, condition/result consistency, and duplicate case suppression. Use it to certify a submission is conformant and complete BEFORE it is sent.

10 data-quality rules for referential integrity. Covers foreign key validation, orphan child detection, self-reference resolution, circular hierarchy detection, bridge table completeness, one-to-one cardinality, type/format matching, soft-delete reference checks, lookup/dimension mapping, and parent-child completeness.

10 data-quality rules for CMS electronic clinical quality measure (eCQM) reporting via QRDA (Quality Reporting Document Architecture) Category I and III. Covers required QRDA header elements, CMS measure identifiers, VSAC value-set conformance, measure population logic (numerator within denominator), reporting-period validity, and performance-rate bounds. Use it to validate a QRDA submission before sending to CMS (Promoting Interoperability / MIPS).