PHI sent, Log missing Bug: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m was getting awkward to read, so added collapsables |
TOstryzniuk (talk | contribs) mNo edit summary |
||
| Line 32: | Line 32: | ||
| full=**Collector stated no sending problem | | full=**Collector stated no sending problem | ||
** 1 Incomplete, did not go into L_Log | ** 1 Incomplete, did not go into L_Log | ||
**HSC_H4H_d-450 | **HSC_H4H_d-450}} | ||
{{Collapsable | |||
** | | always='''2018-Jul-23''' | ||
| full=**Collector stated no sending problem | |||
**STB ACCU-Data Collector deleted therefore, Pagasa will resend from backup | **STB ACCU-Data Collector deleted therefore, Pagasa will resend from backup | ||
**GRA N3 & STB E5 to resend | **GRA N3 & STB E5 to resend | ||
Revision as of 14:17, 5 September 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-Aug-20 |
|
| 2018-Jul-31 |
|
| 2018-Jul-23 |
|
| 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.
|
| 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.
|
Prior to the dates above, Pagasa stated that this has happened before. She recalls this happened on HSC_D4 laptop. She stated that this problem is rare, and happens every few months.