Electronic Health Record

Transcription

1 RESOURCE AND PATIENT MANAGEMENT SYSTEM Electronic Health Record (EHR) Version 1.1 Patch 11 Office of Information Technology (OIT) Division of Information Resource Management Albuquerque, New Mexico

2 Table of Contents 1.0 Introduction Tips Installation Pre-Installation Patched CPRS Required Patched Required Builds Installation Questions Mega Build I (ehr_ mb1) Mega Build II (ehr_ mb2) Mega Build III (ehr_ mb3) Mega Build IV (ehr_ mb4) Mega Build V (ehr_ mb5) Mega Build VI (ehr_ mb6) Mega Build VII (ehr_ mb7) Mega Build VIII (ehr_ mb8) Mega Build IX (ehr_ mb9) Installation Order Mega Build I (ehr_ mb1) Mega Build II (ehr_ mb2) Mega Build III (ehr_ mb3) Mega Build IV (ehr_ mb4) Mega Build V (ehr_ mb5) Mega Build VI (ehr_ mb6) Mega Build VII (ehr_ mb7) Mega Build VIII (ehr_ mb8) Mega Build IX (ehr_ mb9) EHR Patch 11 Build EHR Patch 11 KIDs Build GUI Installation Appendix A: List of Applications Updated with the CPRS 27 Mega Builds Appendix B: APSP*7.0* B.1 General Information B.2 Modifications/Enhancements Included in this Patch B.3 Contents of Distribution B.4 Requirements B ii Table of Contents

3 B.6 Post Contact Information iii Table of Contents

4 Preface This is to be used to bring installations of VistA at Indian Health Services (IHS) up to the Veterans Administration version of VistA compatible with CPRS version 27. Since several of the applications within this environment have been modified to meet the specific needs of IHS, additional patches are included that will result in the IHS functionality being retained, while bringing the software current with CPRS v27. There will also be new IHS only functionality that will be added in EHR patch 11. Purpose This manual provides the information that enables the installation team to successfully load all VistA mega builds as well as the application patches to the IHS environment for both M based code and GUI programs necessary to run the IHS software. This document shows the detailed steps that must be followed for a successful installation. Scope This manual provides the steps for installing EHR Patch 11. Audience Information in this manual is intended for System Administrators who are responsible for installing the work environment and not for the general user population. iv Preface

5 1.0 Introduction 1.1 Tips This manual provides the information necessary to enable a system administrator to install the EHR Patch 11 work environment for a hospital or clinic. All user input should be in ALL CAPITAL LETTERS. Pressing Enter repeatedly generally takes you back to a prompt that you are familiar with. Typing a ^ exits the routine. There is often online Help available by typing?,?? or???. There are various levels of online Help, depending on where you are in the application. When an input request is made, the system will usually respond with a default response. If you press Enter, the system will use the default response. A good option to try is typing??, and then pressing Enter. This presents a list of options for input. For example, if you press Enter after INPUT TO WHAT FILE: NEW PERSON// prompt, it selects the NEW PERSON file. Typing?? gives you a list of files you could choose instead. 1.2 Installation VERY IMPORTANT READ CAREFULLY EHR Patch 11 MUST be installed with no users on the system. There are too many routine updates to allow users access to the system while this is occurring. Find a time when the system can be shut down for approximately two hours so all the patches can be installed. As there will be no users on the system, you can answer NO to inhibit logins and disable options. ALL the patches in this manual MUST be installed and in the order given prior to allowing users back on the system. Installing only the Mega Builds will remove all IHS modifications to the system and cause multiple errors. The instructions advise to say NO to the menu rebuilds. However, once all the builds are installed, DO rebuild the MENUs. Many new options have been added, and a menu rebuild is required so they are all properly placed. The user may be asked for a starting time for a tasked job during installation. Choose a time after the installation has finished. 1 Introduction

6 Place TaskMan in a WAIT state while the installation is occurring. This prevents any automated tasks from starting while the installation is still proceeding If the site is an INPATIENT site, have the Clinical Applications Coordinator (CAC) available to begin any IV quick orders to infusion quick orders. Providers will not be able to use these quick orders until they are converted. The Order Menu (Management Menu in the CPRS Manager Menu) has two options for the CAC to use: 1. MR Medication Quick Order Report This report shows which medications must be converted. It is sent in a Mailman message to the user running the option. 2. CV Convert IV Inpatient QO to Infusion QO This option guides the CAC through the conversion. 2 Introduction

