Generate Person IDs: Difference between revisions

(27 intermediate revisions by 2 users not shown)

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 ==

~~for each L_Log entry for which Person_ID is blank~~

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

* if a record matching PHIN '''~~doesn~~'t''' ~~exist in L_Person~~

# click the 'generate person IDs'

** generate ~~record in L_Person (set death to discharge date if deceased)~~

# screen prompt 'done generating...', click OK

** update L_Log.Person_ID to that new record'~~s Person_ID~~

# email the [[Statistician]] that all data is completed, corrected and vetted.

* if a record matching PHIN ''~~'does''' exist in L_Person~~

** 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 no inconsistent death data, ~~update last_updated~~ and ~~death in L_Person~~

** add Person_ID to L_Log

~~We don't have process to populate~~ [[~~L_Hospitalization~~]] ~~worked out yet~~.

Proceed as instructed in [[Centralized data Vetting Process]].

[[Category: Data Processing]]

== 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

*clean out inconsistent data

** delete [[Person_ID]]s in L_Log where the [[Person_ID]] corresponds to more than one PHIN

** delete [[Person_ID]]s in L_Log for which no [[L_Person table]] entry exists

** delete records in [[L_Person table]] that have no counterpart in L_Log

*for each L_Log entry for which [[Person_ID]] is blank and recordstatus is not "incomplete"

** if a record matching PHIN '''doesn't''' exist in [[L_Person table]]

*** generate record in [[L_Person table]] (set death to discharge date if deceased)

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

}}

== Related Articles ==

[[Category:Data Processing]]

[[Category:Multiple Encounter]]

[[Category:Centralized data front end.accdb]]

@@ 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 ==
-for each L_Log entry for which Person_ID is blank
+At the right point in [[Centralized data Vetting Process]] '''(and only then)''':
-* if a record matching PHIN '''doesn't''' exist in L_Person
+# click the 'generate person IDs'
-** generate record in L_Person (set death to discharge date if deceased)
+# screen prompt 'done generating...', click OK
-** update L_Log.Person_ID to that new record's Person_ID
+# email the  [[Statistician]] that all data is completed, corrected and vetted.
-* if a record matching PHIN '''does''' exist in L_Person
-** 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 no inconsistent death data, update last_updated and death in L_Person
-** add Person_ID to L_Log
-We don't have process to populate [[L_Hospitalization]] worked out yet.
+Proceed as instructed in [[Centralized data Vetting Process]].
-[[Category: Data Processing]]
+== 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
+*clean out inconsistent data
+** delete [[Person_ID]]s in L_Log where the [[Person_ID]] corresponds to more than one PHIN
+** delete [[Person_ID]]s in L_Log for which no [[L_Person table]]  entry exists
+** delete records in [[L_Person table]]  that have no counterpart in L_Log
+*for each L_Log entry for which [[Person_ID]] is blank and recordstatus is not "incomplete"
+** if a record matching PHIN '''doesn't''' exist in [[L_Person table]]
+*** generate record in [[L_Person table]]  (set death to discharge date if deceased)
+*** 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]]
+}}
+== Related Articles ==
+{{Related Articles}}
+[[Category:Data Processing]]
+[[Category:Multiple Encounter]]
+[[Category:Centralized data front end.accdb]]