PHI sent, Log missing Bug: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
PTorres (talk | contribs)
CCMDB_legit, approved
1,617 edits
No edit summary
PTorres (talk | contribs)
CCMDB_legit, approved
1,617 edits
No edit summary
Line 1: Line 1:
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. {{Bug}}
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. {{Bug}}
{{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?
{{discussion}}
* If this happens again, could you also include the D_ID in the log below? Ttenbergen 10:34, 2018 March 19 (CDT)


== Log ==
== Log ==
<!-- newest on top -->
<!-- newest on top -->
*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.
*2018-Jul-23 - patients are present in L_PHI did not end up in L_Log.
**Collectors stated no sending problem  
**Collectors stated no sending problem  
**STB ACCU deleted therefore Pagasa will resend from backup
**STB ACCU deleted therefore Pagasa will resend from backup
**GRA N3 & STB E5 to resend  
**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 (6 Inc.)
**STB_E5-16639
**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-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.  

Revision as of 09:45, 24 July 2018

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 - patients are present in L_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
  • GRA N3 (5 Inc.)
    • GRA_N3-15890
    • GRA_N3-15891
    • GRA_N3-15892
    • GRA_N3-15893
    • GRA_N3-15894
  • STB E5 (6 Inc.)
    • STB_E5-16639
    • 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

Retrieved from "https://ccmdb.kuality.ca/index.php?title=PHI_sent,_Log_missing_Bug&oldid=117839"