Re-sending data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| (22 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
This page explains how one would re-send previously sent data. There are extra steps if this is done by the [[Data processor]]. | 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 == | == Steps == | ||
=== Prepare [[ | === Prepare [[Centralized_data.accdb]] - done by data processor === | ||
{{Collapsable | always= hiding these steps so they don't confuse collectors who don't need to do these steps | full= | {{Collapsable | always= hiding these steps so they don't confuse collectors who don't need to do these steps | full= | ||
==== | ==== Prepare ==== | ||
* [[Determine which sends have failed and need to be re-sent]] | * [[Determine which sends have failed and need to be re-sent]] | ||
* possibly [[Restoring a "known good" version of the centralized data pair]]] | |||
==== Set records to incomplete ==== | ==== Set records to incomplete ==== | ||
#in [[ | #in [[Centralized_data.accdb]], on {{Regionalserver|output}}, set the [[RecordStatus field]] to '''"Incomplete"''' for the records you will re-send | ||
#* this would be done by the [[Data processor]], so if a [[Data collector]] needs to re-send they need to contact the [[Data processor]] to do this; make sure you provide the [[Service/Location]] and [[Pat_ID]] of the patients | #* this would be done by the [[Data processor]], so if a [[Data collector]] needs to re-send they need to contact the [[Data processor]] to do this; make sure you provide the [[Service/Location]] and [[Pat_ID]] of the patients | ||
| Line 15: | Line 16: | ||
Copy the backup data to the PC: | Copy the backup data to the PC: | ||
#find a '''copy of collector's backup''' [[CCMDB data.mdb | CCMDB]] data on the Regional server, and follow [[CCMDB data.mdb restore from Regional Server]] | #find a '''copy of collector's backup''' [[CCMDB data.mdb | CCMDB]] data on the Regional server, and follow [[CCMDB data.mdb restore from Regional Server]] | ||
#* this may not be the latest one since that one may have already deleted the sent files; consider the date of [[Centralized_data.accdb]] that was restored during [[Restoring a "known good" version of the centralized data pair]] | |||
# '''make sure you have the latest version of [[CCMDB.accdb]]''' | # '''make sure you have the latest version of [[CCMDB.accdb]]''' | ||
#* Go to {{Regionalserver|Programs\Master}} and double-click on [[Copy to local.bat]] | #* Go to {{Regionalserver|Programs\Master}} and double-click on [[Copy to local.bat]] | ||
| Line 28: | Line 30: | ||
# press "OK" | # press "OK" | ||
If you get a duplicate error you probably didn't follow [[#Prepare | 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]]. | |||
* 2025 06 30 - Problem with S6 laptop corrupted. It took 2 hours to fix it. | == Error Log Laptop Crashed while [[sending]] == | ||
* 2025 06 09 - Problem with H7 laptop corrupted. It took a day to fix (Pagasa sent records) | * 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-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. | |||
== Related articles == | == Related articles == | ||
| Line 42: | Line 48: | ||
[[Category: CCMDB.accdb]] | [[Category:CCMDB.accdb]] | ||
[[Category: Data Processing]] | [[Category:Data Processing]] | ||
[[Category: Backup]] | [[Category:Backup]] | ||
[[Category: Re-sending]] | [[Category:Re-sending]] | ||
Latest revision as of 13: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.