Payers, regulators and the record

Guides

1. Prior authorization automation data quality: what AI approvals require

   September 16, 2026

   Prior authorization AI systems approve or deny care based on data they never verified. When 50% of provider directories contain errors and claims data lags 30 to 90 days, automation without data quality controls produces automated harm. The question is not whether AI can do prior auths. The question is whether the data feeding those decisions meets a minimum trust threshold.

2. Provider directory accuracy: the 50 percent error rate problem in health plan data

   September 15, 2026

   CMS audits consistently find error rates approaching 50 percent in Medicare Advantage provider directories. That means half the records a member sees when searching for a doctor may list the wrong phone number, wrong address, or wrong acceptance status. The problem is not a technology gap. It is a data trust gap, and fixing it requires scoring every provider record before it reaches a directory.

3. Credentialing data integrity: what the CAQH database gets wrong about providers

   September 14, 2026

   CAQH holds credentialing data on more than 1.6 million providers, yet health plans routinely find that profiles are incomplete, outdated, or contradicted by primary sources. The database was designed to reduce paperwork, not to guarantee data integrity. That gap costs the credentialing system billions in rework, delays, and downstream errors.

4. HEDIS measure data quality: what NCQA requires for star rating accuracy

   September 10, 2026

   NCQA requires health plans to meet strict data quality thresholds across HEDIS measures before star ratings are calculated. A single missed mammogram record or misaligned value set can drop a plan's rating by half a star, costing millions in Quality Bonus Payments. The gap between collecting data and trusting data is where most health plans fail.

5. Medicaid managed care data trust: what state reporting requirements demand

   September 9, 2026

   Forty-two states now contract with managed care organizations to administer Medicaid benefits, and every one of those states imposes reporting requirements that assume the underlying data is trustworthy. Most MCO data fails that assumption before it reaches CMS. State Medicaid reporting requirements create a compliance surface that cannot be satisfied by volume alone; MCO data quality depends on provenance, recency, and validation that most plans never measure.

6. Medicare Advantage risk adjustment data integrity: what upcoding means for AI

   September 8, 2026

   Medicare Advantage plans receive an estimated $12-25 billion annually in excess payments tied to risk adjustment coding practices that inflate patient severity. When AI systems train on this data, they inherit the financial incentives baked into every diagnosis code, producing models that confuse billing optimization with clinical reality.

7. CMS Innovation Center value-based model data requirements

   September 6, 2026

   The CMS Innovation Center has launched over 50 value-based care models since 2010, and every one of them requires participating organizations to submit clinical, financial, and operational data that meets specific quality thresholds. Most participants underestimate what those data requirements actually demand, and the gap between what CMMI expects and what health systems can deliver is where model performance collapses.

8. Optum data assets and the trust question for competing health systems

   September 3, 2026

   Optum controls claims, pharmacy, clinical, and behavioral data on more than 150 million lives. Health systems that send data into Optum's platforms are training the analytics tools of a company that competes with them for patients, contracts, and market share. The trust question is not hypothetical. It is structural.

9. CVS Health and Aetna data integration: what vertical integration means for data trust

   September 2, 2026

   CVS Health's acquisition of Aetna created the largest vertically integrated health company in the United States, merging pharmacy, insurance, and clinic data under one roof. That integration concentrated more patient data in a single corporate entity than any previous transaction in healthcare history. The data trust implications are structural, not theoretical.

10. Drug-drug interaction data trust: what the FDA adverse event database actually contains

    August 20, 2026

    The FDA Adverse Event Reporting System contains over 29 million reports, but duplicate entries, missing drug fields, and inconsistent coding make raw FAERS data unreliable for drug-drug interaction analysis. Most AI models trained on FAERS never quantify these data quality failures before inference.

11. Cross-border health data trust: GDPR and HIPAA combined compliance requirements

    August 15, 2026

    GDPR and HIPAA were designed for different populations, different enforcement models, and different definitions of health data. Any organization transferring health records between the EU and US must satisfy both simultaneously, and the overlap is smaller than most compliance teams assume. Without a unified trust framework that scores data against both regimes, cross-border health data transfers create liability at every handoff.

12. Transportation barrier data trust: what claims-based proxy measures miss

    August 7, 2026

    Claims-based proxy measures for transportation barriers misclassify up to 40% of patients who actually face access problems. Area-level deprivation indices, ZIP code distance calculations, and missed appointment flags each introduce distinct distortions that compound when fed into population health AI. Building a transportation barrier data trust requires patient-level verification, temporal specificity, and provenance scoring that proxy data cannot provide.

13. Post-market surveillance data trust: what FDA expects from device performance data

    August 1, 2026

    FDA expects post-market surveillance data to meet specific standards for completeness, timeliness, and traceability. Most device manufacturers collect the data but fail to prove it is trustworthy. Here is what the agency actually requires, what the ISO standards add, and why AI-enabled devices face a fundamentally different surveillance burden.

14. Real-world evidence data quality: FDA requirements for RWE regulatory submission

    July 31, 2026

    FDA has accepted real-world evidence in over 100 regulatory decisions since 2018, but most RWE submissions fail on data quality, not study design. The agency's requirements for RWD reliability, relevance, and completeness demand provenance-level trust that traditional data pipelines cannot deliver without systematic scoring.

15. Registry data quality for rare disease: what FDA expects from patient registries

    July 26, 2026

    The FDA has issued specific guidance on what patient registries must deliver before rare disease data can support regulatory decisions. Fewer than 7,000 rare diseases have FDA-approved treatments, and registry data quality is a primary reason. This post maps the gap between what registries collect and what the FDA actually requires for accelerated approval, natural history studies, and post-market surveillance.

