Page tree

Title


Narrative description:

From time to time editorial policy may change, either to support changes in modelling practice, to update our approach to what is considered to be within scope for the international edition of SNOMED CT or bring consistency to existing content. Sometimes when this is done the meaning of an FSN or the implied meaning of a logical definition may change the meaning of an existing SNOMED CT concept.

When a change of meaning occurs the legacy concept should be inactivated and where appropriate a replacement concept be created if an equivalent concept does not already exist.

Details:

What is being inactivated (concept/description/any component)?The concept which is considered to be non-conformant to editorial policy
What is the reason for inactivation (description)?Either the FSN or the logical definition does not conform to current editorial policy
Which inactivation value should be used?The concept is non-conformant to editorial policy
Which historical association reference set should be used?Currently no association required

Known issues:

  1. It is currently unclear which elements of a "change" to editorial policy might result in the need to inactivate a concept
  2. There is currently no facility to record which editorial policy resulted in a requirement to inactivate the concept
  3. It is not possible to allocate an historical association and so management of the inactivation at a local level is at best difficult
  4. It is currently not clear whether non-conformance to editorial policy applies to the FSN alone or might include the logical definition

Examples:

Simple Example

185950005 Conf data - other Dr not see (finding)
WAS A (implicit)
270456003 Confidential patient data held (finding)

374547004 Dexamethasone sodium phospha 4mg/mL (product)
WAS A (implicit)
766346003 Dexamethasone sodium phosphate 0.1% conventional release eye drops (product)

331681007 Hydrocortisone ointments (product)
WAS A (implicit)
769209000 Product containing hydrocortisone in cutaneous dosage form (medicinal product form)

226807000 Elmlea cream (substance)
WAS_A (implicit)
226805008 Imitation cream (substance)

Complex Example

376026008 Testosterone 15mg (product) (Duplicate 20040731 → non-conformant 20180731)
SAME AS
404741007 Testosterone 15mg transdermal patch (product) (non-conformant 20180731)
WAS_A (implicit) 350366007 Testosterone patch (product) (also non-conformant 20180731)
WAS_A (implicit) 425047001 Topical form testosterone (product) (ambiguous 20180731)
MAYBE_A (explicit) 768999006 Product containing testosterone in cutaneous dosage form (medicinal product form)

Erroneous Example

312979000 Acquired blindness, one eye (disorder) (non-conformant 20180731)
WAS A (implicit; no explicit historical associations)
232149003 Acquired blindness (now itself ambiguous)
MAYBE 105597003 Blindness AND/OR vision impairment level (disorder)

NB contrast with earlier:

193743000 Acquired blindness, one eye (disorder) (ambiguous 20020131)
MAYBE_A (explicit)
105597003 Blindness AND/OR vision impairment level (disorder)

...noting that neither 312979000 nor 193743000 have any association with 22950006 Blindness of one eye (disorder)

Impact:

  • Authors
  1. Need to be clear about the distinction between editorial policy regarding ambiguous concepts e.g. AND/OR and those that relate to other aspects of non-conformance to editorial policy.
  2. In cases where a replacement term that does conform to ed. policy  is available/created, need to have an historical relationship available.
  • Release Management Team

  • Developers

  • End Users

Impact depends upon:

  1. If the inactivated component replacement is straightforwardly synonymous then there is a minimal effect (in which case there is a designated replacement). This accounts for vast majority of cases.
  2. If the inactivation results in a new component which the end user considers does not have the same meaning, then the end user must determine a replacement.

Potential improvement:

  1. Support a drop down list of potential non-conformance to editorial policy reasons for inactivation:
    1. Change in editorial policy for drugs/substances- add text string to state Ed Guide section or General Content (GC) or EDITPANEL Ticket
    2. Change in editorial policy for clinical findings - add text string to state Ed Guide section or General Content (GC) or EDITPANEL Ticket
    3. Non-conformance to current editorial guide - add text string to state Ed Guide section
  2. Support "REPLACED_BY" and "POSSIBLY_EQUIVALENT_TO" associations (NB: JTC - Not sure that POSSIBLY_EQUIVALENT_TO is an appropriate association.  We are not determining the semantics per se, but simply replacing a "bad" concept")
  3. Explicitly include changes in editorial policy that affect the logical definition of a concept

Supporting resources:

<url><comment>
  • No labels

2 Comments

  1. The logical definition does not conform to current editorial policy as a reason for inactivation?  Toni Morrison does this relate to the Drugs work? This is not something happening across all hierarchies. 

    This inactivation reason is also used for descriptions: IHTSDO-980 Review of description inactivation values#Descriptioninactivationvalueissuesandproposedactions and Description Inactivation. The focus there had been descriptions and it's noted the use with concepts needed further investigation. Changes to its use for concepts also needs to take into account its use for descriptions. In addition, the proposed changes may also impact the guidance on the order of selection of inactivation values for descriptions. 


    1. Hi Cathy Richardson

      In the Drug area, the Non-conformance reason was regularly used for inactivation of existing concepts that were out of scope for the International Release (e.g. a concept type or level of detail that was not being retained as the concept model and editorial guidelines were agreed and existing content was updated accordingly).

      After the first release, we received complaints about not having a historical relationship for these concepts, so we switched over and started using Ambiguous with one or more Possibly equivalent to relationships. We did not use Erroneous or Outdated because the Replaced by historical relationship was not appropriate (since we were not replacing these inactivated concepts).

      This is why I asked if we would be able to use Non-conformance with an option for one or more Possibly equivalent to attributes.

      Hope this helps,

      Toni