Procedure when there are differences between L Log and L PHI

"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.

• By clicking the re-connect button it will tell you if there is a problem or not.
  • Like if it says some records with Record Status "Complete" so a send must have failed. To fix collector need to re-send data

What are the steps/procedure that collectors would follow to "re send"?

• SMW

• Cargo

• Categories

• I will see if I have any problem in CFE once I click the Reconnect button.
• Record status "Complete" on CFE- No Complete Record Status in CFE only in CCMDB .
• If the problem showing Record Status is Complete, I will email the data collector right away to tell them sending did not go through Completely need to resend the batch. Today Pam sent with that problem and her error message say "Invalid SQL statement expected Delete,Insert,Procedure,Select or Update" message. Also I need to change in the master CFE the Record Status Complete to Incomplete so collector can send no problem.

• Number of Records not matched means 1_In_L_Log_but_NOT_in_L_PHI or 1_In_L_Phi_but_NOT_in_L_Log
• With this scenario the number of records in 1_In_L_Phi_but_NOT_in_L_Log means sent did not go through completely, to fix need to re send.
  • If the scenario is 1_In_L_Log_but_NOT_in_L_PHI the counts for the linked tables number are not matched, there was a problem in sending due to the laptop issue. but this scenario never happened anymore.
• I don't do anything except telling the collector to resend did not go through completely.

PTorres 15:15, 2022 March 16 (CDT) 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.

• 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:

Reconnect CFE and initial error checks ‎ (← links) "Re-connect Data" button ‎ (← links)