============================================================================= Run Date: NOV 30, 2006 Designation: TIU*1*211 Package : TIU - TEXT INTEGRATION UTILITIES Priority: Mandatory Version : 1 SEQ #205 Status: Released Compliance Date: DEC 31, 2006 ============================================================================= Associated patches: (v)TIU*1*162 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*173 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*182 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*184 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*186 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*194 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*208 <<= must be installed BEFORE `TIU*1*211' (v)XU*8*407 <<= must be installed BEFORE `TIU*1*211' (v)HDI*1*4 <<= must be installed BEFORE `TIU*1*211' (v)TIU*1*218 <<= must be installed BEFORE `TIU*1*211' Subject: TIU DATA STANDARDIZATION VUID PATCH Category: - Data Dictionary - Routine - Enhancement (Mandatory) - Other Description: ============ This patch introduces the VHA Enterprise Document Type Ontology and a mapping utility to assist CACs with the process of mapping Local TIU Titles (from the TIU DOCUMENT DEFINITION file (#8925.1)) to VHA Enterprise Standard Titles (from the TIU VHA ENTERPRISE STANDARD TITLE file #8926.1). It also assures that the dialogs for editing TIU Document Definitions will prompt for the mapping, and that all views of TIU Documents (e.g., Browse & Detailed Display) as well as any printed formats, will include the VHA Enterprise Standard Title in addition to the Local TIU Title. The standardized files that are being introduced by patch TIU*1*211 include: 8926.1 TIU VHA ENTERPRISE STANDARD TITLE 8926.2 TIU LOINC SUBJECT MATTER DOMAIN 8926.3 TIU LOINC ROLE 8926.4 TIU LOINC SETTING 8926.5 TIU LOINC SERVICE 8926.6 TIU LOINC DOCUMENT TYPE In addition, the TIU STATUS file (#8925.6) will be standardized per VHA Directive 2005-044. Under this directive, all of the files included in the patch will be "locked down" by Data Standardization (DS). Local modification of the file definitions (i.e. data dictionaries) shall not be allowed. All additions, changes and deletions to entries in the files shall be done by Enterprise Reference Terminology (ERT) using the Master File Server (MFS), provided by Common Services (CS). Creating and/or editing locally defined fields in the files shall not be permitted. Use of locally defined fields that were created prior to VHA Directive 2005-044 shall not be supported. Once the TIU*1*211 patch has been installed, the Post-install routine calls an Application Program Interface (API) in the Health Data Informatics (HDI) package which creates an XML file for each of the files being standardized. The XML file includes the Term/Concept (.01 Field) for each entry from each of the files. Each XML file is then forwarded to the central server (FORUM). On the FORUM server, each XML file is compared with the standardized data from Enterprise Terminology Services (ETS), and FORUM sets a VHA Unique Identifier (VUID) value for every entry. In the case of the TIU STATUS File, the typical protocol for standardizing a pre-existing VistA file will be observed. i.e., The data received from the facility is modified as follows: (1) FORUM sets a VHA Unique Identifier (VUID) value for every matching entry; (2) local entries are assigned a VUID from a block of available numbers, and identified as inactive terms; and (3) duplicate entries are identified as inactive terms. However, given the nature and usage of this file, we aren't expecting to encounter any local additions or modifications. Since the other standard files for this application are all being introduced with this patch, are locked-down from their inception, and are identical at all facilities, the resolution of local and duplicate terms described above is unnecessary. The XML File, with the terms and their corresponding VUIDs, is then passed back to the facility. The HDI package on the Facility Server will use the XML file to update the corresponding VistA files. Once the Facility's VistA files have been updated, a MailMan mail message is automatically sent to the Enterprise Reference Terminology (ERT) team. The ERT team will manually initiate a Master File Server (MFS) push through the Vitria Interface Engine (VIE), which will complete the update with standardized data. This ERT update relies on VUIDs as a key for inserting the standardized data. At this point, the facility is considered standardized for that particular VistA file. Once the Facility's VistA files are standardized, the Health Data Repository (HDR) Implementation managers are notified automatically via another MailMan message. The complementary Health Summary patch (GMTS*2.7*81), which is described separately, and assures that the VHA Enterprise Standard Titles of TIU Documents will be displayed, along with their Local Titles, in the HS Components for Progress Notes and Discharge Summaries, will be installed along with the current patch, and is included in the same KIDS distribution. REMEDY TICKETS: =============== No open Remedy tickets are resolved by this patch. E3Rs: ===== No E3Rs are satisfied by this patch. Build Components: ================ Data Dictionaries: ================== UP SEND DATA USER DATE SEC. COMES SITE RSLV OVER FILE # NAME DD CODE W/FILE DATA PTS RIDE -------------------------------------------------------------------------- 8925 TIU DOCUMENT YES NO NO NO Partial DD: subDD: 8925 fld: 89261 This computed field allows calls to FileMan Utilities (e.g. DIQ) to resolve the VHA ENTERPRISE STANDARD TITLE to which the local title is mapped. 8925.1 TIU DOCUMENT DEFINITION YES NO NO NO Partial DD: subDD: 8925.1 fld: 1501 fld: 1502 fld: 1503 Three new fields are added to support the mapping of Local TIU Titles to VHA Enterprise Standard Titles, and the tracking of the who attempted to map a title and when. 8925.6 TIU STATUS YES YES NO OVER NO NO Per VHA Directive 2005-044, this file has been "locked down" by Data Standardization (DS). The file definition (i.e. data dictionary) shall not be modified. All additions, changes and deletions to entries in the file shall be done by Enterprise Reference Terminology (ERT) using the Master File Server (MFS), provided by Common Services (CS). Creating and/or editing locally defined fields in the file are not permitted. Use of locally defined fields that were created prior to the VHA Directive's 2005-044 effective date shall not be supported. 8926.1 TIU VHA ENTERPRISE YES YES YES OVER NO NO STANDARD TITLE This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.2 TIU LOINC SUBJECT YES YES YES OVER NO NO MATTER DOMAIN This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.3 TIU LOINC ROLE YES YES YES OVER NO NO This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.4 TIU LOINC SETTING YES YES YES OVER NO NO This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.5 TIU LOINC SERVICE YES YES YES OVER NO NO This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.6 TIU LOINC DOCUMENT TYPE YES YES YES OVER NO NO This file contains the VistA instance of the VHA Enterprise Standard Document Title Ontology. It allows for the assignment of VHA Unique Identifiers (VUIDS) to each Standard Title. The file will be distributed as "locked down," in compliance with the requirements of Data Standardization (DS). 8926.72 TIU LOINC SMD SYNONYMS YES YES YES OVER NO NO This file supports and facilitates the mapping of local titles to LOINC Standard Titles, by simplifying the correct association between partial names and the LOINC Standard Subject Matter Domains. Unlike the TIU LOINC SUBJECT MATTER DOMAIN File (#8926.2), this file may be locally extended. 8926.73 TIU LOINC ROLE SYNONYMS YES YES YES OVER NO NO This file supports and facilitates the mapping of local titles to LOINC Standard Titles, by simplifying the correct association between partial names and the LOINC Standard Roles. Unlike the TIU LOINC ROLE File (#8926.3), this file may be locally extended. 8926.74 TIU LOINC SETTING YES YES YES OVER NO NO SYNONYMS This file supports and facilitates the mapping of local titles to LOINC Standard Titles, by simplifying the correct association between partial names and the LOINC Standard Settings. Unlike the TIU LOINC SETTING File (#8926.4), this file may be locally extended. 8926.75 TIU LOINC SERVICE YES YES YES OVER NO NO SYNONYMS This file supports and facilitates the mapping of local titles to LOINC Standard Titles, by simplifying the correct association between partial names and the LOINC Standard Services. Unlike the TIU LOINC SERVICE File (#8926.5), this file may be locally extended. 8926.76 TIU LOINC DOCUMENT YES YES YES OVER NO NO TYPE SYNONYMS This file supports and facilitates the mapping of local titles to LOINC Standard Titles, by simplifying the correct association between partial names and the LOINC Standard Document Types. Unlike the TIU LOINC DOCUMENT TYPE file (#8926.6), this file may be locally extended. Option: ====== TIU IRM MAINTENANCE MENU USE AS LINK FOR MENU ITEMS This long-standing menu of configuration management options is simply being extended by this patch to include a sub-menu for mapping activities. TIU MAP ALL LOCAL TITLES SEND TO SITE This option allows CACs to map ALL local titles to the VHA Enterprise Standard Document Title Ontology, by iterating through all of the ACTIVE titles defined for the station. This is a necessary prerequisite to migrating document management to the HDR. TIU MAP SELECTED LOCAL TITLES SEND TO SITE This option allows CACs to map specific local titles to the VHA Enterprise Standard Document Title Ontology, by selecting the ACTIVE title in question. The user may also select a previously mapped title, and re-map it, if necessary. TIU MAP TITLES MENU SEND TO SITE This option allows the Clinical Coordinator or IRM Application Specialist to map LOCAL TIU Titles to VHA Enterprise Standard Titles. TIU MAPPING DOC TYPE SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for the Document Type Axis of the VHA Enterprise Standard Title Ontology. TIU MAPPING ROLE SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for the Role Axis of the VHA Enterprise Standard Title Ontology. TIU MAPPING SERVICE SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for the Service Axis of the VHA Enterprise Standard Title Ontology. TIU MAPPING SETTING SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for the Setting Axis of the VHA Enterprise Standard Title Ontology. TIU MAPPING SMD SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for the Subject Matter Domain Axis of the VHA Enterprise Standard Title Ontology. TIU MAPPING SYNONYMS SEND TO SITE This option allows the CAC (or designee) to extend the list of synonyms for any of the VHA Enterprise Standard Title Axis (i.e., Subject Matter Domain, Role, Setting, Service, or Document Type). TIU MAPPING WORKBENCH SEND TO SITE This option allows the user to generate a list of Local TIU Titles by mapping status, user, and date range (where applicable), and to select titles for mapping/re-mapping to VHA Enterprise Standard Titles. Protocol: ======== TIU ACTION CHANGE VIEW MAPPING SEND TO SITE Allows modification of the current list of mapped or unmapped titles to include either UNMAPPED, MAPPED, FAILED attempts, or ALL Active Titles for a specified user and time range (where applicable). TIU ACTION MAP TITLES SEND TO SITE Allows mapping of Local TIU Titles to VHA Enterprise Standard Titles using the full features of the Mapper utility to assist in the choice. TIU ACTION MAP TITLES DIRECT SEND TO SITE Allows users who know which VHA Enterprise Standard Title should be associated with a given local title to map the Local Title directly, without the assistance of the Mapper. TIU ACTION MENU MAPPING SEND TO SITE Menu of actions which may be executed to map local TIU Titles to VHA Enterprise Standard Titles. TIU ACTION QUIT ATTACH TO MENU Allows user to quit the current menu level. TIU ACTION SEARCH LIST ATTACH TO MENU Allows users to search list of Documents for a text string (word, phrase, or partial word) from current position to the end of the list. Upon reaching the end of the last page of the list, the user will be asked whether to continue the search from the beginning of the list through the origin of the search. List Template: ============= TIU REVIEW UNMAPPED TITLES SEND TO SITE List Template to support a familiar List Manager UI for CACs to use for mapping Local TIU Titles to VHA Enterprise Standard Titles. Host File & Documentation: ========================= This patch will be available only as a host file. Host file name: TIU1_0P211.KID Builds: TIU*1.0*211 GMTS*2.7*81 Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to FTP the files from download.vista.med.va.gov. This transmits the files from the first available FTP server. Sites may also elect to retrieve software directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov This documentation will be in the form of an Adobe Acrobat file. Documentation can also be found at: http://www.va.gov/vdl Below is a list of the files related to this patch that will be needed and available via the FTP sites listed above. File Description File Name FTP Mode ============================================================= TIU Technical Manual TIUTM.PDF (binary) Health Summary User Manual HSUM_2_7_UM.PDF (binary) Installation Instructions: ========================= This patch should be loaded during non-peak hours to minimize disruption to users, who can remain on the system during installation. Installation will take less than 2 minutes. 1. Use the 'Load a Distribution' option on the KIDS installation menu. When prompted to enter a host file, type in TIU_1_0P211.KID. 2. On the KIDS menu under the 'INSTALLATION' menu, use the following options as desired: Print Transport Global Compare Transport Global to Current System Verify checksums in Transport Global Backup a Transport Global 3. On the KIDS menu under the 'INSTALLATION' menu, use the following options to install the patch: Install Package (TIU*1.0*211) 4. When prompted, "Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES//", respond NO. 5. When prompted "Want KIDS to INHIBIT LOGON's during the install? YES//", respond "NO". 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond YES, and DISABLE the TIU* Options and Protocols. 7. When prompted "Delay Install (Minutes): (0-60) 0//" respond "0" 8. After the package has been installed successfully, sites should delete the post-install routine, TIUPS211. Post Installation Instructions: ============================== No special post-installation steps need to be completed on your part. Routine Summary: =============== The following is a list of the routines included in this patch. The second line of each of these routines will look like: ;;1.0;TEXT INTEGRATION UTILITIES;**[patch list]**;Jun 20, 1997 CHECK^XTSUMBLD Routine Name Before Patch After Patch Patch List ============ ============ =========== ========== TIUPS211 535665 211 TIUBR 12153374 12431980 32,87,93,58,100,162,112,173,208 211 TIUFC1 19039288 19477595 211 TIUFD 13638982 13680859 14,184,211 TIUFD2 12268103 12510483 13,64,211 TIUFHA3 18982597 19472015 13,64,211 TIUFIX 5187617 5199225 131,211 TIUFL 8588216 8659514 14,184,211 TIUFLD 13416565 13578015 14,77,184,211 TIUFLF1 16283676 16925628 2,12,17,64,211 TIUFLF6 5637051 6135755 13,211 TIUGBR 2800961 2899074 100,211 TIULA2 15564820 15663672 1,50,86,93,61,100,116,143,211 TIULAPI 2326288 2377499 211 TIULAPIC 7018775 7135407 83,100,121,211 TIULAPIS 6326709 6389250 100,121,211 TIULQ 5716373 5729383 19,100,157,211 TIUMAP 15835281 211 TIUMAP1 19025468 211 TIUMAP2 4468318 211 TIUMAPR 1664723 211 TIUMLIST 10146174 211 TIUMSYN 1707931 211 TIUPRDS1 7186172 7494860 55,52,162,211 TIUPRPN1 12301238 12545757 45,52,87,100,162,182,211 TIUSRV 12499047 12690839 1,19,28,87,61,100,109,113,112 184,211 TIUSRVLO 14350345 14491204 1,15,19,63,108,122,181,194,211 TIUSRVR1 9762192 10140619 19,32,87,89,100,109,112,173,186 208,211 TIUSRVR2 8345231 8369941 100,109,162,211 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: TIUBR Before: B45272783 After: B47301506 **32,87,93,58,100,162,112,173, 208,211** Routine Name: TIUFC1 Before: B33248572 After: B33827579 **211** Routine Name: TIUFD Before: B41470416 After: B41532075 **14,184,211** Routine Name: TIUFD2 Before: B22159389 After: B23047510 **13,64,211** Routine Name: TIUFHA3 Before: B44698275 After: B47490712 **13,64,211** Routine Name: TIUFIX Before: B12351786 After: B12373810 **131,211** Routine Name: TIUFL Before: B34624803 After: B34758795 **14,184,211** Routine Name: TIUFLD Before: B38075587 After: B38657278 **14,77,184,211** Routine Name: TIUFLF1 Before: B39971439 After: B44650573 **2,12,17,64,211** Routine Name: TIUFLF6 Before: B11714184 After: B13508572 **13,211** Routine Name: TIUGBR Before: B6771191 After: B6925721 **100,211** Routine Name: TIULA2 Before: B53053546 After: B53640549 **1,50,86,93,61,100,116,143,211** Routine Name: TIULAPI Before: B3224015 After: B3282376 **211** Routine Name: TIULAPIC Before: B11186937 After: B11325994 **83,100,121,211** Routine Name: TIULAPIS Before: B11357069 After: B11436185 **100,121,211** Routine Name: TIULQ Before: B15406577 After: B15422187 **19,100,157,211** Routine Name: TIUMAP Before: n/a After: B54446041 **211** Routine Name: TIUMAP1 Before: n/a After: B68841316 **211** Routine Name: TIUMAP2 Before: n/a After: B8704484 **211** Routine Name: TIUMAPR Before: n/a After: B3199586 **211** Routine Name: TIUMLIST Before: n/a After: B37016435 **211** Routine Name: TIUMSYN Before: n/a After: B2242263 **211** Routine Name: TIUPRDS1 Before: B15965116 After: B16962491 **55,52,162,211** Routine Name: TIUPRPN1 Before: B47306640 After: B48298695 **45,52,87,100,162,182,211** Routine Name: TIUPS211 Before: n/a After: B689565 **211** Routine Name: TIUSRV Before: B48467254 After: B49262888 **1,19,28,87,61,100,109,113,112, 184,211** Routine Name: TIUSRVLO Before: B67072677 After: B68658317 **1,15,19,63,108,122,181,194,211** Routine Name: TIUSRVR1 Before: B34950114 After: B37035812 **19,32,87,89,100,109,112,173, 186,208,211** Routine Name: TIUSRVR2 Before: B30785703 After: B30852988 **100,109,162,211** ============================================================================= User Information: Entered By : RUSSELL,JOEL Date Entered : FEB 09, 2006 Completed By: BASKETT,BARBARA J Date Completed: NOV 29, 2006 Released By : CHRISTENSEN,LINDA L Date Released : NOV 30, 2006 ============================================================================= Packman Mail Message: ===================== No routines included