Procedure when there are differences between L Log and L PHI

From CCMDB Wiki
Jump to navigationJump to search

"Pulling" Centralized data.mdb should result in consistent data sets being copied, but sometimes differences appear between L_PHI and L_Log. Usually this happens when something goes wrong during sending or during PHI copy automation or when a patient is deleted in one but not the other table.

You would usually find out about this when you try to reconnect tables in CFE and get an error.

To address the problem:

  • In CFE, look at the object listing on the left and open the following two queries to identify the record that is different.
    • 1_In_L_Phi_but_NOT_in_L_Log
    • 1_In_L_Log_but_NOT_in_L_PHI
  • if in L_Log but not in L_PHI:
    • check X:\CCMDB/PHI/PHI_CSV. You want to make sure there is no CSV file sitting in this folder that was not uploaded to PHI.mdb
    • this could mean a problem with PHI copy automation
  • If in L_PHI but not in L_Log
    • check X:\CCMDB/PH/PHI_CSV_Archive folder to check if the missing file was in the batch sent from the data collector.
Data processor.svg

Why, what does that tell you? The only way I can imagine this would happen is if the record was deleted in centralized L_Log. In that case, if you are lucky and there is still a ccmdb_data with the completed/sent record, you can follow the Re-sending data process. If not, find it in a previous version of Centralized data.mdb, print or write down all data for the record, and manually re-enter it in a CCMDB.accdb and follow the Re-sending data process. Or what do you do? Ttenbergen 21:38, 2019 February 6 (CST)

  • SMW


  • Cargo


  • Categories
  • if not sure review with main office or data collector.
  • If file was a test, or error, you can delete it from L_Log and/or L_PHI, whichever still has part of the record.

Related articles

Related articles: