with claims ETL where the script is essentially just running unions and/or exclusions (e.g. where statements) the only table-level QA that comes to mind is to re-run the code to see if the row counts are reproducible, but this seems circular. alternatively we can take the time to find corner cases for a line-level QA, but is the juice worth the squeeze? flagging this as an issue to come back to once we have a database manager/analyst.
with claims ETL where the script is essentially just running unions and/or exclusions (e.g. where statements) the only table-level QA that comes to mind is to re-run the code to see if the row counts are reproducible, but this seems circular. alternatively we can take the time to find corner cases for a line-level QA, but is the juice worth the squeeze? flagging this as an issue to come back to once we have a database manager/analyst.