CCMDB Wiki

ClientGUID field: Difference between revisions

← Older edit
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Data element
{{Data element
|field_name=ClientGUID
|field_name=ClientGUID
|Rank=N/A
|in_table=L_Log table
|in_table=Cognos_import3 table
|data_type=string
|data_type=string
|datafield_length=16
|datafield_length=16
|program_collecting=Med and CC
|program_collecting=Med and CC
|created_raw=Raw
|created_raw=Raw
|data_element_sort_index=
|data_element_start_date=2022-08-29
|element_description=The unique person identifier from [[Cognos]].  
|data_element_sort_index=1.5
|element_description=The unique person identifier from [[Cognos]].
|Rank=N/A
}}
}}
 
This page is about the {{PAGENAME}} which identifies people, not the [[ClientVisitGUID field]] which identifies admissions.  
This page is about the {{PAGENAME}} which identifies people, not the [[ClientVisitGUID]] which identifies admissions.  


=== Background ===
=== Background ===
Many patients don't have MB [[PHIN]]s so we generate [[PseudoPHIN]]s. 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.  
Many patients don't have MB [[PHIN]]s so we generate [[PseudoPHIN]]s. 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.  
* The Client GUID is not visible in EPR
=== Concerns ===
==== Inconsistent with Person_ID ====
Review of [[ClientGUID field]] and [[Person ID field]] showed that the data in {{PAGENAME}} is inconsistent. There are files with same Person_ID and different ClientGUID and vice versa. I have sent an excel to Julie, Pagasa and Lisa with details. For now, I would treat this data as absolutely suspect and we shouldn't use it.


=== Concerns ===
{{Discuss|
==== Data that is entered without a ClientGUID ====
* Lisa, any idea why this might be happening from a collection perspective? Is the problem in what we receive the right info from Cognos, or is there an issue in the collection process that makes this happen? [[User:Ttenbergen|Ttenbergen]] 09:52, 2024 December 5 (CST)
{{DL |  
* Julie, do we need to flag anywhere further that this data is suspect? [[User:Ttenbergen|Ttenbergen]] 09:52, 2024 December 5 (CST)
* Do collectors add all [[HSC IICU]] admissions via Cognos now that each IICU service admission is included on all HSC CC laptops? Or are there still exceptions. [[User:Ttenbergen|Ttenbergen]] 11:41, 2022 June 16 (CDT)
}}
}}


{{DL |
{{Collapsable | always=Query:  | full= .
* Aside from the odd correction entries, are there scenarios where records are ''routinely'' added other than via Cognos? [[User:Ttenbergen|Ttenbergen]] 11:41, 2022 June 16 (CDT)
SELECT PCG_duplicates.Person_ID, PCG_duplicates.CountOfClientGUID, L_Log.D_ID, L_Log.ClientGUID, L_Log.Visit_Admit_DtTm
}}
FROM (SELECT PCG_pairs.Person_ID, Count(PCG_pairs.ClientGUID) AS CountOfClientGUID
FROM (SELECT DISTINCT L_Log.Person_ID, L_Log.ClientGUID
FROM L_Log
WHERE (((L_Log.[RecordStatus])="vetted") AND ((L_Log.[Dispo_DtTm])>=#1/1/2022#) AND ((L_Log.[ClientGUID]) Is Not Null)) )  AS PCG_pairs
GROUP BY PCG_pairs.Person_ID
HAVING (((Count(PCG_pairs.ClientGUID))>1)) )  AS PCG_duplicates INNER JOIN L_Log ON PCG_duplicates.Person_ID = L_Log.Person_ID
WHERE (((L_Log.ClientGUID) Is Not Null))
ORDER BY PCG_duplicates.Person_ID, L_Log.ClientGUID;
}}


{{DL |
==== Data that is entered without a ClientGUID ====
* 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 needed[[User:Ttenbergen|Ttenbergen]] 15:32, 2022 August 4 (CDT)
* Could be a problem:
}}
** Manual entry if we miss an admission and this is identified later past the 28 day of data in COGNOS
** [[Definition_of_a_Medicine_Program_Admission#Excluded_service_admissions_can_lead_to_missed_records]]
* 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) ====
==== Merged records ([[John or Jane Doe patient]] who get identified, and other corrections) ====
Line 47: Line 61:
  | who = Tina   
  | who = Tina   
  | todo_added = 2022-03-24   
  | todo_added = 2022-03-24   
  | todo_action = 2022-08-09
  | todo_action = 2022-09-25
  | question = _dev_ccmdb
  | question = _dev_ccmdb
* '''added''' this field to [[L_Log table]] in CCMDB_data
* '''added''' this field to [[L_Log table]] in Centralized_Data
* '''added''' the VBA so it's entered during profile generation from Cognos
* add the field to sending
* review linking and related processes to see what could change to make best use of this
* 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.
* 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.
Line 65: Line 75:
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.  
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.
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 ===
=== Log ===
* 2022-08-25 - added code to start sending this field to [[Centralized_data.accdb]]
* 2022-08-04 - added field to [[Ccmdb 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.
* 2022-03-24 - added field to [[Cognos_import3 table]] in CCMDB.accdb so the import can still work.
Retrieved from "https://ccmdb.kuality.ca/index.php?title=ClientGUID_field"