|Data Element (edit)|
|CCMDB Label:||not stated|
|CCMDB tab:||not stated|
|Program:||Med and CC|
The unique person identifier from Cognos.
Legacy implementation right in the table
This page is about the ClientGUID field which identifies people, not the ClientVisitGUID field which identifies admissions.
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.
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
- 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.
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. "
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.
- 2022-08-25 - added code to start sending this field to Centralized data.mdb
- 2022-08-04 - added field to Ccmdb data.mdb
- 2022-03-24 - added field to Cognos_import3 table in CCMDB.accdb so the import can still work.