Generate Person IDs: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →algorithm summary: u |
Ttenbergen (talk | contribs) m m |
||
| Line 5: | Line 5: | ||
== algorithm summary == | == algorithm summary == | ||
'' 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 | 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 | * if a record matching PHIN '''doesn't''' exist in L_Person | ||
** generate record in L_Person (set death to discharge date if deceased) | ** generate record in L_Person (set death to discharge date if deceased) | ||
Revision as of 10:39, 1 April 2015
"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.
Related to Encounter processing and L Person.
algorithm summary
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"
- if a record matching PHIN doesn't exist in L_Person
- generate record in L_Person (set death to discharge date if deceased)
- update L_Log.Person_ID to that new record's Person_ID
- 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.