Known data errors

From CCMDB Wiki
Revision as of 13:53, 24 June 2015 by Ttenbergen (talk | contribs) (m)
Jump to navigation Jump to search

Some records have known errors or data that triggers false positives in consistency checks. L Problem is a record of these so they can be excluded from queries.

Instructions for adding a record

If a false positive or known uncorrected error is found:

  1. open table L Problem from Centralized data front end.mdb
  2. make a new line
    • D_ID field: the D_ID of the record
    • Query field: the name of the query that detected this record and from which it should be masked
    • Notes field: explanations, eg why the error was not corrected or why it is a false positive

Instructions for using the table in queries

For every query, filter the L Problem table to only records related to that query and only list if null.

Location of List of old known errors

The Data processor keeps an Excel workbook that includes: reason some profiles are missing data elements (APACHE - 8 ICU profiles), gaps in database because of deletions including reasons for deletions, overlaps, overs. Example missing all APACHE elements in TMSX, MedTMS and reason why could never be obtained.18:01, 2014 May 2 (CDT) M:\GAPS_OVERLAP_OVERS

to do

  • Waiting for Pagasa to give me a query to test this with.
  • Discussion about 8 profiles missing all APACHE elements and specific reason why missing etc.