Person ID field: Difference between revisions
Ttenbergen (talk | contribs) template use |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
|field_name=Person_ID | |field_name=Person_ID | ||
|CCMDB_label=N/A | |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 | |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. | ||
}} | }} | ||
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.mdb]].[[L_Log table]].Person_ID . | |||
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]]. | |||
As of 2019-02-06, Person_ID doesn't show in any form in [[CFE]]. | |||
== 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 == | ||
Latest revision as of 16:11, 2019 March 20
| Data Element (edit) | |
| Field Name: | Person_ID |
| CCMDB Label: | N/A |
| CCMDB tab: | not stated |
| Table: | L Log table, L Person table |
| Data type: | number |
| Length: | long integer |
| Program: | Med and CC |
| Created/Raw: | Created |
| Start Date: | 1988-07-11 |
| End Date: | 2300-01-01 |
| Sort Index: | 1 |
Unique random number id per patient that combines the D_IDs across admissions/encounters.
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.mdb.L_Log table.Person_ID .
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.
As of 2019-02-06, Person_ID doesn't show in any form in CFE.
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: |
|