$TXT Created by MENDOZA,RAUL at PAT-XWB.FO-OAKLAND.MED.VA.GOV (KIDS) on MONDAY, 08/26/02 at 14:56 ============================================================================= Run Date: OCT 17, 2002 Designation: XWB*1.1*28 Package : XWB - RPC BROKER Priority: Mandatory Version : 1.1 SEQ #25 Status: Released ============================================================================= Subject: M2M Broker Category: - Routine Description: ============ Associated Patches: XT*7.3*58 <<= must be installed BEFORE `XWB*1.1*28' XU*8.0*225 <<= **ONLY FOR CACHE SITES** must be installed BEFORE `XWB*1.1*28' XU*8.0*238 <<= must be installed BEFORE `XWB*1.1*28' DESCRIPTION =========== The M-to-M Broker provides a new implementation of the RPC Broker enabling the exchange of VISTA M-based data and business rules between two VISTA M servers, where both servers reside on the same, or on different VISTA M systems. It has been developed to provide Client/Server functionality resident solely within the VISTA environment. The requesting server functions in the capacity of a "client." The server receiving that request functions in the capacity of a "server." The Client/Server roles of each server can change depending on at what point in time each VISTA M server is making the request for data from it's counterpart VISTA M server. The requesting server and the receiving server can reside on the same, or on different VISTA M systems. All M-to-M Broker client and server routines are packaged in one KIDS build. This build will need to be installed on each VISTA system required for M-to-M Broker processing. Further information is provided in a separate document, "M-to-M BROKER Supplemental Documentation, Patch XWB*1.1*28" This document can be obtained by using FTP from the appropriate Customer Service directory: OI FIELD OFFICE FTP ADDRESS DIRECTORY ====================================================== Albany 10.1.19.5 (ftp.fo-albany.med.va.gov) Hines 10.3.29.201 (ftp.fo-chicago.med.va.gov) Salt Lake City 152.131.2.1 (ftp.fo-slc.med.va.gov) Host File Name: XWB1_1P28SP.PDF This document can also be downloaded from the Infrastructure Documentation center web page: http://vista.med.va.gov/vdl/#App128 Background ========== VISTA Imaging requested the development of the M-to-M Broker to be used to communicate between the M client on the VISTA Imaging Digital Imaging and Communications in Medicine (DICOM) Gateway and the M server on the main VISTA Hospital Information System. The VISTA Imaging DICOM Gateway architecture uses M software on a workstation to create associations between newly acquired images and the computerized patient record. Previous to the development of the M-to-M Broker, the gateway system communicated with the main Hospital Information System using the Distributed Data Processing (DDP) protocol, stored the acquired images on NT file servers and set database entries to reference them. Problems with DDP * Causes database inconsistencies. * Complete lack of security. * DDP is bound to MAC addresses. * DDP can be very slow on a busy HIS and/or network. * DDP runs very slowly in a WAN environment because of inherent network latencies. Because of the database inconsistency problem, incidents of matching images to the wrong patient occurred at one particular site. DDP doesn't have any security. M-to-M Broker uses many of the robust security features implemented by the VISTA RPC Broker and Kernel software. These security features are transparent to the end user and without additional impact on IRM. For the VISTA Imaging DICOM Gateway, the M applications on separate VISTA systems will be converted to use this new M-to-M Broker software to communicate to the main HIS. This will then eliminate the need for DDP where it is used. List of Test Sites ================== VISTA Imaging System Team, Washington Office of Information Field Office (OIFO) VAMC San Francisco Blood Bank Team Coordination ============================ Clearance - August 21, 2002 Routine Summary =============== The following routines are included in this patch. The second line of each of these routines now looks like: ;;1.1;RPC BROKER;**[patch list]**; Mar 28, 1997 Remote Procedure Calls ====================== Two new RPCs will be exported with this package to be used as examples for the purposes of testing the M-to-M Broker. XWB M2M EXAMPLE LARRY XWB M2M EXAMPLE REF Checksums ========= Sites should use CHECK^XTSUMBLD to verify checksums. Routine Name Before Patch After Patch Patch List ============ ============ =========== ========== XWBM2MC None 6758340 28 XWBM2MS None 160268 28 XWBM2MT None 7883957 28 XWBRL None 3848552 28 XWBRM None 3795059 28 XWBRMX None 3053319 28 XWBRPC None 10961081 28 XWBRPCC None 5907709 28 XWBUTL None 3238078 28 XWBVL None 1814637 28 XWBVLC None 1920009 28 XWBVLL None 3018372 28 Installation Instructions ========================= >>>Users may remain on the system. >>>TaskMan does *not* need to be stopped. 1. DSM sites - Some of these routines are usually mapped, so you will need to disable mapping for the affected routines. 2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This option will load the KIDS package 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: Verify Checksums in Transport Global Print Transport Global Compare Transport Global to Current System Backup a Transport Global 4. Users can remain on the system. This patch can be loaded any non-peak time. This patch can be queued and installed at any time. TaskMan can remain running. 5. On the KIDS menu, under the 'Installation' menu, use the following option: Install Package(s) 'XWB*1.1*28' ========== Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// NO Want KIDS to INHIBIT LOGONs during the install? YES// NO Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO 6. DSM Sites, after patch has installed, rebuild your map set. Routine Information: ==================== Routine Name: - XWBM2MC Routine Checksum: Routine Name: - XWBM2MS Routine Checksum: Routine Name: - XWBM2MT Routine Checksum: Routine Name: - XWBRL Routine Checksum: Routine Name: - XWBRM Routine Checksum: Routine Name: - XWBRMX Routine Checksum: Routine Name: - XWBRPC Routine Checksum: Routine Name: - XWBRPCC Routine Checksum: Routine Name: - XWBUTL Routine Checksum: Routine Name: - XWBVL Routine Checksum: Routine Name: - XWBVLL Routine Checksum: Routine Name: - XWBVLC Routine Checksum: ============================================================================= User Information: Entered By : MENDOZA,RAUL E Date Entered : JAN 09, 2002 Completed By: SINGH,GURBIR Date Completed: AUG 26, 2002 Released By : PALMER,MICHAEL Date Released : OCT 17, 2002 ============================================================================= Packman Mail Message: ===================== $END TXT