Data Integrity Check under review

From CCMDB Wiki
Revision as of 13:47, 2021 September 15 by Ttenbergen (talk | contribs) (→‎Cross checks that need review)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Cross checks that need review

edit page App Status Timing Firmness Summary question who
edit page App Status Timing Firmness Summary question who
edit Function long LOS() CCMDB.accdb needs review complete soft check LOS/Length of Stay should not be unlikely long based on historical LOS for a given ward (Service/Location field).
edit Query check long transfer delay CCMDB.accdb needs review always soft check Is the Transfer Delay (Critical Care) or Transfer Delay (Medicine) unreasonably long?
edit Query Import request matcher DSM Labs Consistency check.accdb needs review Records in for which we have patients in L_Log but no lab records from DSM
edit Query check CCI each count vs LOS CCMDB.accdb needs review complete soft check Confirm that a Category:Labs Imaging count is not unreasonably high
edit Query cardiac arrest throughout admission Centralized data front end.accdb needs review complete hard check Any patient who is admitted to ICU from Med or another ICU with a #Cardiac Arrest dx should have one in their immediately preceeding Med or ICU record also. JALT Review after 2023-09-15
  • Lisa flagged that, if we do this for Cardiac Arrest, we should really do it for other dxs as well. And if we did that, it could result in a lot of work since it would need to be mediated by Pagasa for now. So we decided to see where the SF implementation goes and review the definition of this check once we have a centralized tool where the data collector would not need to mediate this. Ttenbergen 15:43, 2023 July 13 (CDT)
 all

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Data_Integrity_Check_under_review&oldid=152002"