$TXT Created by ELLZEY,LINDA J at DEVVII.FO-ALBANY.MED.VA.GOV (KIDS) on Friday, 03/10/06 at 10:23 ============================================================================= Run Date: JUN 28, 2006 Designation: PSS*1*92 Package : PSS - PHARMACY DATA MANAGEMENT Priority: Mandatory Version : 1 SEQ #102 Status: Released Compliance Date: JUL 29, 2006 ============================================================================= Associated patches: (v)IB*2*260 <<= must be installed BEFORE `PSS*1*92' (v)PSS*1*91 <<= must be installed BEFORE `PSS*1*92' Subject: PATIENT FINANCIAL SERVICES SYSTEM (PFSS) SUPPORT Category: - Routine - Input Template - Enhancement (Mandatory) - Data Dictionary Description: ============ This Pharmacy Data Management (PDM) patch is part of the Patient Financial Services System (PFSS) project. PFSS patches are being released on various schedules. Some patch functionality will not be active until a new PFSS switch is activated during final implementation. PFSS will initially be implemented at select pilot sites ONLY. The purpose of the PFSS project is to prepare the Veterans Health Information Systems and Technology Architecture (VistA) environment for the implementation of a Commercial-Off-The-Shelf (COTS) billing replacement system. The project consists of the implementation of the billing replacement system, business process improvements, and enhancements to VistA to support integration with the COTS billing replacement system. Significant changes to VistA legacy systems and ancillary packages are necessary. Some of the PFSS software components are not operational until the PFSS On/Off Switch, distributed with patch IB*2*260, is set to "ON". The ability for the local site to set the switch to "ON" will be provided at the appropriate time with the release of a subsequent Integrated Billing patch. For more information about the PFSS project, review the documentation accompanying this patch and refer to the following website: http://vista.med.va.gov/billreplace/. Functional Description: ====================== The Charge Description Master (CDM) is an industry standard financial tool common to all commercial billing systems and used in virtually every private hospital. The CDM is a comprehensive listing of all services performed, drugs supplied, or supplies provided in a particular hospital along with the value of those services, drugs, items, or charge amounts. Each of these entries are represented by a Charge Code, and the Charge Code is made up of a Department Code and Service Code. The Charge Code for Pharmacy will be the Department Code 160 concatenated with the assigned Service Code for the drug. The Department Code 160 will not be stored in any files and the Service Code will be established or approved by a central CDM Change Control Board (CCB). The implementation of the COTS billing system requires the VA PRODUCT file (#50.68) or the DRUG file (#50) to link the service master Service Code to every Pharmacy prescription fill or refill. For drugs that are not associated with an entry in the VA PRODUCT file (#50.68), the approved Service Code must be populated by the user. Technical Description: ====================== This PDM patch PSS*1*92 provides the following functionality needed to support the PFSS project: 1. A new SERVICE CODE field (#400) was added to the DRUG file (#50). 2. The PSSCOMMON input template was modified to accommodate the new SERVICE CODE field (#400) to be used with the Drug Enter/Edit [PSS DRUG ENTER/EDIT] option for drugs that are not associated with an entry in the VA PRODUCT file (#50.68). 3. The Integration Agreement (IA) #4533 was modified to include the new SERVICE CODE field (#400). Associated New Service Request (NSR): ===================================== N/A Associated Remedy Ticket(s): ============================ N/A Associated E3Rs: ================ N/A Test Sites: =========== CLEVELAND, OH DAYTON, OH BOSTON HCS, MA TUSCALOOSA, AL Routine Summary: ================ The following routines are included in this patch. The second line now reads as follows: ;;1.0;PHARMACY DATA MANAGEMENT;**[patch list]**;9/30/97 CHECK^XTSUMBLD results: Routine Before Patch After Patch Patch List ------------------------------------------------------------ PSS50A 17217232 17658727 85,91,92 PSS50DAT 14468122 14548209 85,92 Total number of routines modified: 2 File Summary: ============= UP SEND DATA DATE SEC. COMES SITE RSLV FILE # NAME DD CODE W/FILE DATA PTS -------------------------------------------------------------------- 50 DRUG YES NO NO Field Summary: ============== Field Name (Number) File Name (Number) ------------------- ------------------ SERVICE CODE (#400) DRUG (#50) Template Summary: ================= Template Name Type File Name (Number) ------------- ----- -------------------------- PSSCOMMON INPUT DRUG (#50) Documentation Retrieval: ======================== The PFSS documentation is available on the ANONYMOUS.SOFTWARE directory at one of the following Office of Information (OI) Field Offices. 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 distribution includes: FILE NAME DESCRIPTION PSN_4_103_PSS_1_92_RN.PDF Release Notes PSN_4_103_PSS_1_92_IG.PDF Install Guide PSS_1_P92_UM_CP.PDF User Manual Change Pages (3) Documentation can also be retrieved from VistA Documentation Library (VDL) on the Internet at the following address, http://www.va.gov/vdl. Installation Instructions: ========================== Do not install this patch when Pharmacy Data Management users are on the system. Installation will take no longer than 3 minutes. Suggested time to install: non-peak requirement hours. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. Review your mapped set. If the routines are mapped, they should be removed from the mapped set at this time. 3. From the Kernel Installation & Distribution System menu, select the Installation menu. 4. From this menu, you may select to use the following options (when prompted for INSTALL NAME, enter PSS*1.0*92): a. Backup a Transport Global - this option will create a backup message of any routines exported with the patch. It will NOT backup any other changes such as DDs or templates. b. Compare Transport Global to Current System - this option will allow you to view all changes that will be made when the patch is installed. It compares all components of the patch (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - this option will ensure the integrity of the routines that are in the transport global. 5. Use the Install Package(s) option and select the package PSS*1.0*92. 6. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//" respond NO. 7. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//" respond NO. 8. If any routines were unmapped as part of step 2, they should be returned to the mapped set once the installation has run to completion. Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSS50A Before: B28870400 After: B30585085 **85,91,92** Routine Name: PSS50DAT Before: B33121603 After: B33215766 **85,92** ============================================================================= User Information: Entered By : ANWER,MOHAMED Date Entered : MAR 14, 2005 Completed By: LYNCH,MARY F. Date Completed: JUN 27, 2006 Released By : CONSENTINO,ALBERT Date Released : JUN 28, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT