Re-sending data

From CCMDB Wiki
Revision as of 12:41, 6 January 2026 by Ttenbergen (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

  1. in Centralized_data.accdb, on Regional Server\​output\\ad.wrha.mb.ca\WRHA\REGION\SHARED\ICU_DATA_COLLECTION\output , set the RecordStatus field to "Incomplete" for the records you will re-send

Additional step if Data processor is sending

Copy the backup data to the PC:

  1. find a copy of collector's backup CCMDB data on the Regional server, and follow CCMDB data.mdb restore from Regional Server
  2. make sure you have the latest version of CCMDB.accdb

Re-send

This step may be done by the data collector, or it may be done by the data processor.

  1. Open CCMDB.accdb
  2. review patient list to ensure you have the version of the patients you want to resend (only applies when dealing with restored data)
  3. set the patient RecordStatus field to "complete" from "sent"
  4. Press the Send Records button
  5. press "OK" and type in your own First Name_RESEND, example: Suzie_Resend
  6. press "OK"

If you get a duplicate error you probably didn't follow #Prepare Centralized_data.accdb.

Confirm resolution

  1. pull the CFE
  2. re-run Reconnect CFE and initial error checks
  3. 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.

Related articles

Related articles: