Generate Person IDs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m cat
m Text replacement - "[[Category: " to "[[Category:"
 
(23 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]].


== algorithm summary ==
== Instructions ==
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. 
 
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


for each L_Log entry for which Person_ID is blank and recordstatus is not "incomplete"
*clean out inconsistent data
* if a record matching PHIN '''doesn't''' exist in L_Person
** delete [[Person_ID]]s in L_Log where the [[Person_ID]] corresponds to more than one PHIN
** generate record in L_Person (set death to discharge date if deceased)
** delete [[Person_ID]]s in L_Log for which no [[L_Person table]]  entry exists
** update L_Log.Person_ID to that new record's Person_ID
** delete records in [[L_Person table]]  that have no counterpart in L_Log
* if a record matching PHIN '''does''' exist in L_Person
*for each L_Log entry for which [[Person_ID]] is blank and recordstatus is not "incomplete"
** if patient is deceased in this L_Log, then confirm death date is not before one we already have in L_Person, don't process record and launch error if so
** if a record matching PHIN '''doesn't''' exist in [[L_Person table]]
** if no inconsistent death data, update last_updated and death 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
*** set [[L_Person table]] .last_updated to now
** if a record matching PHIN '''does''' exist in [[L_Person table]]
*** add [[Person_ID]] to [[L_Log table]]
*** update last_updated and death in [[L_Person table]]
}}


We don't have process to populate [[L_Hospitalization]] worked out yet.
== 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

Related articles: