Person ID field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "L_PHI" to "L_PHI table"
mNo edit summary
Line 8: Line 8:
|created_raw=Created
|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.
}}
}}
A random number generated by Access when a new line is added.


It would be permanently stored and therefore remain the same for new encounters of that patient in L_Log/L_PHI table, but if an L_Person record were ever deleted and recreated it would NOT receive the same ID next time around.  
See [[Generate Person IDs]] and [[Correcting Person IDs]] for how Person_IDs are generated and maintained. A new line is generated in [[L_Person table]], and the Person_ID is assinged to [[Centralized data.mdb]].[[L_Log table]].Person_ID .


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.  
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]].  


{{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)
'''If an L_Person record were ever deleted and recreated it would NEVER receive the same Person_ID next time around'''. See [[Generate Person IDs]] and [[Correcting Person IDs]] for how Person_IDs are generated and updated for more info on scenarios that might cause a Patient_ID to change.  


== Related articles ==
== Related articles ==

Revision as of 13:56, 7 November 2018

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
Data Dependencies(Reports/Indicators/Data Elements):

Unique random number id per patient that combines the D_IDs across admissions/encounters.

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


See Generate Person IDs and Correcting Person IDs for how Person_IDs are generated and maintained. A new line is generated in L_Person table, and the Person_ID is assinged 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.

If an L_Person record were ever deleted and recreated it would NEVER receive the same Person_ID next time around. See Generate Person IDs and Correcting Person IDs for how Person_IDs are generated and updated for more info on scenarios that might cause a Patient_ID to change.

Related articles

Related articles: