============================================================================= Run Date: DEC 02, 2020 Designation: DG*5.3*1014 Package : DG - REGISTRATION Priority: Mandatory Version : 5.3 SEQ #897 Status: Released Compliance Date: DEC 16, 2020 ============================================================================= Associated patches: (v)DG*5.3*567 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*890 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*966 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*996 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*997 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*1006 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*1010 <<= must be installed BEFORE `DG*5.3*1014' (v)DG*5.3*1031 <<= must be installed BEFORE `DG*5.3*1014' Subject: PREFERRED NAME, ADDRESS VALIDATION, CCP, MEANS TEST ADJUDICATION Category: - Routine - Enhancement (Mandatory) - Data Dictionary - Other Description: ============ !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT: The deployment will be a simultaneous rollout on December 2, 2020 with a compliance period of 10 business days. In order to expose the Community Care Collateral information for processing, all sites must complete the installation by December 16, 2020. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Veterans Health Information Systems and Technology Architecture (VistA) Registration, Eligibility & Enrollment (REE) patch DG*5.3*1014 is being released to support the enhancements for the Enterprise Health Benefits Determination (EHBD) program that focuses on updates for the Enrollment System Modernization (ESM) Phase 3 project. Patch DG*5.3*1014 is also being released in support of the Enrollment System (ES) 5.13 release. Refer to Informational Patch EAS*1*193 (Enrollment Application System) for additional details regarding the ES release. NOTE: DG*5.3*1014 is being released with IVM*2.0*194 in Host File DG_53_P1014.KID. Patch DG*5.3*1014 modifies the output of the patient lookup when the user is prompted for the patient name. The PREFERRED NAME (#.2405) field is displayed after the NAME (#.01) field of the PATIENT (#2) file after the prompt's response. The change will also be visible in downstream application options that have prompts for the NAME (#.01) field of the PATIENT (#2) file. Patch DG*5.3*1014 standardizes the patient data displayed on the VistA Registration screens and sub-screens banner. The patient data will occupy two separate lines in the banner. In addition, DG*5.3*1014 makes minor changes to the PATIENT DEMOGRAPHIC DATA, SCREEN <1> screen, PATIENT DATA, SCREEN <2> screen, and MILITARY SERVICE DATA, SCREEN <6> screen in order to accommodate the additional line of patient data in the banner. Patch DG*5.3*1014 includes validation of the patient Permanent, Residential, and Confidential Addresses by invoking the Universal Addressing Module (UAM) Address Validation Service. The UAM Address Validation Service is a Representational State Transfer (REST) Application Program Interface (API) web service that matches input addresses to addresses in the United States Postal Service (USPS) database in order to correct postal information. The service returns a list of valid addresses for the input given. The UAM Address Validation Service requires the necessary Secure Sockets Layer (SSL) configuration used by the UAM Service be set up. This set up is described in informational patch XOBW*1*6. Refer to the DG_53_P1014.KID Deployment, Back-out, and Rollback Guide for information on verifying the SSL configuration setup. All VistA entry points where these addresses can be entered or updated are modified to invoke the validation service. Once the address has been entered, the UAM service is invoked and the address is validated. A new screen is added to display the addresses from which the user can select. The UAM Address Validation web server DG UAM AV SERVER and two services, DG UAM AV VALIDATE and DG UAM AV CANDIDATE, are configured by a post-install routine. This routine creates entries in the HWSC configuration files to define these. It may be necessary to change the server name and/or port number for the production connection. Refer to the DG_53_P1014.KID Deployment, Installation, Back-out, and Rollback Guide for instructions on the post installation steps for setting the server and port. ************************************************************************* NOTE: When running the ^XINDEX routine, sites will encounter an XINDEX Error after the installation of this patch. Routine DGUAMWS uses HealtheVet Web Services Client (HWSC). It calls a Cache Class to parse the eXtensible Markup Language (XML) document returned by the web service call. A Department of Veterans Affairs Cache Programming Standards and Conventions (SAC) Exemption (ID 20200806-01) was approved on 08/06/2020. ************************************************************************* The errors reported by XINDEX are: DGUAMWS * * 198 Lines, 11474 Bytes, Checksum: B105727101 S DGHTTPREQ.SSLCheckServerIdentity = 0 EN+24 S - Vendor specific code is restricted. EN+24 F - Unrecognized argument in SET command. EN+24 F - UNDEFINED COMMAND (rest of line not checked). D DGHTTPREQ.EntityBody.Write(DGJSON) ; places the entire json string into EntityBody EN+28 S - Vendor specific code is restricted. F DGHEADER="Accept","ContentType" D DGHTTPREQ.SetHeader(DGHEADER,"application/json") EN+29 S - Vendor specific code is restricted. D DGHTTPREQ.SetHeader("ContentType","application/json") EN+30 S - Vendor specific code is restricted. S DGHTTPRESP=DGHTTPREQ.HttpResponse EN+35 S - Vendor specific code is restricted. S DGDATA=DGHTTPRESP.Data.ReadLine() ; reads json string response from the data stream. EN+36 S - Vendor specific code is restricted. Q DGSTAT_"^"_$$RSPMSG(DGHTTPRESP.StatusCode,.DGRESPMSG) EN+44 S - Vendor specific code is restricted. N DGERRCODE S DGERRCODE=DGRESPERR.code ERRRSPMSG+4 S - Vendor specific code is restricted. ************************************************************************* NOTE: The VistA REE group received a temporary SAC exemption for the VistA production behavior of the timeout when the user is entering address data in the ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1> screen, Residential Address, Data Group [1], Permanent Mailing Address Data Group [2], Temporary Mailing Address Data Group [3], and Confidential Mailing Address Data Group [4], which are not conforming with the following SAC standard: "The program must return to the Menu Manager with no more than one intervening read when a user input READ command times out if the argument of the read is in any way evaluated by the application. A timeout at the menu level must halt through H^XUS." This temporary SAC exemption number is 20201202-01. ************************************************************************* Patch DG*5.3*1014 updates VistA to remove the consistency check/business rule that requires entry of "property information" on the Net Worth screen, as well as removing the Net Worth screen itself from the Means Test process. Additionally, this update will result in VistA no longer evaluating the combined value of Veteran income and net worth at a value above $80,000, thus eliminating the "Do you wish to send this case to adjudication?" prompt. The menu options affected are: Add a New Means Test [DG MEANS TEST ADD], Complete a Required Means Test [DG MEANS TEST COMPLETE], and Edit an Existing Means Test [DG MEANS TEST EDIT]. Patch DG*5.3*1014 will not execute the business rule that requires entry of "property information" when a Veteran's income results in a Means Test status of "MT COPAY EXEMPT". Patch DG*5.3*1014 will not execute the business rule that evaluates the sum of the Veteran's income and "property information" against the THRESHOLD PROPERTY field (#8) of the MEANS TEST DATA multiple (#43.03) of the MAS PARAMETERS file (#43) for the income year of the Means Test. DG*5.3*1014 for Community Care Program (CCP) adds five new fields to the COMMUNITY CARE PROGRAM (#2.191) sub-file in the PATIENT (#2) file: CCP LAST UPDATED DATE (#.01), COMMUNITY CARE PROGRAM CODE (#1), EFFECTIVE DATE (#2), END DATE (#3), and ARCHIVE (#4). DG*5.3*1014 updates Health Level Seven (HL7) message structures for the ORU/ORF-Z11 and ORU/ORF-Z07 by adding the new ZCE segment and five new fields listed in order of position: ELEMENT NAME SET ID, CCP LAST UPDATED DATE, COMMUNITY CARE PROGRAM CODE, EFFECTIVE DATE, and END DATE. DG*5.3*1014 updates the ADDITIONAL ELIGIBILITY VERIFICATION DATA, SCREEN <11.5> to add the label of "Community Care Program (CCP) Collateral Data" as DATA GROUP [2]. Listing of Updates: =================== This patch includes the following enhancements to VistA REE: PART ONE: PREFERRED NAME ------------------------ 1. The patient lookup now displays the PREFERRED NAME (#.2405) field in parenthesis after the NAME (#.01) field of the PATIENT (#2) file whenever the PREFERRED NAME (#.2405) field is populated. The change will also be visible in downstream application options that have prompts for the NAME (#.01) field of the PATIENT (#2) file. * BEGIN SCREEN CAPTURE * Select PATIENT NAME: DGPATIENT,ONE (DGPREFERRED NAME) XX-XX-XX XXXXXXXXX NO NSC VETERAN Enrollment Priority: GROUP 3 Category: IN PROCESS End Date: Press ENTER to continue * END SCREEN CAPTURE * 2. Patient data is standardized on VistA Registration screens 1 - 15, including the sub-screen banners and the "Checking data for consistency..." screen. The following screens are updated: PATIENT DEMOGRAPHIC DATA, SCREEN <1> ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1> PATIENT DATA, SCREEN <2> EMERGENCY CONTACT DATA, SCREEN <3> APPLICANT/SPOUSE EMPLOYMENT DATA, SCREEN <4> INSURANCE DATA, SCREEN <5> MILITARY SERVICE DATA, SCREEN <6> MILITARY SERVICE DATA, SCREEN <6> GROUP [2] Conflict Locations MILITARY SERVICE DATA, SCREEN <6> GROUP [3] Environmental Factors MILITARY SERVICE DATA, SCREEN <6.1> VISTA MILITARY SERVICE DATA, SCREEN <6.2> (View History) ELIGIBILITY STATUS DATA, SCREEN <7> FAMILY DEMOGRAPHIC DATA, SCREEN <8> Expand Dependent INCOME SCREENING DATA, SCREEN <9> INELIGIBLE/MISSING DATA, SCREEN <10> ELIGIBILITY VERIFICATION DATA, SCREEN <11> VHAP <11.1> VHAP <11.3> VHAP <11.3.1> VHAP <11.4> ADDITIONAL ELIGIBILITY VERIFICATION DATA, SCREEN <11.5> Caregiver Data <11.5.1> ADMISSION INFORMATION, SCREEN <12> APPLICATION INFORMATION, SCREEN <13> APPOINTMENT INFORMATION, SCREEN <14> SPONSOR DEMOGRAPHIC INFORMATION, SCREEN <15> Checking data for consistency... a. The patient data is on two lines in the screen's banner. i. The first line contains the NAME (#.01) field in the PATIENT (#2) file, the PREFERRED NAME (#.2405) field in the PATIENT (#2) file in parenthesis when this field is populated, and the DATE OF BIRTH (#.03) field in the PATIENT (#2) file. ii. When the source facility is the Department of Defense (DOD),the second line contains the Electronic Data Interchange Personnel Identifier (EDIPI), which is the SOURCE ID (#11) field in the TREATING FACILITY LIST (#391.91) file, followed by the SOCIAL SECURITY NUMBER (#.09) field in the PATIENT (#2) file, and the TYPE (#391) field in the PATIENT (#2) file. If the EDIPI is blank, the SOCIAL SECURITY NUMBER (#.09) field in the PATIENT (#2) file will be left justified on the second line of the patient data. * BEGIN SCREEN CAPTURE * Military Service May 15, 2020@12:42:24 Page: 1 of 1 MILITARY SERVICE DATA, SCREEN <6.1> DGPATIENT,ONE (DGPREFERRED NAME) MMM DD, CCYY ########### ###-##-####P NSC VETERAN Service Branch/Component Service # Entered Separated Discharge [1] ARMY/REGULAR ####### 03/01/2010 02/29/2016 HONORABLE Enter ?? for more actions AD Add DE Delete ED Edit VH View History Select Action:Quit// * END SCREEN CAPTURE * * BEGIN SCREEN CAPTURE * Checking data for consistency... ===> 9 inconsistencies found in 0 seconds... ===> 9 inconsistencies filed in 0 seconds... DGPATIENT,ONE (DGPREFERRED NAME) MMM DD, YYYY ########### ###-##-####P NSC VETERAN ========================================================================== 6 - RELIGION UNSPECIFIED 8 - ADDRESS DATA INCOMPLETE 13 - POS UNSPECIFIED+ 14 - ELIG CODE UNSPECIFIED 53 - EMPLOYMENT STATUS UNANSWERED 62 - EMERGENCY CONTACT NAME MISSING 64 - POB CITY/STATE MISSING 65 - MOTHER'S MAIDEN NAME MISSING 99 - CAN'T PROCESS FURTHER Inconsistencies followed by [+] will prevent a Z07 DO YOU WANT TO UPDATE THESE INCONSISTENCIES NOW? Yes// * END SCREEN CAPTURE * 3. On the PATIENT DEMOGRAPHIC DATA, SCREEN <1> screen, the Language Date/Time: and the Preferred Language: prompts in DATA GROUP [5] labels are shortened and are moved to the same line: * BEGIN SCREEN CAPTURE * PATIENT DEMOGRAPHIC DATA, SCREEN <1> DGPATIENT,ONE (DGPREFERRED NAME) MMM DD, YYYY ########### ###-##-####P NSC VETERAN ========================================================================== [1] Name: DGPATIENT,ONE [6] Preferred Name: PREFERRED NAME DOB: MMM DD, YYYY SS: ###-##-####P PSSN Reason: No SSN Assigned Family: DGPATIENT Birth Sex: FEMALE MBI: Given: ONE [2] Alias: Middle: EZ Prefix: DR Suffix: Degree: Self-Identified Gender Identity: TRANSFEMALE/TRANSWOMAN/MALE-TO-FEMALE [3] Remarks: NO REMARKS ENTERED FOR THIS PATIENT [4] Cell Phone: ###-###-#### Pager #: UNANSWERED Email Address: DGPATIENT@TESTING.COM [5] Pref Lang: SPANISH Date/Time: FEB 4,2020@12:30 to CONTINUE, 1-6 or ALL to EDIT, ^N for screen N or '^' to QUIT: * END SCREEN CAPTURE * 4. On the PATIENT DATA, SCREEN <2> screen, the dashes under the Previous Care Date and Location of Previous Care labels in DATA GROUP [2] are removed. * BEGIN SCREEN CAPTURE * PATIENT DATA, SCREEN <2> DGPATIENT,ONE (DGPREFERRED NAME) MMM DD, YYYY ########### ###-##-####P NSC VETERAN ========================================================================== [1] Marital: MARRIED POB: UNANSWERED Religion: UNANSWERED Father: UNANSWERED SCI: UNANSWERED Mother: UNANSWERED Mom's Maiden: UNANSWERED [2] Previous Care Date Location of Previous Care NONE INDICATED NONE INDICATED [3] Ethnicity: UNANSWERED Race: UNANSWERED <4> Date of Death Information Date of Death: Source of Notification: Updated Date/Time: Last Edited By: [5] Emergency Response: to CONTINUE, 1,2,3,5 or ALL to EDIT, ^N for screen N or '^' to QUIT: * END SCREEN CAPTURE * 5. The blank line between the GROUP [1] Service Branch/Component and GROUP [2] Conflict Locations: on the MILITARY SERVICE DATA, SCREEN <6> screen is removed: * BEGIN SCREEN CAPTURE * MILITARY SERVICE DATA, SCREEN <6> DGPATIENT,ONE (DGPREFERRED NAME) MMM DD, YYYY ########### ###-##-####P NSC VETERAN ========================================================================== [1] Service Branch/Component Service # Entered Separated Discharge ------------------------ --------- ------- --------- --------- ARMY/REGULAR ####### 03/01/2010 02/29/2016 HONORABLE [2] Conflict Locations: Gulf War(07/01/2010-07/01/2011) [3] Environment Factors: (4) N/T Radium (VERIFIED) [4] POW: UNK From: To: War: [5] Combat: From: To: Loc: [6] Mil Disab Retirement: NO Dischrg Due to Disab: [7] Dent Inj: Teeth Extracted: <8> Purple Heart: NO <9> Medal of Honor: Award Date: Status Date: MOH Copayment Exemption Date: to CONTINUE, 1-7 or ALL to EDIT, ^N for screen N or '^' to QUIT: * END SCREEN CAPTURE * PART TWO: UAM ADDRESS VALIDATION -------------------------------- 1. The modifications described below for validating the Permanent, Residential, and Confidential Addresses apply to the following: a. Load/Edit Patient Data [DG LOAD PATIENT DATA] option - When the user is prompted to edit the Permanent Mailing Address before editing the patient data. b. ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1> screen - The Permanent, Residential, and Confidential Addresses are entered and edited in this screen. This screen is used in the following options: Load/Edit Patient Data [DG LOAD PATIENT DATA] Preregister a Patient [DGPRE PRE-REGISTER OPTION] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Register a Patient [DG REGISTER PATIENT] c. Patient Address Update [DG ADDRESS UPDATE] option - When editing the Permanent Mailing Address. 2. The process for editing addresses on the VistA REE ADDITIONAL PATIENT DEMOGRAPHIC DATA, SCREEN <1.1> screen is modified as follows: a. Entering or editing the Residential, Permanent, or Confidential Address (GROUPS [1], [2] and [4] respectively) includes an additional verification step to validate the address entered or edited. This process is the UAM Address Validation Service. Note: All data fields in the respective group are entered prior to invoking the Address Validation Service. For Residential Address this includes the Home and Office phone numbers. For Permanent Address this includes the Bad Address Indicator. For Confidential Address this includes the From/To dates, the Phone, and the Categories. b. Prior to invoking the UAM Address Validation Service, the ADDRESS [LINE 1], City, and Zip Code fields are required for domestic addresses. ADDRESS [LINE 1] and City are required for foreign addresses. If any of these fields are missing, the user is redirected to enter the address again and make the corrections. * BEGIN SCREEN CAPTURE * COUNTRY: UNITED STATES// UNITED STATES USA United States STREET ADDRESS [LINE 1]: 123 TEST STREET// 123 TEST STREET STREET ADDRESS [LINE 2]: ZIP+4: 01757// @ CITY: MILFORD// MILFORD BAD ADDRESS INDICATOR: RESIDENTIAL ADDRESS [LINE 1], CITY, and ZIP CODE fields are required. COUNTRY: UNITED STATES// * END SCREEN CAPTURE * c. After entering or editing all the data in the DATA GROUP, the user is prompted to view the updated address prior to invoking the UAM Address Validation Service. The user may re-enter the address to make any corrections or may continue to the validation. * BEGIN SCREEN CAPTURE * COUNTRY: UNITED STATES// UNITED STATES USA United States STREET ADDRESS [LINE 1]: TEST STREET// 123 TEST STREET STREET ADDRESS [LINE 2]: ZIP+4: 01757// 01757 CITY: MILFORD// STATE: MASSACHUSETTS// MASSACHUSETTS Select COUNTY: WORCESTER// 027 BAD ADDRESS INDICATOR: [NEW ADDRESS] 123 TEST STREET MILFORD,MASSACHUSETTS 01757 UNITED STATES County: WORCESTER Bad Addr: If address is ready for validation enter to continue, 'E' to Edit or '^' to quit: * END SCREEN CAPTURE * d. If the UAM Address Validation Service is unable to validate the address, a message is displayed to the user indicating the address could not be validated. They are directed to verify the address that was entered before proceeding to step (f) below. * BEGIN SCREEN CAPTURE * No Results - UAM Address Validation Service is unable to validate the address. Please verify the address entered. Press ENTER to continue: * END SCREEN CAPTURE e. If the UAM Address Validation Service succeeds, the user is taken to the Address Validation <1.2> screen (see number 5 below.) The address selected from that screen is returned. f. Normal processing resumes. For Confidential address, the address is saved to the database. For Permanent and Residential Addresses, the user is shown the previous and updated addresses and can accept or reject the changes. * BEGIN SCREEN CAPTURE * [OLD ADDRESS] TEST STREET MILFORD,MASSACHUSETTS 01757 UNITED STATES County: WORCESTER 027 Bad Addr: [NEW ADDRESS] 123 TEST STREET MILFORD,MASSACHUSETTS 01757 UNITED STATES County: WORCESTER 027 Bad Addr: Are you sure that you want to save the above changes? * END SCREEN CAPTURE * 3. Within the Load/Edit Patient Data [DG LOAD PATIENT DATA] option, the user is prompted to edit the Permanent Address prior to entering into the PATIENT DEMOGRAPHIC DATA, SCREEN <1> screen. * BEGIN SCREEN CAPTURE * DGPATIENT,ONE; XXX-XX-XXXX MAY XX,XXXX ========================================================================== VHA Profiles Currently Assigned to Veteran: None Do you want to edit Patient Data? Yes// (Yes) Permanent Mailing Address: XXXX UNION PL FRISCO,TX 75035 UNITED STATES County: COLLIN (085) Bad Addr: Do you want to edit the Patient's Permanent Mailing Address? * END SCREEN CAPTURE * 4. Patient Address Update [DG ADDRESS UPDATE] option allows the user to edit the Permanent and Temporary Address. Only the Permanent Address is validated by the UAM Address Validation Service. 5. When an address is entered or edited by the user in any of the options described above, that address is passed to the UAM Address Validation Service. The service will return one or more addresses from which the user can select. This list is provided via a new screen, the Address Validation <1.2> screen, described below. a. The address entered by the user is displayed as the first address, with those addresses returned by the UAM Address Validation Service listed below it. * BEGIN SCREEN CAPTURE * Address Validation <1.2> Jun 18, 2020@14:53:44 Page: 1 of 1 DGPATIENT,ONE (JUNIOR) FEB 02, 1912 XXX-XX-XXXX NSC VETERAN __________________________________________________________________________ [1] XXX MAIN STREET CHICAGO,ILLINOIS 60606 UNITED STATES (User Entered Address) [2] XXX MAIN STREET SUITE 200 CHICAGO,ILLINOIS 60606-1234 UNITED STATES Delivery Point: CONFIRMED Confidence Score: 100 __________________________________________________________________________ + Next Screen - Prev Screen ?? More Actions SEL Select Address Select Action:SEL// * END SCREEN CAPTURE * b. For domestic addresses, the UAM Address Validation Service includes a Delivery Point field which is displayed below the address. c. All addresses include a Confidence Score displayed below the address. d. If the user exits the screen, the user-entered address is selected by default. d. The only action available is the SEL action, which allows the user to select one of the addresses from the list. * BEGIN SCREEN CAPTURE * _________________________________________________________________________ + Next Screen - Prev Screen ?? More Actions SEL Select Address Select Action:SEL// Select Address Select Address (1-2): * END SCREEN CAPTURE * 6. The UAM Address Validation Service is a Representational State Transfer (REST) Application Program Interface (API) web service that matches input addresses to addresses in the United States Postal Service (USPS) database in order to correct postal information. a. Candidate Address Web Service (POST Method) - VistA makes use of the Candidate Address Web Service. The service returns a list of valid addresses for the input given. i. Web Service: The web service can be accessed at the following url: https://api.domain.ext/address/v1/candidate ii. Protocol: The web service is a REST API and accepts and returns JSON request/response objects. iii. Response Codes: 200: Successful Request. The response may contain "messages" that could describe warnings or further information. 400: Error. Response will contain a "messages" element that will provide further information on the error. 403: Not authorized. Please verify credentials used in the request. 404: The record you requested to retrieve, or update, could not be found. 429: You have exhausted the approved request quota for this API. This request should be retried after the quota window expires (default 60sec). 500: Error. Response will contain a "messages" element that will provide further information on the error. b. HealtheVet Web Services Client (HWSC) - HWSC acts as an adjunct to the web services client functionality provided in Cache, by leveraging Cache's platform-provided web services client capabilities. An entry is made using the HWSC Web Server Manager (EN^XOBWU) for the server and the web service on that server. c. Consuming the Web Service - HWSC wrapper code is used to consume the web service thereby making use of built-in error detection and error trap triggering. i. HWSC Wrapper Calls // gets client REST request object SET REQUEST=$$GETREST^XOBWLIB("MY REST SERVICE","MY SERVER") // executes HTTP POST method SET REQUEST=$$POST^XOBWLIB(REQUEST,XOBRSCE,XOBERR,XOBFERR) Parameters: XOBREST = instance of xobw.RestRequest class XOBRSCE = resource for HTTP POST method XOBERR = where to store HWSC error object if problem encountered XOBFERR = if error object created, force M/Cache error [1], otherwise return to caller [0] => [optional ; default = 1] ii. JSON Response - Response is stored in the REQUEST. HttpResponse.Data object in JSON format. PART THREE: MEANS TEST PENDING ADJUDICATION ------------------------------------------- 1. VistA is updated to remove the consistency check/business rule that requires entry of "property information" on the Net Worth screen <4> screen, as well as removing the Net Worth screen itself from the Means Test process. * BEGIN SCREEN CAPTURE * DEDUCTIBLE EXPENSES, SCREEN <3> DGPATIENT,ONE XXX-XX-XXXX ANNUAL INCOME FOR 2019 ========================================================================== <1> Total Non-Reimbursed Medical Expenses: $0.00 Adjusted Medical Expenses: $0.00 Funeral and Burial Expenses: - Veteran's Educational Expenses: - <2> Child's Education Expenses: N/A to CONTINUE, ^N for screen N, or '^' to EXIT: Select PATIENT NAME: * END SCREEN CAPTURE * 2. VistA will not execute the business rule that requires entry of "property information" when a Veteran's income results in a Means Test status of "MT COPAY EXEMPT". 3. VistA will not execute the business rule that evaluates the sum of the Veteran's income and "property information" against the THRESHOLD PROPERTY field (#8) of the MEANS TEST DATA multiple (#43.03) of the MAS PARAMETERS file (#43) for the income year of the Means Test. PART FOUR: CCP -------------- 1. The following menu options incorporate the new screens detailed below: Load/Edit Patient Data [DG LOAD PATIENT DATA] Register a Patient [DG REGISTER PATIENT] View Registration Data [DG REGISTRATION VIEW] Eligibility Verification [DG ELIGIBILITY VERIFICATION] ********************************************************************** NOTE: Persons eligible for CCP(s) are collaterals. If the SHOW VERIFICATION SCREEN?(#11) field in the TYPE OF PATIENT (#391) file is set to NO for collateral patient types, then the display of the ELIGIBILITY VERIFICATION DATA,SCREEN <11> and subsequent verification screens is prevented. In order to display CCP information, sites should ensure that the SHOW VERIFICATION SCREEN? (#11) field in the TYPE OF PATIENT (#391) file is set to YES for collateral patient types. ********************************************************************** 2. The ADDITIONAL ELIGIBILITY VERIFICATION DATA, SCREEN <11.5> screen has been updated to add the label of "Community Care Program (CCP) Collateral Data" as GROUP [2]. The first line banner will include: the person's name, the preferred name in parenthesis, the person's date of birth; on the next line of the banner: Member ID, Social Security Number, and Patient Type. * BEGIN SCREEN CAPTURE * ADDITIONAL ELIGIBILITY VERIFICATION DATA, SCREEN <11.5> LASTNAME,FIRSTNAME MIDDLENAME (Preferred Name) JAN 02, 1961 EDIPI XXX-XX-XXXX COLLATERAL ========================================================================== [1] Caregiver Status Data: (WARNING: MPI CONNECTION NOT AVAILABLE - Systems will be updated automatically when MPI is available. No further action needed to update.) [2] Community Care Program (CCP) Collateral Data to CONTINUE, 1-2 or ALL to EDIT, ^N for screen N or '^' to QUIT: * END SCREEN CAPTURE * 3. The new CCP Collateral Data <11.5.2> screen is created. The first line banner will include: the person's name, the preferred name in parenthesis, the person's date of birth; on the next line of the banner: Member ID, Social Security Number, and Patient Type. The screen will also include the field labels and associated data of CCP Name and Effective Date; the descriptions are included below. The new screen will allow a user to add, edit, and remove CCPs from a record. Column Field Label: Description: ------------------- ------------ CCP Name The name of the CCP that the person is eligible for. Four CCPs are available for selection: ART/IVF, NEWBORN, MARRIAGE/FAMILY COUNSELING, and VHA TRANSPLANT PROGRAM. Effective Date The date that the CCP is assigned. The entry shall be used to display the CCPs in descending order. The Date cannot be a future date. If the CCP MARRIAGE/FAMILY COUNSELING or VHA TRANSPLANT PROGRAM has been added more than one time to a record, the Effective Date must be unique; otherwise a dialog will be presented to the user: "Effective Date for this CCP entry must be unique. The Effective Date entered is the same date as a previous entry for a particular CCP." * BEGIN SCREEN CAPTURE * CCP Collateral Data <11.5.2> Jul 02, 2020@12:18:56 Page: 1 of 1 LASTNAME,FIRSTNAME MIDDLENAME (Preferred Name) MMM DD, YYYY EDIPI XXX-XX-XXXX COLLATERAL CCP Name Effective Date _______________________________________________________________________ [1] MARRIAGE/FAMILY COUNSELING JUN 27,2020 [2] MARRIAGE/FAMILY COUNSELING JUN 15,2020 + Next Screen - Prev Screen ?? More Actions AD Add ED Edit RE Remove * END SCREEN CAPTURE * NOTE: This screen is available only when the patent has an eligibility code of COLLATERAL OF VET. This eligibility cannot be removed from the patient record if there are any active CCPs for the patient. 4. Five new fields are added to the COMMUNITY CARE PROGRAM (#2.191) sub-file in the PATIENT (#2) file : FIELD NAME GLOBAL DATA NUMBER TITLE LOCATION TYPE ------------------------------------------------------------------------- 2.191,.01 CCP LAST UPDATED DATE 0;1 DATE/TIME 2.191,1 COMMUNITY CARE PROGRAM CODE 0;2 SET 2.191,2 EFFECTIVE DATE 0;3 DATE/TIME 2.191,3 END DATE 0;4 DATE/TIME 2.191,4 ARCHIVE 0;5 SET 5. A new cross reference record index "ACCCP" is added to the PATIENT (#2) file COMMUNITY CARE PROGRAM (#2.191) sub-file. This cross reference will trigger a Z07 message whenever changes are made to CCP LAST UPDATED DATE (#.01), COMMUNITY CARE PROGRAM CODE (#1), EFFECTIVE DATE (#2) and END DATE (#3) fields through add, delete and edit functionality. 6. Parser routines are added to parse, validate, and store ZCE segment data into the COMMUNITY CARE PROGRAM (#2.191) sub-file in the PATIENT (#2) file. a. If the incoming EFFECTIVE DATE and the COMMUNITY CARE PROGRAM CODE in the ZCE segment match the EFFECTIVE DATE (#2) field in the COMMUNITY CARE PROGRAM (#2.191) sub-file and the COMMUNITY CARE PROGRAM CODE (#1) field in the Community Care Program (#2.191) sub-file and the CCP LAST UPDATED DATE in the ZCE segment are more recent than the CCP LAST UPDATED DATE (#.01) field in the COMMUNITY CARE PROGRAM (#2.191) sub-file, then the END DATE in the ZCE segment is stored in the END DATE (#3) field in the COMMUNITY CARE PROGRAM (#2.191) sub-file. b. If the incoming EFFECTIVE DATE and COMMUNITY CARE PROGRAM CODE in the ZCE segment don't match the EFFECTIVE DATE (#2) field in the COMMUNITY CARE PROGRAM (#2.191) sub-file and the COMMUNITY CARE PROGRAM CODE (#1) field in the COMMUNITY CARE PROGRAM (#2.191) sub-file, then a new CCP record is added to the COMMUNITY CARE PROGRAM (#2.191) sub-file. 7. A ZCE builder routine is added to incorporate the new ZCE segment in the HL7 ORU/ORF-Z07, in which all of the CCP data will be added. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PATIENT (#2) PRIMARY ELIGIBILITY CODE Modified (#.361) PATIENT ELIGIBILITIES ELIGIBILITY (#.01) Modified SUB-FILE (#2.0361) COMMUNITY CARE PROGRAM CCP LAST UPDATED DATE New SUB-FILE (#2.191) (#.01) COMMUNITY CARE PROGRAM New CODE (#1) EFFECTIVE DATE (#2) New END DATE (#3) New ARCHIVE (#4) New INDEX: ACCCP TRIGGER A Z07 ON CCP CHANGES New ACCCP (#1563) RECORD MUMPS IR ACTION Short Descr: TRIGGER A Z07 ON CCP CHANGES Description: This cross reference will trigger a Z07 message whenever changes are made to the Community Care Program. This includes add, changes, and deletes. Set Logic: I ($T(EECHG^DGRPCTRG)'="") D EECHG^DGRPCTRG Kill Logic: I ($T(EECHG^DGRPCTRG)'="") D EECHG^DGRPCTRG X(1): CCP LAST UPDATED DATE (2.191,.01) (forwards) X(2): COMMUNITY CARE PROGRAM CODE (2.191,1) (forwards) X(3): EFFECTIVE DATE (2.191,2) (forwards) X(4): END DATE (2.191,3) (forwards) 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 ------------- -------------------- DGEN ADD VALID 1.2 MENU NEW DGEN ADDR SELECT NEW DGEN CCP MENU NEW DGEN CCP ADD NEW DGEN CCP EDIT NEW DGEN CCP REMOVE NEW Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ----------------- ----- ------------- -------------------- DGEN ADDR VALID LIST N/A NEW DGEN CCP DETAIL LIST N/A NEW DGEN HBP DETAIL LIST N/A MODIFIED DGEN HBP PATIENT LIST N/A MODIFIED DGEN MSDS PATIENT LIST N/A MODIFIED DGEN MSDS PATIENT VIEW LIST N/A MODIFIED DGMT EXPAND PROFILE LIST N/A MODIFIED DGMT DEPENDENTS LIST N/A MODIFIED Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A Additional Information: ----------------------- Blood Bank Team Coordination: ----------------------------- N/A New Service Requests (NSRs): N/A Patient Safety Issues (PSIs): N/A Defect Tracking System Ticket(s) & Overview: N/A Test Sites: ----------- Alaska VA Healthcare System, Anchorage, AK Birmingham VA Health Care System, Birmingham, AL Boise VA Medical Center, Boise, ID VA Connecticut Health Care System (Newington, West Haven), CT Amarillo VA Health Care System, Amarillo, TX 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_P1014.KID Documentation describing the new functionality is included in this release. Documentation can be obtained at https://download.vista.domain.ext/index.html/SOFTWARE. The DG_53_P1014.KID Release Notes and User/Technical Manuals can also be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation Title File Name --------------------------------------------------------------------- DG_53_P1014.KID Release Notes DG_5_3_P1014_RN.PDF User Manual - Registration Menu ADT_PIMS_REG_UM.PDF User Manual - Means Test ADT_MTS_UM.PDF Supervisor Menu PIMS Technical Manual ADT_PIMS_TECH_MANUAL.PDF DG_53_P1014.KID Deployment, Installation DG_5_3_P1014_DIBRG.PDF Back-out, and Rollback Guide Patch Installation: ------------------- Detailed information regarding the setup of the server/services, as well as troubleshooting information should the user see errors in the error trap post installation, can be found in the DG_53_P1014.KID Deployment, Installation, Back-out, and Rollback Guide (DG_5_3_P1014_DIBRG.PDF). Refer to the Software and Documentation Retrieval Instructions section of this patch description. Pre/Post Installation Overview: ------------------------------- The post-install routine, DG531014P, was developed to perform the following actions: - Add HWSC web server DG UAM AV SERVER - Add HWSC web service file entries DG UAM AV CANDIDATE DG UAM AV VALIDATE - Each web service will be assigned a key and the key assignment will be by the 5 regions. - Update DG UAM AV SERVER with the DG UAM AV CANDIDATE and DG UAM AV VALIDATE services - All input templates that reference the following two fields (modified by this patch) will be recompiled: 1. PRIMARY ELIGIBILITY CODE (#.361) field in PATIENT (#2) file. 2. ELIGIBILITY (#.01) field in PATIENT ELIGIBILITIES (#2.0361) subfile of PATIENT (#2) file. NOTE: The post install routine will be deleted after installation by the KIDS build. 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 UAM Address Validation Service requires the necessary SSL configuration used by the UAM Service be set up. This set up is described in informational patch XOBW*1*6. Refer to the DG_53_P1014.KID Deployment, Back-out, and Rollback Guide, Appendix A - XOBW*1.0*6 Patch Description. The instructions in patch XOBW*1.0*6 introduce a new SSL/Transport Layer Security (TLS) configuration by the name of 'encrypt_only_tlsv12' that can be utilized by any application with a HealtheVet Web Services Client (HWSC) Web Server. This new configuration will use the TLSv1.2 protocol. A user with SYSTEM MANAGER access should perform a check to ensure the Encrypt Only configuration is set up correctly and completed. Installation Instructions: -------------------------- 1. Use the Load a Distribution option contained on the Kernel Installation and Distribution System Menu to load the Host file. When prompted to "Enter a Host File:", enter /srv/vista/patches/SOFTWARE/DG_53_P1014.KID 2. From the Kernel Installation and Distribution System Menu, 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*1014. 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 of any routines exported with this patch. It will not backup any other changes such as Data Dictionaries (DDs) or templates. C. 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] View Registration Data [DG REGISTRATION VIEW] Eligibility Verification [DG ELIGIBILITY VERIFICATION] Patient Address Update [DG ADDRESS UPDATE] Add a New Means Test [DG MEANS TEST ADD] Complete a Required Means Test [DG MEANS TEST COMPLETE] Edit an Existing Means Test [DG MEANS TEST EDIT] b. When prompted 'Enter protocols you wish to mark as 'Out Of Order':', press the Enter key. c. If 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 post-install routine for patch DG*5.3*1014 creates entries in the HealtheVet Web Services Client (HWSC) configuration files to support a web service call to DG UAM AV SERVER. To verify that the post-install routine set up the server DG UAM AV SERVER and associated services DG UAM AV CANDIDATE and DG UAM AV VALIDATE correctly, follow the steps shown in the DG_53_P1014.KID Deployment, Installation, Back-out, and Rollback Guide. 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" to back up routines was run as directed, then routines will have the ability to be restored from the "backup" MailMan message that was generated. However, the KIDS installation process does not perform a backup of other VistA software components, such as DD, cross-reference, and template changes. Routine Information: ==================== The second line of each of these routines now looks like: ;;5.3;Registration;**[Patch List]**;Aug 13, 1993;Build 42 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: DG531014P Before: n/a After:B210553470 **1014** Routine Name: DGADDLST Before: n/a After: B24537445 **1014** Routine Name: DGADDVAL Before: n/a After: B11247230 **1014** Routine Name: DGDEP Before: B8540114 After: B9896841 **45,688,1014** Routine Name: DGDEPE Before: B1593923 After: B1701846 **45,1014** Routine Name: DGENA6 Before: B28201721 After: B32233157 **232,327,417,491,513,672,940, 993,1014** Routine Name: DGENUPL1 Before: B70228219 After: B75472345 **147,222,232,314,397,379,407, 363,673,653,688,797,842,894, 871,935,959,975,972,952,996, 1014** Routine Name: DGENUPL7 Before: B49503633 After: B88929469 **232,367,397,417,379,431,513, 628,673,653,742,688,797,871, 972,952,977,993,1014** Routine Name: DGENUPLB Before: B42991940 After: B52239102 **625,763,842,871,952,977,1014** Routine Name: DGLOCK1 Before: B21100838 After: B21838410 **121,314,1014** Routine Name: DGLOCK3 Before: B6374544 After: B10959586 **489,527,688,1014** Routine Name: DGMTSC4 Before: B16569452 After: B29917122 **45,130,456,540,567,1014** Routine Name: DGMTSC4V Before: B18024527 After: B31073713 **688,1014** Routine Name: DGMTSCC Before: B36202206 After: B38385133 **33,45,130,438,332,433,462, 456,610,624,611,890,1014** Routine Name: DGMTSCR Before: B14443251 After: B14897236 **45,688,1014** Routine Name: DGR111 Before: B9538715 After: B9351276 **871,987,985,1006,1014** Routine Name: DGR113 Before: B8398670 After: B8401629 **871,987,1006,1014** Routine Name: DGR1131 Before: B6370840 After: B6876398 **987,1006,1014** Routine Name: DGR114 Before: B6061884 After: B6043455 **871,987,1006,1014** Routine Name: DGREGAED Before: B44758249 After: B62965158 **522,560,658,730,688,808,915, 941,1010,1014** Routine Name: DGREGRED Before: B56848691 After: B77348398 **941,1010,1014** Routine Name: DGREGTED Before: B31206434 After: B65810805 **688,851,941,1014** Routine Name: DGRP1 Before: B40365565 After: B40617641 **109,161,506,244,546,570,629, 638,649,700,653,688,750,851, 907,925,941,985,1014** Routine Name: DGRP1152A Before: n/a After: B63227684 **1014** Routine Name: DGRP1152U Before: n/a After: B20019030 **1014** Routine Name: DGRP11A Before: B8975026 After: B9418502 **997,1014** Routine Name: DGRP11B Before: B13570407 After: B13606123 **997,1014** Routine Name: DGRP2 Before: B12657362 After: B12658951 **415,545,638,677,760,867,1014** Routine Name: DGRP6 Before: B27900055 After: B27897413 **161,247,343,397,342,451,672, 689,797,841,842,947,972,1014** Routine Name: DGRP61 Before: B66671182 After: B67709879 **797,909,935,947,966,1014** Routine Name: DGRP62 Before: B4564085 After: B4633656 **797,1014** Routine Name: DGRP6CL Before: B70196214 After: B77220668 **689,751,764,797,1014** Routine Name: DGRP6EF Before: B28412625 After: B33321348 **689,659,737,688,909,1014** Routine Name: DGRPCF Before: B26225283 After: B29623704 **250,653,786,754,867,935,1014** Routine Name: DGRPE Before: B96981177 After:B104572440 **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** Routine Name: DGRPH Before: B31038182 After: B32305129 **114,343,397,415,489,545,638, 624,689,842,941,985,997,1014** Routine Name: DGRPP Before: B21008815 After: B21625700 **92,147,343,404,397,489,689, 688,828,797,871,997,1014** Routine Name: DGRPU Before:B101794854 After:B123342522 **33,114,489,624,672,689,688, 935,941,997,1014** Routine Name: DGRPV Before: B21234422 After: B21728618 **109,114,247,190,327,365,343, 397,415,489,546,545,451,624, 677,672,689,716,688,797,842, 871,887,941,985,997,1014** Routine Name: DGUAMWS Before: n/a After:B107230386 **1014** Routine Name: DPTLK Before:B140750292 After:B144170705 **32,72,93,73,136,157,197,232, 265,277,223,327,244,513,528, 541,576,600,485,633,629,647, 769,857,876,915,919,993,1031, 1014** Routine Name: VAFHLZCE Before: n/a After: B13475226 **1014** Routine list of preceding patches: 567, 890, 966, 996, 997, 1006, 1010, 1031 ============================================================================= User Information: Entered By : Date Entered : APR 28, 2020 Completed By: Date Completed: DEC 02, 2020 Released By : Date Released : DEC 02, 2020 ============================================================================= Packman Mail Message: ===================== No routines included