NAME UMLS::Interface CHANGES Changes from version 0.25 to 0.27 1. Added a --verbose option will print out path information to a file rather than having this be done automatically. This will reduce the amount of storage space required to hold the path information for a given set of sources and relations. Changes from version 0.23 to 0.25 1. Fixed mysql error that was occuring in UMLS-Interface DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 at /usr/local/share/perl/5.10.0/UMLS/Interface.pm line 1063, line 2. This was also happening on line 1066 - both should be fixed now. 2. Updated INSTALL documentation - nothing major just some clean up 3. Added a --forcerun option which will bypass any questions about whether or not you would like to set up an index on a specified set of relations/sources 4. Updated the documentation of the programs in the util/ directory Changes from version 0.21 to 0.23 1. Added a getRelation function which returns all the possible relations in the MRREL file given a specified CUI and source. There is a corresponding util program getRelation.pl to show how this is used. 2. Modified checking the existance of the UMLS tables. Before it was expecting the table names to be all capatalized but now they can be in lower case as well. Changes from version 0.19 to 0.21 1. Added check to see if program files exist prior to removing them just in case they don't exist an error isn't going to display 2. Had an error in getCuiDef.pl when the input was a term. This has been fixed. 3. Modified the upper level taxonomy to be written to tables in its appropriate database. 4. Add the program removeConfigData.pl which will remove the database and all of the associated files created by the program given a specified configuration. Changes from version 0.17 to 0.19 1. Modified the documentation in the utils/ programs. The descriptions were just a mess Changes from version 0.15 to 0.17 1. In SNOMED CT there exist concepts that are used to show why a concept is retired. Unfortunately, the relationship linking that reason to the retired concept is 'is-a'. So you have for example 'stenosis' is-a 'non-current concept - ambiguous'. This is understandable in a plain English sense but doesn't fit into the hierarchical sense of an 'is-a' relationship. We now exclude these nodes: C1274012|Ambiguous concept (inactive concept) C1276325|Reason not stated concept (inactive concept) C1274013|Duplicate concept (inactive concept) C1274014|Outdated concept (inactive concept) C1274015|Erroneous concept (inactive concept) C1274021|Moved elsewhere (inactive concept) If you have a strong reason why they should still be there send us an email and we can probably work something else out. 2. When using the RB/RN and PAR/CHD relations not all of the upper level taxonomy was being looked at to obtain the path information. This has been fixed. 3. Moved the dropTemporaryTables.pl program to removeConfigData.pl and added the functionality to drop the files associated with the configuration data as well. 4. The UMLS-Interface module was not accepting the a configuration file if the first one was printed out incorrectly. We fixed this. 5. Added configuration file information printed out to STDERR containing source, relation and configuration file location information. 6. Added a file option to the findShortestPath.pl program: --inputfile FILE A file containing pairs of concepts or terms in the following format: term1<>term2 or cui1<>cui2 or cui1<>term2 or term1<>cui2 Changes from version 0.13 to 0.15 1. Added three new functions for semantic types: getSt which returns the semantic type TUI of a given CUI getStAbr which returns the semantic type abbreviation given the semantic type TUI getStString which returns the semantic type string given the semantic type abbreviation 2. Added a program to the utils/ directory: getSt.pl which returns the semantic type of a given CUI or TERM in the UMLS. This program uses the three above functions. 3. Added the function checkConceptExists which returns true or false whether a concept exists in the current view of the UMLS (this is based on the sources and relations that are being used). This function was hidden but it seemed like it could be useful to others as well - it became useful for me anyway :) 4. Modified the SYNOPSIS section in the Interface.pm module to include all or at least most of the different functions available through the Interface.pm module. 5. Fixed the permissions on the configuration file directory when it is being created. And chmod the individual files after they were created. Hopefully now they will be created with read and write privlidges so you can see them if you install using the -MCPAN option. 6. Modified the findPathToRoot.pl and findShortestPath.pl to include the term associated with the CUI in the path 7. I forgot to add the UMLS Root to the PATH in the pathToRoot function. It is now added. Changes from version 0.11 to 0.13 1. Speed up the getTermList() option when all of the sources are being used 2. Modified documentation 3. Added the function findMinimumDepth and findMaximumDepth which returns the minimum and maximum depth of a CUI respectively given the view of the UMLS Changes from version 0.09 to 0.11 1. Modified the Changelog directory and tried to remember to add them to the release! 2. Modified documenation - tried to get the misspelling and obvious errors removed. 3. Removed the HTML documentation Changes from version 0.03 to 0.09 1. Allowed the program to create the directory that we prompt the user for (the location that the config files should be stored) if it doesn't exist rather than requiring it be already created. 2. Modified the location of where the utils/ programs are installed. All of them now get installed and they are all in the same location. 3. Found a bug in the code that reads the configuration file. Error would occur if trying to exclude a source. Changes from version 0.01 to 0.03 1. Removed the need for UMLSINTERFACE environment variable indicating the location of the UMLS. Now we prompt the user for the location that the config files should be stored and ask them to set a UMLSINTERFACE_CONFIGFILE_DIR variable.