| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 339 | DBIA339 | Routine | LEXICON UTILITY | 2003/05/19 | Retired | Private |
The Problem List Application has permission to use the entry point ^GMPTDUSR. This entry point will be used to setup user-specific look-up defaults. |
GMPTDUSR | ||||
| 340 | DBIA340 | Routine | LEXICON UTILITY | 2003/05/19 | Retired | Private | GMPTSET | |||||
| 457 | CLINICAL LEXICON EXPRESSIONS | File | LEXICON UTILITY | 1994/04/26 | APPROVED | Active | Supported | 757.01 | The Clinical Lexicon Utility will maintain static internal entry numbers (IENs) for the Expression file (#757.01). As a result, this file may be pointed to to retrieve the Display Text (.01) for both current Expressions and formerly used (deleted) Expressions. |
|||
| 1511 | USE OF ICDONE | Routine | LEXICON UTILITY | 1996/03/08 | APPROVED | Active | Private | The Automated Information Collection System has the ability to print lists of terms based on the Clinical Lexicon on Encounter Forms. When the forms are scanned and data is passed the PCE, the ICD9 diagnosis code associated with the term is required to populate the Purpose of Visit. This agreement is to allow AICS to use the call ICDONE^GMPTU (and its successor) ICDONE^LEXU to determine the correct, or best ICD9 Diagnosis code associated with the selected term. Input variable is the pointer to the clinical lexicon entry in file 757.01. Output is the ICD9 code, or null if none is found. This will be coded in such a way as when Clinical Lexicon converts to the LEX namespace that no changes will be required. |
GMPTU | |||
| 1512 | USE OF ICDONE | Routine | LEXICON UTILITY | 1996/03/08 | Retired | Private | The Automated Information Collection System has the ability to print lists of terms based on the Clinical Lexicon on Encounter Forms. When the forms are scanned and data is passed the PCE, the ICD9 diagnosis code associated with the term is required to populate the Purpose of Visit. This agreement is to allow AICS to use the call ICDONE^LEXU when released to determine the correct, or best ICD9 Diagnosis code associated with the selected term. Input variable is the pointer to the clinical lexicon entry in file 757.01. Output is the ICD9 code, or null if none is found. This will be coded in such a way as when Clinical Lexicon converts to the LEX namespace that no changes will be required. |
LEXU | ||||
| 1571 | LEXICON UTILITY EXPRESSIONS | File | LEXICON UTILITY | 1996/08/07 | APPROVED | Active | Supported | 757.01 | The Lexicon Utility (version 2.0 and greater) will maintain static internal entry numbers (IENs) for the Expression file (#757.01). As a result, this file may be pointed to to retrieve the Display Text (.01) for both current Expressions and deactivated Expressions (Deactivation Flag 757.01;9 1;5 set to 1). This agreement is a follow-on to DBIA 457 (version 1.0) and is re-issued to include the package name, namespace and global root changes occurring in version 2.0. This is not an amendment to 457. Version 1.0 Version 2.0 Package name Clinical Lexicon Utility Lexicon Utility Namespace GMPT LEX Expression File Global Root ^GMP(757.01, ^LEX(757.01, |
|||
| 1573 | LEXU | Routine | LEXICON UTILITY | 1996/08/07 | APPROVED | Active | Supported | LEXU is a utility routine for the Lexicon Utility which contains functions useful in retrieving classification code(s) for a term. This agreement is a follow-on to DBIA 10148 (version 1.0) and is re-issued to include the package name, namespace, routine name and global root changes occurring in version 2.0. This is not an amendment to 10148. |
LEXU | |||
| 1577 | CLINICAL LEXICON REFERENCES | Routine | LEXICON UTILITY | 1996/08/08 | Retired | Controlled Subscription | The purpose of this IA is to access line tag CONFIG in routine ^LEXSET. |
LEXSET | ||||
| 1578 | CLINICAL LEXICON UTILITY | Routine | LEXICON UTILITY | 1996/08/08 | Withdrawn | Controlled Subscription | AICS would like to request access to call linetag CONFIG^GMPTSET until the new version of the Clinical Lexicon Utility is released. At that point, we will reference routine ^LEXSET. |
GMPTSET | ||||
| 1597 | LEXICON EXPRESSION INFORMATION | Routine | LEXICON UTILITY | 1996/08/18 | APPROVED | Active | Supported | LEXA is used by the Lexicon Utility to perform a silent look-up and return an array of the expression found. |
LEXA | |||
| 1599 | LEXICON USER DEFAULTS - FILTER | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Private | The entry point EN1^LEXDFL will be used to setup user default filter for conducting searches in the Lexicon Utility. This entry point, along with EN1^LEXDCC, EN1^LEXDVO, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in verion 1.0 of the Clinical Lexicon Utility (see DBIA 339). |
LEXDFL | |||
| 1601 | LEXICON USER DEFAULTS - DISPLAY | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Private | The entry point EN1^LEXDCC(LEXAP) will be used to setup user default display (classification codes) for conducting searches in the Lexicon Utility. This entry point along with EN1^LEXDFL, EN1^LEXDVO, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in verion 1.0 of the Clinical Lexicon Utility (see DBIA 339). |
LEXDCC | |||
| 1603 | LEXICON USER DEFAULTS - VOCABULARY | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Private | The entry point EN1^LEXDVO will be used to setup user default vocabulary for conducting searches in the Lexicon Utility. This entry point, along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDCX and EN1^LEXDDS replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). |
LEXDVO | |||
| 1605 | LEXICON USER DEFAULTS - SHORTCUTS | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Private | The entry point EN1^LEXDCX will be used to setup user default shortcuts by context for conducting searches in the Lexicon Utility. This entry point along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDVO and EN1^LEXDDS replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). |
LEXDCX | |||
| 1607 | LEXICON USER DEFAULTS - LIST | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Private | The entry point EN1^LEXDDS will be used to list user defaults for searching the Lexicon to a device (terminal or printer). This entry point along with EN1^LEXDFL, EN1^LEXDCC, EN1^LEXDVO and EN1^LEXDCX replaces ^GMPTDUSR used in version 1.0 of the Clinical Lexicon Utility (see DBIA 339). |
LEXDDS | |||
| 1609 | LEXICON SETUP SEARCH PARAMETERS | Routine | LEXICON UTILITY | 1996/08/19 | APPROVED | Active | Supported | The Lexicon Utility uses LEXSET to setup search parameters based on applications definitions, subset definitions and user defaults stored in the Subsets Definition file (#757.2). These search parameters are stored in the global array ^TMP("LEXSCH",$J). |
LEXSET | |||
| 1614 | LEXICON EXPRESSIONS FROM CODES | Routine | LEXICON UTILITY | 1996/08/20 | APPROVED | Active | Supported | The Lexicon Utility uses the LEXCODE routine to extract expressions (terms) in the form of Fileman's output variable "Y" based on a classification code. |
LEXCODE | |||
| 2288 | LEXU | Routine | LEXICON UTILITY | 1998/02/03 | Withdrawn | Supported | LEXU is a utility routine for the Lexicon Utility which contains functions useful in retrieving classification codes for a term. This agreement is an amendment to DBA #1573. |
LEXU | ||||
| 2950 | DBIA2950 | Routine | LEXICON UTILITY | 2003/04/16 | APPROVED | Active | Supported | This entry point is silent and intended to support Graphical User Interface (GUI) development. The lookup returns an array of information on the expressions found. The lookup includes reordering the selection list with the most frequently used at the top, and places any exact match at the top of the list. |
LEXA | |||
| 4083 | LEXICON CODE STATUS | Routine | LEXICON UTILITY | 2003/04/14 | APPROVED | Active | Supported | LEXSRC2 | 2008/09/18 | |||
| 4306 | LEXICAL SERVICES UPDATE Protocol | Other | LEXICON UTILITY | 2003/12/03 | APPROVED | Active | Controlled Subscription | This protocol is used to notify other applications and processes when the Lexicon Utility or the Lexicon Change file is updated. The Lexicon is updated using a temporary maintenance global, ^LEXM. This global is processed by the routine LEXXGI. Once processed, this protocol is triggered and the global ^LEXM is deleted. Required Variable LEXSCHG Array contains a listing of those Lexicon Files (#757 - 757.41) that were updated as a result of a recent install. In the case of the CHANGE LOG (file #757.9), new changes to SDO controlled files will be indicated by file number and the internal entry number to the CHANGE LOG. The variable LEXSCHG is created while processing the Lexicon Maintenance global ^LEXM. It will indicate what files were updated. Example: LEXSCHG(757,0)="" LEXSCHG(757.001,0)="" LEXSCHG(757.01,0)="" LEXSCHG(757.02,0)="" LEXSCHG(757.1,0)="" LEXSCHG(757.11,0)="" LEXSCHG(757.9,0)="" LEXSCHG(757.9,2)=80 LEXSCHG(757.9,3)=80.1 LEXSCHG(757.9,4)=81 LEXSCHG(757.9,"B",80,2)="" LEXSCHG(757.9,"B",80.1,3)="" LEXSCHG(757.9,"B",81,4)="" If ICD-9-CM and/or CPT-4 changes are included in the ^LEXM global, then the following entries will be found in the local array LEXSCHG: LEXSCHG(80,0)="" LEXSCHG(80.1,0)="" LEXSCHG(81,0)="" |
||||
| 4912 | LEXICON CONCEPT DATA FOR CODE | Routine | LEXICON UTILITY | 2006/10/05 | APPROVED | Active | Supported | This API will return an array of data for a given code, code source, optional date, and optional return array name. The data returned will include: code hierarchy or subset (if available) version (if available) legacy code (if available) code status fully specified name (if available) preferred term any applicable synonyms If any of the data in the passed parameters data is incorrect or unrecognizable, the API will return an error message indicating the nature of the error. If no date is specified, then the date will default to the current system date. This API was developed specifically for the SNOMED CT code system in support of the LDSI project, but is applicable to any code system. |
LEXTRAN | |||
| 4913 | LEXICON CONCEPT DATA FOR TEXT | Routine | LEXICON UTILITY | 2006/10/05 | APPROVED | Active | Supported | This API will return an array of data for a given text, optional code source, optional date, optional subset, and optional return array name. The API will display a pick list based on the parameters passed and allow a user to select an item from the list. The API will then return the array for the item selected. The data returned will include: code hierarchy or subset (if available) version (if available) legacy code (if available) code status fully specified name (if available) preferred term any applicable synonyms If any of the data in the passed parameters data is incorrect or unrecognizable, the API will return an error message indicating the nature of the error. If no date is specified, then the date will default to the current system date. This API was developed specifically for the SNOMED CT code system in support of the LDSI project, but is applicable to any code system. |
LEXTRAN | |||
| 4914 | LEXICON VALIDATE CODE FOR SOURCE | Routine | LEXICON UTILITY | 2006/10/05 | APPROVED | Active | Supported | This API will return an array for a given text and code system indicating whether the text is valid for the specified code system. The data array returned will include the following: An indicator of whether the text is valid for the code system The code in the code system to which the text,if valid for code system, belongs. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN | |||
| 5006 | Lexicon Obtain Synonyms for Code | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API will return an array for a given code and coding system. The array will contain all synonyms for the concept including the preferred term and the fully specified name. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN1 | 2007/12/28 | ||
| 5007 | Lexicon Obtain Fully Specified Name | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API returns the fully specified name for a given coding system and code. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN1 | 2007/12/28 | ||
| 5008 | Lexicon Obtain Preferred Term | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API returns the preferred term for a given coding system and code. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN1 | 2007/12/28 | ||
| 5009 | Lexicon Obtain Designation Code | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API returns the designation code for a given coding system and text. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN1 | 2007/12/28 | ||
| 5010 | Lexicon Obtain Mapped Codes | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API returns an array containing the mappings for a specified code for a specified mapping identifier. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN1 | 2007/12/28 | ||
| 5011 | Lexicon Obtain Version Identifier | Routine | LEXICON UTILITY | 2007/06/28 | APPROVED | Active | Supported | This API returns the SDO version identifier for a given coding system, code, and date. If any of the passed parameters are incorrect or unrecognizable, the API will return an error message indicating the nature of the error. |
LEXTRAN | 2007/12/28 | ||
| 5252 | Lexicon/VBA APIs | Routine | LEXICON UTILITY | 2008/08/08 | Pending | Supported | LEXASCD contains APIs for supporting the Automated Service Connected Designation (ASCD) project. |
LEXASCD | ||||
| 5386 | LEXU Lookup Screens | Routine | LEXICON UTILITY | 2009/03/13 | APPROVED | Active | Supported | This agreement includes common entry points for filtering Lexicon searches. Similar to DIC("S") screens. |
LEXU | 2009/03/16 | ||
| 5387 | Access to Lexicon file #757.03 | File | LEXICON UTILITY | 2009/03/16 | Withdrawn | Private | 757.03 | Allows Radiology/Nuclear Medicine package to access Lexicon file #757.03, Coding System, to be used for Fileman lookup as in DIC("S") screen of medical terminology, diagnosis or classification. |
||||
| 5547 | LAB LOINC FILE (#95.3) API(S) | Routine | LEXICON UTILITY | 2010/07/23 | Pending | Controlled Subscription | These API(s) support the custodial transition of the LAB LOINC file (#95.3) from Legacy LAB to Standards and Terminology Services (STS). These API(s) provide Read Access to the LAB LOINC file (#95.3) and should be used when accessing the file. The API(s) support Legacy LAB's encapsulation efforts and STS's LOINC Deployment efforts. |
LEXLR | ||||
| 5679 | LEXU (ICD-10 UPDATE) | Routine | LEXICON UTILITY | 2011/06/03 | APPROVED | Active | Supported | This is an addendum to ICR 1573 and contains functions added to LEXU during the implementation of ICD-10 Coding system. The APIs in this ICR become effective on the date of release of patches ICD*18.0*57 and LEX*2.0*80. |
LEXU | 2014/07/11 | ||
| 5680 | LEXCODE Expression | Routine | LEXICON UTILITY | 2011/06/03 | APPROVED | Active | Supported | This is an addendum to ICR 1614 and contains functions added to LEXCODE during the implementation of ICD-10 Coding system. The API in this ICR becomes effective on the date of release of patches ICD*18.0*57 and LEX*2.0*80. |
LEXCODE | 2014/07/11 | ||
| 5681 | LEX10CS | Routine | LEXICON UTILITY | 2011/06/06 | APPROVED | Active | Supported | Supported APIs for the implementation of ICD-10. The APIs in this ICR become effective on the date of release of patches ICD*18.0*57 and LEX*2.0*80. |
LEX10CS | 2014/07/11 | ||
| 5781 | Mixed Case | Routine | LEXICON UTILITY | 2012/03/08 | APPROVED | Active | Controlled Subscription | This API provides mixed case terminology primarily for ICD-10 Lookup. |
LEXXM | 2014/07/11 | ||
| 5840 | ICD-10 Suggestions | Routine | LEXICON UTILITY | 2012/09/06 | APPROVED | Active | Controlled Subscription | Supported APIs for the implementation of ICD-10. The APIs in this ICR become effective on the date of release of patches ICD*18.0*57 and LEX*2.0*80. |
LEX10CX | 2014/07/11 | ||
| 6224 | UCUM CODES FILE | File | LEXICON UTILITY | 2015/08/26 | APPROVED | Active | Controlled Subscription | 757.5 | 2015/09/02 | |||
| 6225 | UCUM CODES APIs | Routine | LEXICON UTILITY | 2015/08/26 | APPROVED | Active | Controlled Subscription | This ICR works in conjunction with ICR #6224 to allow packages to use UCUM Codes for storing measurements. |
LEXMUCUM | 2015/09/02 | ||
| 6265 | Lexicon Expression Extracts | Routine | LEXICON UTILITY | 2015/11/16 | APPROVED | Active | Supported | Effective upon release of patch LEX*2.0*103. |
LEXU | 2015/01/15 | ||
| 6266 | Convert to Mixed Case | Routine | LEXICON UTILITY | 2015/11/17 | Pending | Supported | Effective upon release of patch LEX*2.0*103. |
LEXXMC | ||||
| 6267 | Lexicon Silent Lookup | Routine | LEXICON UTILITY | 2015/11/17 | Pending | Supported | Effective upon release of patch LEX*2.0*103. Expands upon LOOK^LEXA ICR 2950. |
LEXA | ||||
| 6472 | Get Designation ID for an Expression | Routine | LEXICON UTILITY | 2016/08/23 | Pending | Supported | LEXTRAN1 | |||||
| 6837 | LEXICON CODES | File | LEXICON UTILITY | 2017/11/13 | Pending | Private | 757.02 | LEXICON CODES contain codes, their classification sources (such as ICD), and some flags. |
||||
| 6838 | SUBSET DEFINITIONS | File | LEXICON UTILITY | 2017/11/13 | Pending | Private | 757.2 | SUBSET DEFINITIONS contains various terminologies and codes related to certain areas defined in other LEX globals. |
||||
| 10148 | GMPTU | Routine | LEXICON UTILITY | 2004/11/22 | Retired | Supported | GMPTU |