LexEVS 6.x ICD-9 Mappings

Source Data, General Comments

The ICD-9 data is provided in two text files. One is diagnosis codes (also referred to as Volume 1 and Volume 2) the other is procedure codes (referred to as Volume 3). Each file is formatted as a two column flat file. Column one is the ICD-9 code. Column two is a definition. The columns are separated by white space. Both files are loaded as a single LexGrid coding scheme. Decision for this was based on the behavior of the UMLS load of ICD-9 UMLS data where diagnosis and procedures codes are loaded into a single coding scheme.

Source Data, Source

The ICD-9 data for this loader came from Centers for Medicare & Medicaid Services (CMS, http://www.cms.gov/). http://www.cms.hhs.gov/ICD9ProviderDiagnosticCodes/Downloads/v26_icd9.zip

Source Data, Example:

• 0010 CHOLERA D/T VIB CHOLERAE
• 0011 CHOLERA D/T VIB EL TOR
• 0019 CHOLERA NOS

Source Data, Code Format

The ICD concpet code in the source data files does not contain a decimal point. The loader will add a decimal point to the concpet codes following these rules:

For diagnosis codes, the number part of the code will always be 3 digits with zero or one or two decimal digits. For procedure codes the numeric part of the code will be 2 digits with zero, one or two digits following the decimal point. Using the example diagnosis data above, 0010 will be read by the loader and 001.0 will be stored in the database.

Mappings

Coding Scheme data

No descriptive information about the data is included in the source. Default values are provided by the loader. The user must provided a version value to the loader which will be used as the coding scheme version.

Table: codingScheme

Also the following attributes are supported by coding scheme:
Table: supportedAttrib, tag: CodingScheme

The tables below continue to show default supported attributes for the coding scheme. Only fields with non-null values and non-generated values (such as Global Unique Identifiers or GUIDs) will be displayed.

Table: supportedAttrib (abbreviated), tag: EntityType

Table: supportedAttrib (abbreviated), tag: Language

Table: supportedAttrib (abbreviated), tag: Association

Table: supportedAttrib (abbreviated), tag: Association

Table: supportedAttrib (abbreviated), tag: EntityType

Table: supportedAttrib (abbreviated), tag: Property

Entity

Each row in the source file represents a concept. A LexGrid entityCode is the ICD concept code and entityName is the ICD definition. An entity type of concept is also created in the entityType table. The following tables are updated for each ICD concept: entity, entityType. Also, a property of type PRESENTATION is created for each concept so the property table is updated as well, where the property value is the ICD concept definition.

Table: entity

Table: entityType

Table: property

Relations

A default relations container is created by the loader.

Table: relation

Associations

There is no hierarchy present in the source files. However, the loader does create a root concept, @, that all other concepts are associated with via the hasSubType and isA relationships.

Two Associations are defined: hasSubType and isA. For each type of association an entry will be made in the following tables: associationPredicate, entity, entityType. Only hasSubType is shown in the examples below.

Note: isA is also created as a reverse association for hasSubType. It was thought at the time the loader was written that a reverse assocation was required but that may not be the case. The isA association may be removed in a later version of the loader.

Table: associationPredicate

Table: entity

Table: entityType

Concept to Concept Associations

These are the concepts with relationships to each other. As mentioned earlier, there really are none in the ICD data. But we create a default root concept for all the ICD concepts to associate with.

Each ICD concept will be associated with the root concept by the hasSubType association.

Table: entityAssnsToEntity