[613] | 1 | XDRDOC ;IHS/OHPRD/JCM - DOCUMENTATION OF KERNEL ROUTINES ;09/13/93 08:39
|
---|
| 2 | ;;7.3;TOOLKIT;;Apr 25, 1995
|
---|
| 3 | ;
|
---|
| 4 | XDRDADD ; ADDS POTENTIAL DUPLICATE RECORDS TO DUPLICATE RECORD FILE
|
---|
| 5 | ;
|
---|
| 6 | ; Input Variables: XDRCD,XDRCD2,XDRFL,XDRGL,XDRDSCOR(,XDRDTEST(
|
---|
| 7 | ;
|
---|
| 8 | ; Called by: XDRDUP
|
---|
| 9 | ;
|
---|
| 10 | ; Calls: FILE^DICN,DIE,EN^XDRMAIN
|
---|
| 11 | ;
|
---|
| 12 | XDRDADJ ; ADJUSTS DUPLICATE RECORD FILE UPON MERGE OF A PATIENT
|
---|
| 13 | ;
|
---|
| 14 | ; This routine is executed by a MUMPS xref on the MERGE STATUS field
|
---|
| 15 | ; of the DUPLICATE RECORD file only when the status is set to MERGED.
|
---|
| 16 | ; This routine checks for entries in the file that are affected by
|
---|
| 17 | ; the merging of this entry, and adjusts their .01 and .02 fields
|
---|
| 18 | ; accordingly. The problem being addressed is:
|
---|
| 19 | ;
|
---|
| 20 | ; 1 to 5 If 5 to 10 merged first 1 to 10
|
---|
| 21 | ; 5 to 10 then other entries would 5 to 10
|
---|
| 22 | ; 5 to 20 be adjusted as follows: 10 to 20
|
---|
| 23 | ;
|
---|
| 24 | ; Or, if both 1 to 5 and 1 to 10 existed at the time of the
|
---|
| 25 | ; merge, the 1 to 5 entry would be deleted.
|
---|
| 26 | ;
|
---|
| 27 | ; The STATUS field (.03) is re-indexed because it sets xrefs based
|
---|
| 28 | ; on the values in the .01 and .02 fields. TRIGGERs are not fired
|
---|
| 29 | ; for the .01, .02, or .03 fields.
|
---|
| 30 | ;
|
---|
| 31 | ; Entries previously resolved are ignored.
|
---|
| 32 | ;
|
---|
| 33 | ; Called by: Cross Reference on Merge Status field of
|
---|
| 34 | ; Duplicate Record File entry
|
---|
| 35 | ;
|
---|
| 36 | ; Calls: EN^XDRDUP,DIK
|
---|
| 37 | ;
|
---|
| 38 | XDRDCOMP ; COMPARE TWO PATIENTS VIA THE DUP CHECKER ALGORITHM
|
---|
| 39 | ;
|
---|
| 40 | ; Input variables: XDRFL
|
---|
| 41 | ;
|
---|
| 42 | ; Calls: %ZIS,%ZTLOAD,DIC,DR,EN^DITC,FILE^XDRDQUE,XDRDSCOR,XDRDUP
|
---|
| 43 | ;
|
---|
| 44 | XDRDLIST ; PRINT POTENTIAL AND VERIFIED DUPLICATES
|
---|
| 45 | ;
|
---|
| 46 | ; This routine is the main driver for reports dealing with the
|
---|
| 47 | ; duplicate record file. It will print listings of Potential
|
---|
| 48 | ; duplicates, ready and not ready to merge verified duplicates.
|
---|
| 49 | ;
|
---|
| 50 | ; Input variables: XDRFL
|
---|
| 51 | ;
|
---|
| 52 | ; Calls: EN1^DIP,DIR,FILE^XDRDQUE
|
---|
| 53 | ;
|
---|
| 54 | XDRDMAIN ; MAIN DRIVER FOR DUPLICATE CHECKING SOFTWARE
|
---|
| 55 | ;
|
---|
| 56 | ; Input Variables: XDRFL - File number of File to be Checked
|
---|
| 57 | ; XDRDPDTI - Defined if Potential Threshold Increased
|
---|
| 58 | ; and Previous search completed
|
---|
| 59 | ; XDRDTYPE - Type of search to run
|
---|
| 60 | ;
|
---|
| 61 | ; Calls: NOW^%DTC,DIE,DIK,XDRDPDTI,XDRDUP,XDREMSG,XDRMAINI
|
---|
| 62 | ;
|
---|
| 63 | ; We will pass the variable XDRCD for them to then get the candidates
|
---|
| 64 | ; Expect the routine to send back the possibles in
|
---|
| 65 | ; ^TMP("XDRD",$J,XDRFL,DFN
|
---|
| 66 | ;
|
---|
| 67 | ; There is a basic assumption in the limiting of which records are
|
---|
| 68 | ; checked. It is assumed that if Record 1 gathers Record 2 as a
|
---|
| 69 | ; candidate for duplicate checking that Record 2 will in turn
|
---|
| 70 | ; gather Record 1 as a candidate for duplicate checking.
|
---|
| 71 | ;
|
---|
| 72 | ; It was decided that if a record is being checked again outside of
|
---|
| 73 | ; the BASIC search type any entries in the Duplicate Record file
|
---|
| 74 | ; other than merged entries will be deleted and then the pair
|
---|
| 75 | ; rechecked.
|
---|
| 76 | ;
|
---|
| 77 | XDRDPDTI ; CHECKS POTENTIAL DUPLICATES IF THRESHOLD RAISED
|
---|
| 78 | ;
|
---|
| 79 | ; This routine is called by XDRDMAIN when the Potential Duplicate
|
---|
| 80 | ; threshold has been increased from a previous value. This routine
|
---|
| 81 | ; $O's through the "APOT" cross reference on the Duplicate Record file
|
---|
| 82 | ; and deletes all entries in the Duplicate Record file that had a DC
|
---|
| 83 | ; Dupe Match Score that did not meet the new Potential Duplicate
|
---|
| 84 | ; Threshold value. It also updates the DC Potential Dupe Threshold %.
|
---|
| 85 | ; It should be noted that if a person changes the weights of the
|
---|
| 86 | ; Duplicate Tests, they should delete all Non-Verified Potential
|
---|
| 87 | ; Duplicates and rerun the Duplicate Resolution search.
|
---|
| 88 | ;
|
---|
| 89 | ; Input Variables: XDRGL,XDRFL,XDRDSCOR(
|
---|
| 90 | ;
|
---|
| 91 | ; Called by: XDRDMAIN
|
---|
| 92 | ;
|
---|
| 93 | ; Calls: DIE,DIK
|
---|
| 94 | ;
|
---|
| 95 | XDRDPRGE ; PURGE DUPLICATE RECORD FILE
|
---|
| 96 | ;
|
---|
| 97 | ; This routine is used to purge the Duplicate Record file of either
|
---|
| 98 | ; Potential Duplicates, Verified Non-Duplicates, or both.
|
---|
| 99 | ; Verified Duplicates cannot be purged until Fileman institutes
|
---|
| 100 | ; some sort of archival or merged node.
|
---|
| 101 | ;
|
---|
| 102 | ; Input Variable: XDRFL
|
---|
| 103 | ;
|
---|
| 104 | ; Calls: %ZTLOAD,DIC,DIR,DIK
|
---|
| 105 | ;
|
---|