Date: Thu, 28 Mar 2024 11:39:59 +0000 (UTC) Message-ID: <329734101.433.1711625999917@[3.220.22.64]> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_432_1161620291.1711625999916" ------=_Part_432_1161620291.1711625999916 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Lega=
cy content may not adhere to current guidelines and will be updated as reso=
urces allow.
A comma is allowed in an FSN when = required for meaning or to add clarity.
For= example,
A comma is not allowed to change <= em>sort order for use in the search function.
Una= cceptable example,
Eponymous descriptions should not = include an apostrophe or final s, unless the name normally ends in= s. With rare exception, a concept with an eponym should have= at least one description that follows this rule.
For= example,
When common usage requires it, the= re should be at least one description that has the apostrophe s. F= or descriptions with a possessive apostrophe where the name normally ends i= n s, the apostrophe should follow the s.
For= example,
Existing eponymous descriptions wi= th the possessive s, but no apostrophe, need not be inactivat= ed, but newly added descriptions should either have no s, or = else include the apostrophe.
In protein names, this character (represented by single quote character)= is used to indicate the cleavage location on a substrate and to distinguis= h different subunits with the same notation.
For example, 80222004 |5'-nucleotidase (s= ubstance)|
The prime symbol and apostrophe may look the same, but each has its own = Unicode representation.
Hyphens should follow rules of sty= le for the dialect and language in which the descriptions are used as = found in such publications as the Chicago Manual of Style, th= e American Medical Association=E2=80=99s Manual of Style, a c= urrent medical dictionary, etc. Punctuation is to be used sparingly u= nless used to prevent ambiguity.
When a hyphen is used to join word= s or to separate syllables, there is no space either before or after the hy= phen.
For example,= p>
A hyphen may be used to separate t= wo phrases, to contrast values, or to show a relationship between two thing= s. A hyphen should rarely be used in an FSN, because it may obscure t= he exact meaning of the description; the hyphen should be replaced with wor= ds that clarify the meaning.
A hyphen is used to separate an ac= ronym from its expanded form when no other terms are included in a descript= ion.
For= example,
= 719977005 | Communication Activities of Daily Living (assessment = scale)|= has a synonym of CADL - Communication Activities of Daily Living
The hyphen is represented by UTF-8 and can be entered directly by a stan= dard keyboard. Although the hyphen may sometimes be referred to as a = dash, the EN dash and EM dash are not used in SN= OMED CT.
In general, colons should not be u= sed in fully specified names.
Col= ons are allowed in the FSNs of organisms, substances, or products where the= colon is part of the name. They are also allowed in ratios and in tumor st= ages.
For= example,
Col= ons may be allowed in non-FSN descriptions.
For= example, to separate an abbreviation from the rest of a name or = a specimen from the finding
A double colon ( :: ) notation is allowed in the neop= lastic morphologic abnormalities (400177003 |Neoplasm and/or hamartoma (mor= phologic abnormality)| subhierarchy). The notation can be used to rep= resent gene fusions; for example, BCR::ABL1 fusion.
The forward slash should not be us= ed in FSNs. When the slash is part of the authoritative name (e.g. represen= tation of heterozygosity in hemoglobinopathies), a hyphen (no space before = or after) is used in the FSN. The forward slash, without spaces, may be use= d in a preferred term or synonym.
For= example,
A f= orward slash may be used to represent units of measure, official enzyme nam= es, and laboratory test results. They may also be used in and/or w= hen part of FSNs. There should be no space either before or after the slash= .
For= example,
A f= orward slash may be allowed in non-FSN descriptions in a variety of context= s. Some common examples of use are in acronyms with findings, and as a= n abbreviation meaning and/or concepts.
Protein names may contain the forward sla= sh =E2=80=98/=E2=80=99 for separating multiple domains or functions:
For example, 1222712000 |Serine/threonine= -protein kinase B-raf (substance)|
Certain neoplastic variants incorporate a= slash in their terming (note this slash does not mean 'and' or 'and/or'). = Based on pathology input, a dash can be utilized in the FSN and a slash ret= ained in the Preferred Term for clinical usage.
For example,
The plus sign is generally discouraged for use in descriptions, and lega= cy content still contains this symbol. However, some uses are allowed= . Plus signs may be found in the product, disposition, and substance hierar= chies.
For example,
A pair of caret symbols is used to= enclose character strings that should display as superscript.
Current guidance for substance and= product hierarchies is to not create new instances containing symbols= for superscript and subscript.
The single caret is used to repres= ent exponents, i.e. powers of, in alignment with the Uni= fied Code for Units of Measure (UCUM) guidance on the use of powers of ten.=
For= example,
A description cannot contain a pip= e character, |. Since the | is used to indicate the beginning and&nbs= p;end of a description, it may cause confusion.
An umlaut should only be accepted = for terms that do not have equivalences in English. Synonyms without umlaut= s should be added to facilitate searching in English.
For= example,
The use of brackets " [ ] " for de= scriptions are allowed, including in FSN and PT.
For= example,
Other special characters <, >= ;, &, %, $, @, # are not permitted in FSNs. All instances of FSNs= with these characters should be spelled out in full text.
For= example,
The characters &, %, and # are= permitted in preferred terms or synonyms.
The characters @ and $ are not use= d in any descriptions.