Person ID field: Difference between revisions

(10 intermediate revisions by 2 users not shown)

Line 2:

|field_name=Person_ID

|CCMDB_label=N/A

|in_table=L Log table, L Person table

|data_type=number

|datafield_length=long integer

|program_collecting=Med and CC

|created_raw=Created

|data_element_sort_index=1

|element_description=Unique id per patient that combines the [[D_ID]]s across admissions/encounters.

|element_description=Unique random number id per patient that combines the [[D_ID]]s across admissions/encounters.

}}

A ~~random number generated by Access when a~~ new line is ~~added~~.

See [[Generate Person IDs]] for how Person_IDs are generated and maintained. A new line is generated in [[L_Person table]], and the Person_ID is assigned to [[Centralized_data.accdb]].[[L_Log table]].Person_ID .

~~It would be~~ permanently stored and therefore ~~remain~~ the same for new encounters of that patient in L_Log/~~L_PHI, but if an~~ L_Person ~~record were ever deleted and recreated it would NOT receive the same ID next time around~~.

For the most part, Person_ID is permanently stored and therefore remains the same for new encounters of that patient in [[L_Log table]]/[[L_Person table]].

~~The '''~~Person_ID'~~'' field~~ in [[~~Centralized_data.mdb]]'s [[L_Person table]] contains a unique id per patient that combines the [[D_ID~~]]~~s across admissions~~.

As of 2019-02-06, Person_ID doesn't show in any form in [[CFE]].

~~{{discussion}} The~~ [[~~L_Person~~ table]], it ~~doesn~~'~~t have~~ a ~~D_ID~~. ~~It seems to be populated, though: the last_update column's dates are recent~~. ~~I think~~ we ~~may~~ have ~~abandoned~~ this ~~process~~ in ~~mid-build~~. ~~Do we need to discuss? Ttenbergen 12:10, 2017 September 18 (CDT)~~

== Consistency of Person_ID over time ==

'''If a record in [[L Person table]] were ever deleted and recreated it would ''never'' receive the same Person_ID next time around'''. However, a new, re-generated Person ID would still link all records for that patient. See [[Generate Person IDs#Algorithm summary]] for details.

=== Implication for data we have provided ===

Main office discussed that the Person ID might change over time if a PHIN changes as per [[PHIN_field#Multiple_PHINs_or_PHIN_changes_over_time]]. Julie is aware of this and will include this in any considerations about ongoing data she provides.

== Related articles ==

[[Category: Multiple Encounter]]

[[Category:Multiple Encounter]]

[[Category: Centralized data front end.accdb]]

[[Category:Centralized data front end.accdb]]

@@ Line 2: / Line 2: @@
 |field_name=Person_ID
 |CCMDB_label=N/A
+|in_table=L Log table, L Person table
+|data_type=number
+|datafield_length=long integer
+|program_collecting=Med and CC
+|created_raw=Created
 |data_element_sort_index=1
-|element_description=Unique id per patient that combines the [[D_ID]]s across admissions/encounters.
+|element_description=Unique random number id per patient that combines the [[D_ID]]s across admissions/encounters.
 }}
-A random number generated by Access when a new line is added.
+See [[Generate Person IDs]] for how Person_IDs are generated and maintained. A new line is generated in [[L_Person table]], and the Person_ID is assigned to [[Centralized_data.accdb]].[[L_Log table]].Person_ID .
-It would be permanently stored and therefore remain the same for new encounters of that patient in L_Log/L_PHI, but if an L_Person record were ever deleted and recreated it would NOT receive the same ID next time around.
+For the most part, Person_ID is permanently stored and therefore remains the same for new encounters of that patient in [[L_Log table]]/[[L_Person table]].
-The '''Person_ID''' field in [[Centralized_data.mdb]]'s [[L_Person table]] contains a unique id per patient that combines the [[D_ID]]s across admissions.
+As of 2019-02-06, Person_ID doesn't show in any form in [[CFE]].
-{{discussion}} The [[L_Person table]], it doesn't have a D_ID. It seems to be populated, though: the last_update column's dates are recent. I think we may have abandoned this process in mid-build. Do we need to discuss? Ttenbergen 12:10, 2017 September 18 (CDT)
+== Consistency of Person_ID over time ==
+'''If a record in [[L Person table]] were ever deleted and recreated it would ''never'' receive the same Person_ID next time around'''. However, a new, re-generated Person ID would still link all records for that patient. See [[Generate Person IDs#Algorithm summary]] for details.
+=== Implication for data we have provided ===
+Main office discussed that the Person ID might change over time if a PHIN changes as per [[PHIN_field#Multiple_PHINs_or_PHIN_changes_over_time]]. Julie is aware of this and will include this in any considerations about ongoing data she provides.
 == Related articles ==
 {{Related Articles}}
-[[Category: Multiple Encounter]]
+[[Category:Multiple Encounter]]
-[[Category: Centralized data front end.accdb]]
+[[Category:Centralized data front end.accdb]]