SNOMED CT Editorial Advisory Group

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Jeff Pierson

Saved on

compared with

New Version 3

changes.mady.by.user Paul Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Title


Narrative description

(Describe the inactivation scenario in a few lines)

...

Details

(Provide specifics about the scenario to support comparison to other scenarios)

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?...
Which historical association reference set should be used?...

Known issues

(Describe any issues that may occur for this scenario and which may complicate interpretation of the inactivation)

  1. ...

Examples

Simple Example


Complex Example
Erroneous Example

Impact

(Describe how specific stakeholders are affected by the inactivation)

  •  Authors

  •  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

(Provide an indication of whether the current inactivation mechanism for this scenario is sufficient, or provide your ideas or thoughts on potential improvements)


Supporting resources

(Provide links to any resources relevant for this scenario)

<url><comment>

...