Page History

...

• • Correct US spelling, not GB (General British) spelling 
  • Singular form, not plural form
  • Procedures in present tense, not past tense
  • A semantic tag in parentheses at the end

        An FSN with an approved disjunctive (although not often used), e.g., |Traumatic and/or non-traumatic injury of back (disorder)

...

| should have lower

...

case and/or. 

An FSN should not havenot have:

• • Abbreviations or acronyms
    • For more information, including exceptions, see the Abbreviations and acronyms section at General Naming Conventions
  • Hyphens
  • Duplicate concepts
  • Ambiguity
  • The word OR (
not including
• • exception for the disjunctive and/or)
  • Forward or backslash (/ \)
    
  • Precoordinated numeric ranges
  • Reference to a particular instance
  • Reason or indication for a procedure, unless this directly impacts the method

...

Acronyms are easily misinterpreted. For this reason, all acronyms are unacceptable discouraged in FSNs.

For example, the FSN should be the expanded form, Computed tomography of chest (procedure); however, however as a preferred term, CT of chest (procedure) is acceptable.

If there is an unacceptable acronym in an existing FSN, the FSN DescriptionId is FSN DescriptionId is inactivated, and a new FSN is created (regardless of whether or not the acronym was in parentheses with the expanded form). The replacement FSN concept has the expanded description with the acronym entirely removed. Inactivating the ConceptId the ConceptId is not necessarily required, unless the FSN had significant ambiguity before changing it to its expanded form.  For more information on acronyms, see the Abbreviations and acronyms section of General Naming Conventions.  

Imported FSNs

Before any changes are made to an FSN, imported directly with an extension (local) ID, the submitter should be notified and confirmation sought that no loss of meaning has occurred. This helps to ensure that the original meaning is understood and maintained. Authors should:

...