Classification Derived Concept
Inactivation Reason | Association | Definition |
|---|---|---|
Classification Derived Concept | REPLACED_BY PARTIALLY_EQUIVALENT_TO | The inactivation reason “Classification Concept” explicitly states that the inactivated concept originates from the “closed world” classification paradigm and as such is inappropriate content for use within the clinical record. The inactivated concept (A) may be linked to one or more active concepts (B and/or C…) using historical associations as determined by the type of classification concept and associated guidance given below. Please note that this inactivation reason replaces "Limited Component" and historical association "WAS_A". |
Guidance | ||
Not Otherwise Specified
The concept contains an "and" or "with" representing a clinical statement composition
| ||
Examples
Classification concept:
{"timestamp":1794269501685,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Resolution
Inactivate {"timestamp":1794269501688,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
choose the drop-down list item 'The concept contains; Not Otherwise Specified'
REPLACED_BY {"timestamp":1794269501689,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Classification concept:
{"timestamp":1794269501659,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Resolution
Inactivate {"timestamp":1794269501671,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
choose the drop-down list item 'The concept contains "and or With"
PARTIALLLY_EQUIVALENT_TO {"timestamp":1794269501667,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
PARTIALLY_EQUIVALENT_TO{"timestamp":1794269501668,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Annotation:
Both concepts MUST be included in the patient's record
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 - REPLACED_BY |
|---|
(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 we (SNOMED International) have no knowledge of what has happened to CIntEd
The guidance recommends that EQUIVALENT_TO associations be between
194733006 |Mitral and aortic stenosis (disorder)| and
79619009 |Mitral valve stenosis (disorder)|
60573004 |Aortic valve stenosis (disorder)|
This is wrong. These three concepts are not equivalent.
A referenced component should not have more than one active “EQUIVALENT_TO " at any given time. If it's equivalent to two things, those two things are surely equivalent too?
There's also have consequences for "data healing" activities on longitudinal data stores so the cardinality of these associations is important.
Also, I get that there are some classification concepts that use “and” when they possibly mean “or”, but I’m not convinced this is an example of. Is the intention to get rid of all the conjunction concepts? That seems overzealous as many are very valid, and used. For example, do you prevent people from recording “Diarrhea and vomiting”. It’s easy to say Information models should handle this, but that’s not a simple implementation exercise without causing a poor user experience.
Groupers like “Menopausal and postmenopausal disorders (disorder)" I agree are not appropriate. But I don’t think a blanket rejection of “co-occurrence/conjunction” is the right move.
Similarly for “without”. Although we can’t (currently) model negation, Negative assertions are just as important as conjunctions. “Placenta praevia without haemorrhage" “Refractory migraine without aura".
We obviously don’t want to precoordinate every combination but many are useful, and removing existing concepts is not without downstream impact.