$TXT Created by at SLC4.FO-BAYPINES.DOMAIN.EXT (KIDS) on Monday, 12/19/22 at 16:43 ============================================================================= Run Date: MAY 03, 2023 Designation: MHV*1*74 Package : MHV - MYHEALTHEVET Priority: Mandatory Version : 1 SEQ #79 Status: Released Compliance Date: JUN 03, 2023 ============================================================================= Subject: EXTRACT PHARMACY INDICATION FIELDS INTO HL7 MESSAGES FOR MHV Category: - Routine - Data Dictionary Description: ============ This patch addresses the following issues: 1. Post Install routine MHV1P74 will create a new "AE" cross reference to file named Prescription Refill Request (#52.43) into the field named Prescription IEN (#8). The post routine will calculate the last 100,000 Records in file 52.43 to add the "AE" cross reference so that the VistA environment is not burdened and locked down on timing issues when installing the patch. The "AE" cross reference will help to make My HealtheVet (MHV) HL7 extract more efficient. 2. Post install routine MHV1P74 will add a new entry into file named MHV Request Type (#2275.3), MEDICATIONS2. This new entry will have MHV extract routines MHVXRXM2 and MHV builder routine MHV7B1R2 in fields .05 and .06 respectively. Note: Entries in this file manage custom MHV HL7 queries used to extract data from VistA. 3. The MEDICATIONS2 HL7 extract pulls the same data as the MEDICATIONS extract with the addition of a few data fields from the Prescription file (#52). The fields that will be extracted from file #52 will be: Indication For Use (#128), Indication For Use Flag (#129) and Other Indication For Use (#130). Once this patch is installed, the MEDICATIONS extract will no longer be used and MEDICATIONS2 will become the new extract so that the fields requested by the VA Pharmacy National Team will be sent over via HL7 Messages to MHV. 4. The new MEDICATIONS2 extract will also pull data from the file PRESCRIPTION REFILL REQUEST (#52.43). The fields extracted from file #52.43 will be: Result (#6), Remarks (#10), and Login Date (#11). It also determines if a particular drug is renewable from routine MHVPRNA. (Guidance for this logic was provided by the VA Pharmacy National Team.) 5. The pharmacy builder routine MHV7B1R2 will get the requested indication fields as noted above and also allow the signature field (#10) to be placed at the end of the HL7 string which is then transported to MHV. A correction has also been made to the Signature field to allow delimited characters to be sent as an escaped sequence. 6. The routine MHVPRNA returns whether a prescription is renewable. If it is not, a reason is returned. This routine is called by the builder routine MHV7B1R2, and reported in HL7 fields 56 and 57 in the RDT segment. The logic for MHVPRNA was copied from routine PSORENW and vetted/reviewed by the pharmacy techinical staff. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- PRESCRIPTION REFILL PRESCRIPTION IEN (#8) MODIFIED REQUEST (#52) Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ---- -------------------- N/A Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: --------------------- N/A Template Name Type File Name (Number) New/Modified/Deleted ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- N/A New Service Requests (NSRs): ---------------------------- N/A Patient Safety Issues (PSIs): ----------------------------- N/A Defect Tracking System Ticket(s) & Overview: -------------------------------------------- N/A Problem: -------- N/A Resolution: ----------- N/A Technical Resolution: --------------------- N/A Test Sites: ----------- Hines: domain.ext Portland: fo-portland.domain.ext Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released as a KIDS build via a PackMan message. Sites may retrieve the documentation directly using a web browser with this url: https://download.vista.domain.ext and then selecting the SOFTWARE directory. Documentation can also be found on the VA Software Documentation Library at: http://www4.domain.ext/vdl/ Title File Name ------------------------------------------------------------ MHV Technical Manual MHV_VISTA_1_9_TECHNICALMANUAL.PDF Pre-Installation Instructions: ------------------------------ This patch may be installed with users on the system although it is recommended that it be installed during non-peak hours to minimize potential disruption to users. This patch should take less than 5 minutes to install. Installation Instructions: 1. Choose the PackMan message containing this build. Then select the INSTALL/CHECK MESSAGE PackMan option to load the build. 2. From the Kernel Installation and Distribution System Menu, select the Installation Menu. From this menu, A. Select the Verify Checksums in Transport Global option to confirm the integrity of the routines that are in the transport global. When prompted for the INSTALL NAME enter the patch or build name (ex. MHV*1.0*74) NOTE: Using will not bring up a Multi-Package build even if it was loaded immediately before this step. It will only bring up the last patch in the build. B. Select the Backup a Transport Global option to create a backup message. You must use this option and specify what to backup; the entire Build or just Routines. The backup message can be used to restore the routines and components of the build to the pre-patch condition. i. At the Installation option menu, select Backup a Transport Global ii. At the Select INSTALL NAME prompt, enter your build PSO*7.0*683 iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build R Routines Enter response: Build iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press and take the default IN mailbox or select a different mailbox. C. You may also elect to use the following options: i. Print Transport Global - This option will allow you to view the components of the KIDS build. ii. 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 of the components of this patch, such as routines, DDs, templates, etc. D. Select the Install Package(s) option and choose the patch to install. i. If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO//', answer NO ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install? NO//', answer NO iii. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO//', answer NO Back-out/Rollback Strategy: --------------------------- Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the build in a mail message using the Backup a Transport Global [XPD BACKUP] menu option (this is done at time of install). The message containing the backed-up build can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed up routines onto the VistA System. The back-out plan is to restore the build from the backup created. No data was modified by this patch installation and, therefore, no rollback strategy is required. Validation of Back-out Procedure: --------------------------------- The Back-out Procedure can be verified by printing the first 2 lines of the routines contained in this patch using the option First Line Routine Print [XU FIRST LINE PRINT]. Once the build contained in the MHV*1.0*74 patch has been backed out, the first two lines of the routine will no longer contain the designation of this patch in the patch list section on line 2. Post-Installation Instructions: -------------------------------- Once the patch is installed, make sure the new entry for MEDICATIONS2 in the MHV Request Type File (#2275.3) was created. To check for the entry do the following: Go into Fileman and select the INQUIRE TO FILE option. At the Output from what File: prompt enter MHV REQUEST TYPE or 2275.3 At the the Select MHV REQUEST TYPE NAME: prompt, enter MEDICATIONS2 At the Another one: prompt, just press ENTER At the Standard Captioned Output? Yes// prompt, just press ENTER At the Include COMPUTED fields: (N/Y/R/B): NO// prompt, just press ENTER You should see the following: NOTE: NUMBER might not be 51 NAME: MEDICATIONS2 NUMBER: 51 BLOCKED?: NO REALTIME?: ALLOWED EXECUTE ROUTINE: EXTRACT~MHVXRXM2 BUILDER ROUTINE: MHV7B1R2 MHV DATATYPE: Medications2 DESCRIPTION: QBP^Q13 query for Medications from multiple SOURCES including RX renewal data ------------------------------------------------------------ You may also want to verify that the newly "AE" cross reference has been added to the PRESCRIPTION REQUEST FILE (52.43); PRESCRIPTION IEN field (#8). In Fileman: Select OPTION: 8 DATA DICTIONARY UTILITIES Select DATA DICTIONARY UTILITY OPTION: 1 LIST FILE ATTRIBUTES START WITH What File: PRESCRIPTION REFILL REQUEST// (4607 entries) GO TO What File: PRESCRIPTION REFILL REQUEST// (4607 entries) Select LISTING FORMAT: STANDARD// Start with field: FIRST// 8 PRESCRIPTION IEN Go to field: 8 PRESCRIPTION IEN DEVICE: ;;99999 VIRTUAL Right Margin: 80// STANDARD DATA DICTIONARY #52.43 -- PRESCRIPTION REFILL REQUEST FILE 9/23/22 PAGE 1 STORED IN ^PS(52.43, (4607 ENTRIES) SITE: TEST.SALT-LAKE.DOMAIN.EXT UCI: SL C4,ROU (VERSION 7.0) DATA NAME GLOBAL DATA ELEMENT TITLE LOCATION TYPE -------------------------------------------------------------------------- ----- 52.43,8 PRESCRIPTION IEN 0;8 FREE TEXT INPUT TRANSFORM: K:$L(X)>20!($L(X)<1) X MAXIMUM LENGTH: 20 LAST EDITED: MAR 30, 2022 HELP-PROMPT: Answer must be 1-20 characters in length. DESCRIPTION: This is the internal entry number of the prescription associated with this refill request. CROSS-REFERENCE: 52.43^AE 1)= S ^PS(52.43,"AE",$E(X,1,30),DA)="" 2)= K ^PS(52.43,"AE",$E(X,1,30),DA) Builds Cross ref for rx IEN. RECORD INDEX: AINST (#618) MUMPS IR ACTION Short Descr: QUEUE FOR PROCESSING REFILL REQUESTS Set Logic: S ^PS(52.43,"AINST",X(1),X(2),DA)="" Kill Logic: K ^PS(52.43,"AINST",X(1),X(2),DA) X(1): INSTITUTION (52.43,4) (Subscr 1) (forwards) X(2): PRESCRIPTION IEN (52.43,8) (Subscr 2) (Len 30) (forwards) Routine Information: ==================== The second line of each of these routines now looks like: ;;1.0;My HealtheVet;**[Patch List]**;Aug 23, 2005;Build 42 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: MHV1P74 Before: n/a After: B5692096 **74** Routine Name: MHV7B1R2 Before: n/a After:B115896591 **74** Routine Name: MHVPRNA Before: n/a After: B14420774 **74** Routine Name: MHVXRXM2 Before: n/a After:B194002558 **74** ============================================================================= User Information: Entered By : Date Entered : APR 19, 2022 Completed By: Date Completed: APR 28, 2023 Released By : Date Released : MAY 03, 2023 ============================================================================= Packman Mail Message: ===================== $END TXT