Person ID field: Difference between revisions
Ttenbergen (talk | contribs) m L_Log too |
m Text replacement - "L_PHI" to "L_PHI table" |
||
| Line 12: | Line 12: | ||
A random number generated by Access when a new line is added. | 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, but if an L_Person record were ever deleted and recreated it would NOT receive the same ID next time around. | 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. | ||
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. | 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. | ||
Revision as of 16:57, 29 November 2017
| 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 id per patient that combines the D_IDs 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.
The Person_ID field in Centralized_data.mdb's L_Person table contains a unique id per patient that combines the D_IDs across admissions.
Template: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)
Related articles
| Related articles: |
|