Project

General

Profile

Actions

Issue Monitor #1

open

Add pcc_user_uuid Column to all_users Table for PCC Integration

Added by Jonathan Cabato 2 days ago.

Status:
New
Priority:
Normal
Category:
Normal
Start date:
11/03/2025
Due date:
11/03/2025 (13 days late)
% Done:

100%

Estimated time:
1:00 h
Change Type:
Database
System:
ddxrx.com
Risk Level:
Low
Impact:
Not affected

Description

This change adds a new column, pcc_user_uuid, to the existing all_users table. The column will store the unique identifier for each user from the PointClickCare (PCC) system. This allows the database to reliably link and track PCC user data while keeping the existing fields intact for other user information.


Reason for change

The team is working on the PointClickCare app integration. DDXRX will store all user data received from the PCC API. Therefore, we need to add a new column to our existing database table, all_users, named pcc_user_uuid. The rest of the data will be stored in the existing fields/columns. the pcc_user_uuid column is used to store a unique identifier for each user coming from the PointClickCare (PCC) system. This UUID links your local all_users table to the corresponding user in PCC, allowing your system to track, update, and reference PCC data reliably without conflicts or duplication.


Change Plan

Change Plan: Add pcc_user_uuid to all_users Table

  1. Backup Database - Take a full backup of the database to prevent data loss.
  2. Add New Column - Execute SQL to add the column
  3. Verify Column Addition - Check the all_users table schema to ensure the column exists.
  4. Update Application Logic - Ensure the app writes and reads PCC UUIDs into/from the new column.
  5. Data Sync Test - Run a test to pull user data from PCC API and confirm pcc_user_uuid is populated correctly.
  6. Validation - Verify existing fields are unaffected. Ensure queries and reports work correctly with the new column.
  7. Deployment - Apply the change in production after successful testing.
  8. Post-Deployment Monitoring - Monitor logs and database for any issues with new PCC data integration.

Rollback Plan

Rollback Plan: Remove pcc_user_uuid from all_users Table

  1. Check that no critical processes are using the pcc_user_uuid column.
  2. Take a full backup of the database, including any data in the new column.
  3. Run this SQL to remove the column: ALTER TABLE all_users DROP COLUMN pcc_user_uuid;
  4. Revert any application changes that read or write to pcc_user_uuid.
  5. Verify the table schema is restored and existing functionality works correctly.
  6. Monitor logs and reports to ensure there are no issues after the rollback.

No data to display

Actions

Also available in: Atom PDF