============================================================================= Run Date: FEB 22, 2022 Designation: DG*5.3*1067 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #936 Status: Released Compliance Date: FEB 25, 2022 ============================================================================= Associated patches: (v)DG*5.3*1059 <<= must be installed BEFORE `DG*5.3*1067' (v)DG*5.3*557 <<= must be installed BEFORE `DG*5.3*1067' (v)DG*5.3*1045 <<= must be installed BEFORE `DG*5.3*1067' (v)DG*5.3*1056 <<= must be installed BEFORE `DG*5.3*1067' Subject: NOK-EC-DESIGNEE RELATIONSHIP, REG ONLY REASONS, AND VHAP UPDATES Category: - Enhancement (Mandatory) - Routine - Data Dictionary - Other Description: ============ Veterans Health Information Systems and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE) patch DG*5.3*1067 is being released to support enhancements for the Eligibility and Enrollment (E&E) program. This patch focuses on updates for the Enrollment System Modernization (ESM) Phase 3 project. Patch DG*5.3*1067 is also being released in support of the Veterans Health Administration (VHA) Enrollment System (VES) 6.0 release. Refer to Informational Patch EAS*1*208 (Enrollment Application System) for additional details regarding the VES release. Patch DG*5.3*1067 includes the following enhancements, with details provided below: - Standardizes Next of Kin (NOK), Emergency Contact (EC) and Designee Relationship to Patient. - Adds new Self-Reported Registration Reasons for Clinical Evaluations, Housing and Urban Development - VA Supportive Housing (HUD-VASH), 4TH MISSION, and Immunizations. - Adds FileMan field cross-references to support VES/Veterans Administration (VA) Profile Demographic Integration. - Adds two and modifies four Veterans Health Administration (VHA) Profiles (VHAPs) to support CERNER billing. Two new VHA Profiles: NAME : ACTIVE DUTY PLAN CODE: 303 NAME : JOINT INCENTIVE FUND PLAN CODE: 304 Modified VHA Profiles: NAME: VA DOD SHARING MEDICAL RESOURCES PLAN CODE: 295 NAME: TRICARE PLAN CODE: 229 NAME: VETERAN PLAN CCP RESTRICTED CARE PLAN CODE: 300 NAME: APPLICANT IN PROCESS PLAN CODE: 226 - Adds and modifies VHAP information related to Veteran Family Member Programs (VFMPs) summarized below. These will be assigned to patients by the VES only after a future VES release. New VHA Profiles: NAME: CHAMPVA CAREGIVER PLAN CODE: 305 Modified VHA Profiles: (The plan below replaces VETERAN BENEFICIARY PLAN - CAMP LEJEUNE FAMILY, Plan Code 139.) NAME: CAMP LEJEUNE FAMILY PLAN CODE: 306 (The plan below is renamed from BENEFICIARY CHAMPVA.) NAME: CHAMPVA STANDARD PLAN CODE: 108 NAME: BENEFICIARY SPINA BIFIDA PLAN CODE: 109 NAME: BENEFICIARY CHILDREN OF WOMEN PLAN CODE: 110 OF VIETNAM VETERANS NAME: VETERAN FOREIGN MEDICAL PROGRAM PLAN CODE: 122 NOTE: DG*5.3*1067 is being released with IVM*2.0*204 (Income Verification Match) in Host File DG_53_P1067.KID. Listing of Updates: ================== This patch makes the following enhancements to VistA REE: ************************************************************************** SECTION 1: DATA DICTIONARY UPDATES ************************************************************************** 1. A new PATIENT CONTACT RELATION file (#12.11) is added to VistA. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- This file contains all acceptable relationships for persons named as Primary Next of Kin, Secondary Next of Kin, Primary Emergency Contact, Secondary Emergency Contact, and Designee. These relationships are consistent with the values used by Defense Manpower Data Center (DMDC) and Cerner for these relationships. Additions or modifications to entries in this file should only be done through a national patch release. Records in this file should not be added, edited, or deleted locally. Doing so would likely cause database corruption. DD ACCESS: @ RD ACCESS: @ WR ACCESS: @ DEL ACCESS: @ LAYGO ACCESS: @ AUDIT ACCESS: @ IDENTIFIED BY: NAME (#.02) POINTED TO BY: K2-RELATIONSHIP TYPE field (#.2104) of the PATIENT File (#2) K-RELATIONSHIP TYPE field (#.224) of the PATIENT File (#2) E-RELATIONSHIP TYPE field (#.3309) of the PATIENT File (#2) E2-RELATIONSHIP TYPE field (#.331015) of the PATIENT File (#2) D-RELATIONSHIP TYPE field (#.34015) of the PATIENT File (#2) CROSS REFERENCED BY: NUMBER(B), NAME(C) CREATED ON: NOV 29, 2021 BY DGAdmin,One LAST MODIFIED: DEC 6,2021@15:11:25 12.11,.01 NUMBER 0;1 NUMBER (Required) INPUT TRANSFORM: K:+X'=X!(X>999)!(X<1)!(X?.E1"."4N.N) X LAST EDITED: NOV 29, 2021 HELP-PROMPT: Type a whole number between 1 and 999. DESCRIPTION: This field contains the number of the Patient Contact Relation. CROSS-REFERENCE: 12.11^B 1)= S ^DG(12.11,"B",$E(X,1,30),DA)="" 2)= K ^DG(12.11,"B",$E(X,1,30),DA) This cross-reference allows the user to lookup an entry by the NUMBER field. 12.11,.02 NAME 0;2 FREE TEXT INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X MAXIMUM LENGTH: 30 LAST EDITED: DEC 06, 2021 HELP-PROMPT: Enter a name for the Patient Contact Relation between 3 and 30 characters. DESCRIPTION: This field contains Standardized Name of the Patient Contact Relation. CROSS-REFERENCE: 12.11^C 1)= S ^DG(12.11,"C",$E(X,1,30),DA)="" 2)= K ^DG(12.11,"C",$E(X,1,30),DA) This cross-reference allows the user to lookup an entry by the NAME field. 12.11,.03 ACTIVE? 0;3 SET (BOOLEAN Data Type) LAST EDITED: NOV 30, 2021 HELP-PROMPT: Enter 1 if the Patient Contact Relation is active. Enter 0 if the Patient Contact is no longer active. DESCRIPTION: This field indicates whether the Patient Contact Relation may be selected by the user. INPUT TEMPLATE(S): PRINT TEMPLATE(S): SORT TEMPLATE(S): FORM(S)/BLOCK(S): 2. The PATIENT CONTACT RELATION file (#12.11) is populated with the following data. Only active entries are allowed to be entered. NUMBER NAME ACTIVE? ------ ---------------- ------- 1 BROTHER YES 2 CHILD-IN-LAW YES 3 DAUGHTER YES 4 EXTENDED FAMILY MEMBER YES 5 FATHER YES 6 GRANDCHILD YES 7 HUSBAND YES 8 MOTHER YES 9 NIECE/NEPHEW YES 10 SISTER YES 11 SON YES 12 STEPCHILD YES 13 UNRELATED FRIEND/OTHER YES 14 WARD YES 15 WIFE YES 3. The PATIENT file (#2) has the following new fields added. - K-RELATIONSHIP TYPE field (#.224) - K2-RELATIONSHIP TYPE field (#.2104) - E-RELATIONSHIP TYPE field (#.3309) - E2-RELATIONSHIP TYPE field (#.331015) - D-RELATIONSHIP TYPE field (#.34015) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.224 K-RELATIONSHIP TYPE .21;15 POINTER TO PATIENT CONTACT RELATION FILE (#12.11) (audited) INPUT TRANSFORM: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X I $D(X) S DFN =DA D K1^DGLOCK2 LAST EDITED: JAN 06, 2022 HELP-PROMPT: Enter the relationship of the primary NOK to the patient. DESCRIPTION: If a primary next-of-kin is specified, enter the relationship of that person to the applicant. This field cannot be deleted as long as a 'next of kin' name is on file. SCREEN: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"")" EXPLANATION: Enter active relation types only. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D K1D^DGLOCK2 I '$D(X) NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM3 (#597) MUMPS ACTION Short Descr: PRIMARY NOK Cross-Reference Description: This cross-reference will update the PRIMARY NOK CHANGE DATE/TIME field when the Primary Next of Kin data changes for a patient. Set Logic: D PNOK^DGDDDTTM Kill Logic: D PNOK^DGDDDTTM X(1): K-NAME OF PRIMARY NOK (2,.211) (forwards) X(2): K-RELATIONSHIP TO PATIENT (2,.212) (forwards) X(3): K-STREET ADDRESS [LINE 1] (2,.213) (forwards) X(4): K-STREET ADDRESS [LINE 2] (2,.214) (forwards) X(5): K-STREET ADDRESS [LINE 3] (2,.215) (forwards) X(6): K-CITY (2,.216) (forwards) X(7): K-STATE (2,.217) (forwards) X(8): K-ZIP CODE (2,.218) (forwards) X(9): K-ADDRESS SAME AS PATIENT'S? (2,.2125) (forwards) X(10): K-ZIP+4 (2,.2207) (forwards) X(11): K-PHONE NUMBER (2,.219) (forwards) X(12): K-WORK PHONE NUMBER (2,.21011) (forwards) X(13): K-COUNTRY (2,.221) (forwards) X(14): K-PROVINCE (2,.222) (forwards) X(15): K-POSTAL CODE (2,.223) (forwards) X(16): K-RELATIONSHIP TYPE (2,.224) (forwards) FILES POINTED TO FIELDS PATIENT CONTACT RELATION (#12.11) K-RELATIONSHIP TYPE (#.224) 2,.2104 K2-RELATIONSHIP TYPE .211;15 POINTER TO PATIENT CONTACT RELATION FILE (#12.11) (audited) INPUT TRANSFORM: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"")" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X I $D(X) S DFN=DA D K2^DGLOCK2 LAST EDITED: JAN 05, 2022 HELP-PROMPT: Enter the relationship of the secondary NOK to the patient. DESCRIPTION: If a secondary next-of-kin is specified, enter the relationship of that person to the applicant. This field cannot be deleted as long as a secondary NOK is on file. SCREEN: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"")" EXPLANATION: Enter active relation types only. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D K2D^DGLOCK2 I '$D(X) NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM4 (#598) MUMPS ACTION Short Descr: SECONDARY NOK Cross-Reference Description: This cross-reference will update the SECONDARY NOK CHANGE DATE/TIME field when the Secondary Next of Kin data changes for a patient. Set Logic: D SNOK^DGDDDTTM Kill Logic: D SNOK^DGDDDTTM X(1): K2-NAME OF SECONDARY NOK (2,.2191) (forwards) X(2): K2-RELATIONSHIP TO PATIENT (2,.2192) (forwards) X(3): K2-STREET ADDRESS [LINE 1] (2,.2193) (forwards) X(4): K2-STREET ADDRESS [LINE 2] (2,.2194) (forwards) X(5): K2-STREET ADDRESS [LINE 3] (2,.2195) (forwards) X(6): K2-CITY (2,.2196) (forwards) X(7): K2-STATE (2,.2197) (forwards) X(8): K2-ZIP CODE (2,.2198) (forwards) X(9): K2-ADDRESS SAME AS PATIENT'S? (2,.21925) (forwards) X(10): K2-ZIP+4 (2,.2203) (forwards) X(11): K2-PHONE NUMBER (2,.2199) (forwards) X(12): K2-WORK PHONE NUMBER (2,.211011) (forwards) X(13): K2-COUNTRY (2,.2101) (forwards) X(14): K2-PROVINCE (2,.2102) (forwards) X(15): K2-POSTAL CODE (2,.2103) (forwards) X(16): K2-RELATIONSHIP TYPE (2,.2104) (forwards) FILES POINTED TO FIELDS PATIENT CONTACT RELATION (#12.11) K2-RELATIONSHIP TYPE (#.2104) 2,.3309 E-RELATIONSHIP TYPE .33;15 POINTER TO PATIENT CONTACT REL ATION FILE (#12.11) (audited) INPUT TRANSFORM: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X I $ D(X) S DFN=DA D E1^DGLOCK2 LAST EDITED: JAN 05, 2022 HELP-PROMPT: Enter the relationship of the emergency contact to the patient. DESCRIPTION: If a primary emergency contact is specified, enter the relationship of that person to the applicant. This field cannot be deleted as long as a primary emergency contact is on file. SCREEN: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" EXPLANATION: Enter active relation types only. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D E1D^DGLOCK2 I '$D(X) NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM5 (#599) MUMPS ACTION Short Descr: E-CONTACT Cross-Reference Description: This cross-reference will update the E-CONTACT CHANGE DATE/TIME field when the Emergency Contact data changes for a patient. Set Logic: D ECON^DGDDDTTM Kill Logic: D ECON^DGDDDTTM X(1): E-NAME (2,.331) (forwards) X(2): E-RELATIONSHIP TO PATIENT (2,.332) (forwards) X(3): E-STREET ADDRESS [LINE 1] (2,.333) (forwards) X(4): E-STREET ADDRESS [LINE 2] (2,.334) (forwards) X(5): E-STREET ADDRESS [LINE 3] (2,.335) (forwards) X(6): E-CITY (2,.336) (forwards) X(7): E-STATE (2,.337) (forwards) X(8): E-ZIP CODE (2,.338) (forwards) X(9): E-EMER. CONTACT SAME AS NOK? (2,.3305) (forwards) X(10): E-ZIP+4 (2,.2201) (forwards) X(11): E-PHONE NUMBER (2,.339) (forwards) X(12): E-WORK PHONE NUMBER (2,.33011) (forwards) X(13): E-COUNTRY (2,.3306) (forwards) X(14): E-PROVINCE (2,.3307) (forwards) X(15): E-POSTAL CODE (2,.3308) (forwards) X(16): E-RELATIONSHIP TYPE (2,.3309) (forwards) FILES POINTED TO FIELDS PATIENT CONTACT RELATION (#12.11) E-RELATIONSHIP TYPE (#.3309) 2,.331015 E2-RELATIONSHIP TYPE .331;15 POINTER TO PATIENT CONTACT RE LATION FILE (#12.11) (audited) INPUT TRANSFORM: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X I $ D(X) S DFN=DA D E2^DGLOCK2 LAST EDITED: JAN 05, 2022 HELP-PROMPT: Enter the relationship of the secondary emergency contact to the patient. DESCRIPTION: If a secondary emergency contact is specified, enter the relationship of that person to the applicant. This field cannot be deleted as long as a secondary emergency contact is on file. SCREEN: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" EXPLANATION: Enter active relation types only. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D E2D^DGLOCK2 I '$D(X) NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM6 (#600) MUMPS ACTION Short Descr: E2-CONTACT Cross-Reference Description: This cross-reference will update the E2-CONTACT CHANGE DATE/TIME field when the Secondary Emergency Contact data changes for a patient. Set Logic: D ECON2^DGDDDTTM Kill Logic: D ECON2^DGDDDTTM X(1): E2-NAME OF SECONDARY CONTACT (2,.3311) (forwards) X(2): E2-RELATIONSHIP TO PATIENT (2,.3312) (forwards) X(3): E2-STREET ADDRESS [LINE 1] (2,.3313) (forwards) X(4): E2-STREET ADDRESS [LINE 2] (2,.3314) (forwards) X(5): E2-STREET ADDRESS [LINE 3] (2,.3315) (forwards) X(6): E2-CITY (2,.3316) (forwards) X(7): E2-STATE (2,.3317) (forwards) X(8): E2-ZIP CODE (2,.3318) (forwards) X(9): E2-ZIP+4 (2,.2204) (forwards) X(10): E2-PHONE NUMBER (2,.3319) (forwards) X(11): E2-WORK PHONE NUMBER (2,.331011) (forwards) X(12): E2-COUNTRY (2,.331012) (forwards) X(13): E2-PROVINCE (2,.331013) (forwards) X(14): E2-POSTAL CODE (2,.331014) (forwards) X(15): E2-RELATIONSHIP TYPE (2,.331015) (forwards) FILES POINTED TO FIELDS PATIENT CONTACT RELATION (#12.11) E2-RELATIONSHIP TYPE (#.331015) 2,.34015 D-RELATIONSHIP TYPE .34;15 POINTER TO PATIENT CONTACT REL ATION FILE (#12.11) (audited) INPUT TRANSFORM: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X I $ D(X) S DFN=DA D D^DGLOCK2 LAST EDITED: JAN 05, 2022 HELP-PROMPT: Enter the relationship of the designee to the patient. DESCRIPTION: If a designee is specified, enter the relationship of that person to the applicant. This field cannot be deleted as long as a designee is on file. SCREEN: S DIC("S")="I $$GET1^DIQ(12.11,Y,.03,""I"" )" EXPLANATION: Enter active relation types only. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D DD^DGLOCK2 I '$D(X) NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM7 (#601) MUMPS ACTION Short Descr: DESIGNEE Cross-Reference Description: This cross-reference will update the DESIGNEE CHANGE DATE/TIME field when the Designee data changes for a patient. Set Logic: D DESIG^DGDDDTTM Kill Logic: D DESIG^DGDDDTTM X(1): D-NAME OF DESIGNEE (2,.341) (forwards) X(2): D-RELATIONSHIP TO PATIENT (2,.342) (forwards) X(3): D-STREET ADDRESS [LINE 1] (2,.343) (forwards) X(4): D-STREET ADDRESS [LINE 2] (2,.344) (forwards) X(5): D-STREET ADDRESS [LINE 3] (2,.345) (forwards) X(6): D-CITY (2,.346) (forwards) X(7): D-STATE (2,.347) (forwards) X(8): D-ZIP CODE (2,.348) (forwards) X(9): D-DESIGNEE SAME AS NOK? (2,.3405) (forwards) X(10): D-ZIP+4 (2,.2202) (forwards) X(11): D-PHONE NUMBER (2,.349) (forwards) X(12): D-WORK PHONE NUMBER (2,.34011) (forwards) X(13): D-COUNTRY (2,.34012) (forwards) X(14): D-PROVINCE (2,.34013) (forwards) X(15): D-POSTAL CODE (2,.34014) (forwards) X(16): D-RELATIONSHIP TYPE (2,.34015) (forwards) FILES POINTED TO FIELDS PATIENT CONTACT RELATION (#12.11) D-RELATIONSHIP TYPE (#.34015) 4. The Help Text and Descriptions for the K-RELATIONSHIP TO PATIENT field (#.212), K2-RELATIONSHIP TO PATIENT field (#.2192) E-RELATIONSHIP TO PATIENT field (#.332), E2-RELATIONSHIP TO PATIENT field (#.3312) and D-RELATIONSHIP TO PATIENT field (#.342) of the PATIENT file (#2), shown below, are modified. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.212 K-RELATIONSHIP TO PATIENT .21;2 FREE TEXT (audited) INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X I $D(X) S DFN=DA D K1^DGLOCK2 LAST EDITED: DEC 14, 2021 HELP-PROMPT: Enter any notes related to the relationship of the primary NOK to the patient [1-30 characters]. DESCRIPTION: If a primary next-of-kin is specified, enter any additional information regarding the relationship of that person to the applicant [1-30 characters]. This field cannot be deleted as long as a 'next of kin' name is on file. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D K1D^DGLOCK2 I '$D(X) GROUP: NK1 NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 2^ADGRU212^MUMPS 1)= D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA) 2)= D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA) This cross reference is used to remember that changes were made to a monitored data field in the PATIENT File (#2) required for a vendor RAI/MDS COTS system. Execution of this cross reference will create an entry in the ADT/HL7 PIVOT file (#391.71) and mark it as requiring transmission of an HL7 demographic A08 update message to the COTS interface. The local variable DGRUGA08 will be set to 1 if the cross reference is not to be executed as part of a re-indexing. RECORD INDEX: ADTTM3 (#597) MUMPS ACTION Short Descr: PRIMARY NOK Cross-Reference Description: This cross-reference will update the PRIMARY NOK CHANGE DATE/TIME field when the Primary Next of Kin data changes for a patient. Set Logic: D PNOK^DGDDDTTM Kill Logic: D PNOK^DGDDDTTM X(1): K-NAME OF PRIMARY NOK (2,.211) (forwards) X(2): K-RELATIONSHIP TO PATIENT (2,.212) (forwards) X(3): K-STREET ADDRESS [LINE 1] (2,.213) (forwards) X(4): K-STREET ADDRESS [LINE 2] (2,.214) (forwards) X(5): K-STREET ADDRESS [LINE 3] (2,.215) (forwards) X(6): K-CITY (2,.216) (forwards) X(7): K-STATE (2,.217) (forwards) X(8): K-ZIP CODE (2,.218) (forwards) X(9): K-ADDRESS SAME AS PATIENT'S? (2,.2125) (forwards) X(10): K-ZIP+4 (2,.2207) (forwards) X(11): K-PHONE NUMBER (2,.219) (forwards) X(12): K-WORK PHONE NUMBER (2,.21011) (forwards) X(13): K-COUNTRY (2,.221) (forwards) X(14): K-PROVINCE (2,.222) (forwards) X(15): K-POSTAL CODE (2,.223) (forwards) X(16): K-RELATIONSHIP TYPE (2,.224) (forwards) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.2192 K2-RELATIONSHIP TO PATIENT .211;2 FREE TEXT (audited) INPUT TRANSFORM: K:$L(X)>30!($L(X)<1) X I $D(X) S DFN=DA D K2^DGLOCK2 LAST EDITED: DEC 13, 2021 HELP-PROMPT: Enter any notes related to the relationship of the secondary NOK to the patient [1-30 characters]. DESCRIPTION: If a secondary next-of-kin is specified, enter any additional information regarding the relationship of that person to the applicant [1-30 characters]. This field cannot be deleted as long as a secondary NOK is on file. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D K2D^DGLOCK2 I '$D(X) GROUP: NK2 NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM4 (#598) MUMPS ACTION Short Descr: SECONDARY NOK Cross-Reference Description: This cross-reference will update the SECONDARY NOK CHANGE DATE/TIME field when the Secondary Next of Kin data changes for a patient. Set Logic: D SNOK^DGDDDTTM Kill Logic: D SNOK^DGDDDTTM X(1): K2-NAME OF SECONDARY NOK (2,.2191) (forwards) X(2): K2-RELATIONSHIP TO PATIENT (2,.2192) (forwards) X(3): K2-STREET ADDRESS [LINE 1] (2,.2193) (forwards) X(4): K2-STREET ADDRESS [LINE 2] (2,.2194) (forwards) X(5): K2-STREET ADDRESS [LINE 3] (2,.2195) (forwards) X(6): K2-CITY (2,.2196) (forwards) X(7): K2-STATE (2,.2197) (forwards) X(8): K2-ZIP CODE (2,.2198) (forwards) X(9): K2-ADDRESS SAME AS PATIENT'S? (2,.21925) (forwards) X(10): K2-ZIP+4 (2,.2203) (forwards) X(11): K2-PHONE NUMBER (2,.2199) (forwards) X(12): K2-WORK PHONE NUMBER (2,.211011) (forwards) X(13): K2-COUNTRY (2,.2101) (forwards) X(14): K2-PROVINCE (2,.2102) (forwards) X(15): K2-POSTAL CODE (2,.2103) (forwards) X(16): K2-RELATIONSHIP TYPE (2,.2104) (forwards) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.332 E-RELATIONSHIP TO PATIENT .33;2 FREE TEXT (audited) INPUT TRANSFORM: K:$L(X)>30!($L(X)<2) X I $D(X) S DFN=DA D E1^DGLOCK2 LAST EDITED: DEC 13, 2021 HELP-PROMPT: Enter any notes related to the relationship of the emergency contact to the patient [3-35 characters]. DESCRIPTION: If a primary emergency contact is specified, enter any additional information regarding the relationship of that person to the applicant [3-35 characters]. This field cannot be deleted as long as a primary emergency contact is on file. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D E1D^DGLOCK2 I '$D(X) GROUP: EC1 NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM5 (#599) MUMPS ACTION Short Descr: E-CONTACT Cross-Reference Description: This cross-reference will update the E-CONTACT CHANGE DATE/TIME field when the Emergency Contact data changes for a patient. Set Logic: D ECON^DGDDDTTM Kill Logic: D ECON^DGDDDTTM X(1): E-NAME (2,.331) (forwards) X(2): E-RELATIONSHIP TO PATIENT (2,.332) (forwards) X(3): E-STREET ADDRESS [LINE 1] (2,.333) (forwards) X(4): E-STREET ADDRESS [LINE 2] (2,.334) (forwards) X(5): E-STREET ADDRESS [LINE 3] (2,.335) (forwards) X(6): E-CITY (2,.336) (forwards) X(7): E-STATE (2,.337) (forwards) X(8): E-ZIP CODE (2,.338) (forwards) X(9): E-EMER. CONTACT SAME AS NOK? (2,.3305) (forwards) X(10): E-ZIP+4 (2,.2201) (forwards) X(11): E-PHONE NUMBER (2,.339) (forwards) X(12): E-WORK PHONE NUMBER (2,.33011) (forwards) X(13): E-COUNTRY (2,.3306) (forwards) X(14): E-PROVINCE (2,.3307) (forwards) X(15): E-POSTAL CODE (2,.3308) (forwards) X(16): E-RELATIONSHIP TYPE (2,.3309) (forwards) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.3312 E2-RELATIONSHIP TO PATIENT .331;2 FREE TEXT (audited) INPUT TRANSFORM: K:$L(X)>30!($L(X)<2) X I $D(X) S DFN=DA D E2^DGLOCK2 LAST EDITED: DEC 13, 2021 HELP-PROMPT: Enter any notes related to the relationship of the secondary emergency contact to the patient [2-30 characters]. DESCRIPTION: If a secondary emergency contact is specified, enter any additional information regarding the relationship of that person to the applicant [2-30 characters]. This field cannot be deleted as long as a secondary emergency contact is on file. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D E2D^DGLOCK2 I '$D(X) GROUP: EC2 NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM6 (#600) MUMPS ACTION Short Descr: E2-CONTACT Cross-Reference Description: This cross-reference will update the E2-CONTACT CHANGE DATE/TIME field when the Secondary Emergency Contact data changes for a patient. Set Logic: D ECON2^DGDDDTTM Kill Logic: D ECON2^DGDDDTTM X(1): E2-NAME OF SECONDARY CONTACT (2,.3311) (forwards) X(2): E2-RELATIONSHIP TO PATIENT (2,.3312) (forwards) X(3): E2-STREET ADDRESS [LINE 1] (2,.3313) (forwards) X(4): E2-STREET ADDRESS [LINE 2] (2,.3314) (forwards) X(5): E2-STREET ADDRESS [LINE 3] (2,.3315) (forwards) X(6): E2-CITY (2,.3316) (forwards) X(7): E2-STATE (2,.3317) (forwards) X(8): E2-ZIP CODE (2,.3318) (forwards) X(9): E2-ZIP+4 (2,.2204) (forwards) X(10): E2-PHONE NUMBER (2,.3319) (forwards) X(11): E2-WORK PHONE NUMBER (2,.331011) (forwards) X(12): E2-COUNTRY (2,.331012) (forwards) X(13): E2-PROVINCE (2,.331013) (forwards) X(14): E2-POSTAL CODE (2,.331014) (forwards) X(15): E2-RELATIONSHIP TYPE (2,.331015) (forwards) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.342 D-RELATIONSHIP TO PATIENT .34;2 FREE TEXT (audited) INPUT TRANSFORM: K:$L(X)>30!($L(X)<3) X I $D(X) S DFN=DA D D^DGLOCK2 LAST EDITED: DEC 13, 2021 HELP-PROMPT: Enter any notes related to the relationship of the designee to the patient [3-30 characters]. DESCRIPTION: If a designee is specified, enter any additional information regarding the relationship of that person to the applicant [3-30 characters]. This field cannot be deleted as long as a designee is on file. AUDIT: YES, ALWAYS DELETE TEST: 1,0)= S DFN=DA D DD^DGLOCK2 I '$D(X) GROUP: D1 NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER RECORD INDEX: ADTTM7 (#601) MUMPS ACTION Short Descr: DESIGNEE Cross-Reference Description: This cross-reference will update the DESIGNEE CHANGE DATE/TIME field when the Designee data changes for a patient. Set Logic: D DESIG^DGDDDTTM Kill Logic: D DESIG^DGDDDTTM X(1): D-NAME OF DESIGNEE (2,.341) (forwards) X(2): D-RELATIONSHIP TO PATIENT (2,.342) (forwards) X(3): D-STREET ADDRESS [LINE 1] (2,.343) (forwards) X(4): D-STREET ADDRESS [LINE 2] (2,.344) (forwards) X(5): D-STREET ADDRESS [LINE 3] (2,.345) (forwards) X(6): D-CITY (2,.346) (forwards) X(7): D-STATE (2,.347) (forwards) X(8): D-ZIP CODE (2,.348) (forwards) X(9): D-DESIGNEE SAME AS NOK? (2,.3405) (forwards) X(10): D-ZIP+4 (2,.2202) (forwards) X(11): D-PHONE NUMBER (2,.349) (forwards) X(12): D-WORK PHONE NUMBER (2,.34011) (forwards) X(13): D-COUNTRY (2,.34012) (forwards) X(14): D-PROVINCE (2,.34013) (forwards) X(15): D-POSTAL CODE (2,.34014) (forwards) X(16): D-RELATIONSHIP TYPE (2,.34015) (forwards) 5. Four entries are added to the PATIENT REGISTRATION ONLY REASON file (#408.43). The field values for each are listed below. REASON (#.01) AVAILABILITY (#.02) CODE (#.03) ------------- ------------------- ----------- 4TH MISSION COLLATERAL OF PATIENT 20 CLINICAL EVALUATION REGISTER A PATIENT 21 HUD-VASH REGISTER A PATIENT 22 IMMUNIZATIONS COLLATERAL OF PATIENT 23 NOTE: These entries are not available for selection by the user during registration until the current date/time is greater than or equal to the "DG PATCH DG*5.3*1067 ACTIVE" parameter date/time value. See item 9 below for information on this parameter. 6. A new cross-reference is added to the RELIGIOUS PREFERENCE field (#.08) of the PATIENT file (#2). This cross-reference is used to notify HEC of changes that may affect enrollment. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2,.08 RELIGIOUS PREFERENCE 0;8 POINTER TO RELIGION FILE (#13) (audited) RELIGION LAST EDITED: DEC 07, 2021 HELP-PROMPT: Select from the available list this patients religious preference. DESCRIPTION: Select from the available listing the religious preference of this applicant. AUDIT: YES, ALWAYS GROUP: DEMOG CROSS-REFERENCE: 2^AVAFC08^MUMPS 1)= I ($T(AVAFC^VAFCDD01)'="") S VAFCF=".08;" D AVAFC^VAFCDD01(DA) 2)= I ($T(AVAFC^VAFCDD01)'="") S VAFCF=".08;" D AVAFC^VAFCDD01(DA) This cross reference is used to remember that changes were made to the PATIENT file (#2) outside of the Registration process. Execution of this cross reference will create an entry in the ADT/HL7 PIVOT file (#391.71) and mark it as requiring transmission of an HL7 ADT-A08 message. The local variable VAFCFLG will be set to 1 if the cross reference is not executed because the change is being made from within the Registration process. Execution of this cross reference can be prevented by setting the local variable VAFCA08 equal to 1. The local variable VAFCF is used to identify the field edited. This data is stored in the FIELD(S) EDITED (#2.1) field in the ADT/HL7 PIVOT file (#391.71). CROSS-REFERENCE: 2^ADGRU08^MUMPS 1)= D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA) 2)= D:($T(ADGRU^DGRUDD01)'="") ADGRU^DGRUDD01(DA) This cross reference is used to remember that changes were made to a monitored data field in the PATIENT File (#2) required for a vendor RAI/MDS COTS system. Execution of this cross reference will create an entry in the ADT/HL7 PIVOT file (#391.71) and mark it as requiring transmission of an HL7 demographic A08 update message to the COTS interface. The local variable DGRUGA08 will be set to 1 if the cross reference is not to be executed as part of a re-indexing. CROSS-REFERENCE: 2^AENR08^MUMPS 1)= D EVENT^IVMPLOG(DA) 2)= D EVENT^IVMPLOG(DA) 3)= DO NOT DELETE This cross-reference is used to notify HEC of changes that may affect enrollment. FILES POINTED TO FIELDS RELIGION (#13) RELIGIOUS PREFERENCE (#.08) 7. A new cross-reference is added to the RACE INFORMATION field (#.01) of the RACE INFORMATION subfile (#2.02) of the PATIENT file (#2). This cross-reference is used to notify HEC of changes that may affect enrollment. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE --------------------------------------------------------------------- 2.02,.01 RACE INFORMATION 0;1 POINTER TO RACE FILE (#10) (Multiply asked) INPUT TRANSFORM: S DIC("S")="I '$G(^(.02))" D ^DIC K D IC S DIC=$G(DIE),X=+Y K:Y<0 X S:$D(X) DINUM=X LAST EDITED: DEC 05, 2021 HELP-PROMPT: Select from the available listing all races which best identify this patient DESCRIPTION: Patient's race SCREEN: S DIC("S")="I '$G(^(.02))" EXPLANATION: Inactive values are not selectable NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 2.02^B 1)= S ^DPT(DA(1),.02,"B",$E(X,1,30),DA)="" 2)= K ^DPT(DA(1),.02,"B",$E(X,1,30),DA) CROSS-REFERENCE: ^^TRIGGER^2.02^.02 1)= X ^DD(2.02,.01,1,2,1.3) I X S X=D IV S Y(1)=$S($D(^DPT(D0,.02,D1,0)):^( 0),1:"") S X=$P(Y(1),U,2),X=X S DIU=X K Y S X=DIV S X=+$O(^DIC(10.3,"C","S ",0)) S:X=0 X="" X ^DD(2.02,.01,1,2,1 .4) 1.3)= K DIV S DIV=X,D0=DA(1),DIV(0)=D 0,D1=DA,DIV(1)=D1 S Y(0)=X S Y(1)=$S( $D(^DPT(D0,.02,D1,0)):^(0),1:"") S X= $S('$D(^DIC(10.3,+$P(Y(1),U,2),0)):"" ,1:$P(^(0),U,1))="" 1.4)= S DIH=$G(^DPT(DIV(0),.02,DIV(1) ,0)),DIV=X S $P(^(0),U,2)=DIV,DIH=2.0 2,DIG=.02 D ^DICR 2)= Q CREATE CONDITION)= METHOD OF COLLECTION="" CREATE VALUE)= S X=+$O(^DIC(10.3,"C", "S",0)) S:X=0 X="" DELETE VALUE)= NO EFFECT FIELD)= METHOD SELF IDENTIFICATION is the default value for collection method CROSS-REFERENCE: 2^AENR20201^MUMPS 1)= D EVENT^IVMPLOG($G(DA(1))) 2)= D EVENT^IVMPLOG($G(DA(1))) 3)= DO NOT DELETE This cross-reference is used to notify HEC of changes that may affect enrollment. FIELD INDEX: AVAFC20201 (#374) MUMPS I ACTION Short Descr: This x-ref calls the DG FIELD MONITOR event point. Description: This cross reference activates the DG FIELD MONITOR event point. Applications that wish to monitor edit activity related to this field may subscribe to that event point and take action as indicated by the changes that occur. Refer to the DG FIELD MONITOR protocol for a description of the information available at the time of the event. Set Logic: D FC^DGFCPROT(.DA,2.02,.01,"SET",$H,$ G(DUZ),.X,.X1,.X2,$G(XQY0)) Q Kill Logic: D FC^DGFCPROT(.DA,2.02,.01,"KILL",$H, $G(DUZ),.X,.X1,.X2,$G(XQY0)) Q X(1): RACE INFORMATION (2.02,.01) (forwards) FILES POINTED TO FIELDS RACE (#10) RACE INFORMATION (#.01) 8. A new cross-reference is added to the ETHNICITY INFORMATION field (#.01) of the ETHNICITY INFORMATION subfile (#2.06) of the PATIENT file (#2). This cross-reference is used to notify HEC of changes that may affect enrollment. DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- 2.06,.01 ETHNICITY INFORMATION 0;1 POINTER TO ETHNICITY FILE (#10.2) INPUT TRANSFORM: S DIC("S")="I '$G(^(.02))" D ^DIC K DIC S DIC=DIE,X=+Y K:Y<0 X S:$D(X) DINUM=X LAST EDITED: DEC 05, 2021 HELP-PROMPT: Select from the available listing the ethnicity which best identifies this patient DESCRIPTION: Patient's ethnicity TECHNICAL DESCR: Although this field is defined to be multi-valued, the AONLYONE cross reference prevents multiple values from being stored. This is because the current business definition for ethnicity only accounts for a single value. SCREEN: S DIC("S")="I '$G(^(.02))" EXPLANATION: Inactive values are not selectable NOTES: XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER CROSS-REFERENCE: 2.06^B 1)= S ^DPT(DA(1),.06,"B",$E(X,1,30),DA)="" 2)= K ^DPT(DA(1),.06,"B",$E(X,1,30),DA) CROSS-REFERENCE: ^^TRIGGER^2.06^.02 1)= X ^DD(2.06,.01,1,2,1.3) I X S X=DIV S Y(1)=$S($D(^DPT(D0,.06,D1,0)):^(0),1:"") S X=$P(Y(1),U,2),X=X S DIU=X K Y S X=DIV S X=+$O(^DIC(10.3,"C","S",0)) S:X=0 X="" X ^ DD(2.06,.01,1,2,1.4) 1.3)= K DIV S DIV=X,D0=DA(1),DIV(0)=D0,D1= DA,DIV(1)=D1 S Y(0)=X S Y(1)=$S($D(^DPT(D0 ,.06,D1,0)):^(0),1:"") S X=$S('$D(^DIC(10. 3,+$P(Y(1),U,2),0)):"",1:$P(^(0),U,1))="" 1.4)= S DIH=$G(^DPT(DIV(0),.06,DIV(1),0)), DIV=X S $P(^(0),U,2)=DIV,DIH=2.06,DIG=.02 D ^DICR 2)= Q CREATE CONDITION)= METHOD OF COLLECTION="" CREATE VALUE)= S X=+$O(^DIC(10.3,"C","S",0 )) S:X=0 X="" DELETE VALUE)= NO EFFECT FIELD)= METHOD SELF IDENTIFICATION is the default value for collection method CROSS-REFERENCE: 2^AENR20601^MUMPS 1)= D EVENT^IVMPLOG($G(DA(1))) 2)= D EVENT^IVMPLOG($G(DA(1))) 3)= DO NOT DELETE This cross-reference is used to notify HEC of changes that may affect enrollment. FIELD INDEX: AONLYONE (#172) MUMPS ACTION Short Descr: Only one entry allowed in multiple Description: Cross reference deletes all entries in the multiple EXCEPT the one just added. This has the net affect of only allowing one entry to exist in the multiple. Set Logic: N DGFDA,DGMSG,DGD0,DGD1,DGLOOP S DGD0=DA(1 ),DGD1=DA S DGLOOP=0 F S DGLOOP=$O(^DPT(D GD0,.06,DGLOOP)) Q:'DGLOOP I DGLOOP'=DGD1 S DGFDA(2.06,DGLOOP_","_DGD0_",",.01)="@" D FILE^DIE("","DGFDA","DGMSG") K DGFDA,DG MSG Kill Logic: Q X(1): ETHNICITY INFORMATION (2.06,.01) (forwards) FIELD INDEX: AVAFC20601 (#375) MUMPS I ACTION Short Descr: This x-ref calls the DG FIELD MONITOR event point. Description: This cross reference activates the DG FIELD MONITOR event point. Applications that wish to monitor edit activity related to this field may subscribe to that event point and take action as indicated by the changes that occur. Refer to the DG FIELD MONITOR protocol for a description of the information available at the time of the event. Set Logic: D FC^DGFCPROT(.DA,2.06,.01,"SET",$H,$G(DUZ ),.X,.X1,.X2,$G(XQY0)) Q Kill Logic: D FC^DGFCPROT(.DA,2.06,.01,"KILL",$H,$G(DU Z),.X,.X1,.X2,$G(XQY0)) Q X(1): ETHNICITY INFORMATION (2.06,.01) (forwards) FILES POINTED TO FIELDS ETHNICITY (#10.2) ETHNICITY INFORMATION (#.01) 9. A new parameter DG PATCH DG*5.3*1067 ACTIVE is added to the PARAMETER DEFINITION file (#8989.51). A timestamp value of Feb 26, 2022@1700 is stored in this parameter indicating when the new Registration Only Reasons (see item 5 above) will be active. The timestamp value is set via post-install routine POST^DG531067P. ** BEGIN SCREEN CAPTURE ** NUMBER: 1055 NAME: DG PATCH DG*5.3*1067 ACTIVE DISPLAY TEXT: Active date/time for patch DG*5.3*1067 MULTIPLE VALUED: No PROHIBIT EDITING: No VALUE DATA TYPE: date/time VALUE DOMAIN: ::T VALUE HELP: Enter the date/time when patch DG*5.3*1067 becomes active. DESCRIPTION: This parameter contains the date/time when the functionality in patch DG*5.3*1067 becomes active. PRECEDENCE: 1 ENTITY FILE: PACKAGE ** END SCREEN CAPTURE ** An instance of this parameter is created in the PARAMETER file (#8989.5) with a timestamp value of Feb 26, 2022@1700. This parameter indicates when the new Registration Only Reasons (see item 5 above) will be active. The parameter is created and the timestamp value is set via post-install routine POST^DG531067P. ** BEGIN SCREEN CAPTURE ** ENTITY (PKG): REGISTRATION PARAMETER: DG PATCH DG*5.3*1067 ACTIVE INSTANCE: 1 VALUE: FEB 26, 2022@17:00 ** END SCREEN CAPTURE ** ************************************************************************** SECTION 2: VHAP UPDATES ************************************************************************** 1. Two new VHA Profiles are added to the VistA HEALTH BENEFIT PLAN file (#25.11), shown below. NUMBER: 94 NAME : ACTIVE DUTY PLAN CODE: 303 COVERAGE CODE: AD01001 SHORT DESCRIPTION: AD LONG DESCRIPTION: Active Duty (AD) and AD Family Prime ------------------------------------ Patient receiving care at a VAMC as AD of the Department of Defense: *TRICARE Authorization: - Required for TRICARE Prime patients - AD and AD Family Prime *If patient has a Veteran status and on Active Duty Orders, then all Active Duty rules apply - Even if treatment is Service Connected - Patient considered TRICARE Prime enrollee - Includes active Reserve and National Guard - Federal orders must exceed 30 days NUMBER: 95 NAME : JOINT INCENTIVE FUND PLAN CODE: 304 COVERAGE CODE: JF01001 SHORT DESCRIPTION: JIF LONG DESCRIPTION: VA/DoD Joint Incentive Fund (JIF) --------------------------------- Patient receiving care at either VA Medical Center or Department of Defense (DoD) facility under an active JIF project in which bi-directional billing for shared resources will not occur: * Eligible Veteran referred to DoD for health care treatment / (ref. VHA OCC DoD Referral Management SOP) * Eligible DoD beneficiaries (including TRICARE beneficiaries) referred to VA for health care treatment * TRICARE authorization not applicable (services are not billed to TRICARE) 2. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 295 field values for NAME field (#.01), SHORT DESCRIPTION field (#.03), and LONG DESCRIPTION field (#.04) are modified as shown below. The plan was originally named VA DOD DIRECT RESOURCE SHARING AGREEMENTS. NAME : VA DOD SHARING MEDICAL RESOURCES PLAN CODE: 295 COVERAGE CODE: DR01001 SHORT DESCRIPTION: SHAGR LONG DESCRIPTION: VA/DoD Health Care Resource Sharing Agreements (38 USC 8111) ------------------------------------------------------------ Patient receiving care at Department of Defense (DoD) under a Health Care Resource Sharing Agreement: * Eligible Veteran referred to DoD for health care treatment / (ref. VHA OCC DoD Referral Management SOP) * TRICARE authorization not applicable (ref. TRICARE Health Plan) / (e.g. dual eligible Veteran elects TRICARE Health Plan vs Veteran benefit * Inactive Reserve and National Guard / Patients potentially enrolled at VAMC (ref VHA Directive 1601A.02)(e.g. VAMC provides annual health screenings or fitness for duty screenings) * If patient has a Veteran status and on Active Duty Orders (ref. Active Duty Health Plan) / Includes active Reserve and National Guard - Federal orders must exceed 30 days 3. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 229 field values for NAME field (#.01), SHORT DESCRIPTION field (#.03), and LONG DESCRIPTION field (#.04) are modified as shown below. The plan was originally named ACTIVE DUTY AND TRICARE SHARING AGREEMENT. NAME : TRICARE PLAN CODE: 229 COVERAGE CODE: AC01001 SHORT DESCRIPTION: TRI LONG DESCRIPTION: TRICARE Health Plan ------------------- Patient receiving care at a VAMC as a TRICARE patient of the Department of Defense: * TRICARE Authorization: - Required for TRICARE Prime patients - Retiree and Retiree Family enrollees - NOT required for TRICARE Select patients - AD Family, Retiree, Retiree Family and Reserve Select enrollees * VA/DoD Health Care Resource Sharing Agreements not applicable (ref. VA/DoD Direct Resource Sharing Agreements) - (e.g. dual eligible Veteran elects Veteran benefit vs TRICARE Health Plan) * If patient has a Veteran status and on Active Duty Orders, then all Active Duty rules apply - Even if treatment is Service Connected - Patient considered TRICARE Prime enrollee - Includes active Reserve and National Guard - Federal orders must exceed 30 days 4. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 300, the field value for the LONG DESCRIPTION field (#.04) is modified as shown below. NAME : VETERAN PLAN CCP RESTRICTED CARE PLAN CODE: 300 COVERAGE CODE: CR01001 SHORT DESCRIPTION: CCP R LONG DESCRIPTION: VHA Profile Veteran Plan CCP Restricted Care is assigned if one of the following eligibilities is met: Not enrolled Covered Veterans who are otherwise entitled to hospital care, medical services, extended care services and community care services, however they are only eligible for care related to their service connected conditions (less than 50% SC, and 0% non-compensable); was discharged or released from active military service for a disability incurred or aggravated in the line of duty for that disability for the 12-month period following discharge or release; Military Sexual Trauma (MST); or Mental Health Other Than Honorable (OTH); as otherwise documented in their record. For COMPACT Act 2020, eligible Individuals are ones who served in the active military service, regardless of length of service, and who were discharged, excluding anyone who received a dishonorable discharge or was discharged or dismissed by reason; are not enrolled in the health care system established by section 1705 of this title; and served in the Armed Forces for a period of more than 100 cumulative days: and was deployed in a theater of combat operations, or while serving in the Armed Forces, was the victim of a physical assault of a sexual nature, a battery of a sexual nature, or sexual harassment. 5. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 226, the field value for the LONG DESCRIPTION field (#.04) is modified as shown below. The wording is corrected in the "Pending; Eligibility Unverified" bulleted item. NAME : APPLICANT IN PROCESS PLAN CODE: 226 COVERAGE CODE: AN01001 SHORT DESCRIPTION: INC LONG DESCRIPTION: Veterans who applied for VA healthcare benefits, but eligibility has not been verified or a final enrollment determination could not be made. . Pending; Means Test Required - Veterans whose Veterans Status has been verified and who have not provided initial Means Test to determine enrollment. . Pending; Purple Heart Unconfirmed - A temporary eligibility for 14 days. . Pending; Other - Enrollment System cannot determine enrollment status. . Pending; No Eligibility Code - Enrollment System cannot determine enrollment status. . Pending - Enrollment System cannot determine enrollment status. . Unverified - Enrollment System cannot determine enrollment status. . Pending; Eligibility Unverified - Veterans who do not have a prior period of enrollment and are still within the 365-day period who have not provided evidence of Veteran status. For Eligible Individuals, under Veterans Comprehensive Prevention, Access to Care, and Treatment Act of 2020 (COMPACT), Section 201, VA will furnish, reimburse, pay for emergent suicide care, make referrals, as appropriate, for care following the period of emergent suicide care. Eligible Individuals are ones who served in the active military service, regardless of length of service, and who were discharged, excluding anyone who received a dishonorable discharge or was discharged or dismissed by reason or while serving in the Armed Forces, was the victim of a physical assault of a sexual nature, a battery of a sexual nature, or sexual harassment. NOTE: The following VHAP modifications are for the Claims Processing and Eligibility (CP&E) project: 6. In the HEALTH BENEFIT PLAN file (#25.11), plan code 139, VETERAN BENEFICIARY PLAN - CAMP LEJEUNE FAMILY, is replaced by the plan shown below. NUMBER: 40 NAME : CAMP LEJEUNE FAMILY PLAN CODE: 306 COVERAGE CODE: CL01001 SHORT DESCRIPTION: CLF LONG DESCRIPTION: The Camp Lejeune Family Member Program (CLFMP) is for family members of Veterans that lived or served at U.S. Marine Corps Base Camp Lejeune, North Carolina, between August 1, 1953, and December 31, 1987, and were potentially exposed to drinking water contaminated with industrial solvents, benzene, and other chemicals. On August 6, 2012, the Honoring America's Veterans and Caring for Camp Lejeune Families Act of 2012 was signed into law. This law (H.R. 1627, now Public Law 112-154) requires the Department of Veterans Affairs (VA) to provide health care to Veterans who served on active duty at Camp Lejeune and to reimburse eligible Camp Lejeune family members for health care costs related to one or more of 15 specified illnesses or medical conditions listed in the law. For more information: https://www.domain.ext/COMMUNITYCARE/programs/dependents/CLFMP.asp 7. Plan code 305, CHAMPVA CAREGIVER is added to the VistA HEALTH BENEFIT PLAN file (#25.11). NUMBER: 96 NAME : CHAMPVA CAREGIVER PLAN CODE: 305 COVERAGE CODE: CV01002 SHORT DESCRIPTION: CHAMPVACG LONG DESCRIPTION: The VHA Office of Community Care (VHA OCC) is responsible for enrolling the eligible Primary Family Caregiver into the Civilian Health and Medical Program of the Department of Veterans Affairs (CHAMPVA) when there is no other health insurance (OHI) coverage, to include TRICARE, Medicare, Medicaid, commercial health plans through employment and individual plans. VHA Office of Community Care is also responsible for processing health care claims for eligible Primary Family Caregivers under CHAMPVA, processing reconsiderations, and providing customer service support to Primary Family Caregivers for questions related to stipend payment and CHAMPVA benefits. For more information: https://www.domain.ext/COMMUNITYCARE/programs/caregiver/index.asp 8. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 108, the field values for NAME field (#.01), SHORT DESCRIPTION field (#.03), and LONG DESCRIPTION field (#.04) are modified as shown below. The plan was originally named BENEFICIARY CHAMPVA. NAME : CHAMPVA STANDARD PLAN CODE: 108 COVERAGE CODE: CV01001 SHORT DESCRIPTION: CHAMPVA LONG DESCRIPTION: The Civilian Health and Medical Program of the Department of Veterans Affairs (CHAMPVA) is a comprehensive health care program in which the VA shares the cost of covered health care services and supplies with eligible beneficiaries. The program is administered by the Veterans Health Administration Office of Community Care (VHA OCC) in Denver, Colorado. CHAMPVA plan provides health care to dependents who may qualify for VA's Civilian Health and Medical Program of the Department of Veteran Affairs (CHAMPVA). They must not have eligibility under TRICARE and must be dependents of a: . Veteran who is rated Permanently and Totally (P&T) disabled due to a Service-connected condition. . Veteran who died from VA rated Service-connected condition, or who, at the time of death, was rated Permanently and Totally disabled. . Veteran who died on active duty and in the line of duty (not due to misconduct). For more information, call 1-800-733-8387 or go to: https://www.domain.ext/COMMUNITYCARE/programs/dependents/champva/index.asp 9. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 109, the field value for the LONG DESCRIPTION field (#.04) is modified as shown below. NAME : BENEFICIARY SPINA BIFIDA PLAN CODE: 109 COVERAGE CODE: SB01001 SHORT DESCRIPTION: SB LONG DESCRIPTION: Spina Bifida (SB) Plan provides monetary allowances, vocational training and rehabilitation, and VA-financed health care benefits to certain Korean and Vietnam Veterans' birth children who have been diagnosed with spina bifida. For the purpose of the program, spina bifida is defined as all forms or manifestations of spina bifida (except spina bifida occulta). The Veterans Health Administration Office of Community Care (VHA OCC) in Denver, CO, manages the SB Health Care Benefits Program, including authorization of benefits and the subsequent processing and payment of health care claims after a determination of eligibility has been made by the Denver VA Regional Office (VARO). For more information, call 1-888-820-1756 or go to: https://www.domain.ext/COMMUNITYCARE/programs/dependents/spinabifida/index.as p 10. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 110, the field value for the LONG DESCRIPTION field (#.04) is modified as shown below. NAME : BENEFICIARY CHILDREN OF WOMEN OF VIETNAM VETERANS PLAN CODE: 110 COVERAGE CODE: CW01001 SHORT DESCRIPTION: CWVV LONG DESCRIPTION: Children of Women Vietnam Veterans (CWVV) Plan provides "NEEDED CARE" to an eligible child, such health care as the Secretary determines is needed by the child for that child's covered birth defects or any disability that is associated with those birth defects. (38 USC 1811-1816) For more information: https://www.domain.ext/COMMUNITYCARE/programs/dependents/cwvv/index.asp 11. In the HEALTH BENEFIT PLAN file (#25.11), VHAP plan code 122, the field value for the LONG DESCRIPTION field (#.04) is modified as shown below. NAME : VETERAN FOREIGN MEDICAL PROGRAM PLAN CODE: 122 COVERAGE CODE: FM01001 INACTIVE: NO SHORT DESCRIPTION: FMP LONG DESCRIPTION: Foreign Medical Program Plan provides pay for medical services for treating your service-connected disabilities, or any disability that is associated with and aggravates a service-connected disability if you live or travel outside the United States. This program will also reimburse you for certain treatment of medical services while you are outside the United States, if needed as part of your VA-approved vocational rehabilitation program. If you are living or planning to travel outside the U.S. (other than in the Philippines), you need to register with VA's Foreign Medical Program office, P.O. Box 469061, Denver, CO 80246-9061, USA: telephone 303-331-7590. For information, visit: https://www.domain.ext/COMMUNITYCARE/programs/veterans/fmp/index.asp ************************************************************************** SECTION 3: REGISTRATION SCREEN UPDATES ************************************************************************** 1. At the SELF-REPORTED REGISTRATION ONLY REASON: prompt, the following new reasons are available when registering a new Veteran in Register A Patient [DG REGISTER PATIENT] and Enter A Request/Notification [FBCH ENTER REQUEST] options: 4TH MISSION, CLINICAL EVALUATION, HUD-VASH and IMMUNIZATIONS. 2. At the SELF-REPORTED REGISTRATION ONLY REASON: prompt, the following new reasons are available when registering a new non-veteran in Register A Patient [DG REGISTER PATIENT] and Enter A Request/ Notification [FBCH ENTER REQUEST] options: 4TH MISSION, HUD-VASH and IMMUNIZATIONS. 3. At the SELF-REPORTED REGISTRATION ONLY REASON: prompt, the following new reasons are available in the Collateral Patient Register [DG COLLATERAL PATIENT] option: 4TH MISSION and IMMUNIZATIONS. 4. The EMERGENCY CONTACT DATA, SCREEN <3> screen is updated to add the Relation Type prompts and to rename the RELATIONSHIP TO PATIENT prompts to Relation Note: ** BEGIN SCREEN CAPTURE ** EMERGENCY CONTACT DATA, SCREEN <3> DGPatient,ONE (PREFERRED NAME) MON DD,YYYY ###-##-#### NSC VETERAN ========================================================================== [1] NOK: DGNOK,ONE [2] NOK-2: DGNOK,TWO Relation Type: STEPCHILD Relation Type: GRANDCHILD Relation Note: PRIMARY NOK Relation Note: DEPLOYED 200 S ANY ST 200 S ANY ST ANY CITY,MI ##### 211 UNITED STATES ANY CITY,MI ##### UNITED STATES Phone: ########## Phone: UNANSWERED Work Phone: UNANSWERED Work Phone: UNANSWERED [3] E-Cont.: DGEC,ONE [4] E2-Cont.: DGEC,TWO Relation Type: STEPCHILD Relation Type: GRANDCHILD Relation Note: LIVES OVERSEAS Relation Note: GRANDCHILD 100 S ANY ST 300 S ANY ST 100 S ANY ST 300 S ANY ST ANY CITY,ST ##### 322 UNITED STATES ANY CITY,ST ##### UNITED STATES Phone: UNANSWERED Phone: UNANSWERED Work Phone: UNANSWERED Work Phone: UNANSWERED [5] Designee: DGDESIGNEE,ONE Relation Type: CHILD-IN-LAW 342 ANY ST Relation Note: POWER OF ATTORNEY ANY CITY,ST ##### UNITED STATES Phone: ########## Work Phone: UNANSWERED to CONTINUE, 1-5 or ALL to EDIT, ^N for screen N or '^' to QUIT: ** END SCREEN CAPTURE ** 4. When the Emergency Contact Name is changed, the RELATION NOTE field is updated to match what is in RELATIONSHIP TYPE field: ** BEGIN SCREEN CAPTURE ** E2-NAME OF SECONDARY CONTACT: DGEC,TWO// E2-RELATION TYPE: GRANDCHILD// 3 DAUGHTER **The E2-RELATION NOTE field is changed from DEPLOYED to DAUGHTER** E2-RELATION NOTE: DAUGHTER// ** END SCREEN CAPTURE ** 5. The DG PATIENT INQUIRY option is updated to add the "Relation Type:" and change the Emergency Contact labels to "Relation Note:" ** BEGIN SCREEN CAPTURE ** DGPatient,ONE;(PREFERRED NAME) ###-##-#### MON DD,YYYY ========================================================================== Emergency Contact Information: E-Cont.: RELATED,PERSON E2-Cont.: WIFE,SECONDARY Relation Type: NIECE/NEPHEW Relation Type: WIFE Relation Note: OVERSEAS Relation Note: HEALTHCARE PROXY 100 S ANY ST 300 S ANY ST 322 ANY CITY, ST ##### ANY CITY, ST ##### UNITED STATES UNITED STATES Phone: UNSPECIFIED Phone: UNSPECIFIED Work Phone: UNSPECIFIED Work Phone: UNSPECIFIED VHA Profiles Currently Assigned to Veteran: None ** END SCREEN CAPTURE ** ************************************************************************** SECTION 4: HL7 ZCT SEGMENT UPDATE ************************************************************************** The HL7 VA Specific Emergency Contact Segment (ZCT) is updated with a new sequence (#11) CONTACT RELATIONSHIP TYPE. There are five possible contacts in a patient record. Each contact has a Relationship Type field. The five Relationship Type fields for each contact are listed below. (See section 1 item 3 above for details on these five fields.) Any contact defined in the patient record has a corresponding ZCT segment in the HL7-ORF/ORU Z07 message. Sequence #11 contains the Relationship Type value for that contact. Refer to the IVM*2.0*204 patch description for information on the modifications to the Z07 message. - K-RELATIONSHIP TYPE field (#.224) - K2-RELATIONSHIP TYPE field (#.2104) - E-RELATIONSHIP TYPE field (#.3309) - E2-RELATIONSHIP TYPE field (#.331015) - D-RELATIONSHIP TYPE field (#.34015) ************************************************************************** SECTION 5: VADPT API & ICR MODIFICATIONS ************************************************************************** 1. The DGRR GET PATIENT SERVICES DATA Remote Procedure Call (RPC) is modified with the addition of the field "RelationshipType" to the ContactInfo structure. This field contains, for each contact type, the corresponding relationship type field (K-RELATIONSHIP TYPE field (#.224), or K2-RELATIONSHIP TYPE field (#.2104), or E-RELATIONSHIP TYPE field (#.3309), or E2-RELATIONSHIP TYPE field (#.331015), or D-RELATIONSHIP TYPE field (#.34015)). The external value of the field is returned. 2. The VADPT ICR#10061 is modified to add the new RELATION TYPE field to the OAD component. It replaces the RELATIONSHIP TO PATIENT in the tenth (10th) node of the output array. RELATIONSHIP TO PATIENT is moved from the 10th node to the new twelfth (12th) node of the output array. Please see the PIMS Technical Manual for details. Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT CONTACT RELATION NUMBER (#.01) NEW (#12.11) NAME (#.02) NEW ACTIVE? (#.03) NEW PATIENT (#2) K-RELATIONSHIP TYPE (#.224) NEW K2-RELATIONSHIP TYPE NEW (#.2104) E-RELATIONSHIP TYPE NEW (#.3309) E2-RELATIONSHIP TYPE NEW (#.331015) D-RELATIONSHIP TYPE NEW (#.34015) K-RELATIONSHIP TO PATIENT MODIFIED (#.212) K2-RELATIONSHIP TO PATIENT MODIFIED (#.2192) E-RELATIONSHIP TO PATIENT MODIFIED (#.332) E2-RELATIONSHIP TO PATIENT MODIFIED (#.3312) D-RELATIONSHIP TO PATIENT MODIFIED (#.342) RELIGIOUS PREFERENCE (#.08) MODIFIED RACE INFORMATION (#2.02) RACE INFORMATION (#.01) MODIFIED ETHNICITY INFORMATION ETHNICITY INFORMATION MODIFIED (#2.06) (#.01) Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- DGRR GET PATIENT SERVICES DATA MODIFIED Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- DG PATCH DG*5.3*1067 ACTIVE NEW DG UAM API KEY MODIFIED Additional Information: ----------------------- New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. Jira VES-18014: UAM - Edit DG UAM API Key in FileMan Problem: -------- The DG UAM API KEY parameter stored in the PARAMETER DEFINITION file (#8989.51) can be edited in FileMan. Resolution: ----------- The PROHIBIT EDITING field in the DG UAM API KEY parameter stored in the PARAMETER DEFINITION file (#8989.51) is set to "Yes" to prevent a user from modifying the value stored in this parameter. 2. Jira VES-17777: Applicant in Process VHAP minor Description update needed Problem: -------- The LONG DESCRIPTION field (#.04) of the APPLICANT IN PROCESS VHAP in the HEALTH BENEFIT PLAN file (#25.11) is incorrectly worded. Resolution: ----------- The wording "and have provided" in the description is corrected to "who have not provided" as shown below. . Pending; Eligibility Unverified - Veterans who do not have a prior period of enrollment and are still within the 365-day period who have not provided evidence of Veteran status. Test Sites: ----------- VA New Jersey Healthcare System, East Orange & Lyons, NJ Michael E. DeBakey VA Medical Center, Houston, TX Alaska VA Healthcare System, Anchorage, AK Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/DG_53_P1067.KID Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. Documentation Title File Name --------------------------------------------------------------------- DG_53_P1067.KID Release Notes DG_5_3_P1067_RN.PDF User Manual Version 5.3 - Registration Menu PIMS_REG_UM.PDF PIMS Version 5.3 Technical Manual PIMS_TM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- The pre-install routine PRE^DG531067P renames four VHAPs. All other VHAP modifications described above are installed from the HEALTH BENEFIT PLAN file (#25.11) included in the build. The routine is automatically deleted once the installation completes. The four plans are: - ACTIVE DUTY AND TRICARE SHARING AGREEMENT is renamed to TRICARE - VA DOD DIRECT RESOURCE SHARING AGREEMENTS is renamed to VA DOD SHARING MEDICAL RESOURCES - BENEFICIARY CHAMPVA is renamed to CHAMPVA STANDARD - VETERAN BENEFICIARY PLAN - CAMP LEJEUNE FAMILY is renamed to CAMP LEJEUNE FAMILY The post-install routine POST^DG531067P creates an instance of the DG PATCH DG*5.3*1067 ACTIVE parameter definition in the PARAMETER file (#8989.5) and sets it to a value of "Feb 26, 2022@1700". The post-install routine also sets the PROHIBIT EDITING field in the DG UAM API KEY parameter stored in the PARAMETER DEFINITION file (#8989.51) to "Yes" to prevent a user from modifying the value stored in this parameter. The routine is automatically deleted once the installation completes. The post-install also recompiles any Input Templates associated with the fields that were modified by the patch. Patch IVM*2.0*204, included in the Host file for this build, contains a pre-install routine, PRE^IVM20204P, which deletes entries from the IVM DEMOGRAPHIC UPLOAD FIELDS file (#301.92) for the NOK processing. Updated entries are installed from the patch. This routine must be manually deleted upon successful patch installation. See the Post-Installation Instructions section below. Pre-Installation Instructions: ------------------------------ This patch may be installed with users on the system, although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. It should NOT be installed while the IVM BACKGROUND JOB [IVM BACKGROUND JOB] is running. 1. The IVM BACKGROUND JOB [IVM BACKGROUND JOB] should be unscheduled. Use the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TaskMan Management [XUTM MGR] menu. Note the currently scheduled date/time. 2. The HL7 incoming/outgoing filers should be stopped. Stop All Messaging Background Processes by using the [HL STOP ALL] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. The following is a list of menu options to disable: Option Name Menu Text ------------------------------ --------------------------- Register a Patient [DG REGISTER PATIENT] Load/Edit Patient Data [DG LOAD PATIENT DATA] Preregister a Patient [DGPRE PRE-REGISTER OPTION] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Patient Inquiry [DG PATIENT INQUIRY] View Registration Data [DG REGISTRATION VIEW] IVM Upload Menu [IVM UPLOAD MENU] Enter A Request/Notification [FBCH ENTER REQUEST] Installation Instructions: 1. Use the Load a Distribution option contained on the Kernel Installation & Distribution System Menu [XPD MAIN] to load the Host file. When prompted to "Enter a Host File:" enter /srv/vista/patches/SOFTWARE/DG_53_P1067.KID 2. From the Kernel Installation & Distribution System Menu [XPD MAIN], select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME, enter the patch DG*5.3*1067. NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global. ii. At the Select INSTALL NAME prompt, enter DG*5.3*1067. iii. At the Subject prompt after the subject name, press Enter to accept the default. iv. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// Press Enter to select Build v. When prompted for Enter a Host File:, enter the path and name for the host file backup file. If you don't specify a directory, the default directory of HFS Primary Directory will be used. C. When prompted for Header Comment:, press enter to accept the default value. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO. ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', answer YES. a. When prompted 'Enter options you wish to mark as 'Out Of Order':', select the following option: Option Name Menu Text ------------------------------ --------------------------- Register a Patient [DG REGISTER PATIENT] Load/Edit Patient Data [DG LOAD PATIENT DATA] Preregister a Patient [DGPRE PRE-REGISTER OPTION] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Patient Inquiry [DG PATIENT INQUIRY] View Registration Data [DG REGISTRATION VIEW] IVM Upload Menu [IVM UPLOAD MENU] Enter A Request/Notification [FBCH ENTER REQUEST] Press the Enter key when you are done selecting options. b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. When prompted 'Delay Install (Minutes): (0 - 60): 0//', answer 0. Post-Installation Instructions: ------------------------------- The HL7 incoming filers should be restarted. Use the Restart/Start All Links and Filers [HL TASK RESTART] option on the Filer and Link Management Options [HL MENU FILER LINK MGT] menu on the HL7 Main Menu [HL MAIN MENU]. The IVM BACKGROUND JOB [IVM BACKGROUND JOB] should be rescheduled. Use the Schedule/Unschedule Options [XUTM SCHEDULE] option on the TaskMan Management [XUTM MGR] menu and enter the scheduled date/time that was noted in the Pre-Installation instruction section above. The pre-installation routine IVM20204P should be manually deleted from your system using the KERNEL option Delete Routines [XTRDEL]. Back-Out/Roll Back Plan: ------------------------ In the event a site/patch installer determines that this patch should be backed out, the site/patch installer should submit a YOUR IT Services ticket with the Enterprise Service Desk (ESD) for assistance with the procedure. Any issues would need to be evaluated to determine if: a back-out of the software is appropriate; a new patch is needed; or if data requires correction or restoration. During installation, if the option Backup a Transport Global [XPD BACKUP] was run as directed, either the entire build or routines will be available for restoration should the need arise. If only the routines were backed up, they will be available in a MailMan message with a subject similar to the following: "Subject: Backup of DG*5.3*1067, IVM*2.0*204 on Jan 27, 2021." For multi-builds, if the full build was backed up, the backup will be available in the Host File specified during the backup process. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 19 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DG531067P Before: n/a After: B41053164 **1067** Routine Name: DGDDC Before: B9576741 After: B9931209 **489,244,527,700,673,997,1067** Routine Name: DGDDDTTM Before: B8431744 After: B8629835 **665,653,688,754,941,997,1067** Routine Name: DGREG Before:B206081713 After:B217762062 **1,32,108,147,149,182,245,250, 513,425,533,574,563,624,658, 864,886,915,926,1024,993,1040, 1027,1045,1067** Routine Name: DGRP3 Before: B7640767 After: B25723602 **997*1067** Routine Name: DGRPD1 Before: B19740990 After: B23428127 **703,730,688,863,935,985,997,1067** Routine Name: DGRPE Before:B109773175 After:B118339416 **32,114,139,169,175,247,190, 343,397,342,454,415,489,506, 244,547,522,528,555,508,451, 626,638,624,677,672,702,689, 735,688,797,842,865,871,887, 941,985,997,1014,1040,1044,1056, 1067** Routine Name: DGRRPSKN Before: B10519494 After: B11934523 **557,1067** Routine Name: VADPT1 Before: B68594806 After: B70654177 **415,489,516,614,688,754,887, 941,1059,1067** Routine Name: VAFHLZCT Before: B10401035 After: B11784897 **68,653,754,997,1067** Routine list of preceding patches: 557, 1045, 1056, 1059 ============================================================================= User Information: Entered By : Date Entered : OCT 26, 2021 Completed By: Date Completed: FEB 18, 2022 Released By : Date Released : FEB 22, 2022 ============================================================================= Packman Mail Message: ===================== No routines included