Re-sending data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 34: | Line 34: | ||
=== Confirm resolution === | === Confirm resolution === | ||
# [[pull]] the CFE | # [[pull]] the CFE | ||
# | # re-run [[Reconnect CFE and initial error checks]] | ||
# If no more data errors, then [[push]] back the CFE so collectors can [[send]]. | # If no more data errors, then [[push]] back the CFE so collectors can [[send]]. | ||
== Error Log Laptop Crashed while [[sending]] == | == Error Log Laptop Crashed while [[sending]] == | ||
* 2025-07-03 - Laptop crashed while [[sending]] / [[Breaking out of a frozen program]] /[[Lccmdb and ldb files]] system of problems. To fix, we need to [[restore from backup]] [[Centralized_data.accdb]] and [[PHI.mdb]]. If any data got sent, those records need to be resent. [[User:PTorres|PTorres]] 16:23, 3 July 2025 (CDT) | |||
* 2025 06 30 - Problem with S6 laptop corrupted. It took 2 hours to fix it. (S6 was [[sending]] in the office) | * 2025-06-30 - Problem with S6 laptop corrupted. It took 2 hours to fix it. (S6 was [[sending]] in the office) | ||
* 2025 06 09 - Problem with H7 laptop corrupted. It took a day to fix (Pagasa sent records) | * 2025-06-09 - Problem with H7 laptop corrupted. It took a day to fix (Pagasa sent records) | ||
* 2025 02 14 - Problem with S8 laptop corrupted. It took a day to fix (Pagasa sent records) | * 2025-02-14 - Problem with S8 laptop corrupted. It took a day to fix (Pagasa sent records) | ||
* 2024 11 18 - Problem with H3 and S9 corrupted both laptops sending at the same time. | * 2024-11-18 - Problem with H3 and S9 corrupted both laptops sending at the same time. | ||
== Related articles == | == Related articles == | ||
Latest revision as of 12:41, 6 January 2026
This page explains how one would re-send previously sent data. There are extra steps if this is done by the Data processor, which are masked by the collapsible below.
Steps
Prepare Centralized_data.accdb - done by data processor
| hiding these steps so they don't confuse collectors who don't need to do these steps |
Prepare
Set records to incomplete
Additional step if Data processor is sendingCopy the backup data to the PC:
|
Re-send
This step may be done by the data collector, or it may be done by the data processor.
- Open CCMDB.accdb
- review patient list to ensure you have the version of the patients you want to resend (only applies when dealing with restored data)
- set the patient RecordStatus field to "complete" from "sent"
- Press the Send Records button
- press "OK" and type in your own First Name_RESEND, example: Suzie_Resend
- press "OK"
If you get a duplicate error you probably didn't follow #Prepare Centralized_data.accdb.
Confirm resolution
- pull the CFE
- re-run Reconnect CFE and initial error checks
- If no more data errors, then push back the CFE so collectors can send.
Error Log Laptop Crashed while sending
- 2025-07-03 - Laptop crashed while sending / Breaking out of a frozen program /Lccmdb and ldb files system of problems. To fix, we need to restore from backup Centralized_data.accdb and PHI.mdb. If any data got sent, those records need to be resent. PTorres 16:23, 3 July 2025 (CDT)
- 2025-06-30 - Problem with S6 laptop corrupted. It took 2 hours to fix it. (S6 was sending in the office)
- 2025-06-09 - Problem with H7 laptop corrupted. It took a day to fix (Pagasa sent records)
- 2025-02-14 - Problem with S8 laptop corrupted. It took a day to fix (Pagasa sent records)
- 2024-11-18 - Problem with H3 and S9 corrupted both laptops sending at the same time.