PHI sent, Log missing Bug

From CCMDB Wiki
Revision as of 09:38, 24 July 2018 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.


Template:Discussion

  • When you say "didn't report problems" do you mean they didn't say one way or the other, or that they reported specifically that there were no problems sending?

Template:Discussion

  • If this happens again, could you also include the D_ID in the log below? Ttenbergen 10:34, 2018 March 19 (CDT)

Log

  • 2018-Jul-23 - GRA N3 (5 Inc.), STB E5 (6 Inc.)and STB ACCU (8 Sent), didn't report problems, but patients who are present in PHI did not end up in L_Log.
    • Collectors stated no sending problem
    • STB ACCU deleted therefore Pagasa will resend from backup
    • GRA N3 & STB E5 to resend
  • 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