Generate Person IDs: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
"Generate Person IDs" is the | "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]]. | Related to [[Encounter processing]] and [[L Person table]]. | ||
| Line 34: | Line 34: | ||
If data becomes inconsistent (eg for some reason two [[Person_ID]]s for same PHIN, [[L_Person table]] entry without corresponding L_Log entry, [[L_Log table|L_Log]].[[Person_ID]] without correspoinding [[L_Person table]] entry) the old data will be cleaned out and the records will be treated as if newly encountered patients. | If data becomes inconsistent (eg for some reason two [[Person_ID]]s for same PHIN, [[L_Person table]] entry without corresponding L_Log entry, [[L_Log table|L_Log]].[[Person_ID]] without correspoinding [[L_Person table]] 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) | {{Discuss | who = Julie | question = Person_ID | ||
* 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) | |||
** I think we since discussed that this would actually create problems... }} | |||
== Related Articles == | == Related Articles == | ||
Revision as of 22:42, 6 February 2019
"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) press the "Generate Person IDs" button.
Proceed as instructed in Centralized data Vetting Process.
Correcting Person_IDs
algorithm summary
see encounter_processing module Sub Encounter_processor() for most current implementation
- clean out inconsistent data
- delete Person_IDs in L_Log where the Person_ID corresponds to more than one PHIN
- delete Person_IDs 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.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
- if a record matching PHIN doesn't exist in L_Person table
|
We don't have process to populate L_Hospitalization worked out yet. |
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 table entry without corresponding L_Log entry, L_Log.Person_ID without correspoinding L_Person table entry) the old data will be cleaned out and the records will be treated as if newly encountered patients.
|
Person_ID
|
Related Articles
| Related articles: |