Are you logged on?
You do not have permission to edit this page, for the following reason:
unstructured part of page:
This page is about the {{PAGENAME}} which identifies people, not the [[ClientVisitGUID field]] which identifies admissions. === 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. * 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. {{Discuss| * 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) * Julie, do we need to flag anywhere further that this data is suspect? [[User:Ttenbergen|Ttenbergen]] 09:52, 2024 December 5 (CST) }} {{Collapsable | always=Query: | full= . 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; }} ==== 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 ** [[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) ==== Chastity confirmed there is a merge process for J Does who get identified. Confirming how this works, emailed Chastity 2022-06-16. {{Todo | who = Tina | todo_added = 2022-04-13 | todo_action = 2022-06-30 | question = * 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. }} == 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 | who = Tina | todo_added = 2022-03-24 | todo_action = 2022-09-25 | question = _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. }} === 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 === * 2022-08-25 - added code to start sending this field to [[Centralized_data.accdb]] * 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. == Changing D_IDs == [[Changing D_IDs]] == Related Articles == {{Related Articles}}
Save page Show preview Show changes Cancel