Comment on the CDC Data Intermediaries RFI: Data Quality Certification as a Universal Intermediary Baseline
Box Commons · 30 N Gould St Ste N, Sheridan WY 82801
- HITRUST certifies the pipe. Nobody certifies the water. TEFCA mandates third-party security certification for QHINs but nothing comparable for the data payload.
- Extend NCQA DAV with three domains it does not assess: consent chains for secondary AI use, provenance metadata that survives de-identification, and demographic representativeness for bias testing.
- A three-tier maturity model, FHIR Provenance Resource support, and multi-stakeholder governance with anti-capture safeguards give intermediaries a structured path to AI-ready data.
+ Jump to Section
I. Executive Summary
The health data exchange ecosystem has achieved a robust, independently certified infrastructure for cybersecurity, most notably through the HITRUST certification required by TEFCA Common Agreement Section 12.1.2 for all Qualified Health Information Networks. No analogous certification exists for data quality, accuracy, or provenance.
HITRUST certifies the pipe. Nobody certifies the water.
As data intermediaries increasingly feed AI pipelines for clinical decision support, prior authorization, and public health surveillance, this asymmetry exposes the ecosystem to compounding risks. Box Commons recommends that the CDC incorporate independent, third-party data quality and provenance certification as a core component of the proposed Universal Intermediary Baseline.
II. The Data Quality Certification Gap
USCDI standardizes the format of exchanged data elements. It does not certify the accuracy of their content. A USCDI-compliant exchange can transmit perfectly formatted records that are clinically inaccurate, duplicated, or stripped of the provenance metadata needed for downstream AI use.
The NCQA Data Aggregator Validation (DAV) program is the closest existing analogue to "HITRUST for data quality": a 12-to-18-week cycle of process review, system conformance testing, and primary source verification. But DAV certifies fidelity to the source record, not suitability for AI training. The Sequoia Project's Data Usability Workgroup guide addresses provenance thoughtfully, but adoption is voluntary and unaudited.
III. What the Baseline Should Certify
Data quality certification for intermediaries should encompass four elements:
- Semantic accuracy: clinical data faithfully represents the source encounter, validated through methods analogous to NCQA DAV.
- Provenance integrity: the chain of custody through each intermediary transformation is documented and verifiable.
- Consent documentation: verifiable authorization for data entering secondary use pathways, including AI training.
- Demographic representativeness metadata: enough granularity to support the fairness testing required by ONC HTI-1 and state frameworks such as Colorado Regulation 10-1-1.
We recommend a three-tier maturity model: Tier 1 baseline compliance (USCDI, HITRUST, FHIR Provenance Resource support); Tier 2 DAV-equivalent data quality certification; Tier 3 AI-readiness certification covering consent chains, representativeness, and metadata survivability through de-identification.
IV. Governance and Anti-Capture Safeguards
Data intermediaries are often both the entities being certified and the entities writing the certification criteria. Any certifying body should operate under multi-stakeholder governance with equal-weight chambers for industry, civil society, and academic research, plus four structural safeguards: a 25 percent cap on revenue from any single entity, cooling-off periods for individuals moving from regulated entities into governance roles, funded participation for consumer advocates and independent researchers, and an annual public independence audit.
Certification standards should default to royalty-free IP, specify outcomes rather than technologies, and issue machine-readable credentials queryable through open registries.
V. Recommendations
- Include data quality and provenance certification in the Universal Intermediary Baseline.
- Adopt and extend the NCQA DAV methodology with AI-readiness criteria.
- Establish tiered certification maturity levels.
- Require FHIR Provenance Resource support as a baseline capability.
- Condition certification frameworks on multi-stakeholder governance.
- Address AI-specific risks, including the de-identification provenance paradox and consent gaps in ambient AI documentation, in intermediary assessment.
Contact:
Brice Love, Acting Executive Director
Box Commons
[email protected]
Content Integrity Notice: This comment was authored by the Box Commons Policy Working Group. Generative AI was used for research synthesis and drafting support. All policy positions, recommendations, and normative claims were formulated and reviewed by human authors.
Related Analysis
Related Filings
Comment on the Robocall Mitigation Database FNPRM: Content Provenance as a Complement to Call Authentication
STIR/SHAKEN authenticates who is calling, not what the caller says. Recommends the Commission recognize independent content provenance certification, aligned with C2PA content credentials, as a media-layer complement to signaling-layer call authentication within the Robocall Mitigation Database framework.
Colorado AGComment on Colorado ADMT Proposed Rules: Training Data Certification
Recommends that Colorado's ADMT proposed rules recognize independent data certification as a mechanism for developers to satisfy training data documentation obligations, with a rebuttable presumption that certified datasets meet disclosure requirements. Backed by a live 22-station broadcast radio certification pipeline.
NAICComment on NAIC BDAI Working Group: Exhibit B/D Mapping
Proposes a 'Presumption of Conformity' framework within the NAIC AI Systems Evaluation Tool permitting insurers to satisfy third-party vendor oversight obligations under Exhibits B and D through valid certifications from independent AI credentialing bodies, following the HITRUST precedent.