$TXT Created by MORTON,RANDY at DEV.ISC-DALLAS.VA.GOV  (KIDS) on THURSDAY, 05/11/00 at 14:09
=============================================================================
Run Date: MAY 19, 2000                     Designation: LA*5.2*53
Package : LA - AUTOMATED LAB INSTRUMENTS     Priority: Mandatory
Version : 5.2        SEQ #36                    Status: Released
=============================================================================


Subject: CONVERT CAREVUE PACKAGE FROM CLASS III TO CLASS I SOFTWARE

Category: 
  - Routine
  - Data Dictionary

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

 This patch to the Laboratory package does not contain any changes to the
 VISTA BLOOD BANK Software as defined by VHA DIRECTIVE 99-053 titled VISTA
 BLOOD BANK SOFTWARE.
  
 This patch should be installed prior to installing patch LR*5.2*254.
  
 *NOTE*  All sites SHOULD install this patch even if site does not have
         or does not plan to use CareVue instrumentation.
  
  
 This patch will install the CareVue interface package under the Namespace
 LA7D as a Class I national patch.
  
 1. Problem: Current CareVue interface is Class III software.
  
    Solution: The code has been validated, brought up to national
              standard and released as a Class I national patch.
  
  
 An interface engine must exist to connect CareVue (or other clinical
 system) and Vista using TCP/IP and HL7 messages.  Three possible contacts
 for this interface engine are STC, Inc., MSI Solutions Inc. and Agilent
 Technologies.
  
 STC, Inc. can be contacted at:
       Richard Garcia
       voice: 626.471.6000 x6755
       fax:   626.471.6104
       email: rmg@stc.com
  
 MSI Solutions, Inc. can be contacted at:
       Bob Kelliher
       voice: 678.256.4505
       fax:   678.256.4677
       email: bob.kelliher@msi-solutions.com
  
 Agilent Technologies can be contacted at:
       Linda Vanderhulst
       voice: 847.342.2521
       email: linda_vanderhulst@agilent.com
  
  
 About this software:
 ====================
 1.   An option to enter/delete supported wards for the FOREIGN
      INTERFACE file(#62.487) is exported with this version of the patch.
  
     **NOTE** 
        All wards in the hospital location file (#44) that will be
        used for the CareVue interface must have a UNIQUE abbreviation for
        each ward (Inactive and Active)
  
 2.  Resulting from this installation, the entries DHCP CARELIFE and 
     MRTS CARELIFE will automatically be added to the HL7 APPLICATION 
     PARAMETER file(#771). These entries will be used to send HL7 messages
     to the CareVue system.  These parameters also need to be edited to 
     enter your facility name.
    
 3.  The following file is included in this release.  It is in the LA7D
     namespace, also listed in the main installation procedure:
  
             File #62.487 File name FOREIGN INTERFACE
  
 4.  The following mail group will be automatically added to the MAIL
     GROUP file(#3.8) during this installation:  CARELIFE RESULT ERROR
  
 5.  This installation automatically adds the two new protocols to the
     PROTOCOL file(#101).  They are:  LA7D CARELIFE RESULTS
                                      LA7D CARELIFE SERVER
  
 6   The routines exported with this release, listed in the Routines 
     section of this document, are customized to send verified 
     Laboratory data to CareVue for all patients located on a CareVue 
     ward.
  
      
 Associated NOIS
 ===============
 None
  
 Test Sites
 =============== 
 Philadelphia, PA
 Martinsburg, WVA
  
 ROUTINE SUMMARY
 =================
 The following is a list of routines included in this patch. The second
 line of each routine now looks like:
  
 <tab>;;5.2;AUTOMATED LAB INSTRUMENTS;**[patch list]**;Sep 27, 1994
  
                  CHECK^XTSUMBLD Results
   Routine Name    Before Patch      After Patch    Patch List
   ------------    ------------      -----------    ------------
   LA7DVC               NEW             7338732          53
   LA7DVEXT             NEW             5618546          53
   LA7DVM               NEW             6983644          53
   LA7DEDT              NEW             3765930          53
  
  
 CareVue installation manuals
 ============================
 VAMC's are encouraged to use their FTP capability to obtain the
 Documentation PDF files from one of the following OI Field Office's
 ANONYMOUS directories.  
  
     OI FIELD OFFICE       FTP ADDRESS             DIRECTORY
     ===============       ===========             ==========
      HINES               152.129.1.110      [ANONYMOUS.SOFTWARE]
      SALT LAKE CITY      152.131.2.1        [ANONYMOUS.SOFTWARE]
      ALBANY              152.127.1.5        [ANONYMOUS.SOFTWARE]
  
  File names are:                                                  
  
  BINARY FILES
   LA7DIG.PDF  -- CareVue Installation Guide
   LA7DIS.PDF  -- CareVue Interface Specifications
   LA7DTP.PDF  -- CareVue Interface Test Plan
  
 The CareVue interface utilizes VISTA'S Laboratory Test Result system to
 send Observation Request Unsolicited (ORU) messages to the CareVue system.
  The interface messages are based on ward location and passed to an
 interface engine.  When Lab results are verified and the requesting ward
 is identified as having a supported entry in the new CareVue FOREIGN
 INTERFACE file #62.487, the lab results are forwarded, via HL7, to the
 interface engine and then on to the CareVue Clinical Information
 Management System.
  
 Each facility will need to refer to the CareVue Interface Specifications
 Manual, LA7DIS.PDF, as noted above for further requirements regarding
 interface engines.
  
 INSTALLATION INSTRUCTIONS
 ==========================
 The patch is distributed in KIDS format in a PackMan message.
  
 The install time for this patch is less than 2 minutes. This patch can be
 installed when Laboratory users are on the system.
  
 1.   All routines installed with this patch are new to the system and 
      mapping is not recommended.
  
 2.   Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu.      
      This option will load the KIDS patch onto your system.
  
 3.   The patch has now been loaded into a Transport global on your   
      system. You now need to use KIDS to install the transport 
      global.
  
         On the KIDS menu, under the 'Installation' menu, use the
         following options:
            Print Transport Global
            Compare Transport Global to Current System
            Verify Checksums in Transport Global
            Backup a Transport Global
  
 4.   Use the 'Install Package(s)' option under the 'Installation' men
      and select the package 'LA*5.2*53'.  When prompted 'Want to 
      DISABLE Scheduled Options, Menu Options, and Protocols? YES//',  
      choose 'NO'.
  
 5.   At the DEVICE prompt, you can send your output to any printer of
      HFS file, display it on the terminal screen, or queue it to run 
      at a scheduled time.
  
 6.   No options need to be placed out of service.
  
 7.   This installation automatically adds the two new protocols to 
      the PROTOCOL file(#101). They are:  LA7D CARELIFE RESULTS
                                          LA7D CARELIFE SERVER
    
 8.   User will need to enter your facility name in the HL7 
      APPLICATION PARAMETER file(#771).
  
 NOTE:  Fields marked with <-- below need to have information entered.
  
 Select OPTION: ENTER OR EDIT FILE ENTRIES  
 INPUT TO WHAT FILE: FOREIGN INTERFACE// HL7 APPLICATION PARAMETER  
                                           (34 entries)
 EDIT WHICH FIELD: ALL// FACILITY NAME  
 THEN EDIT FIELD: <RET>
 Select HL7 APPLICATION PARAMETER NAME: DHCP CARELIFE    <--   ACTIVE
 FACILITY NAME: 428// 428  <--   enter your facility name here
 Select HL7 APPLICATION PARAMETER NAME: MRTS CARELIFE    <--   ACTIVE
 FACILITY NAME: 642// 428  <--  enter your facility name here
 Select HL7 APPLICATION PARAMETER NAME: <RET>
  
 9.    The new mail group CARELIFE RESULT ERROR was created as part of 
       the installation.  However the entry in the MAIL GROUP file(#3.8)
       is only a stub and requires the site to perform the following edit:
  
 NOTE:  Fields marked with <-- below need to have information entered.
  
 Select MAIL GROUP NAME: CARELIFE RESULT ERROR  
 NAME: CARELIFE RESULT ERROR  Replace 
 Select MEMBER: CROSN,PAM        <--
   Are you adding 'CROSS,PAM' as a new MEMBER (the 1ST for this MAIL
 GROUP)
 ? No// Y (Yes)                  <--
   TYPE: 
 Select MEMBER: <RET>
 DESCRIPTION:
   No existing text
   Edit? NO//  YES _
         All error report for CAREVUE ORU Messages
  
 TYPE: public// PUBLIC           <--
 ORGANIZER: CROSS,PAM            <--
 COORDINATOR: CROSS,PAM          <--
 Select AUTHORIZED SENDER: 
 ALLOW SELF ENROLLMENT?: NO//  NO  <--
 REFERENCE COUNT: <RET>
 LAST REFERENCED:  <RET>
 RESTRICTIONS: INDIV/LOCAL/ORGANIZER// <RET>
 Select MEMBER GROUP NAME: <RET>
 Select REMOTE MEMBER: <RET>
 Select DISTRIBUTION LIST: <RET>
 Select FAX RECIPIENT: <RET>
 Select FAX GROUP: <RET>
  
 Select MAIL GROUP NAME: <RET>
  
 10.  The FOREIGN INTERFACE file(#62.487) was put on the system during the 
      installation process but it does not contain any data.  You 
      must enter your site's data concerning your CareVue wards.
  
 NOTE:  Fields marked with <-- below need to have information entered.
  
 Select MailMan Menu Option: Edit Foreign Interface Parameters  <--
 Enter BEDSIDE MONITOR INTERFACE NAME: CAREVUE  <--
 Enter CAREVUE WARD: ICU         <--   enter your CareVue wards here
 Enter CAREVUE WARD: ADMISSIONS  <--
 Enter CAREVUE WARD: ^
  
     **NOTE** 
        All wards in the hospital location file (#44) that will be
        used for the CareVue interface must have a UNIQUE abbreviation for
        each ward (Inactive and Active)
  
 11.    Set up Logical Link for HL7 parameters.  This will need to contain
        the outgoing device name used from VistA to the interface engine.
        Sites should ensure that entries corresponding to their unique
        system requirements be input at the recommended places.
  
 NOTE:  Fields marked with <-- below need to have information entered.
  
 Select Systems Manager Menu Option:  HL7 Main Menu
  
 Select HL7 Main Menu Option:  V1.6 OPTIONS
  
 Slect V1.6 OPTIONS Option:  Interface Workbench
 At the bottom of the screen you will see:
  
 Select Tool: Jump to Next App// SL   Show Logical Links
 Select Tool: Jump to Next Link// CL  Create Logical Link
  
 Select HL LOGICAL LINK NODE:  VOICE1   <--
  
 Logical Link information
 ------------------------
 Queue Size:  245             <--
 LLP Parameter:  HLLP         <--
  
 LLP Parameters
 --------------
 LLP Type:  HLLP              <--
 Device: OG_LAB_PROD          <--  this will be your device name
 Version ID: 2.3              <--
 Block Size: 245              <--
 Read Timeout: 30             <--
 ACK Timeout: 2               <--
 Re-transmission Attempts: 3  <--
 Start Block Character: <RET>
 End Block Character: <RET>
  
 Select HL LOGICAL LINK NODE:  VOICE1   <--
  
 Select Tool: Jump to Next Link// ^
  
 NOTE:  Add the Logical Link just created to the LA7D CARELIFE
        RESULTS protocol.
  
 NOTE:  Fields marked with <-- below need to have information entered.
  
 Select OPTION: ENTER OR EDIT FILE ENTRIES  
  
 INPUT TO WHAT FILE: PROTOCOL// PROTOCOL  <--  (3569 entries)
 EDIT WHICH FIELD: ALL// NAME             <--
 THEN EDIT FIELD: LOGICAL LINK            <--
 THEN EDIT FIELD: 
  
 Select PROTOCOL NAME: LA7D CARELIFE RESULTS <--
      This client is tied to the MRTS CARELIFE entry
 NAME: LA7D CARELIFE RESULTS  Replace <RET>
 LOGICAL LINK: OG_LAB_PROD    <--  Enter your Logical Link that was set up
  
 12.  Follow the Interface Specifications Manual, LA7DIS.PDF,
      for interface engine requirements.
  
 13.  Follow the CareVue Test Plan Manual, LA7DTP.PDF, to test the CareVue
      package.

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

=============================================================================
User Information:                               
Entered By  : MORTON,RANDY                   Date Entered : JAN 10, 2000
Completed By: DEVLIN,MARK J                Date Completed: MAY 19, 2000
Released By : LECLAIR,RAY                   Date Released : MAY 19, 2000
=============================================================================


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

$END TXT