$TXT Created by PHELPS,TY at MNTVBB.FO-ALBANY.MED.VA.GOV (KIDS) on Friday, 01/13/06 at 14:20 ============================================================================= Run Date: SEP 20, 2006 Designation: GMRC*3*42 Package : GMRC - CONSULT/REQUEST TRACKING Priority: Mandatory Version : 3 SEQ #45 Status: Released Compliance Date: OCT 21, 2006 ============================================================================= Associated patches: (v)GMRC*3*22 <<= must be installed BEFORE `GMRC*3*42' Subject: HOME TELEHEALTH INTERFACE Category: - Routine - Other Description: ============ This patch modifies an existing API (DBIA #3252) and adds a new service to the REQUEST SERVICES (#123.5) file in support of the Home Telehealth project. ASSOCIATED NSR(s): ================== N/A ASSOCIATED NOIS/REMEDY: ======================= 1. HD0000000068817 ISW-0205-20756 Deploy standard name for Home Telehealth consult PARTICIPATING TEST SITES: ========================= Altoona,PA Connecticut HCS Huntington,WV Puget Sound HCS Salt Lake City,UT NOIS/REMEDY OVERVIEW: ===================== 1. HD0000000068817 ISW-0205-20756 Deploy standard name for Home Telehealth consult Problem: -------- The Home Telehealth project group has requested a new Service be created entitled: CARE COORDINATION HOME TELEHEALTH SCREENING In addition to this, the Registration package needed to access Consult information in support of the Home Telehealth project. An API (DBIA #3252) to return the needed information already existed, but would only accept the Consult Service IEN as input. They needed it to accept the Consult Service Name as well, in order for them to use it. Resolution: ----------- A new Consult Service will be created in the REQUEST SERVICES (#123.5) file and a modification will be made to the existing API (DBIA #3252) to allow it to use the Consult Service name as well as the Consult Service IEN. TECHNICAL: ========== The Consult Service will be added via the pre-installation routine, PRE^GMRCYP42. This routine will either create a new entry or it will overwrite an existing entry in the REQUEST SERVICES (#123.5) file. If overwritten, only the fields listed below will by modified while other existing entries in fields not listed below will remain unchanged. The Consult Service is being exported to support the Home Telehealth project. The Consult Service will contain the following settings: SERVICE NAME: CARE COORDINATION HOME TELEHEALTH SCREENING SERVICE USAGE: DISABLED PRINT NAME: CCHT SC PROVISIONAL DX PROMPT: OPTIONAL PROVISIONAL DX INPUT: LEXICON RESTRICT DEFAULT REASON EDIT: UNRESTRICTED SYNONYM: CCHT SCRN INTERNAL NAME: CCHT SCREENING OE/RR DISPLAY GROUP: CONSULTS PROTOCOL ACTION MENU BY USERS: GMRCACTM SERVICE ACTION MENU DEFAULT REASON FOR REQUEST: Initial Screening for Home Telehealth services. An environment check routine, ^GMRCYP42, will identify any existing services that partially or exactly match the one being imported. Upon identification of any partial or exact matches, the service name is reported to the installer. The environment check routine advises the installing person to abort installation if the environment check identifies a potential conflict. All messages from the environment check are available for later review by using the Install File Print [XPD PRINT INSTALL FILE] option and printing install name GMRC*3.0*42. What to do if the environment check identifies a partial match: 1) Review the service identified as being a partial match. 2) Determine if the existing service should be disabled based on whether the incoming service will replace it. 3) Remember, ONLY the imported service name will be recognized by the Home Telehealth software. 4) If the existing service should remain active in addition to the new service, the warning may be ignored. What to do if the environment check identifies an exact match: 1) If an exact match was found for the service being installed, the existing service will be overwritten with the new service settings listed above. If the values in the existing service must be maintained, the name of the existing service MUST be changed. 2) Any changes to the name of a service MUST be done via the Set up Consult Services [GMRC SETUP REQUEST SERVICES] option. Changing the name of a service via VA FileManager can have negative effects on the ordering of Consults in CPRS. ************************************************************************ WARNING: The use of VA FileManager for editing of the REQUEST SERVICES (#123.5) file is highly discouraged. Specific safeguards are in place when utilizing the Set up Request Services [GMRC SETUP REQUEST SERVICES] option. These safeguards are not present when using Fileman. ************************************************************************ The post-installation routine, POST^GMRCYP42, will add the new Consult Service as a sub-service to ALL SERVICES. Routine GMRCASV1, the GUI tag entry point, is being modified to accept the Consult Service name (#.01) field, as well as the Consult Service IEN of the REQUEST SERVICES (#123.5) file, as a valid input. It previously would only accept the Consult Service IEN as input. The routine will attempt to find a Consult Service name with an exact match to the input. If one is not found, then the routine will attempt to match the input to a Consult Service IEN and continue processing as it always has. ************************************************************************ WARNING: The basis of the interface between Consult/Request Tracking and Registration is the name of the Consult service. Since the name of the service is critical to the stability of the interface, the new service name must not be edited. ************************************************************************ INSTALLATION INSTRUCTIONS: ========================= This patch can be loaded with users in the system, but it should be installed during non-peak hours. Installation time will be less than two minutes. 1. Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: Installation --- 1 Load a Distribution 2 Verify Checksums in Transport Global 3 Print Transport Global 4 Compare Transport Global to Current System 5 Backup a Transport Global 6 Install Package(s) Restart Install of Package(s) Unload a Distribution 3. From this menu, you may elect to use the following options (When prompted for the INSTALL NAME, enter GMRC*3.0*42): 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 or templates. 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, templates, 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. Use the Install Package(s) option and select the package GMRC*3.0*42. a. When prompted "Want KIDS to INHIBIT LOGONs during the install? YES//", answer NO. b. When prompted "Want to DISABLE Scheduled Options and Menu Options and Protocols? YES//", answer NO. 5. The environment/pre/post installation routine, GMRCYP42, can be deleted after a successful install. POST-INSTALLATION INSTRUCTIONS: =============================== 1) When your site is prepared to use the Consult service provided in this patch, the DISABLED entry in the SERVICE USAGE field should be deleted. Again, this change should be done using the Set up Consult Services [GMRC SETUP REQUEST SERVICES] option. If you chose to install the service over an existing service that matched exactly, THIS STEP MUST BE PERFORMED IMMEDIATELY. 2) Any user that should receive notifications can be configured in one of the fields in the REQUEST SERVICES (#123.5) file. Details of which fields to configure can be found in the Consult/Request Tracking Technical Manual available from the VistA Documentation Library (VDL) at http://www.va.gov/vdl/Clinical.asp?appID=62. 3) If automatic printing of requests to this service should occur, a VistA printer should be entered in field #123.09 SERVICE PRINTER. 4) During the installation the service was made a sub-service of ALL SERVICES. If you want it to be arranged differently within your Consult hierarchy, that will need to be done after installation. INSTRUCTIONS FOR MANUAL ADDITION OF A NEW CONSULT SERVICE: ========================================================== ************************************************************************** WARNING: DO NOT USE THESE INSTRUCTIONS UNLESS DIRECTED TO DO SO BY THE FOLLOWING MESSAGE DURING THE INSTALL: CARE COORDINATION HOME TELEHEALTH SCREENING failed to be added to the REQUEST SERVICES (#123.5) file. Follow the instructions in the patch description for manually adding this service. ************************************************************************** These instructions are for adding the new Consult Service, CARE COORDINATION HOME TELEHEALTH SCREENING, in the event the service fails to be added automatically during the installation of this patch. The following entries need to be added exactly as shown below. Afterwards, the POST-INSTALLATION INSTRUCTIONS above should be followed. MNTDEM>D ^XUP Setting up programmer environment This is a TEST account. Terminal Type set to: C-VT100 You have 13 new messages. Select OPTION NAME: GMRC MGR Consult Management You have PENDING ALERTS Enter "VA to jump to VIEW ALERTS option Select Consult Management Option: SS Setup Consult/Request Services Select Service/Specialty:CARE COORDINATION HOME TELEHEALTH SCREENING Are you adding 'CARE COORDINATION HOME TELEHEALTH SCREENING' as a new REQUEST SERVICES (the 14TH)? No// Y (Yes) SERVICE NAME: CARE COORDINATION HOME TELEHEALTH SCREENING Replace ABBREVIATED PRINT NAME (Optional): CCHT SC INTERNAL NAME: CCHT SCREENING Select SYNONYM: CCHT SCRN Are you adding 'CCHT SCRN' as a new SYNONYM (the 1ST for this REQUEST SERV ICES)? No// Y (Yes) Select SYNONYM: SERVICE USAGE: DISABLED DISABLED SERVICE PRINTER: NOTIFY SERVICE ON DC: REPRINT 513 ON DC: PREREQUISITE: 1> PROVISIONAL DX PROMPT: O OPTIONAL PROVISIONAL DX INPUT: L LEXICON DEFAULT REASON FOR REQUEST: 1>Initial Screening for Home Telehealth services. 2> EDIT Option: RESTRICT DEFAULT REASON EDIT: UN UNRESTRICTED Inter-facility information IFC ROUTING SITE: IFC REMOTE NAME: Select IFC SENDING FACILITY: SERVICE INDIVIDUAL TO NOTIFY: Select SERVICE TEAM TO NOTIFY: Select NOTIFICATION BY PT LOCATION: PROCESS PARENTS FOR NOTIFS: Select UPDATE USERS W/O NOTIFICATIONS: Select UPDATE TEAMS W/O NOTIFICATIONS: Select UPDATE USER CLASS W/O NOTIFS: Select ADMINISTRATIVE UPDATE USER: Select ADMINISTRATIVE UPDATE TEAM: PROCESS PARENTS FOR UPDATES: SPECIAL UPDATES INDIVIDUAL: RESULT MGMT USER CLASS: UNRESTRICTED ACCESS: Select SUB-SERVICE/SPECIALTY: Add/Edit Another Service? NO// YES (Answer 'YES' and continue following the below instructions for adding a consult service as a sub-service to ALL SERVICES.) INSTRUCTIONS FOR ADDING A CONSULT SERVICE AS A SUB-SERVICE TO ALL SERVICES: =========================================================================== ************************************************************************** WARNING: DO NOT USE THESE INSTRUCTIONS UNLESS DIRECTED TO DO SO BY THE PREVIOUS SECTION'S INSTRUCTION FOR ADDING A NEW CONSULT SERVICE OR BY THE FOLLOWING MESSAGE RECEIVED DURING THE INSTALL: CARE COORDINATION HOME TELEHEALTH SCREENING failed to be added as a sub-service to ALL SERVICES in the REQUEST SERVICES (#123.5) file. Follow the instructions in the patch description for manually adding this sub-service. ************************************************************************** These instructions are for adding the new Consult Service, CARE COORDINATION HOME TELEHEALTH SCREENING, as a sub-service to the ALL SERVICES consult service in the event the service fails to be added automatically during the installation of this patch. The only field being changed below is the SUB-SERVICE/SPECIALTY (#.01) sub-field of the SUB-SERVICE SUB-FIELD (#123.51) file. Please be careful not to inadvertantly edit any other field entries. Afterwords, the POST-INSTALLATION INSTRUCTIONS above should be followed. MNTDEM>D ^XUP Setting up programmer environment This is a TEST account. Terminal Type set to: C-VT100 You have 13 new messages. Select OPTION NAME: GMRC MGR Consult Management You have PENDING ALERTS Enter "VA to jump to VIEW ALERTS option Select Consult Management Option: SS Setup Consult/Request Services Select Service/Specialty:ALL SERVICES GROUPER ONLY SERVICE NAME: ALL SERVICES// ABBREVIATED PRINT NAME (Optional): INTERNAL NAME: Select SYNONYM: SERVICE USAGE: GROUPER ONLY// SERVICE PRINTER: NOTIFY SERVICE ON DC: REPRINT 513 ON DC: PREREQUISITE: 1> PROVISIONAL DX PROMPT: PROVISIONAL DX INPUT: DEFAULT REASON FOR REQUEST: 1> RESTRICT DEFAULT REASON EDIT: Inter-facility information IFC ROUTING SITE: IFC REMOTE NAME: Select IFC SENDING FACILITY: SERVICE INDIVIDUAL TO NOTIFY: Select SERVICE TEAM TO NOTIFY: Select NOTIFICATION BY PT LOCATION: PROCESS PARENTS FOR NOTIFS: Select UPDATE USERS W/O NOTIFICATIONS: Select UPDATE TEAMS W/O NOTIFICATIONS: Select UPDATE USER CLASS W/O NOTIFS: Select ADMINISTRATIVE UPDATE USER: Select ADMINISTRATIVE UPDATE TEAM: PROCESS PARENTS FOR UPDATES: SPECIAL UPDATES INDIVIDUAL: RESULT MGMT USER CLASS: UNRESTRICTED ACCESS: Select SUB-SERVICE/SPECIALTY: PROSTHETICS REQUEST // CARE COORDINATION HOME TELEHEALTH SCREENING DISABLED Are you adding 'CARE COORDINATION HOME TELEHEALTH SCREENING' as a new SUB-SERVICE (the 5TH for this REQUEST SERVICES)? No// Y (Yes) MNEMONIC: Select SUB-SERVICE/SPECIALTY: Add/Edit Another Service? NO// ROUTINE SUMMARY: =============== The following is a list of the routines included in this patch. The second line of each of these routines now looks like: ;;3.0;CONSULT/REQUEST TRACKING;**[patch list]**;DEC 27, 1997 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== =========== GMRCASV1 2073849 2237306 18,15,23,22,42 GMRCYP42 N/A 10709436 42 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: GMRCASV1 Before: B4425153 After: B4836288 **18,15,23,22,42** Routine Name: GMRCYP42 Before: n/a After: B28654410 **42** ============================================================================= User Information: Entered By : PHELPS,TY Date Entered : FEB 09, 2005 Completed By: ILUSTRISIMO,LUCY Date Completed: SEP 13, 2006 Released By : GAWRONSKI,ROXANNE Date Released : SEP 20, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT