Ambiguous Component

Narrative description

(Describe the inactivation scenario in a few lines)

The concept is considered to be ambiguous when there is the potential for a user to interpret the meaning in more than one way. This may arise due to inherent conflict between or within the descriptions, where the modelling of the concept does not reflect the meaning of the FSN or where the

Details

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

Ambiguity may be apparent for a number of reasons:

• The FSN is ambiguous
• Modeling is more specific than the FSN meaning
• The FSN meaning is more specific than the modeling; inactivation is determined case-by-case as this could simply be a primitive concept which cannot be defined
• Moving to a different top-level hierarchy
• Changing the common name to the scientific name
• Ancestors and descendants (if any) of the concept are inconsistent with what is implied by the FSN - inactivate concepts

Known issues

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

1. ...

Examples

Simple Example

Impact

(Describe how specific stakeholders are affected by the inactivation)

• Authors

• Release Management Team

• Developers

• End Users

Impact depends upon:

1. If the end user agrees the component is ambiguous then management i

2. If the end user disagrees that the component is erroneous, then a suitable replacement SNOMED component is needed. This can pose a problem.

3. Including the exact reason the component is determined to be erroneous would help the end user reconcile the inactivation.

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)