ClientGUID field: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 36: | Line 36: | ||
| todo_action = 2022-04-13 | | todo_action = 2022-04-13 | ||
| question = | | question = | ||
* ask Chastity what happens to John Doe's for ClientGUID }} | * ask Chastity what happens to John Doe's for ClientGUID | ||
* Ask Chastity if 3 month updates will be possible [[User:Ttenbergen|Ttenbergen]] 11:43, 2022 May 4 (CDT) | |||
* change IICU listing in Cognos IICU so collectors can enter from Cognos. [[User:Ttenbergen|Ttenbergen]] 11:43, 2022 May 4 (CDT) }} | |||
Revision as of 11:43, 2022 May 4
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.
This page is about the ClientGUID field which identifies people, not the ClientVisitGUID which identifies admissions.
Many patients don't have MB PHINs so we generate PseudoPHINs. I figured EPR must already solve this problem, and they use this field. We now get this as part of the Cognos data dump. 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.
|
|
|
|
|
Implementation
This would likely replace Person ID field; Generate Person IDs would still need to be done to enter this into L_Person table.
_dev_ccmdb_data, _dev_ccmdb
|
|
Data Processing improvements
Having this field might further cut down on Pre-linking checks, or at least on how many problems those find.
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. Chances are ancient records won't have a ClientGUID; we could fill in our PHIN/PseudoPHIN for those.
Log
- 2022-03-24 - added field to Cognos_import3 table in CCMDB.accdb so the import can still work.