16. Surgical outcomes data trust: what the NSQIP registry requires for quality benchmarking

    July 25, 2026

    The ACS NSQIP registry tracks 30-day surgical outcomes across 700+ hospitals, but its benchmarking value depends entirely on the integrity of the data feeding it. Incomplete case capture, variable abstraction quality, and coding inconsistencies degrade the registry's ability to serve as ground truth for surgical AI models. Without a formal trust score applied before data enters quality benchmarking pipelines, surgical outcomes intelligence starts on unstable ground.

17. Medication adherence data trust: what pharmacy claims miss and wearables catch

    July 21, 2026

    Pharmacy claims data tells you a prescription was filled. It cannot tell you whether the pill was swallowed, when it was taken, or what happened to the patient between refills. Wearable sensors and smart packaging now capture the signals that claims miss, but the data they generate carries its own trust problem. Closing the pharmacy claims data gap requires scoring both sources before any AI model acts on them.

18. Claims data lags 30 to 90 days. Here is what it costs AI models

    July 19, 2026

    Claims data reaches AI models 30 to 90 days after the clinical event it describes. That reporting delay introduces survivorship bias, truncates longitudinal records, and trains predictive models on a version of reality that no longer exists. For health plans and AI developers building on claims, the lag is not a nuisance. It is a structural defect in the training data.

19. Amazon Clinic and the retail health data trust gap

    May 13, 2026

    Amazon Clinic collected health data from millions of consumers before quietly shutting down in 2024. The retail health data trust gap it exposed remains unsolved: consumer health records generated outside traditional clinical settings lack provenance, consent governance, and quality scoring. Until health data has a trust layer, retail health platforms will keep creating records that cannot be safely used for AI, research, or clinical decision-making.

20. UnitedHealth Group AI denial rate controversy: what data trust had to do with it

    May 12, 2026

    UnitedHealth Group's AI claim denial controversy exposed a systemic failure that most coverage missed: the underlying data the algorithm trained on was never independently scored for trust, provenance, or recency. When a payer deploys AI on unverified data to deny care at scale, the problem is not just the model. It is the data supply chain that no one audited.

21. Why audit trails are the foundation of health AI accountability

    May 10, 2026

    Over 4,000 fabricated references were recently found across 2,800+ published research papers. When AI systems in healthcare produce outputs that cannot be traced back to verified source data, the consequences extend far beyond bad citations. Audit trails are the structural mechanism that makes health AI accountable, and most deployments still lack them.

22. CMS ACCESS and the data foundation requirement: what health systems need to know

    May 3, 2026

    The CMS ACCESS model ties $420 per beneficiary per month to outcome-aligned chronic care management, but participating organizations cannot meet reporting requirements if their underlying data fails on provenance, recency, or concordance. Health systems applying for ACCESS need a data foundation that goes beyond EHR completeness. This post breaks down what ACCESS actually requires, what most applicants underestimate, and how trust-scored data closes the gap.

23. FDA AI guidance and data provenance: what is coming for healthcare AI developers

    April 26, 2026

    The FDA's evolving guidance on AI in healthcare is converging on a single requirement most developers are not ready for: data provenance. Draft frameworks for AI-enabled medical devices and drug development now treat training data lineage as a core submission element, not an afterthought. Here is what is coming and what developers need to build now.

24. Health data integrity for value-based care programs

    April 25, 2026

    Ninety-seven percent of providers agree that strong data strategies are essential for value-based care, yet most VBC programs still operate on claims data riddled with coding inconsistencies, missing fields, and stale records. Without a trust layer that scores every record before it enters a payment model, value-based care becomes volume-based guessing with extra steps.

25. CBO data trust for Medicaid value-based programs: what community organizations need

    April 22, 2026

    Community-based organizations hold some of the most critical social determinants of health data in the Medicaid system, yet most lack the infrastructure to prove that data is trustworthy. Without a formal data trust framework, CBOs cannot participate meaningfully in value-based care contracts that require measurable, auditable outcomes.

26. How the FDA Will Audit Your Health AI's Training Data

    April 9, 2026

    FDA's AI/ML SaMD action plan identifies training data quality as the most significant gap in the current framework for clinical AI. When an auditor arrives, they will ask six specific questions about your training data. Most health AI companies cannot answer any of them.

27. CMS CRUSH Compliance: What Health Plans Need Beyond Accurate Provider Directories

    March 28, 2026

    CMS CRUSH compliance is not just about having accurate provider directories. It is about having defensible, auditable data processes. Health plans that cannot demonstrate how they know their data is accurate are exposed even if the data itself looks clean.

28. Payer data trust: what health plans need from their data before deploying AI

    March 21, 2026

    Most health plans say they want to deploy AI, but fewer than 30% trust their own data enough to act on AI outputs. Payer data trust starts with measuring data quality at the record level before any model touches a claim, a member profile, or a care decision. SuperTruth's Data Trust Index gives health plans a quantifiable score for every record so they can deploy AI with confidence, not hope.

29. What makes health data Platinum-grade for FDA regulatory submission

    March 7, 2026

    The FDA rejects submissions with incomplete provenance, inconsistent formatting, or unverifiable consent chains. Platinum-grade health data meets every dimension of trust before it reaches a reviewer's desk. SuperTruth's Data Trust Index scores each record across eight dimensions so sponsors know exactly where their data stands.

30. CMS ACCESS Program: What the $420 Per Beneficiary Payment Actually Requires

    March 4, 2026

    CMS ACCESS ties federal payments directly to documented health outcomes. The maximum is $420 per beneficiary per year. The minimum is $90. The difference between them is data documentation.