Unified Medical Language System | |
General Information:
For 2008AB, there are 2 new sources (FMA, MEDCIN), 1 new translation source (MDRCZE), 27 updated English sources, and 10
updated translation sources.
FMA (Foundation Model of Anatomy) is a reference ontology for the domain of anatomy and makes available anatomical information in symbolic form.
MEDCIN, developed by Medicomp Systems, is a medical terminology that encompasses symptoms, history, tests, diagnoses, physical examinations, and therapy.
MDRCZE (Medical Dictionary for Regulatory Activities Terminology (MedDRA), Czech Edition)
As translation sources are updated, we continue to attempt to represent them as closely as possible to the English
version. This includes using the same term types and creating the same relationships in the translation source. If there are
concepts missing from the translation source that would cause gaps in the hierarchy, those gaps are filled in with the
English language version of the missing concept. For 2008AB, affected sources are MSHJPN and MSHSWE.
For more detailed information about each source:
Foundational Model of Anatomy Ontology, 2_0
Medical Dictionary for Regulatory Activities Terminology (MedDRA), Czech Edition, 11.0
MEDCIN, 3_2008_07_14
Gene Ontology, 2008_04_01
Gold Standard Alchemy, 2008_08_11
HUGO Gene Nomenclature, 2008_03
ICD-9-CM, 2009
Logical Observation Identifier Names and Codes, 224
The Braden Scale for Predicting Pressure Sore Risk, 224_1988
The Faces, Legs, Activity, Cry, and Consolability (FLACC) Scale, 224_1997
Minimum Data Set, 2.0, 224_20
Outcome and Assessment Information Set, 224_2002
Patient Health Questionnaire, 224_1999
Patient Monitoring Guidelines for HIV care and antiretroviral therapy (ART), 224_2006
Master Drug Data Base, 2008_08_06
Medical Dictionary for Regulatory Activities Terminology (MedDRA), 11.0
Medical Dictionary for Regulatory Activities Terminology (MedDRA), Dutch Edition, 11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), French Edition, 11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), German Edition, 11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), Italian Edition, 11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), Japanese Edition, 11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), Portuguese Edition,
11.0
Medical Dictionary for Regulatory Activities
Terminology (MedDRA), Spanish Edition,
11.0
MedlinePlus Health Topics, 20080614
Multum MediSource Lexicon, 2008_08_01
Micromedex DRUGDEX, 2008_08_04
Medical Subject Headings, 2009_2008_08_06
Japanese translations of the Medical Subject Headings, 2008
Swedish Translation of MeSH, 2008
Metathesaurus FDA National Drug Code Directory, 2008_08_04
Metathesaurus additional entry terms for ICD-9-CM, 2009
Metathesaurus FDA Structured Product Labels, 2008_08_26
NCBI Taxonomy, 2008_05_07
NCI Thesaurus, 2008_05D
National Drug Data File Plus Source Vocabulary, 2008_08_08
National Drug File - Reference Terminology Public Inferred Edition, 2008_03_11
RxNorm Vocabulary, 08AA_080902F
SNOMED Terminos Clinicos (SNOMED CT),
Edicion en Espanol, Distribucion Internacional,
Octubre de 2007, 2008_04_30
SNOMED Clinical Terms, 2008_07_31
Veterans Health Administration National Drug
File, 2008_08_11
-----------------------------------------
Source: Foundational Model of Anatomy
VSAB: FMA2_0:
status: new source
1) New term type (TTY):
PT
SY
2) Dropped term type (TTY):
not applicable
3) New attribute name (ATN):
ADJACENT
ANATOMICAL_OR_ARBITRARY
CELL_APPENDAGE_TYPE
CELL_LAYER
CHROMOSOME_PAIRS_PER_NUCLEUS
CONNECTED_TO
CONNECTION_TYPE
CONTACT_TYPE
COORDINATE
DIMENSION
HAS_BOUNDARY
HAS_MASS
LANGUAGE
LATERALITY
MUSCLE_INSERTION
MUSCLE_ORIGIN
PARTITION
POLARITY
SHAPE_TYPE
SHARED_OR_UNSHARED
STATE_OF_DETERMINATION
VIEW
4) Dropped attribute name (ATN):
not applicable
5) New relationship|relationship attribute (RELA)|RELA inverse:
RO|adjacent_to|adjacent_to
RO|afferent_to|efferent_to
RO|arterial_supply_of|has_arterial_supply
RO|attaches_to|receives_attachment
RO|attributed_continuous_with|attributed_continuous_with
RO|bounded_by|bounds
RO|branch_of|has_branch
RO|constitutional_part_of|has_constitutional_part
RO|contained_in|contains
RO|continuous_with|continuous_with
RO|continuous_with_distally|continuous_with_proximally
RO|develops_from|gives_rise_to
RO|has_attributed_constitutional_part|attributed_constitutional_part_of
RO|has_attributed_part|attributed_part_of
RO|has_attributed_regional_part|attributed_regional_part_of
RO|has_cell_connecting_part|cell_connecting_part_of
RO|has_cell_shape|cell_shape_of
RO|has_cell_surface_specialization|cell_surface_specialization_of
RO|has_continuation_branch|continuation_branch_of
RO|has_eipthelial_cell_shape|eipthelial_cell_shape_of
RO|has_fascicular_architecture|fascicular_architecture_of
RO|has_germ_origin|germ_origin_of
RO|has_inherent_3d_shape|inherent_3d_shape_of
RO|has_location|location_of
RO|has_lymphatic_drainage|lymphatic_drainage_of
RO|has_member|member_of_cluster
RO|has_muscle_attachment|muscle_attachment_of
RO|has_muscle_insertion|muscle_insertion_of
RO|has_muscle_origin|muscle_origin_of
RO|has_nerve_supply|nerve_supply_of
RO|has_orientation|orientation_of
RO|has_physical_state|physical_state_of
RO|has_primary_segmental_supply|primary_segmental_supply_of
RO|has_regional_part|regional_part_of
RO|has_secondary_segmental_supply|secondary_segmental_supply_of
RO|has_segmental_composition|segmental_composition_of
RO|has_shape|shape_of
RO|has_systemic_part|systemic_part_of
RO|has_tributary|tributary_of
RO|has_venous_drainage|venous_drainage_of
RO|homonym_for|has_homonym
RO|origin_of|has_origin
RO|receives_input_from|sends_output_to
RO|segmental_supply_of|has_segmental_supply
RO|surrounded_by|surrounds
6) Dropped relationship|relationship attribute (RELA):
not applicable
7) Definitions
Definitions are included in MRDEF.RRF.
A. General notes/comments
We only inverted English and Latin-language terms, both with LAT=ENG; we create a LANGUAGE attribute (sg_type=SRC_ATOM_ID) with value "Latin" for the Latin terms. We did not process other non-English terms, since they occur in relatively small numbers:
Count | Language Value |
---|---|
4650 | French |
491 | Spanish |
361 | German |
70 | Filipino |
52 | Italian |
For the most part, we only inverted the data in the "instances.fma.pins" file, because most of the data in the "classes.fma.pons" file is actually meta-data, such as the data types of the various slots each instance may have.
However, to get the hierarchy, we used the Class -> Parent-class ("is-a") relationships from the "classes" file rather than the Instance -> Class "is-a" relationships from the "instances" file because, although about 90% of the time these two relationships duplicate each other, the other 10% are meaningful only in the "classes" data.
Also, while there are some other relationships (represented as instance slots) besides these is-a rels that could also be considered hierarchical (e.g. "regional_part_of"), these were so incomplete and complex that we decided to invert them only as relationships, not as additional hierarchies.
There are 2005 classes that have a "comment" field, and a few (203)concept-instances that are referenced by the ":ANNOTATED-INSTANCE" slot of a separate ":INSTANCE-ANNOTATION" instance, which is also like a comment, and which sometimes duplicates the "comment" field of the referenced instance's class; currently, neither of these is being inverted. Here is one example of this: the concept-instance for Clavicle is referenced by an :INSTANCE-ANNOTATION with the following value in the ":ANNOTATION-TEXT" slot:
"Surg Radiol Anat. 1989;11(3):211-4. The arterial supply of the clavicle - Knudsen FW, Andersen M, Krag C.- Department of Plastic Surgery, Gentofte Hospital, University of Copenhagen, Denmark.\n\nThis report based on delineation of the arterial system with 3 component plastic material on 10 human cadavers describes the arterial supply to the clavicle. The study was performed in 2 parts. One part, which showed the total arterial supply to the clavicle and one part with selective injections of the relevant arteries, with the intention of finding a central nutrient arterial supply to the clavicle. Three arteries were found to supply the clavicle: the suprascapular a.; the thoracoacromial a.; and the internal thoracic (mammary) a. The main supply was primarily periosteal. No nutrient artery was found."
B. Mapping of source data:
For each field/piece of data in the source files, explain where it will end up in the inversion. Note any data that is being ignored.
Slot names are mapped to UMLS TTY, ATN (sg_type=ROOT_SOURCE_CUI or SRC_REL_ID for relationship attributes), and RELA (sg_type=ROOT_SOURCE_CUI) values as follows, as specified in the etc/fma.cfg file:
Slot TTY
---------------------- ---
Preferred+name PT
Synonym SY
Non-English+equivalent SY [names with Language=Latin only]
Slot ATN
---------------------- ----------------------------
adjacent ADJACENT
anatomical%2Farbitrary ANATOMICAL_OR_ARBITRARY
cell+appendage+type CELL_APPENDAGE_TYPE
cell+layer CELL_LAYER
chromosome+pair+number CHROMOSOME_PAIRS_PER_NUCLEUS
connected+to CONNECTED_TO
connection+type CONNECTION_TYPE
contact+type CONTACT_TYPE
coordinate COORDINATE
definition DEFINITON
dimension DIMENSION
has+boundary HAS_BOUNDARY
has+mass HAS_MASS
has+shape+type SHAPE_TYPE
laterality LATERALITY
muscle+insertion MUSCLE_INSERTION
muscle+origin MUSCLE_ORIGIN
partition PARTITION
polarity POLARITY
shared%2Funshared SHARED_OR_UNSHARED
state+of+determination STATE_OF_DETERMINATION
view VIEW
Slot RELA
------------------------------- ---------------------
adjacent+to adjacent_to
afferent+to afferent_to
arterial+supply+of arterial_supply_of
arterial+supply has_arterial_supply
attaches+to attaches_to
attributed+constitutional+part has_attributed_constitutional_part
attributed+continuous+with attributed_continuous_with
attributed+part has_attributed_part
attributed+regional+part has_attributed_regional_part
bounded+by bounded_by
bounds bounds
branch+%28continuity%29 has_continuation_branch
branch+of branch_of
branch has_branch
cell+connectivity has_cell_connecting_part
cell+shape has_cell_shape
cell+surface+specialization has_cell_surface_specialization
constitutional+part+of constitutional_part_of
constitutional+part has_constitutional_part
contained+in contained_in
contains contains
continuous+with+distally continuous_with_distally
continuous+with+proximally continuous_with_proximally
continuous+with continuous_with
develops+from develops_from
efferent+to efferent_to
epithelial+morphology has_eipthelial_cell_shape
fascicular+architecture has_fascicular_architecture
germ+origin has_germ_origin
gives+rise+to gives_rise_to
has+shape has_shape
homonym+for homonym_for
inherent+3-D+shape has_inherent_3d_shape
location has_location
lymphatic+drainage+of lymphatic_drainage_of
lymphatic+drainage has_lymphatic_drainage
member+of member_of_cluster
member has_member
muscle+attachment has_muscle_attachment
muscle+insertion has_muscle_insertion
muscle+origin has_muscle_origin
nerve+supply+of nerve_supply_of
nerve+supply has_nerve_supply
orientation has_orientation
origin+of origin_of
physical+state has_physical_state
primary+segmental+supply+of primary_segmental_supply_of
primary+segmental+supply has_primary_segmental_supply
receives+attachment receives_attachment
receives+input+from receives_input_from
input+from [used only once] receives_input_from
regional+part+of regional_part_of
regional+part has_regional_part
secondary+segmental+supply+of secondary_segmental_supply_of
secondary+segmental+supply has_secondary_segmental_supply
segmental+composition+of segmental_composition_of
segmental+composition has_segmental_composition
segmental+supply+of segmental_supply_of
segmental+supply has_segmental_supply
sends+output+to sends_output_to
surrounded+by surrounded_by
surrounds surrounds
systemic+part+of systemic_part_of
systemic+part has_systemic_part
tributary+of tributary_of
tributary has_tributary
venous+drainage+of venous_drainage_of
venous+drainage has_venous_drainage
C. META UI fields:
Indicate what source data (if any) is being used to populate the following fields:
CODE: FMAID
SAUI: (blank)
SCUI: FMAID
SDUI: (blank)
There were 27 concepts that didn't have an explicit name in the instances file, so we created a "cleansed" form (with "+" characters translated to blanks) of their instance name as their PT atom. This was necessary because without these concepts, there would be "holes" in their hierarchy. It also represents what the Protege browser does automatically when a nameless concept is viewed.
There were 27 concepts that lack an explicit name in the instances File. NLM generated names for these based on their instance names.
-----------------------------------------
Source: MEDCIN, Medicomp Systems
VSAB: MEDCIN3_2008_07_14
status: new source
1) New term type (TTY):
FN
PT
SY
XM
2) Dropped term type (TTY):
not applicable
3) New attribute name (ATN):
PREF_FLAG_ID
4) Dropped attribute name (ATN):
not applicable
5) New relationship|relationship attribute (RELA)|RELA inverse:
RN|isa|inverse_isa
RO|associated_with|associated_with
RO|due_to|cause_of
RO|has_associated_finding|associated_finding_of
RO|has_associated_morphology|associated_morphology_of
RO|has_associated_procedure|associated_procedure_of
RO|has_causative_agent|causative_agent_of
RO|has_clinical_course|clinical_course_of
RO|has_direct_substance|direct_substance_of
RO|has_finding_informer|finding_informer_of
RO|has_finding_method|finding_method_of
RO|has_finding_site|finding_site_of
RO|has_focus|focus_of
RO|has_laterality|laterality_of
RO|has_method|method_of
RO|has_occurrence|occurs_in
RO|has_pathological_process|pathological_process_of
RO|has_procedure_site|procedure_site_of
RO|has_severity|severity_of
RO|has_specimen|specimen_of
RO|occurs_after|occurs_before
SY|same_as|same_as
6) Dropped relationship|relationship attribute (RELA):
not applicable
General notes/comments:
1. There is one RELATIONSHIPTYPE value, "Grade" (103421006), that is not used as a RELATIONSHIPTYPE in SNOMEDCT. The 3 relationships that use this value are not represented.
2. There are 15 complete MEDCIN concepts (including concept IDs, descriptions,and hierarchical positions) that seem to be end-of-file markers, copyright info, etc. These all have the form "**<concept>**":
1|**-copyright-1984-05-by-Medicomp-Systems,-Inc.-** (symptom)
2|**-msi-** (symptom)
1098|**-mvi-** (symptom)
1267|**-end-of-symptom-file-** (symptom)
3411|**Medicomp-Systems-14500 Avion Parkway-Chantilly,VA-20151 (history)
3468|**copyright 1984-2005, Medicomp Systems inc, all rights reserved (history)
9199|**-end-of-physical-findings-file-** (physical finding)
12000|**-msi-** (procedure)
13255|**-msi-** (procedure)
17892|**-end-of-test-file-** (procedure)
30000|**-copyright_1984-2005_Medicomp_Systems,_inc._all_rights_reserved-* (diagnosis)
33716|**14500 Avion Parkway-Suite 175, Chantilly, VA 20151-** (diagnosis)
33717|**-end-of-disease-file-** (diagnosis)
41813|**copyright 1984-2005, Medicomp Systems inc-all rights reserved (treatment)
41814|**-end-of-therapy-file-** (treatment)
There is also a concept, complete with ID and hierarchical position, whose full concept name is "[see also: specific organ system] (treatment)". This is treed under "transfusions, transplantation (treatment)".
These metadata concepts are included as part of MEDCIN.
3. There are various other concepts ending with "[bracketed]" notes of various sorts (preceeding the parenthesized "domain" which occurs at the end of every fully-specified concept name). We represented these terms as they were supplied.
4. Mapping of source data:
UMLS_MEDCIN_CONCEPTS.txt:
MEDCINID: represented as Source CUI (SCUI) and CODE
CONCEPT_DESCRIPTION: represented as atom name (TTY=FN)
UMLS_MEDCIN_DESCRIPTIONS.txt:
MEDCINID: represented as Source CUI (SCUI) and CODE
DESCRIPTION: represented as atom name
PREF_FLAG_ID: represented as an attribute; determines TTY (0=SY, 1=PT)
UMLS_MEDCIN_HIERARCHY.txt:
MEDCINID: represented as ID for context attributes
NODEKEY: used to generate concept tree position for contexts
UMLS_MEDCIN_SNOMED.txt (SNOMED mapping relationships):
MEDCINID: represented as id_1
RELATIONSHIPTYPE: mapped to values used as relationship_name and relationship_attribute
SCT_CONCEPTID: represented as id_2
PREF_FLAG_ID: represented as a relationship attribute (RELA)
Last reviewed: 21 November 2008
Last updated: 21 November 2008
First published: 18 November 2008
Metadata| Permanence level: Permanent: Dynamic Content