Data Meaning Layer: Difference between revisions
Ttenbergen (talk | contribs) Created page with "This page introduces the concept of the Data Meaning Layer, a shared framework for defining, tracking, and communicating the meaning of data elements and metrics in CCMDB. It serves as a central reference point for how we manage evolving definitions, support consistent interpretation, and connect meaning across tools like Access/SQL, SAS, Power BI, and the wiki. == The Problem == * We have a complex legacy dataset that has had significant data encoding changes over time..." |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Discuss | | |||
* This had been percolating in my head for a while and I finally had a chance to look into it. Looking forward to thoughts. [[User:Ttenbergen|Ttenbergen]] 18:11, 18 July 2025 (CDT) | |||
}} | |||
This page introduces the concept of the Data Meaning Layer, a shared framework for defining, tracking, and communicating the meaning of data elements and metrics in CCMDB. It serves as a central reference point for how we manage evolving definitions, support consistent interpretation, and connect meaning across tools like Access/SQL, SAS, Power BI, and the wiki. | This page introduces the concept of the Data Meaning Layer, a shared framework for defining, tracking, and communicating the meaning of data elements and metrics in CCMDB. It serves as a central reference point for how we manage evolving definitions, support consistent interpretation, and connect meaning across tools like Access/SQL, SAS, Power BI, and the wiki. | ||
| Line 100: | Line 104: | ||
** Cache and manage intermediate forms (e.g., “semantic LOS definition v3 applied to 2023 discharges”) | ** Cache and manage intermediate forms (e.g., “semantic LOS definition v3 applied to 2023 discharges”) | ||
== possible extension == | |||
* '''cross checks''' - our cross-checks are currently hard coded as queries in MS Access, which are also not transparent to users. Depending on implementation details this framework would allow us to include them | |||
* '''test data and validation''' - this framework could also include test data and validation or unit test functionality | |||
* '''branching, merging and code review''' - depending on the repository of the code, and the integration into the tool, this could introduce git-like code version management | |||
[[Category:Reporting]] | [[Category:Reporting]] | ||
[[Category:Statistical Analysis]] | [[Category:Statistical Analysis]] | ||