In Episode 3 of Data Quality Perspectives, host Burke Burnett is joined by NCQA Chief Product and Transformation Officer Vik Wadhwani and Availity Chief Medical Officer Dr. Hannah Alphs Jackson to examine what trusted healthcare data actually means.
The conversation explores why trust depends on context. Data that is appropriate for one purpose may be incomplete or insufficient for another, especially when it supports high-stakes decisions involving payment, prior authorization, risk adjustment, quality measurement and care delivery. Jackson and Wadhwani explain why trusted data must be evaluated across its full journey, from capture and exchange to aggregation, transformation and use.
The speakers also examine the difference between a true care gap and a data gap. Missing or unusable evidence can make completed care appear absent, leading to unnecessary patient outreach, lost credit for providers and unreliable quality signals. A depression-screening example further illustrates how a reported rate may reflect weaknesses in the data path rather than the quality of care itself.
Burnett, Jackson and Wadhwani discuss why healthcare needs shared terminology, methodologies and expectations for assessing data quality. They outline the importance of evaluating conformance, integrity, stability and plausibility, while giving data quality the same attention and rigor as interoperability and exchange.
Viewers will learn why trusted data does not necessarily mean perfect data. It means having enough transparency and understanding to determine whether data is fit for its intended use at the time it is used, supported by a shared framework to measure, detect and continuously improve data quality.
“
Trusted data doesn’t necessarily mean perfect data in perpetuity. It means actually having enough transparency and understanding of the fit for use of that data for the intended purpose and the intended time when it is being used.”
Vik Wadhwani
Trust Depends on Context
Healthcare data cannot be labeled simply good or bad. Trust depends on the use case, the stakes and whether the data is fit for the decision it needs to support.
- Trusted Data Must Be Complete, Timely and Usable
Accuracy alone is not enough. Data that arrives late or cannot be consumed for the intended purpose may be functionally equivalent to missing data.
- Care Gaps and Data Gaps Require Different Responses
A missing service and missing evidence of a completed service may appear identical in a report, but they call for very different actions for patients, providers and health plans.
- Quality Signals Can Reflect the Data Path Instead of Care
When information is recorded in places that measurement specifications or interoperable pipelines do not capture, reported performance may reveal a data-quality problem rather than a care-quality problem.
- More Data Does Not Automatically Mean Better Data
Healthcare has expanded access to clinical data, but greater quantity flowing through a complex ecosystem can amplify uncertainty when quality is not measured and managed.
- Shared Frameworks Make Trust More Scalable
Common terminology, methodologies and expectations can help organizations assess data consistently across its lineage, transformations and uses.
- Data Quality Needs the Same Rigor as Interoperability
The industry should address data quality alongside data exchange, not as an adjacent concern or downstream afterthought.
- Multiple Dimensions Shape Data Quality
Conformance, integrity, stability and plausibility provide different lenses for determining whether data remains trustworthy over time and for a specific purpose.
- Trust Requires Continuous Measurement and Improvement
Healthcare organizations need to measure and detect data-quality issues, then apply relentless incremental improvement rather than waiting for downstream reporting.
- Trusted Does Not Mean Perfect
Trust comes from transparency and sufficient understanding of whether data is fit for its intended purpose and moment of use.