Generate Person IDs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m L_hosp issue is flagged in L Hospitalization table, no need to duplicate here.
m Text replacement - "[[Category: " to "[[Category:"
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
== Instructions ==
== Instructions ==
At the right point in [[Centralized data Vetting Process]] '''(and only then)''':  
At the right point in [[Centralized data Vetting Process]] '''(and only then)''':  
# click the 'generate person IDs'
# click the 'generate person IDs'
# screen prompt 'done generating...', click OK
# screen prompt 'done generating...', click OK
Line 11: Line 10:


Proceed as instructed in [[Centralized data Vetting Process]].
Proceed as instructed in [[Centralized data Vetting Process]].
== Correcting [[Person_ID]]s ==
see [[Correcting Person IDs]]


== Consistency of [[Person_ID]] over time ==
== Consistency of [[Person_ID]] over time ==
Line 41: Line 37:
{{Related Articles}}
{{Related Articles}}


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

Latest revision as of 10: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: