XDRDOC ;IHS/OHPRD/JCM - DOCUMENTATION OF KERNEL ROUTINES ;09/13/93 08:39
;;7.3;TOOLKIT;;Apr 25, 1995
;
XDRDADD ; ADDS POTENTIAL DUPLICATE RECORDS TO DUPLICATE RECORD FILE
;
; Input Variables: XDRCD,XDRCD2,XDRFL,XDRGL,XDRDSCOR(,XDRDTEST(
;
; Called by: XDRDUP
;
; Calls: FILE^DICN,DIE,EN^XDRMAIN
;
XDRDADJ ; ADJUSTS DUPLICATE RECORD FILE UPON MERGE OF A PATIENT
;
; This routine is executed by a MUMPS xref on the MERGE STATUS field
; of the DUPLICATE RECORD file only when the status is set to MERGED.
; This routine checks for entries in the file that are affected by
; the merging of this entry, and adjusts their .01 and .02 fields
; accordingly. The problem being addressed is:
;
; 1 to 5 If 5 to 10 merged first 1 to 10
; 5 to 10 then other entries would 5 to 10
; 5 to 20 be adjusted as follows: 10 to 20
;
; Or, if both 1 to 5 and 1 to 10 existed at the time of the
; merge, the 1 to 5 entry would be deleted.
;
; The STATUS field (.03) is re-indexed because it sets xrefs based
; on the values in the .01 and .02 fields. TRIGGERs are not fired
; for the .01, .02, or .03 fields.
;
; Entries previously resolved are ignored.
;
; Called by: Cross Reference on Merge Status field of
; Duplicate Record File entry
;
; Calls: EN^XDRDUP,DIK
;
XDRDCOMP ; COMPARE TWO PATIENTS VIA THE DUP CHECKER ALGORITHM
;
; Input variables: XDRFL
;
; Calls: %ZIS,%ZTLOAD,DIC,DR,EN^DITC,FILE^XDRDQUE,XDRDSCOR,XDRDUP
;
XDRDLIST ; PRINT POTENTIAL AND VERIFIED DUPLICATES
;
; This routine is the main driver for reports dealing with the
; duplicate record file. It will print listings of Potential
; duplicates, ready and not ready to merge verified duplicates.
;
; Input variables: XDRFL
;
; Calls: EN1^DIP,DIR,FILE^XDRDQUE
;
XDRDMAIN ; MAIN DRIVER FOR DUPLICATE CHECKING SOFTWARE
;
; Input Variables: XDRFL - File number of File to be Checked
; XDRDPDTI - Defined if Potential Threshold Increased
; and Previous search completed
; XDRDTYPE - Type of search to run
;
; Calls: NOW^%DTC,DIE,DIK,XDRDPDTI,XDRDUP,XDREMSG,XDRMAINI
;
; We will pass the variable XDRCD for them to then get the candidates
; Expect the routine to send back the possibles in
; ^TMP("XDRD",$J,XDRFL,DFN
;
; There is a basic assumption in the limiting of which records are
; checked. It is assumed that if Record 1 gathers Record 2 as a
; candidate for duplicate checking that Record 2 will in turn
; gather Record 1 as a candidate for duplicate checking.
;
; It was decided that if a record is being checked again outside of
; the BASIC search type any entries in the Duplicate Record file
; other than merged entries will be deleted and then the pair
; rechecked.
;
XDRDPDTI ; CHECKS POTENTIAL DUPLICATES IF THRESHOLD RAISED
;
; This routine is called by XDRDMAIN when the Potential Duplicate
; threshold has been increased from a previous value. This routine
; $O's through the "APOT" cross reference on the Duplicate Record file
; and deletes all entries in the Duplicate Record file that had a DC
; Dupe Match Score that did not meet the new Potential Duplicate
; Threshold value. It also updates the DC Potential Dupe Threshold %.
; It should be noted that if a person changes the weights of the
; Duplicate Tests, they should delete all Non-Verified Potential
; Duplicates and rerun the Duplicate Resolution search.
;
; Input Variables: XDRGL,XDRFL,XDRDSCOR(
;
; Called by: XDRDMAIN
;
; Calls: DIE,DIK
;
XDRDPRGE ; PURGE DUPLICATE RECORD FILE
;
; This routine is used to purge the Duplicate Record file of either
; Potential Duplicates, Verified Non-Duplicates, or both.
; Verified Duplicates cannot be purged until Fileman institutes
; some sort of archival or merged node.
;
; Input Variable: XDRFL
;
; Calls: %ZTLOAD,DIC,DIR,DIK
;
XDRDOC ;IHS/OHPRD/JCM - DOCUMENTATION OF KERNEL ROUTINES ;09/13/93 08:39
+1 ;;7.3;TOOLKIT;;Apr 25, 1995
+2 ;
XDRDADD ; ADDS POTENTIAL DUPLICATE RECORDS TO DUPLICATE RECORD FILE
+1 ;
+2 ; Input Variables: XDRCD,XDRCD2,XDRFL,XDRGL,XDRDSCOR(,XDRDTEST(
+3 ;
+4 ; Called by: XDRDUP
+5 ;
+6 ; Calls: FILE^DICN,DIE,EN^XDRMAIN
+7 ;
XDRDADJ ; ADJUSTS DUPLICATE RECORD FILE UPON MERGE OF A PATIENT
+1 ;
+2 ; This routine is executed by a MUMPS xref on the MERGE STATUS field
+3 ; of the DUPLICATE RECORD file only when the status is set to MERGED.
+4 ; This routine checks for entries in the file that are affected by
+5 ; the merging of this entry, and adjusts their .01 and .02 fields
+6 ; accordingly. The problem being addressed is:
+7 ;
+8 ; 1 to 5 If 5 to 10 merged first 1 to 10
+9 ; 5 to 10 then other entries would 5 to 10
+10 ; 5 to 20 be adjusted as follows: 10 to 20
+11 ;
+12 ; Or, if both 1 to 5 and 1 to 10 existed at the time of the
+13 ; merge, the 1 to 5 entry would be deleted.
+14 ;
+15 ; The STATUS field (.03) is re-indexed because it sets xrefs based
+16 ; on the values in the .01 and .02 fields. TRIGGERs are not fired
+17 ; for the .01, .02, or .03 fields.
+18 ;
+19 ; Entries previously resolved are ignored.
+20 ;
+21 ; Called by: Cross Reference on Merge Status field of
+22 ; Duplicate Record File entry
+23 ;
+24 ; Calls: EN^XDRDUP,DIK
+25 ;
XDRDCOMP ; COMPARE TWO PATIENTS VIA THE DUP CHECKER ALGORITHM
+1 ;
+2 ; Input variables: XDRFL
+3 ;
+4 ; Calls: %ZIS,%ZTLOAD,DIC,DR,EN^DITC,FILE^XDRDQUE,XDRDSCOR,XDRDUP
+5 ;
XDRDLIST ; PRINT POTENTIAL AND VERIFIED DUPLICATES
+1 ;
+2 ; This routine is the main driver for reports dealing with the
+3 ; duplicate record file. It will print listings of Potential
+4 ; duplicates, ready and not ready to merge verified duplicates.
+5 ;
+6 ; Input variables: XDRFL
+7 ;
+8 ; Calls: EN1^DIP,DIR,FILE^XDRDQUE
+9 ;
XDRDMAIN ; MAIN DRIVER FOR DUPLICATE CHECKING SOFTWARE
+1 ;
+2 ; Input Variables: XDRFL - File number of File to be Checked
+3 ; XDRDPDTI - Defined if Potential Threshold Increased
+4 ; and Previous search completed
+5 ; XDRDTYPE - Type of search to run
+6 ;
+7 ; Calls: NOW^%DTC,DIE,DIK,XDRDPDTI,XDRDUP,XDREMSG,XDRMAINI
+8 ;
+9 ; We will pass the variable XDRCD for them to then get the candidates
+10 ; Expect the routine to send back the possibles in
+11 ; ^TMP("XDRD",$J,XDRFL,DFN
+12 ;
+13 ; There is a basic assumption in the limiting of which records are
+14 ; checked. It is assumed that if Record 1 gathers Record 2 as a
+15 ; candidate for duplicate checking that Record 2 will in turn
+16 ; gather Record 1 as a candidate for duplicate checking.
+17 ;
+18 ; It was decided that if a record is being checked again outside of
+19 ; the BASIC search type any entries in the Duplicate Record file
+20 ; other than merged entries will be deleted and then the pair
+21 ; rechecked.
+22 ;
XDRDPDTI ; CHECKS POTENTIAL DUPLICATES IF THRESHOLD RAISED
+1 ;
+2 ; This routine is called by XDRDMAIN when the Potential Duplicate
+3 ; threshold has been increased from a previous value. This routine
+4 ; $O's through the "APOT" cross reference on the Duplicate Record file
+5 ; and deletes all entries in the Duplicate Record file that had a DC
+6 ; Dupe Match Score that did not meet the new Potential Duplicate
+7 ; Threshold value. It also updates the DC Potential Dupe Threshold %.
+8 ; It should be noted that if a person changes the weights of the
+9 ; Duplicate Tests, they should delete all Non-Verified Potential
+10 ; Duplicates and rerun the Duplicate Resolution search.
+11 ;
+12 ; Input Variables: XDRGL,XDRFL,XDRDSCOR(
+13 ;
+14 ; Called by: XDRDMAIN
+15 ;
+16 ; Calls: DIE,DIK
+17 ;
XDRDPRGE ; PURGE DUPLICATE RECORD FILE
+1 ;
+2 ; This routine is used to purge the Duplicate Record file of either
+3 ; Potential Duplicates, Verified Non-Duplicates, or both.
+4 ; Verified Duplicates cannot be purged until Fileman institutes
+5 ; some sort of archival or merged node.
+6 ;
+7 ; Input Variable: XDRFL
+8 ;
+9 ; Calls: %ZTLOAD,DIC,DIR,DIK
+10 ;