IWeb Administrator Guide |
The deduplication procedures are native-stored Oracle procedures that are run through the SQL+ user interface. These procedures should run at least once per day and can be submitted one at a time or all at one time using the RUNALL.SQL command. These procedures run in varied time lengths (hours or minutes), depending on the number of new patient records. The progress of each procedure is updated every minute and is located in a separate table. See the Procedure Names/Progress Table Names section for more information.
Regardless of the executable procedure entered, the command-line and command content appear similar to this:
SQL>Exec[Procedure Name](Parameter):
Each portion of the command is as follows:
The executable process names, descriptions, and progress-check table names are as follows:
Procedure Name | Description | Progress-Check Table Name |
H33_Dedup_Patients(1); | Moves patient records from the Pre-Reserve table into the Reserve, Master, and Possible Duplicate tables | H33_Dedup_Patients_Progress |
H33_Process_Possible(1); | Moves patient records from the manual deduplication tables (Ambiguous ID and Possible Duplicate) into the Reserve and Master tables. Only the records that completed manual review are moved and those that have not been evaluated are skipped by the procedure.
The procedure has two steps:
|
H33_Process_Possible_Progress |
H33_Dedup_Vaccinations(1); | Moves vaccination records from the vaccination Pre-Reserve table into the vaccination Reserve and Master tables and performs all four of these parameter steps:
Deduplication - Moves vaccination records from the vaccination Pre-Reserve table to the Reserve table. Vaccinations are checked to see if they have already been sent and, if so, are updated.
|
H33_Dedup_Vaccination_Progress |
H33_Dedup_Vaccinations(2); | Moves vaccination records from the vaccination Pre-Reserve table into the vaccination Reserve and Master tables and does not perform an association. This non-linking process runs because the new patients have not been brought into the system and are not yet available for linking. | H33_Dedup_Vaccination_Progress |
H33_Master_Duplicate_Scan("); | Reviews all of the records in the patient Master table and merges the similar records | H33_Master_Duplicate_Scan_Progress |
H33_Update_RC_Patient(1); | Moves records from Remote Clinic into the registry | H33_Update_RC_Patient_Progress |
H33_Dedup_Simple_Masters(1); | Dedup_Simple_Masters merges the two or more patient reserve records into one record. The most recent record is the one that is kept. It then moves the incoming record back to the H33_patient_pre_reserve table to be reprocessed (presumably, it matches automatically when it is reprocessed) | H33_Dedup_Simple_Masters_Progress |
Runall.sql | This is a program that is set up by the database administrator and runs all of the above procedures:
|
Progress can be checked in each of the corresponding Progress tables. These tables have similar fields that are used to view and control a running procedure.
The fields most commonly used for viewing and controlling are as follows:
Field | Description |
Start_Time |
The time the procedure was started |
Pulse |
Updated with the system time every time a record is updated |
Stop |
This field, used with any character, can be used to stop a running procedure |
Stop_Time |
A pre-determined time to stop the running of the procedure |