Generate Person IDs: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 37: Line 37:
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.  


{{Discuss | who = Julie | question = Person_ID
{{Discuss | who = Julie | question = [[Person ID field]]
* 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)
* 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... }}
** I think we since discussed that this would actually create problems... }}

Revision as of 23:41, 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

see Correcting Person IDs

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

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

  • SMW


  • Cargo


  • Categories

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 field

  • 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...
  • SMW


  • Cargo


  • Categories

Related Articles

Related articles: