What is Data Lineage

Data Lineage Definition

Data Lineage is the "Family Tree" of a piece of information. For C-level Executives, lineage provides "Data Provenance"—the ability to prove where a piece of information came from and why it looks the way it does now. For example, if a provider's specialty is listed as "Cardiology," lineage tells you if that came from their medical license, a CAQH download, or a manual update by a practice manager. Operationally, lineage is critical for "Troubleshooting." If the public directory shows the wrong phone number, lineage allows the data team to trace that error back through the system to see where the data was corrupted. Strategically, lineage supports "Data Trust"; when executives can see the transparent history of a metric, they are more confident using that data for high-stakes decisions like network expansion or rate negotiations.

FAQs

What is the difference between an Audit Trail and Data Lineage?

An Audit Trail focuses on "Who and When" a single field changed; Data Lineage focuses on the "Path and Transformation" of data as it moves between different systems and databases.

Why is lineage important for "Regulatory Reporting"?

When submitting an HSD table to CMS, lineage allows you to prove that the NPIs and addresses used in the report were pulled from verified, primary sources rather than "stale" secondary files.

How does lineage help during a "System Migration"?

It ensures that "Legacy Data" is correctly mapped to the new system by providing a clear understanding of the original data's context and intended use.