$TXT Created by TJERNAGEL,STEVE at MNTVBB.FO-ALBANY.MED.VA.GOV (KIDS) on Thursday, 11/04/10 at 13:16 ============================================================================= Run Date: DEC 15, 2010 Designation: XU*8*548 Package : XU - KERNEL Priority: Mandatory Version : 8 SEQ #444 Status: Released Compliance Date: JAN 15, 2011 ============================================================================= Associated patches: (v)XU*8*528 <<= must be installed BEFORE `XU*8*548' (v)XU*8*549 <<= must be installed BEFORE `XU*8*548' Subject: HIPAA 5010 - NPI CROSSWALK EXTRACT Category: - Routine - Enhancement (Mandatory) Description: ============ **************************************************** ** It is highly important that one reads the ** ** release notes BEFORE installing this patch. ** **************************************************** This patch contains enhancements and modifications relating to the XUS NPI EXTRACT REPORT [XUS NPI EXTRACT] option which is already loaded at the sites. The changes contained in this patch address the following: 1) Create logic to pull the Organization Name and Pay-To Address that appear in the Pay-To Provider loop on X12 claims as viewed from the local facility VistA option "MCCR Site Parameter Display/Edit" [IBJ MCCR SITE PARAMETERS]. 2) Create a field in NPI individual extract data to house the primary taxonomy code. The primary taxonomy code should no longer appear in the current taxonomy code field. The taxonomy code field should carry the practitioner's other taxonomy codes, if they have any. 3) Create a field in the NPI individual extract data to house the practitioner's current status and a second field for the date on which that status began. 4) Ensure that each site sends NPI Crosswalk Extract scheduling and execution messages to the VHA CO NPI EXTRACT MONITORING email group after each extract job is scheduled and subsequently run, respectively. This patch addresses the following New Service Request (NSR): ------------------------------------------------------------- The NSR associated with this patch is out of date with the requirements. Please refer to the Requirements Software Document (RSD) in TSPR for the appropriate requirments. This patch addresses the following Remedy Ticket(s): ---------------------------------------------------- There is no Remedy Ticket associated with this patch. Blood Bank Team Coordination ============================ EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch XU*8*548 contains changes to a package referenced in VHA OI SEPG SOP 192-023 Review of VISTA Patches for Effects on VISTA Blood Bank Software. This patch does not alter or modify any VistA Blood Bank software design safeguards or safety critical elements functions. RISK ANALYSIS: Changes made by patch XU*8*548 have no effect on Blood Bank software functionality, therefore RISK is none. Test Sites: ----------- Heartland-West HCS Upstate NY HCS Loma Linda Documentation Retrieval ----------------------- The release notes may also be retrieved from the following OI Field Offices' Anonymous.Software Directories. Use the appropriate FTP capability to retrieve the files and use BINARY format. OI Field Office FTP Address Directory --------------- ----------- --------- ALBANY ftp.fo-albany.med.va.gov anonymous.software HINES ftp.fo-hines.med.va.gov anonymous.software SALT LAKE ftp.fo-slc.med.va.gov anonymous.software FIRST AVAILABLE SERVER download.vista.med.va.gov anonymous.software File Name --------- XU_80_P548_RN.pdf ================INSTALLATION INSTRUCTIONS ================= **************************************************************** **************************************************************** ** ** ** PLEASE NOTE ** ** ** ** THIS PATCH HAS POST INSTALLATION STEPS ** ** WHICH MUST BE COMPLETED FOR THIS PATCH ** ** TO FUNCTION PROPERLY ** ** ** **************************************************************** **************************************************************** It is recommended that this patch be installed outside of normal working hours, however, if installed during the normal workday, other VistA users will not be affected. Users ARE allowed to be on the system during the installation except for those options listed below. It is recommended that the patch be installed during non-peak time. It will take less than five minutes to install the patch, but you may queue the installation if you wish. You DO NOT need to stop TaskMan or the background filers. Install Time - less than 5 minutes. 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. Enter message action (in IN basket): Ignore// x Xtract KIDS Select PackMan function: INSTALL/CHECK MESSAGE 2. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: INStallation Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global Select Installation Option: 3. Select Installation Option: --------------------------- NOTE: The following are OPTIONAL - (When prompted for the INSTALL NAME, enter XU*8.0*548): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. b. 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 components of this patch (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. Select Installation Option: Install Package(s) ------------------ **This is the step to start the installation of this KIDS patch: a. Choose the Install Package(s) option to start the patch install. b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO. c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//' answer NO ************** POST-INSTALLATION INSTRUCTIONS ************** There is no post installation routine associated with this patch; however there are several manual post-installation steps associated with this patch. The purpose of these instructions is to make sure that your system is configured properly for this NPI Crosswalk Extract so that it will run every time the CBO requests it via the NPI Administration web site. The Chief Business Office schedules an NPI Crosswalk Extract report periodically (typically once a month) from all Veteran's Administration provider sites. The scheduling of this report is done via the VA NPI Crosswalk Extract Administration web site using HL7 messages. The NPI Crosswalk Extract process is automated and runs in the background at each site. Once the NPI Crosswalk Extract has been requested by the VA NPI Crosswalk Extract Administration web site, each site responds with an acknowledgement that it has received the request. When the extract is actually scheduled in TaskMan, a second acknowledgement message is sent to the web site stating that the report has actually been scheduled. This same process occurs when the VA NPI Crosswalk Extract Administration web site cancels the extract. Finally, once the NPI Crosswalk has been run, three final messages are sent. The first message is an acknowledgement to the web site that the extract was indeed run. The second message, which is sent via Mailman, is a summary message about the extract. The final message, also sent via Mailman, is the actual NPI Crosswalk Extract. For this process to work correctly several requirements must be met: 1. The NPI EXTRACT VERIFICATION mail group must be defined and correctly configured. The most common problem is that the REMOTE MEMBER address is not present or is incorrectly typed. The correct configuration is: NPI EXTRACT VERIFICATION TYPE: public ALLOW SELF ENROLLMENT: NO REFERENCE COUNT: 65 LAST REFERENCED: JUN 01, 2010 RESTRICTIONS: UNRESTRICTED MEMBER: XXXXX,XXXXXX DESCRIPTION: Members of this mail group will automatically receive an email verification entry for each NPI Extract file that has been generated at the sites. ORGANIZER: POSTMASTER REMOTE MEMBER: vhaconpiextractmonitoring@VA.GOV The remote member MUST be entered exactly as shown above. **************************************************************** *** *** *** Common mistake: The remote member is NOT entered into *** *** the system correctly. It usually *** *** misspelled or not defined. *** *** *** **************************************************************** 2. The Q-NPS.VA.GOV domain must exist and defined as: Select DOMAIN NAME: Q-NPS.VA.GOV NUMBER: 579 NAME: Q-NPS.VA.GOV FLAGS: NS RELAY DOMAIN: FOC-AUSTIN.VA.GOV DHCP ROUTING INDICATOR: NPS DISABLE TURN COMMAND: YES LEVEL 1 NAME (c): GOV LEVEL 2 NAME (c): VA.GOV LEVEL 3 NAME (c): Q-NPS.VA.GOV LEVEL 4 NAME (c): Q-NPS.VA.GOV 3. The VA.GOV domain must be defined and allowed to send messages: This is just an example. *************************************************************** *** *** *** The DOMAIN NAME and LEVEL 4 NAME should NOT be VISN2's *** *** VO2.MED.VA.GOV unless you are VISN 2. *** *** *** *** The common mistake for the domain is that VA.GOV is not *** *** defined or allowed to send messages. This is needed so *** *** that the remote member in Post-Installation step 1 above ** *** may receive mail messages. This group recieves an *** *** important email that CBO relies on. *** *** *** *************************************************************** OUTPUT FROM WHAT FILE: // DOMAIN (600 entries) Select DOMAIN NAME: YOUR SITE NUMBER: 94 NAME: V02.MED.VA.GOV FLAGS: NS MCTS ROUTING INDICATOR: DIM STATION: xxx DHCP ROUTING INDICATOR: DOR TRANSMISSION SCRIPT: TCP/IP PRIORITY: 1 NUMBER OF ATTEMPTS: 5 TYPE: Simple Mail Transfer Protocol PHYSICAL LINK / DEVICE: NULL DEVICE NETWORK ADDRESS (MAILMAN HOST): xx.xx.xx.xx TEXT: O H=V02.MED.VA.GOV,P=TCP/IP-MAILMAN C TCPCHAN-SOCKET25 NOTES: SYNONYM: XXXXXXXX SYNONYM: VA.GOV LEVEL 1 NAME (c): GOV LEVEL 2 NAME (c): VA.GOV LEVEL 3 NAME (c): MED.VA.GOV LEVEL 4 NAME (c): V02.MED.VA.GOV 4. The logical link NPI OUT must exist and be configured as follows: Select HL LOGICAL LINK NODE: NPI OUT ANOTHER ONE: STANDARD CAPTIONED OUTPUT? Yes// Y (Yes) Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number (IEN) LLP TYPE: TCP AUTOSTART: Enabled QUEUE SIZE: 10 RE-TRANSMISSION ATTEMPTS: 3 READ TIMEOUT: 27 ACK TIMEOUT: 270 TCP/IP ADDRESS: 00.00.00.00 TCP/IP PORT: 8090 TCP/IP SERVICE TYPE: CLIENT (SENDER) PERSISTENT: NO RETENTION: 50 SAY HELO: NO NOTE: the IP address MUST be populated and the AUTOSTART field MUST be enabled. The IP address shown is NOT a valid IP address for your site. It should point to your local VIE. **************************************************************** *** *** *** Common mistake: The HL LOGIGAL LINK does not have the *** *** AUTOSTART field set to "Enabled". *** *** *** **************************************************************** Routine Information: ==================== The second line of each of these routines now looks like: ;;8.0;KERNEL;**[Patch List]**; Jul 10, 1995;Build 24 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: XUSNPIX1 Before: B78458745 After:B172188323 **438,452,453,481,528,548** Routine Name: XUSNPIX2 Before: B90700763 After: B99916076 **438,452,453,481,548** Routine Name: XUSNPIX3 Before: B20621795 After: B23716384 **438,452,453,481,548** Routine Name: XUSNPIX4 Before: B75484055 After: B99303079 **438,452,453,481,528,548** Routine Name: XUSNPIX5 Before: B15950901 After: B15963770 **453,481,548** Routine Name: XUSNPIXU Before: B16989884 After: B28263362 **438,453,528,548** Routine list of preceding patches: 528 ============================================================================= User Information: Entered By : WHITE,DARLENE Date Entered : JUN 04, 2010 Completed By: NULL,RODGER Date Completed: DEC 15, 2010 Released By : TILLIS,LEWIS Date Released : DEC 15, 2010 ============================================================================= Packman Mail Message: ===================== $END TXT