ClientGUID field
| 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.
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.
|
_ccmdb_data_dev, _ccmdb_dev
|
|
|
Do we even still need the L_Person table if we have this field? It contains last updated and death. Since we never got hospital deaths, we probably don't use that field. And I doubt we use the last-updated field - and in any case, it could easily be recreated from data, no need to store it. Unless of course we want to use it so we can streamline the re-checking and re-indexing of data somehow. Ttenbergen 09:28, 2022 March 24 (CDT) |
Log
- 2022-03-24 - added field to Cognos_import3 table in CCMDB.accdb so the import can still work.