7 2.0 Pre-Installation Patched Each of the Mega Builds requires that certain patches be installed prior to running the Mega Build. The list below includes those patches. To verify that the patch already exists on the system, check the PACKAGE file (#9.4) to verify that the Patch Application History Sub-Field under the Version Field Multiple exist contains the information using the instructions below. These steps assume that the user has programmer rights and that a value for DUZ has been set. The user must also be in the correct UCI in order to install or validate software. 1. From a programmer s prompt, type >D P^DI and then press Enter. 2. At Select Option: prompt, type?. The following menu appears: 1 ENTER OR EDIT FILE ENTRIES 2 PRINT FILE ENTRIES 3 SEARCH FILE ENTRIES 4 MODIFY FILE ATTRIBUTES 5 INQUIRE TO FILE ENTRIES 6 UTILITY FUNCTIONS 7 OTHER OPTIONS 8 DATA DICTIONARY UTILITIES 9 TRANSFER ENTRIES 3. At Select Option prompt, select ENTER or EDIT FILE ENTRIES and then press Enter. 4. At INPUT TO WHAT FILE: prompt, select PACKAGE//, and then press Enter. 5. At EDIT WHICH FIELD: prompt, select ALL// VERSION (multiple), and then press Enter. 6. At the EDIT WHICH VERSION SUB-FIELD: ALL// prompt, select PATCH APPLICATION HISTORY (multiple), and then press Enter. 7. At the EDIT WHICH PATCH APPLICATION HISTORY SUB-FIELD: prompt, select ALL//, then EDIT VERSION SUB-FIELD:, and then EDIT FIELD:, and then press Enter. 8. At the Select PACKAGE NAME: LEXICON UTILITY prompt, type LEX, and then press Enter. 9. At the Select VERSION: prompt, type 2.0//, and then press Enter. 10. At the Select PATCH APPLICATION HISTORY: 54//? prompt, type PATCH APPLICATION HISTORY and then press Enter. 11. At the Do you want the entire 54-Entry PATCH APPLICATION HISTORY List? prompt, type Y (Yes), and then press Enter. The following appears: 3 Pre-Installation Patched

8 Choose from: SEQ #10 11 SEQ #11 12 SEQ #12 13 SEQ #13 14 SEQ #14 15 SEQ #15 16 SEQ #16 17 SEQ #17 18 SEQ #18 19 SEQ #19 21 SEQ #20 22 SEQ #21 23 SEQ #22 24 SEQ #23 25 SEQ #24 25 SEQ# 0 NOTE: This shows that patch 25, with a sequence number has been installed. 26 SEQ #25 27 SEQ #26 28 SEQ #27 29 SEQ #28 30 SEQ #29 31 SEQ #30 32 SEQ #34 33 SEQ #31 34 SEQ #32 35 SEQ #33 36 SEQ #35 37 SEQ #36 38 SEQ #38 39 SEQ #37 40 SEQ #39 42 SEQ #41 45 SEQ #43 50 SEQ #48 6 SEQ #7 7 SEQ #6 8 SEQ #8 9 SEQ #9 You may enter a new PATCH APPLICATION HISTORY, if you wish. Answer must be 8-15 characters in length. 4 Pre-Installation Patched

9 12. At the Select PATCH APPLICATION HISTORY: promp, type 54//, and then press Enter. The following appears: PATCH APPLICATION HISTORY: 54// DATE APPLIED: APR 21, 2010// APPLIED BY: USER,DEMO// DESCRIPTION: No existing text 13. At the Edit? prompt, type NO//, and then keep pressing Enter until exited. The following appears: Select PATCH APPLICATION HISTORY: Select PACKAGE NAME: Select OPTION 2.1 CPRS Required Patched The following patches must be installed prior to loading each of the Mega Builds: 1. Mega Build I (ehr_ mb1.k) LEX*2.0*25 2. Mega Build II (ehr_ mb2.k) PXRM*1.5*12 SD*5.3*478 GMTS*2.7*66 TIU*1.0* Mega Build III (ehr_ mb3.k) LR*5.2*311 TIU*1.0*178 TIU*1.0*179 PSN*4.0*86 PSN*4.0*88 PSN*4.0*84 PSN*4.0* Mega Build IV (ehr_ mb4.k) DG*5.3*522 SD*5.3*316 5 Pre-Installation Patched

10 SD*5.3*285 DG*5.3*554 LR*5.2* Mega Build V (ehr_ mb5.k) RA*5.0*72 DG*5.3* Mega Build VI (ehr_ mb6.k) LR*5.2* Mega Build VII (ehr_ mb7.k) HDI*1.0*8 8. Mega Build VIII (ehr_ mb8.k) NONE 9. Mega Build IX (ehr_ mb9.k) NONE 6 Pre-Installation Patched

11 3.0 Required Builds It is essential that all the required builds are installed on the database prior to beginning the EHR Patch 11 installation. Failure will potentially leave your database is a state of corruption that may require you to revert to the most recent backup. Kernel Version 8.0 Patch 1017, which includes: xu k xt k di k xwb_ k xu 0800va.1017k Radiology Version 5.0 Patch 1003 including bra_ k Laboratory Version 5.2 Patch 1031 PIMS Version 5.3 Patch 1015 IHS PCC SUITE (BJPC) Version 2.0 Patch 8 ADVERSE REACTION TRACKING (GMRA) Version 4.0 Patch 1005 PROBLEM LIST (GMPL) Version 2.0 Patch 1001 GEN. MED. REC. VITALS (GMRV) Version 5.0 Patch 1001 CONSULT/REQUEST TRACKING (GMRC) Version 3.0 Patch 1002 TEXT INTEGRATION UTILITIES (TIU) Version 1.0 Patch 1010 CLINICAL REMINDERS (PXRM) Version 1.5 Patch 1009 IHS PHARMACY MODIFICATIONS (APSP) Version 7.0 Patch 1014 ELECTRONIC HEALH RECORD (EHR) Version 1.1 Patch 10 Note: An environment checker is including at the beginning of ehr_ mb1. DO NOT ATTEMPT to install ANY of the EHR 11 patches if this check fails until you have installed the missing patches. 7 Required Builds

12 4.0 Installation Questions Below is a listing of the questions a user will be asked while installed all the patches for EHR Patch 11. Keep this handy as you begin the process. Refer to Section 5.1 for the order of install. ehr_ mb1.k ehr_ mb2.k ehr_ mb3.k ehr_ mb4.k ehr_ mb5.k ehr_ mb6.k ehr_ mb7.k ehr_ mb8.k ehr_ mb9.k These files should be located where the installation process can find them when prompted. For example, the installation program asks: 1. At the Select Installation Option: prompt, select 1 LOAD A DISTRIBUTION, and then press Enter. 2. At the Enter a Host File: prompt, type C:\TEMP\MEGA BUILD_CPRS27\ehr_ mb1.k, and then press Enter. This information must be entered so that the installation routine can find the.kid file and Load it. At the end of the LOAD, the system displays the INSTALL NAME. The installer should make a note of this name as it will be asked when the INSTALL is done. The following Installation Questions must be answered during installation of each individual Mega Build. Have the answers available before starting the installation to avoid delays in processing. 4.1 Mega Build I (ehr_ mb1) 1. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group GMPL CODE SET VERSION UPDATES:, and then press Enter. The following appears: Want KIDS to Rebuild Menu Trees Upon Completion of Install? NOTE: This is asked several times. 8 Installation Questions

13 2. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group ORCM CSV EVENT:, and then press Enter. The following appears: Build McKesson VSN to Dispense Units Per Order Unit and Drug Description Data 4.2 Mega Build II (ehr_ mb2) Build SR*3.0*100 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This will be asked several times. Do you have the completed pre-installation worksheet? >>> New Site Parameter <<< 1. Answer the following question to define the default site parameter related to the use of the Anesthesia Report at your facility. This response will be stored for each division defined in the SURGERY SITE PARAMETERS file (#133) and may be updated after this patch is installed. Does this facility use the Anesthesia Report? >>> Starting Date for Reports to be Signed Electronically <<< During the post-installation process, all reports for completed cases with an operation date on or after the date selected will be identified to be signed electronically and stub entries will be created in TIU. 2. Enter a starting date for reports to be signed electronically. For example,: TODAY// (APR 22, 2010). >>> Making Reports for Historical Cases Viewable through CPRS <<< This patch includes a post-installation process that moves designated reports for historical Surgery cases into TIU. By doing so, these reports, while unsigned electronically, are viewable within the CPRS Surgery tab. These electronically unsigned reports contain a disclaimer stating; "This information is provided from historical files and cannot be verified that the author has authenticated/approved this information. The authenticated source document in the patient's medical record should be reviewed to ensure that all information concerning this event has been reviewed or noted. 9 Installation Questions

14 Note: The site parameters entered above will be applied in this process. For multi-divisional facilities, if different parameter settings should be applied for each division, or if for any reason the process to make reports for historical surgery cases viewable in CPRS should not be run during this patch installation, answer NO to this question. A new option is provided to run this process later. Do you want to move reports during the patch installation? If you need to move additional reports for a different date range, the Make Reports Viewable in CPRS option contained on the Surgery Package Management Menu can be used after this patch is installed. The post-installation process will be tasked to run immediately at the end of patch installation. The following actions will occur in the following order: a. Conversion of cases with documents in TIU filed by the Boston Prototype (Class III) software. b. Creation of stub entries in TIU for reports for cases completed on or after the date selected above as the starting date for reports to be signed electronically. c. Movement of reports for historical cases into TIU (if selected). 136 SURGERY PROCEDURE/DIAGNOSIS CODES *BUT YOU ALREADY HAVE 'SURGERY TRANSCRIPTION' AS FILE #136! Shall I write over your SURGERY TRANSCRIPTION File? 136 SURGERY PROCEDURE/DIAGNOSIS CODES (Partial Definition) *BUT YOU ALREADY HAVE 'SURGERY TRANSCRIPTION' AS FILE #136! Shall I write over your SURGERY TRANSCRIPTION File? Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 3. At the Enter the Device you want to print the Install messages prompt, you can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 4. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. Note: This prints information to your screen. 4.3 Mega Build III (ehr_ mb3) Build OR*3.0*195 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. 10 Installation Questions

15 1. At Enter when to Queue the Tally job to run in format: prompt Queue the task to run in about one hour following the install. That way it will not conflict with other patches and then press Enter. 2. The following appears: Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 3. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 4. At DEVICE: HOME//, type VIRTUAL, and then press Enter. Note: This prints the information to your screen. 4.4 Mega Build IV (ehr_ mb4) Build OR*3.0*215 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This will be asked several times. 1. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'PSO EXTERNAL DISPENSE ALERTS':, and then press Enter. 2. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'OR DRUG ORDER CANCELLED':, and then press Enter. The following appears: Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 3. Enter the Device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 4. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. Note: This prints the information to your screen. 4.5 Mega Build V (ehr_ mb5) Build PSO*7.0*254 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? 11 Installation Questions

16 Note: This question will be asked several times. 1. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'SR TRANSPLANT':, and then press Enter. The post-install routine included with this patch sends out a Mailman message with the list of Pharmacy Divisions in your site along with their related National Provider Identifier (NPI) Institution, which is being automatically assigned by this patch. It also indicatea if there were problems in the automatic assignment, which will have to be followed-up by an Outpatient Pharmacy user as outlined in the patch description. 2. Enter the Outpatient Pharmacy user(s) (e.g., Pharmacy ADPAC or designee) who should receive this message (at least one user is required). The user entered should be the person responsible for the maintenance of the PSO Site Parameters. The message will also be sent to the user installing the patch. PHARMACY USER:? ANOTHER ONE: Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 3. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 4. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. The following appears: Note: A build PSO*7.0*254 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. 5. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'SR TRANSPLANT':, and then press Enter. The post-install routine included with this patch sends out a Mailman message with the list of Pharmacy Divisions in your site, along with their related National Provider Identifier (NPI) Institution, which is being automatically assigned by this patch. It also indicates if there were problems in the automatic assignment, which will have to be followed-up by an Outpatient Pharmacy user as outlined in the patch description. 12 Installation Questions

17 6. Enter the Outpatient Pharmacy user(s) (e.g., Pharmacy ADPAC or designee) who should receive this message (at least one user is required). The user entered should be the person responsible for the maintenance of the PSO Site Parameters. The message is also sent to the user installing the patch. PHARMACY USER:? ANOTHER ONE: Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 7. Enter the Device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 8. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. Note: This prints information on your screen. 4.6 Mega Build VI (ehr_ mb6) Build PSU*4.0*3 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 1. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 2. At the DEVICE: HOME//, type VIRTUAL, and then press Enter. Note: This displays information on your screen. 4.7 Mega Build VII (ehr_ mb7) Build PSS*1.0*123 has an Environmental Check Routine. Want to RUN the Environment Check Routine? Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. Install Questions for GMRC*3.0*50: Print Full Patient Names on pre-install report? Checking Install for Package PSS*1.0*129 Will first run the Environment Check Routine, PSS129EN 13 Installation Questions

18 Upon completion of the Post Install, a mail message will be sent to the patch installer, and at least one pharmacy user. Enter one or more Pharmacy users (e.g., Pharmacy ADPAC or designee) who should receive this message. Enter Pharmacy User: Note: Type name here. Enter Pharmacy User: Continue with install? 1. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'PSO REJECTS BACKGROUND MESSAGE':, and then press Enter. The following appears: 115 NUTRITION PERSON *BUT YOU ALREADY HAVE 'DIETETICS PATIENT' AS FILE #115! Shall I write over your DIETETICS PATIENT File? NUTRITION EVENTS *BUT YOU ALREADY HAVE 'DIETETIC EVENTS' AS FILE #119.8! Shall I write over your DIETETIC EVENTS File? Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 2. Type the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 3. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. Note: This will display information to your screen. 4.8 Mega Build VIII (ehr_ mb8) Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 1. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 2. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. 4.9 Mega Build IX (ehr_ mb9) Want KIDS to Rebuild Menu Trees Upon Completion of Install? Note: This question will be asked several times. 14 Installation Questions

19 Want KIDS to INHIBIT LOGONs during the install? Want to DISABLE Scheduled Options, Menu Options, and Protocols? 1. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. 2. At the DEVICE: HOME// prompt, type VIRTUAL, and then press Enter. Note: This will display information on your screen. 15 Installation Questions

20 5.0 The following is the actual installation dialog for each of the Mega Builds. These instructions assume that the installer has Programmer rights, is in the correct UCI, and has a value set for DUZ. If not, refer to the Contact Information section for whom to contact for assistance. EHR11 needs to be installed with NO users on the system. Because of the extremely large numbers of routines being edited, there will be multiple errors if users remain on the system. The EHR will need to be shut down and no log-ins allowed. 5.1 Installation Order The mega builds MUST be installed in numeric order. DO NOT ATTEMPT to install them in any other order or it may result in database corruption! Each mega build is comprised of individual VA patches. After loading each mega build, scroll back and verify that none of the VA patches failed an environment check. If they did, the site MUST load the missing patch before proceeding. DO NOT NEGLECT THIS STEP! 1. ehr_ mb1.k 2. ehr_ mb2.k 3. ehr_ mb3.k 4. ehr_ mb4.k 5. ehr_ mb5.k 6. ehr_ mb6.k 7. ehr_ mb7.k 8. ehr_ mb8.k 9. ehr_ mb9.k DO NOT ATTEMPT to install ehr_ k UNTIL AFTER ALL the mega builds identified above have been successfully installed. This is the final step of the install. 10. ehr_ k 16

21 This patch puts IHS modifications back in the routines. DO NOT ATTEMPT to run the EHR until this build is installed. 5.2 Mega Build I (ehr_ mb1) 1. At the Select OPTION NAME: prompt, type INS,MENU, and then press Enter. The following appears: 1 INSTALLATION XPD INSTALLATION MENU Installation 2 INSURER FILE MENU AG TM INS MENU Insurer File Menu 3 INSURER FILE MENU ABMD TM INS MENU Insurer File Menu Select 1:3: 2. Select 1 XPD INSTALLATION MENU Installation, and then press Enter. The following appears: 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. Select 1 Load a Distribution, and then press Enter. 4. At the Enter a Host File: prompt, type YOUR DIRECTORY\ehr_ _mb1.k, and then press Enter. Note: The location of the ehr_ mb1.k file may not be in this folder. This is determined individually for each installation. The following appears: KIDS Distribution saved on Aug 08, 2007@14:36:33 Comment: Mega Build 1 - CPRS 26 - PSN Patches removed This Distribution contains Transport Globals for the following Package(s): PSO*7.0*156 PSO*7.0*189 PSO*7.0*159 PSO*7.0*182 PSO*7.0*118 PSO*7.0*185 PSO*7.0*181 PSO*7.0*177 PSO*7.0*193 PSO*7.0*184 PSO*7.0*188 PSO*7.0*194 PSO*7.0*192 PSO*7.0*186 GMPL*2.0*28 17

22 OR*3.0*181 OR*3.0*214 PSS*1.0*79 PSJ*5.0*110 OR*3.0*213 PSU*3.0*32 PSU*3.0*24 PSU*3.0*34 PSU*3.0*31 PSU*3.0*35 PSS*1.0*82 PSS*1.0*85 Distribution OK! 5. At the Want to Continue with Load? YES// prompt, type YES, and then press Enter. The following appears: Loading Distribution PSO*7.0*156 PSO*7.0*189 PSO*7.0*159 PSO*7.0*182 PSO*7.0*118 PSO*7.0*185 PSO*7.0*181 PSO*7.0*177 PSO*7.0*193 PSO*7.0*184 PSO*7.0*188 PSO*7.0*194 PSO*7.0*192 PSO*7.0*186 GMPL*2.0*28 OR*3.0*181 OR*3.0*214 PSS*1.0*79 PSJ*5.0*110 OR*3.0*213 PSU*3.0*32 PSU*3.0*24 PSU*3.0*34 PSU*3.0*31 Build PSU*3.0*35 has an Environmental Check Routine 6. At the Want to RUN the Environment Check Routine? YES// prompt, type YES, and then press Enter. The following appears: PSU*3.0*35 Will first run the Environment Check Routine, PSU35PRE PSS*1.0*82 PSS*1.0*85 7. At the INSTALL NAME: prompt, type PSO*7.0*156, and then press Enter to install this distribution. The following appears: 1 Load a Distribution 18

23 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 8. At the Select Installation Option:, type 6: INSTALL Package(s), and then press Enter. 9. At the Select INSTALL NAME: prompt, type PSO*7.0*156, and then press Enter. The following appears: Loaded from Distribution Loaded from Distribution 4/19/10@08:19:47 => Mega Build 1 - CPRS 26 - PSN Patches removed; Created on Aug 08, 200 This Distribution was loaded on Apr 19, 2010@08:19:47 with header of Mega Build 1 - CPRS 26 - PSN Patches removed; Created on Aug 08,2007@14:36:33 It consisted of the following Install(s): PSO*7.0*156 PSO*7.0*189 PSO*7.0*159 PSO*7.0*182 PSO*7.0*118 PSO*7.0*185 PSO*7.0*181 PSO*7.0*177 PSO*7.0*193 PSO*7.0*184 PSO*7.0*188 PSO*7.0*194 PSO*7.0*192 PSO*7.0*186 GMPL*2.0*28 OR*3.0*181 OR*3.0*214 PSS*1.0*79 PSJ*5.0*110 OR*3.0*213 PSU*3.0*32 PSU*3.0*24 PSU*3.0*34 PSU*3.0*31 PSU*3.0*35 PSS*1.0*82 PSS*1.0*85 Checking Install for Package PSO*7.0*156 Install Questions for PSO*7.0* PRESCRIPTION (Partial Definition) Note: You already have the 'PRESCRIPTION' File 59 OUTPATIENT SITE (Partial Definition) Note: You already have the 'OUTPATIENT SITE' File Checking Install for Package PSO*7.0*189 Install Questions for PSO*7.0*189 Checking Install for Package PSO*7.0*159 Install Questions for PSO*7.0*159 Checking Install for Package PSO*7.0*182 Install Questions for PSO*7.0*182 Checking Install for Package PSO*7.0*118 Install Questions for PSO*7.0*118 Checking Install for Package PSO*7.0*185 Install Questions for PSO*7.0*185 Checking Install for Package PSO*7.0*181 Install Questions for PSO*7.0*181 Checking Install for Package PSO*7.0*177 Install Questions for PSO*7.0* OUTPATIENT SITE (Partial Definition) Note: You already have the 'OUTPATIENT SITE' File. Checking Install for Package PSO*7.0*193 Install Questions for PSO*7.0*193 Checking Install for Package PSO*7.0*184 Install Questions for PSO*7.0*184 Checking Install for Package PSO*7.0*188 Install Questions for PSO*7.0*188 Checking Install for Package PSO*7.0*194 Install Questions for PSO*7.0*194 Checking Install for Package PSO*7.0*192 19

24 Install Questions for PSO*7.0* At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: Checking Install for Package PSO*7.0*186 Install Questions for PSO*7.0*186 Checking Install for Package GMPL*2.0*28 Install Questions for GMPL*2.0* At the Incoming Mail Groups: prmopt, type the Coordinator for Mail Group 'GMPL CODE SET VERSION UPDATES':, and then press Enter. 12. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO and then press Enter. The following appears: Checking Install for Package OR*3.0*181 Install Questions for OR*3.0* At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'ORCM CSV EVENT':, and then press Enter. 14. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: Checking Install for Package OR*3.0*214 Install Questions for OR*3.0*214 Checking Install for Package PSS*1.0*79 Install Questions for PSS*1.0*79 55 PHARMACY PATIENT (Partial Definition) Note: You already have the 'PHARMACY PATIENT' File PHARMACY SYSTEM (Partial Definition) Note: You already have the 'PHARMACY SYSTEM' File. Checking Install for Package PSJ*5.0*110 Install Questions for PSJ*5.0* NON-VERIFIED ORDERS (Partial Definition) Note: You already have the 'NON-VERIFIED ORDERS' File. 15. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'PSJ STAT NOW PENDING ORDER':, and then press Enter. 16. At the Incoming Mail Groups: prompt, type the Coordinator for Mail Group 'PSJ STAT NOW ACTIVE ORDER':, and then press Enter. The following appears: Checking Install for Package OR*3.0*213 Install Questions for OR*3.0*213 Checking Install for Package PSU*3.0*32 Install Questions for PSU*3.0*32 Checking Install for Package PSU*3.0*24 Install Questions for PSU*3.0*24 Checking Install for Package PSU*3.0*34 20

25 Install Questions for PSU*3.0*34 Checking Install for Package PSU*3.0*31 Install Questions for PSU*3.0*31 Checking Install for Package PSU*3.0*35 Will first run the Environment Check Routine, PSU35PRE Install Questions for PSU*3.0*35 Checking Install for Package PSS*1.0*82 Install Questions for PSS*1.0* At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//, type NO, and then press Enter. The following appears: Checking Install for Package PSS*1.0*85 Install Questions for PSS*1.0* At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. 19. At the Want KIDS to INHIBIT LOGONs during the install? YES// prompt, type NO, and then press Enter. 20. At the Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// prompt, type NO, and then press Enter. 21. Enter the device you want to print the Install messages. You can queue the install by entering a Q at the device prompt. Or, type a caret (^) to abort the install. The following appears: DEVICE: HOME// VIRTTUAL Install Started for PSO*7.0*156: Apr 19, 2010@08:50:33 Build Distribution Date: Sep 16, 2004 Installing Routines Apr 19, 2010@08:50:34 Apr 9, 2010@08:50:35 Installing INPUT TEMPLATE Installing HL LOGICAL LINK Installing HL7 APPLICATION PARAMETER Installing PROTOCOL Apr 19, 2010@08:50:35 Updating Routine file The following Routines were created during this install: PSOXZA PSOXZA1 PSOXZA2 PSOXZA3 PSOXZA4 PSOXZA5 PSOXZA6 PSOXZA7 PSOXZA8 Updating KIDS files PSO*7.0*156 Installed. Apr 19, 2010@08:50:35 21

26 Install Started for PSO*7.0*189: Apr 19, Build Distribution Date: Oct 20, 2004 Apr 19, Updating Routine file PSO*7.0*189 Installed. Apr 19, Install Started for PSO*7.0*159: Apr 19, Build Distribution Date: Sep 20, 2004 Apr 19, Updating Routine file PSO*7.0*159 Installed. Apr 19, Install Started for PSO*7.0*182: Apr 19, Build Distribution Date: Sep 14, 2004 Installing Routines Apr 19, Updating Routine file Updating KIDS files PSO*7.0*182 Installed. Apr 19, Install Started for PSO*7.0*118: Apr 19, Build Distribution Date: Oct 26, 2004 Apr 19, Running Post-Install Routine Creating Prescription file cross-references OK! Updating Routine file PSO*7.0*118 Installed. Apr 19, Install Started for PSO*7.0*185: Apr 19, Build Distribution Date: Aug 24, 2004 Apr 19, Updating Routine file PSO*7.0*185 Installed. Apr 19, Install Started for PSO*7.0*181: Apr 19, Build Distribution Date: Nov 15, 2004 Apr 19, PSO*7.0*181 Installed. Apr 19, Install Started for PSO*7.0*177: Apr 19, Build Distribution Date: Sep 12,

27 Apr 19, Apr 19, PSO*7.0*177 Installed. Apr 19, Install Started for PSO*7.0*193: Apr 19, Build Distribution Date: Dec 01, 2004 Apr 19, PSO*7.0*193 Installed. Apr 19, PSO*7.0*184 Install Started for PSO*7.0*184: Apr 19, Build Distribution Date: Oct 28, 2004 Apr 19, PSO*7.0*184 Installed. Apr 19, Install Started for PSO*7.0*188: Apr 19, Build Distribution Date: Oct 15, 2004 Apr 19, PSO*7.0*188 Installed. Apr 19, Install Started for PSO*7.0*194: Apr 19, Build Distribution Date: Feb 03, 2005 Apr 19, PSO*7.0*194 Installed. Apr 19, Install Started for PSO*7.0*192: Apr 19, Build Distribution Date: Jan 03, 2005 Apr 19, Installing OPTION Apr 19, PSO*7.0*192 Installed. Apr 19, Install Started for PSO*7.0*186: Apr 19, Build Distribution Date: Jan 24,

28 Apr 19, PSO*7.0*186 Installed. Apr 19, Install Started for GMPL*2.0*28: Apr 19, Build Distribution Date: Jul 31, 2003 Apr 19, Installing MAIL GROUP Installing PROTOCOL PROTOCOL ICD CODE UPDATE EVENT Lookup failed, NO Action Taken. Installing OPTION Apr 19, GMPL*2.0*28 Installed. Apr 19, Install Started for OR*3.0*181: Apr 19, Build Distribution Date: Jul 31, 2003 Apr 19, Installing MAIL GROUP Installing PROTOCOL PROTOCOL ICD CODE UPDATE EVENT Lookup failed, NO Action Taken. Installing OPTION Apr 19, OR*3.0*181 Installed. Apr 19, Install Started for OR*3.0*214: Apr 19, Build Distribution Date: Jan 16, 2004 Apr 19, OR*3.0*214 Installed. Apr 19, Install Started for PSS*1.0*79: Apr 19, Build Distribution Date: Sep 08, 2004 Apr 19, Running Pre-Install Routine: Creating Pharmacy Patient cross-references. Apr 19, The following Routines were created during this install: PSSJXR PSSJXR1 PSSJXR10 PSSJXR11 PSSJXR12 24

29 PSSJXR13 PSSJXR14 PSSJXR15 PSSJXR16 PSSJXR17 PSSJXR18 PSSJXR19 PSSJXR2 PSSJXR20 PSSJXR21 PSSJXR22 PSSJXR23 PSSJXR24 PSSJXR25 PSSJXR26 PSSJXR27 PSSJXR28 PSSJXR29 PSSJXR3 PSSJXR30 PSSJXR31 PSSJXR32 PSSJXR4 PSSJXR5 PSSJXR6 PSSJXR7 PSSJXR8 PSS JXR9 PSS*1.0*79 Installed. Apr 19, Install Started for PSJ*5.0*110: Apr 19, Build Distribution Date: Sep 08, 2004 Apr 19, Apr 19, Installing MAIL GROUP Apr 19, The following Routines were created during this install: PSGXR3 PSGXR31 PSGXR310 PSGXR311 PSGXR312 PSGXR32 PSGXR33 PSGXR34 PSGXR35 PSGXR36 PSGXR37 PSGXR38 PSGXR39 PSJ*5.0*110 Installed. Apr 19, Install Started for OR*3.0*213: Apr 19, 25

30 Build Distribution Date: Sep 08, 2004 Apr 19, OR*3.0*213 Installed. Apr 19, Install Started for PSU*3.0*32: Apr 19, Build Distribution Date: Dec 11, 2003 Apr 19, PSU*3.0*32 Installed. Apr 19, Install Started for PSU*3.0*24: Apr 19, Build Distribution Date: Jul 19, 2004 Apr 19, PSU*3.0*24 Installed. Apr 19, Install Started for PSU*3.0*34: Apr 19, Build Distribution Date: Sep 08, 2004 Apr 19, PSU*3.0*34 Installed. Apr 19, Install Started for PSU*3.0*31: Apr 19, Build Distribution Date: Oct 30, 2003 Apr 19, PSU*3.0*31 Installed. Apr 19, Install Started for PSU*3.0*35: Apr 19, Build Distribution Date: Dec 09, 2004 Apr 19, PSU*3.0*35 Installed. Apr 19, Install Started for PSS*1.0*82: Apr 19, Build Distribution Date: May 26, 2004 Apr 19, Installing HL7 APPLICATION PARAMETER 26

31 Installing PROTOCOL Installing OPTION Apr 19, PSS*1.0*82 Installed. Apr 19, Install Started for PSS*1.0*85: Apr 19, Build Distribution Date: Sep 30, 2004 Apr 19, PSS*1.0*85 Installed. Apr 19, 5.3 Mega Build II (ehr_ mb2) 1. At the Select OPTION NAME: prompt, type INS,MENU, and then press Enter. The following appears: 1 INSTALLATION XPD INSTALLATION MENU Installation 2 INSURER FILE MENU AG TM INS MENU Insurer File Menu 3 INSURER FILE MENU ABMD TM INS MENU Insurer File Menu Select 1:3: 2. Select 1 XPD INSTALLATION MENU Installation, and then press Enter. The following appears: 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. Select 1 Load a Distribution, and then press Enter. 4. At the Enter a Host File: prompt, type YOUR DIRECTORY\ehr_ mb2.k, and then press Enter. Note: The location of the ehr_ mb2.k file may not be in this folder. This is determined for each installation. The following appears: KIDS Distribution saved on Feb 26, 2010@08:22:31 Comment: CPRS 27 Mega Build 2 This Distribution contains Transport Globals for the following Package(s): 27

32 OR*3.0*200 OR*3.0*194 OR*3.0*225 OR*3.0*157 OR*3.0*227 OR*3.0*217 PSS*1.0*81 PSS*1.0*89 PSS*1.0*91 IB*2.0*315 SR*3.0*86 SR*3.0*41 SR*3.0*80 SR*3.0*96 SR*3.0*99 SR*3.0*105 SR*3.0*101 SR*3.0*116 SR*3.0*123 SR*3.0*121 SR*3.0*118 SR*3.0*124 SR*3.0*122 SR*3.0*126 SR*3.0*100 SR*3.0*128 SR*3.0*129 SR*3.0*132 SR*3.0*125 SR*3.0*135 SR*3.0*127 SR*3.0*130 SR*3.0*136 SR*3.0*138 SR*3.0*137] SR*3.0*131 SR*3.0*134 SR*3.0*141 SR*3.0*140 SR*3.0*143 SR*3.0*119 SR*3.0*145 SR*3.0*147 SR*3.0*149 SR*3.0*150 SR*3.0*148 SR*3.0*151 SR*3.0*155 SR*3.0*142 SR*3.0*146 SR*3.0*152 SR*3.0*144 SR*3.0*156 SR*3.0*154 SR*3.0*158 SR*3.0*153 SR*3.0*157 GMRY*4.0*6 FH*5.0*40 FH*5.0*41 GMRC*3.0*33 28

33 MRC*3.0*32 GMRC*3.0*35 GMRC*3.0*41 GMRC*3.0*40 GMRC*3.0*38 GMRC*3.0*43 GMRC*3.0*37 GMRC*3.0*39 GMRC*3.0*45 GMRC*3.0*49 GMRC*3.0*52 GMRC*3.0*51 GMRC*3.0*42 GMRV*5.0*12 GMRV*5.0*9 GMRV*5.0*13 GMRV*5.0*14 GMRV*5.0*3 GMRV*5.0*17 GMRV*5.0*18 GMPL*2.0*27 GMPL*2.0*31 GMPL*2.0*33 MC*2.3*39 PSD*3.0*60 PSD*3.0*63 PSD*3.0*59 PSD*3.0*66 PSD*3.0*62 PSD*3.0*65 PSD*3.0*64 PSD*3.0*67 NUR*4.0*41 NUR*4.0*40 NUR*4.0*42 MC*2.3*42 GMRV*5.0*11 GMRV*5.0*19 GMRV*5.0*22 GMRV*5.0*25 GMRV*5.0*23 Distribution OK! 5. At the Want to Continue with Load? YES// prompt, type YES, and then press Enter. The following appears: Loading Distribution... OR*3.0*200 OR*3.0*194 OR*3.0*225 OR*3.0*157 OR*3.0*227 OR*3.0*217 PSS*1.0*81 PSS*1.0*89 PSS*1.0*91 IB*2.0*315 SR*3.0*86 SR*3.0*41 SR*3.0*80 29

34 SR*3.0*96 SR*3.0*99 SR*3.0*105 SR*3.0*101 SR*3.0*116 SR*3.0*123 SR*3.0*121 SR*3.0*118 SR*3.0*124 SR*3.0*122 SR*3.0*126 Build SR*3.0*100 has an Environmental Check Routine 6. At the Want to RUN the Environment Check Routine? YES// prompt, type YES, and then press Enter. The following appears: SR*3.0*100 Will first run the Environment Check Routine, SR100ENV SR*3.0*128 SR*3.0*129 SR*3.0*132 SR*3.0*125 SR*3.0*135 SR*3.0*127 SR*3.0*130 SR*3.0*136 SR*3.0*138 SR*3.0*137 SR*3.0*131 SR*3.0*134 SR*3.0*141 SR*3.0*140 SR*3.0*143 SR*3.0*119 SR*3.0*145 SR*3.0*147 SR*3.0*149 SR*3.0*150 SR*3.0*148 SR*3.0*151 SR*3.0*155 SR*3.0*142 SR*3.0*146 SR*3.0*152 SR*3.0*144 SR*3.0*156 SR*3.0*154 SR*3.0*158 SR*3.0*153 SR*3.0*157 GMRY*4.0*6 FH*5.0*40 FH*5.0*41 GMRC*3.0*33 GMRC*3.0*32 GMRC*3.0*35 GMRC*3.0*41 GMRC*3.0*40 GMRC*3.0*38 GMRC*3.0*43 30

35 GMRC*3.0*37 GMRC*3.0*39 GMRC*3.0*45 GMRC*3.0*49 GMRC*3.0*52 GMRC*3.0*51 GMRC*3.0*42 Will first run the Environment Check Routine, GMRCYP42 No conflicts with service being filed. GMRV*5.0*12 GMRV*5.0*9 Will first run the Environment Check Routine, GMRVP59 GMRV*5.0*13 GMRV*5.0*14 GMRV*5.0*3 GMRV*5.0*17 GMRV*5.0*18 GMPL*2.0*27 GMPL*2.0*31 GMPL*2.0*33 MC*2.3*39 PSD*3.0*60 PSD*3.0*63 PSD*3.0*59 PSD*3.0*66 PSD*3.0*62 PSD*3.0*65 PSD*3.0*64 PSD*3.0*67 NUR*4.0*41 NUR*4.0*40 NUR*4.0*42 MC*2.3*42 GMRV*5.0*11 GMRV*5.0*19 GMRV*5.0*22 GMRV*5.0*25 GMRV*5.0*23 7. At the INSTALL NAME: prompt, type OR*3.0*200 to install this Distribution. The following appears: 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 8. At the Select Installation Option: prompt, Type 6: INSTALL PACKAGE(S), and then press Enter. 9. At the Select INSTALL NAME: prompt, type OR*3.0*200. The following appears: Loaded from Distribution 31

36 Loaded from Distribution => CPRS 27 Mega Build 2; Created on Feb 26, This Distribution was loaded on Apr 22, with header of CPRS 27 Mega Build 2 ;Created on Feb 26, 2010@08:22:31 It consisted of the following Install(s): OR*3.0*200 OR*3.0*194 OR*3.0*225 OR*3.0*157 OR*3.0*227 OR*3.0*217 PSS*1.0*81 PSS*1.0*89 PSS*1.0*91 IB*2.0*315 SR*3.0*86 SR*3.0*41 SR*3.0*80 SR*3.0*96 SR*3.0*99 SR*3.0*105 SR*3.0*101 SR*3.0*116 SR*3.0*123 SR*3.0*121 SR*3.0*118 SR*3.0*124 SR*3.0*122 SR*3.0*126 SR*3.0*100 SR*3.0*128 SR*3.0*129 SR*3.0*132 SR*3.0*125 SR*3.0*135 SR*3.0*127 SR*3.0*130 SR*3.0*136 SR*3.0*138 SR*3.0*137 SR*3.0*131 SR*3.0*134 SR*3.0*141 SR*3.0*140 SR*3.0*143 SR*3.0*119 SR*3.0*145 SR*3.0*147 SR*3.0*149 SR*3.0*150 SR*3.0*148 SR*3.0*151 SR*3.0*155 SR*3.0*142 SR*3.0*146 SR*3.0*152 SR*3.0*144 SR*3.0*156 SR*3.0*154 SR*3.0*158 SR*3.0*153 SR*3.0*157 GMRY*4.0*6 FH*5.0*40 FH*5.0*41 GMRC*3.0*33 GMRC*3.0*32 GMRC*3.0*35 GMRC*3.0*41 GMRC*3.0*40 GMRC*3.0*38 GMRC*3.0*43 GMRC*3.0*37 GMRC*3.0*39 GMRC*3.0*45 GMRC*3.0*49 GMRC*3.0*52 GMRC*3.0*51 GMRC*3.0*42 GMRV*5.0*12 GMRV*5.0*9 GMRV*5.0*13 GMRV*5.0*14 GMRV*5.0*3 GMRV*5.0*17 GMRV*5.0*18 GMPL*2.0*27 GMPL*2.0*31 GMPL*2.0*33 MC*2.3*39 PSD*3.0*60 PSD*3.0*63 PSD*3.0*59 PSD*3.0*66 PSD*3.0*62 PSD*3.0*65 PSD*3.0*64 PSD*3.0*67 NUR*4.0*41 NUR*4.0*40 NUR*4.0*42 MC*2.3*42 GMRV*5.0*11 GMRV*5.0*19 GMRV*5.0*22 GMRV*5.0*25 GMRV*5.0*23 Checking Install for Package OR*3.0*200 Install Questions for OR*3.0*200 Checking Install for Package OR*3.0*194 Install Questions for OR*3.0*194 Checking Install for Package OR*3.0*225 Install Questions for OR*3.0*225 Checking Install for Package OR*3.0*157 Install Questions for OR*3.0*157 Checking Install for Package OR*3.0*227 Install Questions for OR*3.0*227 Checking Install for Package OR*3.0*217 Install Questions for OR*3.0* At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: Checking Install for Package PSS*1.0*81 Install Questions for PSS*1.0*81 Checking Install for Package PSS*1.0*89 Install Questions for PSS*1.0*89 Checking Install for Package PSS*1.0*91 Install Questions for PSS*1.0*91 Checking Install for Package IB*2.0*315 Install Questions for IB*2.0*315 Checking Install for Package SR*3.0*86 Install Questions for SR*3.0*86 Checking Install for Package SR*3.0*41 Install Questions for SR*3.0*41 Checking Install for Package SR*3.0*80 Install Questions for SR*3.0*80 Checking Install for Package SR*3.0*96 Install Questions for SR*3.0*96 Checking Install for Package SR*3.0*99 Install Questions for SR*3.0*99 32

37 Checking Install for Package SR*3.0*105 Install Questions for SR*3.0*105 Checking Install for Package SR*3.0*101 Install Questions for SR*3.0*101 Checking Install for Package SR*3.0*116 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*123 Install Questions for SR*3.0*123 Checking Install for Package SR*3.0*121 Install Questions for SR*3.0*121 Checking Install for Package SR*3.0*118 Install Questions for SR*3.0*118 Checking Install for Package SR*3.0*124 Install Questions for SR*3.0*124 Checking Install for Package SR*3.0*122 Install Questions for SR*3.0*122 Checking Install for Package SR*3.0*126 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*100 Will first run the Environment Check Routine, SR100ENV Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. 133 SURGERY SITE PARAMETERS (Partial Definition) Note: You already have the 'SURGERY SITE PARAMETERS' File. 11. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. 12. At the Do you have the completed pre-installation worksheet? NO// prompt, type YES, and then press Enter. New Site Parameter: Answer the following question to define the default site parameter related to the use of the Anesthesia Report at your facility. This response will be stored for each division defined in the SURGERY SITE PARAMETERS file (#133) and may be updated after this patch is installed. 13. At the Does this facility use the Anesthesia Report? NO// prompt, type NO, and then press Enter. Starting Date for Reports to be Signed Electronically during the post-installation process, all reports for completed cases with an operation date on or after the date selected will be identified to be signed electronically and stub entries will be created in TIU. 33

38 14. At the Enter starting date for reports to be signed electronically: prompt, type TODAY//(APR 22, 2012), and then press Enter. At this point, you may make reports for historical cases viewable through CPRS. See Appendix A: for details. 15. At the Do you want to move reports during the patch installation? prompt, type NO// and then press Enter 16. Press Enter to continue. The following appears: Checking Install for Package SR*3.0*128 Install Questions for SR*3.0*128 Checking Install for Package SR*3.0*129 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File ATTENDING CODES (including data) Checking Install for Package SR*3.0*132 Install Questions for SR*3.0* At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: Checking Install for Package SR*3.0*125 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File PERIOPERATIVE OCCURRENCE CATEGORY (including data) Note: You already have the 'PERIOPERATIVE OCCURRENCE CATEGORY' File. I will OVERWRITE your data with mine. 18. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: Checking Install for Package SR*3.0*135 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*127 Install Questions for SR*3.0*127 Checking Install for Package SR*3.0*130 Install Questions for SR*3.0*130 Checking Install for Package SR*3.0*136 Install Questions for SR*3.0*136 Checking Install for Package SR*3.0*138 Install Questions for SR*3.0*138 Checking Install for Package SR*3.0*137 Install Questions for SR*3.0*137 Checking Install for Package SR*3.0*131 Install Questions for SR*3.0*131 Checking Install for Package SR*3.0*134 Install Questions for SR*3.0*134 34

39 130 SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*141 Install Questions for SR*3.0*141 Checking Install for Package SR*3.0*140 Install Questions for SR*3.0*140 Checking Install for Package SR*3.0*143 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*119 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. 133 SURGERY SITE PARAMETERS (Partial Definition) Note: You already have the 'SURGERY SITE PARAMETERS' File SURGERY WAITING LIST (Partial Definition) Note: You already have the 'SURGERY WAITING LIST' File. Checking Install for Package SR*3.0*145 Install Questions for SR*3.0*145 Checking Install for Package SR*3.0*147 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*149 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*150 Install Questions for SR*3.0* SURGERY SITE PARAMETERS (Partial Definition) Note: You already have the 'SURGERY SITE PARAMETERS' File. Checking Install for Package SR*3.0*148 Install Questions for SR*3.0*148 Checking Install for Package SR*3.0*151 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. Checking Install for Package SR*3.0*155 Install Questions for SR*3.0*155 Checking Install for Package SR*3.0*142 Install Questions for SR*3.0* SURGERY (Partial Definition) Note: You already have the 'SURGERY' File. 136 SURGERY PROCEDURE/DIAGNOSIS CODES *BUT YOU ALREADY HAVE 'SURGERY TRANSCRIPTION' AS FILE #136! 19. At the Shall I write over your SURGERY TRANSCRIPTION File? prompt, type YES//, and then press Enter. 20. At the Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// prompt, type NO, and then press Enter. The following appears: 35