ClientGUID field

From CCMDB Wiki
Data Element (edit)
Field Name: ClientGUID
CCMDB Label: not stated
CCMDB tab: not stated
Table: Cognos_import3 table
Data type: string
Length: 16
Program: Med and CC
Created/Raw: Raw
Start Date: 1988-07-11
End Date: 2300-01-01
Sort Index:

The unique person identifier from Cognos.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


This page is about the ClientGUID field which identifies people, not the ClientVisitGUID field which identifies admissions.

Background

Many patients don't have MB PHINs so we generate PseudoPHINs. EPR solves this by using a field ClientGUID, which we get as part of the Cognos EPR Report. If we set up the infrastructure to actually put this into patient records then we might be able to step away from the PseudoPhin process, and should have many fewer link errors.

Concerns

Data that is entered without a ClientGUID

  • Could be a problem:
    • Manual entry if we miss an admission and this is identified later past the 28 day of data in COGNOS
LK.png
  • Do you know if the ClientGUID is visible in EPR anywhere? It is usually a long number, like 4000012345678912 at HSC. There are shorter ones and some start with a different number. If these were actually visible in EPR then the question of whether we ever enter a record otherwise would go away, as we would be ale to just enter them explicitly as neededTtenbergen 15:32, 2022 August 4 (CDT)
  • I would need a specific example of Client GUID and the patient to look in EPR Lisa Kaita 12:26, 2022 August 24 (CDT)
    • The second field in your L_Log table is now being populated with these, so sort it z-to-a and you should see examples of ClientGUIDs. Ttenbergen 15:01, 2022 August 24 (CDT)
  • I looked at a few and the ClientGUID does not appear to be on the EPR, the only long # in EPR other than MRN is the Visit ID # Lisa Kaita 14:04, 2022 August 25 (CDT)
  • SMW


  • Cargo


  • Categories
  • Not a problem:
    • IICU: we use COGNOS now to enter all IICU admissions so it will be entered with ClientGUID automatically

Merged records (John or Jane Doe patient who get identified, and other corrections)

Chastity confirmed there is a merge process for J Does who get identified. Confirming how this works, emailed Chastity 2022-06-16.

Todo.svg

Swiss Army Knife.svg

  • Chastity confirmed there is a merge process for J Does who get identified. Confirming how this works, emailed Chastity 2022-06-16.
  • Asked Chastity if 3 month updates will be possible.
  • added: 2022-04-13
  • action: 2022-06-30
  • Cargo


  • Categories

Implementation

This would likely replace Person ID field eventually, but we'd keep it until tested; Generate Person IDs would still need to be done to enter this into L_Person table.

Todo.svg

Swiss Army Knife.svg

_dev_ccmdb

  • review linking and related processes to see what could change to make best use of this
  • remove the L_Person table - we don't use it and this further means we don't need/use it. as confirmed with Julie here.
  • added: 2022-03-24
  • action: 2022-09-25
  • Cargo


  • Categories

Data Processing improvements

Having this field might further cut down on Pre-linking checks, or at least on how many problems those find. Or it might add to them, since merges could be messy.

Pagasa confirmed that we already see very few pre-linking checks that are actual errors, and that those are usually from PL_SamePHIN_Site_Diff_chart now: "I have few errors common for HSC assigned a temporary chart which starts to 300 number but patient had already old chart number, another scenario old chart number but single admission nothing to compare with then have a current admission which is the correct one. "

Backfilling

I started discussion with DSS that we would like to eventually back-fill this data. So, for any MRN where we don't have a ClientGUID we would ask for it to be provided.

Ancient records won't have a ClientGUID; Chastity doesn't know what method they used to generate the ID so we can't use it to recreate these. We can insert our PHIN/PseudoPHIN for those, but would need to have a cross check method to capture and update if a same PHIN ever comes in new with a ClientGUID.

Log

Changing D_IDs

Changing D_IDs

Related Articles

Related articles: