Erroneous Concept
k guidance
Inactivation Reason | Association Type | Description |
|---|---|---|
Erroneous | REPLACED_BY | The inactivation reason “Erroneous Component” explicitly states that the inactivated concept (A) has an FSN which contains an error that when corrected potentially changes the semantic meaning of the concept and that in the judgment of the author/editor the true original meaning is now represented by the “REPLACED_BY” concept (B). Note: this inactivation reason should not be used to correct punctuation, word order changes, or minor spelling mistakes that do not change the meaning of the FSN - these changes can be made by inactivation and replacement of the FSN. |
Guidance | ||
| ||
Examples
Inactivate concept:
{"timestamp":1794269552717,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
REPLACED_BY {"timestamp":1794269552717,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Annotation
Drug description incomplete
Although superficially some typographical errors can appear insignificant it is safer to inactivate and replace as the spelling differences between organism names can be small.
Inactivate concept:
{"timestamp":1794269552729,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
REPLACED_BY:{"timestamp":1794269552741,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Annotation
Incorrect spelling of organism requiring inactivation
Resolving sequences of Historical Associations
The intention is that functionality to resolve sequences of Historical Associations will normally be seamlessly integrated into the tooling so as to present to the user the appropriate updated historically association to be allocated.
Whenever an already stated REPLACED_BY target itself also becomes inactive - whether at the same release or later, identifying the replacement for the original concept, should follow the combinatorial logic stated below.
Combinatorial Logic |
|---|
(A) REPLACED_BY (B) and (B) SAME_AS (C) implies (A) REPLACED_BY (C) (A) REPLACED_BY (B) and (B) REPLACED_BY (C) implies (A) REPLACED_BY (C) (AIntEd) REPLACED_BY (BIntEd) and (BIntEd) MOVED_TO (CNRC) implies (AIntEd) MOVED_TO (CNRC) (A) REPLACED_BY (B) and (B) POSSIBLY_EQUIVALENT_TO (C, D) implies (A) POSSIBLY_EQUIVALENT_TO (C, D) (A) REPLACED_BY (B) and (B) WAS_A (C AND D) implies (A) WAS_A (C AND D) |
Note: Once MOVED_TO the NRC, SNOMED International have no knowledge of what has happened to BIntEd
This reason for inactivation is also used for descriptions and at present the definition present on Erroneous component is 'A component that contains a technical error'.
https://dailybuild.ihtsdotools.org/?perspective=full&conceptId1=900000000000485001&edition=MAIN&release=&languages=en
Description Inactivation
This guidance should comment on the use for both, though given the change of meaning of 'Erroneous', consideration is going to need to be given to descriptions using this reason for inactivation (or those which need inactivation where erroneous would have been used) prior to this being brought in.
Also given (as noted previously) this document is used by external users guidance such as 'Therefore, do not hesitate to consider internal discussion if there is any doubt as to the most appropriate solution' and tooling guidance (for those using a different platform) should be recognised as guidance given as required.