Generate Person IDs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "[[Category: " to "[[Category:"
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
"Generate Person IDs" is the process by which unique Person IDs are generated in [[L Person]] and associated with the ward-admission records in [[centralized_data.mdb]]. It also refers to the button "Generate Person IDs" in [[CFE]].
"Generate Person IDs" is the step during [[Centralized data Vetting Process]] by which unique Person IDs are generated in [[L Person table]] and associated with the ward-admission records in [[centralized_data.mdb]]. It also refers to the button "Generate Person IDs" in [[CFE]].


Related to [[Encounter processing]] and [[L Person]].
Related to [[Encounter processing]] and [[L Person table]].


== Instructions ==
== Instructions ==
At the right point in [[Centralized data Vetting Process]] '''(and only then)''' press the "Generate Person IDs" button.  
At the right point in [[Centralized data Vetting Process]] '''(and only then)''':
# click the 'generate person IDs'
# screen prompt 'done generating...', click OK
# email the  [[Statistician]] that all data is completed, corrected and vetted. 


== algorithm summary ==
Proceed as instructed in [[Centralized data Vetting Process]].
 
== Consistency of [[Person_ID]] over time ==
See [[Person ID field#Consistency of Person_ID over time]]
 
== Algorithm summary ==
{{Collapsable
| always= collapsed so it doesn't look like steps the [[Data processor]] needs to do.
| full= 
'' see encounter_processing module Sub Encounter_processor() for most current implementation
'' see encounter_processing module Sub Encounter_processor() for most current implementation


*clean out inconsistent data
*clean out inconsistent data
*for each L_Log entry for which Person_ID is blank and recordstatus is not "incomplete"
** delete [[Person_ID]]s in L_Log where the [[Person_ID]] corresponds to more than one PHIN
** if a record matching PHIN '''doesn't''' exist in L_Person
** delete [[Person_ID]]s in L_Log for which no [[L_Person table]]  entry exists
*** generate record in L_Person (set death to discharge date if deceased)
** delete records in [[L_Person table]]  that have no counterpart in L_Log
*** update L_Log.Person_ID to that new record's Person_ID
*for each L_Log entry for which [[Person_ID]] is blank and recordstatus is not "incomplete"
*** set L_Person.last_updated to now
** if a record matching PHIN '''doesn't''' exist in [[L_Person table]]
** if a record matching PHIN '''does''' exist in L_Person
*** generate record in [[L_Person table]]  (set death to discharge date if deceased)
*** add Person_ID to L_Log
*** update [[L_Log table|L_Log]].[[Person_ID]] to that new record's Person_ID
*** update last_updated and death in L_Person
*** set [[L_Person table]] .last_updated to now
 
** if a record matching PHIN '''does''' exist in [[L_Person table]]
We don't have process to populate [[L_Hospitalization]] worked out yet. {{discussion}}
*** add [[Person_ID]] to [[L_Log table]]
 
*** update last_updated and death in [[L_Person table]]  
== Consistency of Person_ID over time ==
}}
Once generated the Person_ID for new entries with same PHIN would be the same for new encounters.
 
If data becomes inconsistent (eg for some reason two person_ids for same PHIN, L_Person entry without corresponding L_Log entry, L_Log.Person_ID without correspoinding L_Person entry) the old data will be cleaned out and the records will be treated as if newly encountered patients.
 
Tina discussed with Julie that this will affect previously given out data, and we will address by giving out fresh data as a set including the old where linking is necessary. 17:15, 2015 April 1 (CDT)
 


== Related Articles ==
{{Related Articles}}


[[Category: Data Processing]]
[[Category:Data Processing]]
[[Category:Multiple Encounter]]
[[Category:Multiple Encounter]]
[[Category:Centralized data front end.accdb]]

Latest revision as of 11:34, 30 July 2025

"Generate Person IDs" is the step during Centralized data Vetting Process by which unique Person IDs are generated in L Person table and associated with the ward-admission records in centralized_data.mdb. It also refers to the button "Generate Person IDs" in CFE.

Related to Encounter processing and L Person table.

Instructions

At the right point in Centralized data Vetting Process (and only then):

  1. click the 'generate person IDs'
  2. screen prompt 'done generating...', click OK
  3. email the Statistician that all data is completed, corrected and vetted.

Proceed as instructed in Centralized data Vetting Process.

Consistency of Person_ID over time

See Person ID field#Consistency of Person_ID over time

Algorithm summary

collapsed so it doesn't look like steps the Data processor needs to do.   

see encounter_processing module Sub Encounter_processor() for most current implementation

Related articles: