Inactivation Scenarios Template

Narrative description

(Describe the inactivation scenario in a few lines)

2 concepts appear to have the same meaning. This may arise for the following reasons:

• The FSN has different word order but the implied meaning is the same
• The concept shares the same descriptions (synonyms) but the FSNs are slightly different
• While the descriptions may be different the 2 concepts share the same modelling
• The FSNs imply that the concepts are the same but the modelling is different

Details

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

Known issues

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

1. Establishing semantic equivalence is key and may be difficult. If there is doubt consider using ambiguous as the inactivation reason
2. Where the concepts have subtypes consider whether they add 'meaning' to the parent term and provide further evidence of semantic equivalence
3. Where the modeling indicates semantic difference establish whether these differences impact other concepts and analytics
4. Consider whether the following might be semantically equivalent:

   1. xxx disorder and xxx disorder without yyy disorder

   2. xxx disorder and xxx finding

   3. on examination xxx and xxx finding

Examples

Simple Example

Impact

(Describe how specific stakeholders are affected by the inactivation)

• Authors

• Release Management Team

• Developers

• End Users

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)