Page History

In addition to the general naming conventions below, please also see any applicable naming conventions for specific hierarchies in their respective domain Domain Specific Modeling.

Generally, names should:

...

Abbreviations are shortened forms of words or phrases.  An acronym is a specific type of abbreviation formed from the initial letters of words and is sometimes pronounced as a word (e.g. AIDS for Acquired Immunodeficiency Syndrome; NICU for Neonatal Intensive Care Unit).  Neither abbreviation nor acronym is permitted in a fully specified name (FSN).

For example, 

• • Sperm is a shortened form of the word spermatozoa.  The proper term of spermatozoa should be used in the FSN, while sperm can be used as a synonym.

Abbreviations and acronyms are allowed in a preferred term or synonym when followed by the term expansion. If the abbreviation or acronym stands alone (meaning, no additional terms are included; the letters represent the entire meaning of the description without any other text), it is followed by a space, a hyphen, and another space, then the expanded term.  The The first word after the dash should be lower case as hyphen should be lower case as per usual capitalization rules.

...

When creating the descriptions for a concept (e.g. a disorder concept) that name an entity such as a body structure, substance or organism, the conventions that are applied for naming the entity in the source hierarchy should be used.

For example,

...

...

• • Concept

...

• • Concept
    t 11218009 |Infection caused by Pseudomonas aeruginosa (disorder)|

    
    

This concept references the organism hierarchy in the causative agent of 52499004 |Pseudomonas aeruginosa (organism)| and uses that description in the FSN.

• • 143491000146106 |Felis catus protein (substance)|

448169003 |Felis catus (organism)| has a preferred term of “Domestic cat”. As a result a related concept in the Substance hierarchy, 143491000146106 |Felis catus protein (substance)| has a preferred term of “Domestic cat protein”.

• • Concept
    t 337311000119101 |Blepharochalasis of left upper eyelid (disorder)|

This concept references the body structure hierarchy in the finding site of |Structure of left upper eyelid (body structure)| and uses "left upper eyelid" in the FSN.  

• • Concept
    t 12081931000119106 126885006 |Burn of left eye region Neoplasm of urinary bladder (disorder)|

This concept references the body structure hierarchy in the finding site of

...

89837001 |Urinary bladder structure (body structure)| and uses "

...

urinary bladder" in the FSN and PT.  

The descriptions should be context neutral for these foundation hierarchies. Where context is explicit for a disease or procedure, the preferred term from foundation hierarchies can be used instead. For example, procedure CT of abdomen indicates that the context of CT imaging is cross-sectional. The procedure site should be modeled with the cross-sectional abdomen. However, it is not necessary to change 'Computed tomography of abdomen (procedure)' to 'Computed tomography of cross-sectional abdomen (procedure)'. It is the same reason for the preferred term 'CT of abdomen'.

...

• Where an infection caused by a microorganism has a common name, the common name of the disease can be used in the preferred term if accompanied by the explicitly-stated organism. 
• If a common name is shared between more than one organism, the organism preferred organism preferred term may include the scientific name with annotated common name. Generally, a dash is a hyphen is used to separate the two names. However, if the organism name falls in the middle of the term,  parentheses parentheses should be used to separate the separate the two names.
• When defining concepts in other hierarchies by referring to an organism, the taxonomical rank of the organism should not be included in the FSN or synonyms.
  • For example, 
    • Instead of |Gingivitis caused by Genus Candida (disorder)|, drop the taxonomical rank of Genus, as in |Gingivitis caused by Candida (disorder)|.
• There are instances where the requested term for a concept containing an organism common name doesn’t correspond to specific taxa. Rather, the term is found as part of common names in multiple taxa belonging to a higher level taxon. For example, “parakeet” and “parrot” are not common names to any specific taxa, but are found as part of common names in multiple genera in 447329007 |Subfamily Psittacinae (organism)|. To avoid ambiguity, a grouper concept referring to high-level taxon should be created.
  • For example, In the Substance hierarchy, a grouper concept, 1149419004 |Psittacidae protein (substance)|, was created as a parent concept to the following two concepts:
    • 146711000146102 |Parakeet protein (substance)|
    • 146701000146104 |Parrot protein (substance)|

...