| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | file to be checked(+) | 0;1 | POINTER | 1 | B | This is the file that is being checked for duplicates and if duplicates are found, to be merged. |
| .02 | duplicate search status(+) | 0;2 | SET OF CODES | c:COMPLETED h:HALTED r:RUNNING e:ERROR(STOP) | This is the status of the duplicate checker at any given time. | |
| .03 | search beginning date | 0;3 | DATE-TIME | This is the date and time that the present search started. This field does not require user input, it is automatically filled in when you start the search. | ||
| .04 | search completion date | 0;4 | DATE-TIME | This field is used to store the date and time that the duplicate search is completed. | ||
| .05 | type of search | 0;5 | SET OF CODES | b:BASIC n:NEW | This field describes the type of search the Duplicate Resolution software will conduct. A 'BASIC' search starts at the beginning of a file while the 'NEW' search will only check those newly added entries. | |
| .06 | cross-ref for new search | 0;6 | FREE TEXT | This is the name of the cross reference that should be utilized to separate out any records that you wish to run through the Duplicate Resolution software checking to see if any potential duplicates. | ||
| .07 | number of records processed | 0;7 | NUMERIC | This is the number of records that have been checked for duplicates by the duplicate checking software. | ||
| .08 | last record processed | 0;8 | NUMERIC | This is the last record that was processed by the duplicate checking software. | ||
| .09 | candidate collection routine(+) | 0;9 | FREE TEXT | This is the name of the routine which will be used to gather any potential duplicate records which should be checked by the Duplicate Resolution software. | ||
| .1 | seconds searched | 0;10 | NUMERIC | This field is used to track the number of seconds that the search process was running PRIOR TO the most current start (or restart). The value is determined at the time the process stops for any reason (completed, halt, or error). While the search is running it does NOT include time for the current process. | ||
| .11 | duplicate manager mail group | 0;11 | POINTER | 3.8 | This is the mail group that will be sent a bulletin whenever any known problems occur during the duplicate checking or merging process. | |
| .12 | number selected | 0;12 | NUMERIC | This field is used to indicate the number of potential duplicates that have been found in the current search. | ||
| .13 | days before final verify | 0;13 | NUMERIC | The value of this field is the number of days available for ancillary reviewers to conduct their reviews. If action is still pending by any ancillary reviewers after this period, the site may take alternative action; notify designated persons via a mail group, establish an additional reviewer, or otherwise resolve the review. All reviews must be resolved prior to merging the affected record pair. The default with this application release is five days. Days 1 to 30. | ||
| .14 | days between verify and merge | 0;14 | NUMERIC | This field contains the sites determination on the number of days that MUST pass before a completely verified duplicate pair may be merged. This time period is included to provide for outstanding tests which might have been ordered for the entry which is to be merged into the other one to be completed prior to the merge, so that data are not entered for the merged entry after the merge has been completed. | ||
| .15 | potential duplicate threshold%(+) | 0;15 | NUMERIC | This is the percentage of the total possible score that needs to be obtained before a duplicate record pair is placed in the Duplicate Record file as a Potential Non-Verified Duplicate pair. | ||
| .16 | verified duplicate mail group | 0;16 | POINTER | 3.8 | This is the mail group that will be sent a bulletin whenever a Potential Non-Verified Duplicate is changed to a Verified Duplicate status. | |
| .17 | verified duplicate msg routine | 0;17 | FREE TEXT | Enter the name of the routine which will be called to send a bulletin to members of the Verified Duplicate Mail Group. No '^' should be included. | ||
| .18 | verified duplicate threshold% | 0;18 | NUMERIC | This is the percentage that needs to be obtained before a duplicate record pair is placed in the Duplicate Record file as a Verified Potential Duplicate pair. | ||
| .25 | merge style(+) | 0;25 | SET OF CODES | 0:INTERACTIVE 1:NON-INTERACTIVE | This field is used to define whether during the merge process the operator will be able to select certain field values to transfer (Interactive) or if the merge will occur automatically (Non-interactive). | |
| .26 | delete from entry | 0;26 | BOOLEAN | 0:NO 1:YES | This field is used to tell the Duplicate Resolution software whether or not you wish to delete the From entry in this file. | |
| .27 | pre-merge routine | 0;27 | FREE TEXT | This field is utilized to name a routine that should be done prior to the merging process. This may be a entry point call to a routine or just a routine name. | ||
| .28 | post-merge routine | 0;28 | FREE TEXT | This field is utilized to name a routine that should be done after the completion of the merge process. This may be a entry point call to a routine or just a routine name. | ||
| .29 | merge mail group | 0;29 | POINTER | 3.8 | This is the mail group that will be sent a bulletin whenever the merge process has been completed for a duplicate record pair. | |
| .31 | merge msg routine | 0;31 | FREE TEXT | Enter the name of the routine which will be called to send a bulletin to members of the Merge Mail Group. No '^' should be included. | ||
| .32 | auto merge status | 0;32 | SET OF CODES | 0:RUN 1:STOP | This field is used by the Kernel Merge routines to determine if it should stop automatically merging the Ready to Merge Verified Duplicates. | |
| .33 | merge direction inp transform | 0;33 | FREE TEXT | This field contains the routine that will be executed by the input transform on the merge directions field of the Duplicate record file. This routine will execute code that will help the user decide whether or not they have selected the best record to be the target record. | ||
| 1.01 | number of threads | 1;1 | NUMERIC | This field is used to indicate the number of threads that should be used during the longest phase of the merge process. Entry of 1 would indicate that only the main process (the same as null) would be running. Entry of 2 to 5 indicates that the main process along with 1 to 4 other threads should be used during this phase. Each additional thread will be used to process one of the most time consuming files. Which will reduce the amount of time that the main process takes. | ||
| 1.02 | thread files | 1;2 | FREE TEXT | This field is used to indicate the preference for files which be used as separate threads during the 3rd phase of the merge if extra threads are indicated in field 1.01. The files to be threaded should be those which take the longest during this phase of the merge process with the most time consuming file indicated first. The files are indicated by file numbers separated by semi-colons, e.g., 44;52;50.8; | ||
| 1.03 | seconds to wait for stop check(+) | 1;3 | NUMERIC | This field will define how many seconds a merge process should run before making a call to ZTLOAD to see if the user requested the background processes to stop. | ||
| 2 | ancillary service | 2;0 | MULTIPLE | 15.12 | Ancillary Service is a multiple of the service packages that are associated with the duplicates. | |
| 3.01 | last time noted | 3;1 | DATE-TIME | This field is entered and updated during the search for potential duplicates. It is entered and updated by XDRDMAIN on each entry of the file that is being searched for duplicates. It is used by XDRDSTAT to determine if an apparently running process has stopped processing. If this is the case, the process is marked as having errored out after 15 minutes of no recorded activity. | ||
| 99 | suppress new dup email | 99;1 | BOOLEAN | 1:Yes 0:No | When a PATIENT pair entry is added to the DUPLICATE RECORD file by PSIM, an email is sent to the mail group specified in the DUPLICATE MANAGER MAIL GROUP field, notifying them that the patient pair has been added to the file with POTENTIAL DUPLICATE, UNVERIFIED status. If this field is set to 1 (YES), the email will be suppressed (NOT sent). If this field is set to 0 (NO), the email will be sent. | |
| 1100 | duplicate tests | 11;0 | MULTIPLE | 15.111 | Enter the name of the duplicate test you wish to run to determine if a pair of records are duplicates. | |
| 1200 | dinum files for merge | 12;0 | MULTIPLE | 15.112 | This multiple contains files that you want an operator to be able to compare and merge specific fields from prior to the merging and deletion of the duplicate record From entry. You may only enter files that point to and are dinum with the file you specified in the File to Be Checked field (#.01). You should only place entries in this multiple if you have chosen 'Interactive' for the type of merge in the Merge Style field (#.25). It uses Fileman's Compare and Merge option to display the duplicate record pair side by side allowing the operator to merge specific fields from the From entry to the To entry. |
Not Referenced