Select DATA DICTIONARY UTILITY OPTION:
=============================================================================
Run Date: AUG 08, 2005                     Designation: PSN*4*101
Package : PSN - NATIONAL DRUG FILE            Priority: Mandatory
Version : 4        SEQ #94                      Status: Released
                  Compliance Date: AUG 22, 2005
=============================================================================

Associated patches: (v)XU*8*299    <<= must be installed BEFORE `PSN*4*101'
                    (v)XT*7.3*93   <<= must be installed BEFORE `PSN*4*101'
                    (v)PSN*4*99    <<= must be installed BEFORE `PSN*4*101'

Subject: PHARMACY DATA STANDARDIZATION

Category: 
  - Enhancement (Mandatory)
  - Routine
  - Data Dictionary

Description:
============

 
 This patch does not affect any Pharmacy functionality or end-users.
 This patch requires the HEALTH DATA & INFORMATICS (HDI) 1.0 package in
 addition to required patch release checks.
  
 The scope of Data Standardization - Pharmacy enhancement project is to
 modify the VISTA Pharmacy National Drug File (NDF) structures in order to
 meet the established standards for elements required by Data Standardization
 to implement a common set of standards for Clinical Health Data Repository
 (CHDR) and the Health Data Repository (HDR).
 To accomplish data standardization with VISTA Pharmacy and data flow to CHDR
 and HDR a Veterans Health Administration Unique Identifier (VUID) and the
 TERMSTATUS subscript Effective Date/Status will be populated in four files
 within the VISTA Pharmacy National Drug File package. VUID numbers will be
 generated dynamically and programmatically for each product. The VUID
 numbers have been assigned to National Drug File with a predetermined range
 (4000624- 4500623). There will be a one time conversion to update the
 National Drug File package files. Once the Application Patch (PSN*4*101) and
 the VUID data have been installed in the four Globals for the Data Domain
 (NDF), the Application Post-install routine calls an API in the HDI package
 to update the VUID Seeding Process as Complete.
  
 This KIDS Build will only install ONCE in a Production UCI.
  
 Sites with Class III BCMA software must test their functionality PRIOR
 to installing this patch. Data Standardization DOES NOT check against
 Class III contingency plan.
  
 The four VISTA Pharmacy files being "standardized" are: 
  
    VA PRODUCT file (#50.68)
    DRUG INGREDIENTS file (#50.416)
    VA DRUG CLASS file (#50.605)
    VA GENERIC file (#50.6)
  
 Associated NOIS:
 ================
 N/A
  
 Test Sites:
 ===========
 Cheyenne, WY
 Heartland-East HCS
 Martinsburg, WV
  
 Routine Summary:
 ================
  
 The following routines are included in this patch.
  
 The second line of this routine reads:
  
  <tab>;;4.0; NATIONAL DRUG FILE;**[patch list]**; 30 Oct 98
  
              CHECK^XTSUMBLD results
  
 Routine Name          Before Patch           After Patch      Patch List
 ============          ============           ===========      ==========
 PSNVUID               N/A                    4667539          101
 PSNPREDS              N/A                    2297905          101
  
  
   Documentation Retrieval:
   ========================
   Sites may retrieve documentation in one of the following ways:
   
   (1) The preferred method is to FTP the files from
   download.vista.med.va.gov, which will transmit the files from the first
   available FTP server.
   
   (2) Sites may also elect to retrieve documentation directly
   from a specific server as follows:
   
   Albany          ftp.fo-albany.med.va.gov
   Hines           ftp.fo-hines.med.va.gov
   Salt Lake City  ftp.fo-slc.med.va.gov
   
   The documentation includes:
   
   FILE NAME                   DESCRIPTION
   PSN_4_P101_TM_CP.pdf      Technical Manual (change pages)
   PSN_4_TM_R0805.pdf        Technical Manual (updated)
   
   Once released, documentation may be retrieved from VISTA Documentation
   Library (VDL) on the Internet at the following address,
   http://www.va.gov/vdl  
 Installation Instructions:
 ==========================
  
 ****************************NOTE**********************************
  
 There is no conflict between this patch and the CoreFLS software.
 Installation of this patch by the CoreFLS sites will not cause any
 problems.
 ******************************************************************
  
 Installation Instructions and Software Retrieval:
 =================================================
 The data for these files (#50.68, #50.6, #50.416, #50.605) is provided via
 the file PSN4P101.KID and is not included in this patch distribution.
  
 This patch and documentation can be obtained from the ANONYMOUS.SOFTWARE
 directory at one of the OI Field Offices.  The preferred method is to FTP
 the file from DOWNLOAD.VISTA.MED.VA.GOV, which will transmit the file from
 the first available server.  Alternatively, sites may elect to retrieve 
 the file from a specific OI Field Office.
  
    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 City      FTP.FO-SLC.MED.VA.GOV          anonymous.software
  
  
 The software distribution includes:
  
  FILE NAME             DESCRIPTION                BLOCK SIZE
  
 PSN4P101.KID            KIDS Build                4174/4209 blocks 
   
 Installation takes less than five minutes.  This patch should be installed
 during non-peak requirement hours. No options need to be placed out of order.
  
  
 The environment check routine for this patch checks that the patch has 
 not been installed in a Production UCI before and that the HDI 1.0
 package has been installed.
  
 1.  Follow this procedure for EACH of the four "standardized" files:
     VA PRODUCT file (#50.68), DRUG INGREDIENTS file (#50.416), VA DRUG
     CLASS file (#50.605), VA GENERIC file (#50.6).
  
     This example is a representative example of your results, but is NOT
     intended to be an exact example of results. Results will vary from site
     to site. From Programmer Mode:
  
     D P^DI
  
  
     VA FileMan 22.0
  
     Select OPTION: DATA DICTIONARY UTILITIES
     Select DATA DICTIONARY UTILITY OPTION: CHECK/FIX DD STRUCTURE
  
     Check the Data Dictionary.
     Note: Messages that begin with an asterisk(*) can NOT be corrected and
     will need careful evaluation by software development!
  
      START WITH WHAT FILE: DRUG INGREDIENTS//
           GO TO WHAT FILE: DRUG INGREDIENTS//
     Remove erroneous nodes? NO// YES
     DEVICE// ;;999 GENERIC INCOMING TELNET
  
  
     Checking file 50.416
          *File: 50.416 Index: "APS" has duplicate Fields.
                          Field  .01  Field 2
          File: 521030 is missing.
               ^DD(50.416,0,"PT",521030) was killed.
          File: 521030.6814 is missing.
               ^DD(50.416,0,"PT",521030.6814) was killed.
          File: 521033 is missing.
               ^DD(50.416,0,"PT",521033) was killed.
          File: 521037 is missing.
               ^DD(50.416,0,"PT",521037) was killed.
         Checking subfile 50.4161
         Returning to main file 50.416.
         Checking subfile 50.4169
         Returning to main file 50.416.
  
  
     Select DATA DICTIONARY UTILITY OPTION:
  
  (Run the same option a second time for the same file. Make sure all the
  (missing file messages are gone and it has run clean.)
  
     Select DATA DICTIONARY UTILITY OPTION: CHECK/FIX DD STRUCTURE
  
     Check the Data Dictionary.
     Note: Messages that begin with an asterisk(*) can NOT be corrected and
     will need careful evaluation by software development!
  
      START WITH WHAT FILE: DRUG INGREDIENTS//
           GO TO WHAT FILE: DRUG INGREDIENTS//
     Remove erroneous nodes? NO// <return>
     DEVICE// ;;999 GENERIC INCOMING TELNET
  
     Checking file 50.416
          *File: 50.416 Index: "APS" has duplicate Fields.
                          Field  .01  Field 2
         Checking subfile 50.4161
         Returning to main file 50.416.
         Checking subfile 50.4169
         Returning to main file 50.416.
  
     Select DATA DICTIONARY UTILITY OPTION:
  
  Repeat this procedure for each of the files:
     VA PRODUCT file (#50.68), DRUG INGREDIENTS file (#50.416), VA DRUG
     CLASS file (#50.605), VA GENERIC file (#50.6).
  
 2.  Retrieve the file PSN4P101.KID using one of the methods described
     above.
  
 3.  All components of this patch are new, so there are no mapping issues.
  
 4.  From the Kernel Installation & Distribution System menu, select
     the Installation menu.
  
 5.  From this menu, select the option Load a Distribution and select
     PSN4P101.KID. You will be displayed the message, "Build has an
     Environmental Check Routine". Then you are prompted, "Want to RUN the
     Environmental Check Routine? YES//". respond YES.
     "Will first run the Environmental Check Routine, PSNPREDS"
  
 6.  From this menu, you may choose to use the option Verify Checksums in
     Transport Global.  When prompted, select PSN*4.0*101. All components of
     this patch are new, so the option Backup a Transport Global and
     the option Compare Transport Global to Current System do not have
     to be invoked.
  
 7.  Use the Install Package(s) option and select PSN*4.0*101.
  
 8.  When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//"
     respond NO.
  
 9.  When prompted "Want to DISABLE Scheduled Options, Menu Options, and
     Protocols? YES//" respond NO.                      

Routine Information:
====================

Routine Name:
  - PSNPREDS


Routine Checksum:

Routine Name:
  - PSNVUID


Routine Checksum:

=============================================================================
User Information:
Entered By  : ALEXANDER,DAVID               Date Entered  : FEB 17, 2005
Completed By: DAVIS,DOUG                    Date Completed: AUG 05, 2005
Released By : BARRON,LUANNE                 Date Released : AUG 08, 2005
=============================================================================


Packman Mail Message:
=====================