ClientGUID field: Difference between revisions
Ttenbergen (talk | contribs) Created page with "{{Data element |field_name=ClientGUID |Rank=N/A |in_table=Cognos_Import3 |data_type=string |datafield_length=16 |program_collecting=Med and CC |created_raw=Raw |data_element_sort_index= |element_description=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 infra..." |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 16: | Line 16: | ||
* Do all collectors now add records from Cognos only or do some still do manual entry? Manual entry would break this. [[User:Ttenbergen|Ttenbergen]] 09:20, 2022 March 24 (CDT) | * Do all collectors now add records from Cognos only or do some still do manual entry? Manual entry would break this. [[User:Ttenbergen|Ttenbergen]] 09:20, 2022 March 24 (CDT) | ||
}} | }} | ||
== Implementation == | |||
This would likely replace [[Person ID field]]; [[Generate Person IDs]] would still need to be done to enter this into [[L_Person table]]. | |||
{{Discuss | 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. [[User:Ttenbergen|Ttenbergen]] 09:28, 2022 March 24 (CDT)}} | |||
=== Log === | |||
* 2022-03-24 - added field to table in CCMDB.accdb so the import can still work. | |||
== Changing D_IDs == | == Changing D_IDs == | ||