PHI sent, Log missing Bug

From CCMDB Wiki
Revision as of 11:32, 2018 July 24 by PTorres (talk | contribs)
Jump to navigation Jump to search

Occasionally we get a PHI record for a patient, but no Log record. It isn't clear yet why, we need further observation to find out. This article is the observation log.


Log

  • 2018-Jul-23 - when sending, patients are present in L_PHI did not end up in L_Log.
    • Collectors stated no sending problem
    • STB ACCU (12 sent, 8 did not go not go into L_phi). Data Collector deleted therefore, Pagasa will resend from backup
    • GRA N3 & STB E5 to resend
  • GRA N3 (5 Inc.)
    • GRA_N3-15890
    • GRA_N3-15891
    • GRA_N3-15892
    • GRA_N3-15893
    • GRA_N3-15894
  • STB E5 (5 Inc. 1 Sent)
    • STB_E5-16639 - Sent
    • STB_E5-16640
    • STB_E5-16641
    • STB_E5-16642
    • STB_E5-16643
    • STB_E5-16644
  • STB ACCU (8 Sent)
    • STB_ACCU-31454
    • STB_ACCU-31455
    • STB_ACCU-31456
    • STB_ACCU-31457
    • STB_ACCU-31458
    • STB_ACCU-31459
    • STB_ACCU-31460
    • STB_ACCU-31461
  • 2018-Mar-01 - HSC A4, didn't report problems, but one of the Incomplete patients who is present in CCMDB and PHI did not end up in L_Log.
  • 2018-Feb-20 - HSC_B3/D5 sent, didn't report problems, but one of the Incomplete patients who is present in CCMDB and PHI did not end up in L_Log.
    • collector resend data and issue resolved.
  • 2018-Jan-08 - HSC_D4 sent, didn't report problems, but one of the Incomplete patients who is present in CCMDB and PHI did not end up in L_Log.
    • collector resend data and issue resolved.

Prior to the dates above, Pagasa says this has happened before, for the HSC_D4 laptop, but it is rare, every few months.

Different Error Record Status is "Complete"

moved to Problem with sent vs complete records