$TXT Created by ATKINSON,DEVEN D at DEV.DEV.FO-HINES.MED.VA.GOV (KIDS) on Monday, 07/13/09 at 08:41 ============================================================================= Run Date: SEP 23, 2009 Designation: RMPR*3*83 Package : RMPR - PROSTHETICS Priority: Mandatory Version : 3 SEQ #132 Status: Released Compliance Date: OCT 24, 2009 ============================================================================= Associated patches: (v)GMRC*3*44 <<= must be installed BEFORE `RMPR*3*83' Subject: PROSTHETIC INTERFACILITY CONSULTS Category: - Data Dictionary - Routine - Enhancement (Mandatory) Description: ============ This patch provides the ability for Prosthetics to electronically send and process consult or order requests between VAMC facilities. Users will be able to request a consult at their facility and the consult will be electronically delivered to the consulting facility. The quality of patient care will be improved by increasing the efficiency and reliability of the communication of inter-facility information and by providing facilities with access to complete and up-to-date patient information. Description of '****Discontinued****' will be displayed in the Suspense Processing screen if the consult is discontinued by the provider. PROSTHETICS IFC SETUP Each VAMC should set up a consult for RECEIVING consults and additionally should set up a consult for each VAMC that they are SENDING consults to. (For additional information regarding Inter-Facility Consults, please refer to the Inter-Facility Consults Implementation Guide (October 2002), pages 4-5, 24 and 29.) a) The software that allows the consult data to populate into the PROSTHETIC SUSPENSE file (#668) requires that the name of the Service/Specialty in Consults follows a specific character format. All Prosthetics service/specialty entries must start with the characters "PROSTHETICS IFC". If this protocol is not followed, the consult data will not enter the Prosthetics application. b) For consistency and to assure that there will be no conflicts in IFC consult naming between potential sending/receiving systems, Prosthetics is requiring that the Receiving VAMC's station number be appended immediately after "PROSTHETICS IFC" c) The Consults package menu option "Set up Consult Services [GMRC SETUP REQUEST SERVICES] should be used to create the Service/Specialty entries as follows: 1) For the VAMC receiving the consult: It is recommended that the service name be set up before the sending facility creates their Service/Specialty entry because the name of this service will be shared with the sending facility. (Example of RECEIVING consult service name: "PROSTHETICS IFC nnn", where "nnn" is this VAMC's three to five character station number.) The data field, IFC SENDING FACILITY, must include the name(s) of the VA Medical Center(s) sending the consult. Note: this is a multiple field and more than one VAMC can send an Inter-Facility Consult to this service. 2) For the VAMC sending the consult: Since the consult will not be processed locally, most of the data fields can be left blank. It is recommended that the service name of this consult be human readable. (Example: "PROSTHETICS IFC aaa", where aaa is text that is easily understood to be the VAMC that is RECEIVING the consult, such as the facility name or abbreviation.) It is required that the characters "IFC" are part of the consult name. The following fields are required: o PROVISIONAL DX PROMPT must be set to REQUIRE. o PROVISIONAL DX INPUT must be set to LEXICON. o IFC ROUTING SITE must be set to the name of the VAMC that will receive the Inter-Facility Consult. o IFC REMOTE NAME must be the name of the service at the receiving facility and it must exactly match the text that is entered as the receiving consult at that VAMC. If this name does not match the name of the service at the routing site, the request will fail to be filed at the remote site. This will delay or prohibit the performance and processing of this request. Coordination with the receiving facility should occur before creating this entry to avoid problems. (Example of SENDING site's IFC REMOTE NAME: "PROSTHETICS IFC nnn", where "nnn" is the three to five character station number of the VAMC that will be receiving the consult. Coordination with the RECEIVING VAMC staff is required to assure that this data is entered correctly.) Remedy: ======= None New Service Request (NSR): ========================== None Associated E3R: =============== None Routine Added: ============= RMPRFC3 RMPRFC4 RMPRFC5 The above routines have been added to the Prosthetics application to handle the intercept of the Inter-facility Consults HL7 message and manage the records in the Prosthetic Suspense file (#668). Routines Modified: ================= RMPR9VR RMPREO RMPREOL RMPREOU RMPRHL7A Fields Added: ============ The following fields have been added to Prosthetic Suspense file (#668): Field # Field Name 27 Ordering Provider Documentation: ============== rmpr_3_83rn.doc PATCH 83 Release Notes WORD Binary The install instructions can be found in the following [ANONYMOUS.SOFTWARE] directories: Preferred Address ------------------------- First available FTP server download.vista.med.va.gov Specific Field Office FTP Address --------------------- ------------------------ Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov Test Sites: =========== New York Clarksburg Pittsburgh Houston Biloxi Alexandria, LA Oklahoma City Milwaukee Installation Instructions: ========================== This patch should be installed during non-peak hours, as all Prosthetics users must be off the system. The install time for this patch is less than five (5) minutes. 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. On the KIDS menu, under the 'Installation' menu, use the option 'Verify Checksum in Transport Global' and verify that all routines have the correct checksums. 3. From the 'Installation' menu of KIDS, use the option 'Install Package(s)'. Select the package 'RMPR*3.0*83' and proceed with the install. 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. 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, 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. It is recommended that you do not queue this patch for install. 5. When prompted 'Want KIDS to INHIBIT LOGINs during the install? YES//', response NO. 6. When prompted 'Want to DISABLE Schedule Options, Menu Options, and Protocols? YES//', response YES. When prompted to select the option you would like to place out of order, enter the following: RMPR OFFICIAL RMPR CLERK Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;PROSTHETICS;**[Patch List]**;Feb 09, 1996;Build 20 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: RMPR9VR Before: B5492507 After: B5833491 **59,83** Routine Name: RMPREO Before: B9728753 After: B10452539 **45,55,83** Routine Name: RMPREOL Before: B11453654 After: B12020197 **62,83** Routine Name: RMPREOU Before: B17695537 After: B19592813 **45,55,59,135,83** Routine Name: RMPRFC3 Before: n/a After: B5404403 **83** Routine Name: RMPRFC4 Before: n/a After: B13693524 **83** Routine Name: RMPRFC5 Before: n/a After: B202840 **83** Routine Name: RMPRHL7A Before: B33495720 After: B34526281 **45,78,83** Routine list of preceding patches: 62, 78, 135 ============================================================================= User Information: Entered By : HSI,TUAN Date Entered : NOV 17, 2003 Completed By: CHAN,DONALD Date Completed: SEP 14, 2009 Released By : LAMBERT,WENDEL R Date Released : SEP 23, 2009 ============================================================================= Packman Mail Message: ===================== $END TXT