You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In US data sources there is place of service. there is a field in care_site table for place of service. Place of service tells in the claims where the place was that the service was rendered. If that information is present, it should correspond to visit_concept_id . It is also descendant of conceptID 9202.
A check if there is concordance between visit_concept_id and place_of_service_concept_id maybe a good check of ETL?
The text was updated successfully, but these errors were encountered:
Thinking further, these checks maybe useful to check for concordance between visit table and other sources of visit information. e.g. revenue codes when present, cpt4 codes when present.
Maybe the check is "Concordance between expect vs observed values by visit"
gowthamrao
changed the title
Proposal for a data quality check for Data Quality Dashboard
Proposal for Concordance between expect vs observed values by visit
Apr 11, 2024
Interesting idea! Curious what sorts of issues you've seen with these concepts?
We have found these concept plausibility checks hard to maintain, with all the different flavors of data out there and the ever-changing vocabularies. That said, it's worth considering if there are consistent trends you've observed and think are worth monitoring for, and we could come up with a short initial list of the most critical/common mismatches :)
In US data sources there is place of service. there is a field in care_site table for place of service. Place of service tells in the claims where the place was that the service was rendered. If that information is present, it should correspond to visit_concept_id . It is also descendant of conceptID 9202.
A check if there is concordance between visit_concept_id and place_of_service_concept_id maybe a good check of ETL?
The text was updated successfully, but these errors were encountered: