ClientGUID field: Difference between revisions

Line 15:

{{DiscussTask |

* Do all collectors now add records from Cognos only or do some still do manual entry? Manual entry would break any processes we change to use this. [[User:Ttenbergen|Ttenbergen]] 09:20, 2022 March 24 (CDT)

** ClientGUID is defined as '''unique identifier of the visit, seems to be used as prefix by later fields ending in *Chg''' - is that the same as unique person (PHIN and Pseudo PHIN) or it is only unique by visit per site? For NON-MB, you still need to run Person_ID, correct? what will be the gain having the clientGUID, is there a running time advantage? I am using Person_ID instead of PHIN/PseudoPHIN as unique patient identifier when providing individual patient data and when linking admissions - I need to be assured that the ClientGUID is really unique by patient. --[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT) }}

** ClientGUID is defined as '''unique identifier of the visit, seems to be used as prefix by later fields ending in *Chg''' - is that the same as unique person (PHIN and Pseudo PHIN) or it is only unique by visit per site? For NON-MB, you still need to run Person_ID, correct? what will be the gain having the clientGUID, is there a running time advantage? I am using Person_ID instead of PHIN/PseudoPHIN as unique patient identifier when providing individual patient data and when linking admissions - I need to be assured that the ClientGUID is really unique by patient. --[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)

*** I think you mean field Client'''Visit'''GUID. This is a new field and it actually identifies the patient, regardless of which province etc. The Non-MB issue is exactly what this field would solve. So, yes, unique by pt. [[User:Ttenbergen|Ttenbergen]] 12:10, 2022 March 24 (CDT) }}

== Implementation ==

Line 33:

Line 34:

{{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)

** I haven't used this table [[L_Person table]] and not aware of its purpose. Is it intended to know quickly how many unique patients there are in the database? but without any other relevant data, not useful at all.--[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT) }}

** I haven't used this table [[L_Person table]] and not aware of its purpose. Is it intended to know quickly how many unique patients there are in the database? but without any other relevant data, not useful at all.--[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)

*** Agreed, not much use, it was added when we thought we would get Hospital Death in the near future. It is also used to contain the PersonID to make sure it's unique, but it really doesn't do a great job with it for now. I just wanted to be sure you are not using it for anything before possibly making big changes to it. [[User:Ttenbergen|Ttenbergen]] 12:10, 2022 March 24 (CDT)}}

=== Data Processing improvements ===

@@ Line 15: / Line 15: @@
 {{DiscussTask |
 * Do all collectors now add records from Cognos only or do some still do manual entry? Manual entry would break any processes we change to use this. [[User:Ttenbergen|Ttenbergen]] 09:20, 2022 March 24 (CDT)
-**  ClientGUID is defined as '''unique identifier of the visit, seems to be used as prefix by later fields ending in *Chg''' - is that the same as unique  person  (PHIN and Pseudo PHIN) or it is only unique by visit per site?  For NON-MB, you still need to run Person_ID, correct? what will be the gain having the clientGUID, is there a running time advantage?   I am using Person_ID instead of PHIN/PseudoPHIN as unique patient identifier when providing individual patient data and when linking admissions - I need to be assured that the ClientGUID is really unique by patient.  --[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)   }}
+**  ClientGUID is defined as '''unique identifier of the visit, seems to be used as prefix by later fields ending in *Chg''' - is that the same as unique  person  (PHIN and Pseudo PHIN) or it is only unique by visit per site?  For NON-MB, you still need to run Person_ID, correct? what will be the gain having the clientGUID, is there a running time advantage?   I am using Person_ID instead of PHIN/PseudoPHIN as unique patient identifier when providing individual patient data and when linking admissions - I need to be assured that the ClientGUID is really unique by patient.  --[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)
+*** I think you mean field Client'''Visit'''GUID. This is a new field and it actually identifies the patient, regardless of which province etc. The Non-MB issue is exactly what this field would solve. So, yes, unique by pt. [[User:Ttenbergen|Ttenbergen]] 12:10, 2022 March 24 (CDT) }}
 == Implementation ==
@@ Line 33: / Line 34: @@
 {{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)
-** I haven't used  this table [[L_Person table]] and not aware of its purpose. Is it  intended to know quickly how many unique patients there are in the database? but without any other relevant data, not useful at all.--[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)  }}
+** I haven't used  this table [[L_Person table]] and not aware of its purpose. Is it  intended to know quickly how many unique patients there are in the database? but without any other relevant data, not useful at all.--[[User:JMojica|JMojica]] 10:20, 2022 March 24 (CDT)
+*** Agreed, not much use, it was added when we thought we would get Hospital Death in the near future. It is also used to contain the PersonID to make sure it's unique, but it really doesn't do a great job with it for now. I just wanted to be sure you are not using it for anything before possibly making big changes to it. [[User:Ttenbergen|Ttenbergen]] 12:10, 2022 March 24 (CDT)}}
 === Data Processing improvements ===