# Semantic duplicates **URL:** \ **Category:** Using SNOMED CT\ **Created:** [April 28, 2026, 11:02am UTC](https://forums.snomed.org/t/semantic-duplicates/1253 "2026-04-28T11:02:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Tessa](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@Tessa](https://forums.snomed.org/u/Tessa)\ **Post date:** [April 28, 2026, 11:02am UTC](https://forums.snomed.org/t/semantic-duplicates/1253/1 "2026-04-28T11:02:31Z")
Hello everyone, is there a substantive reason why the same diagnosis has two SCTIDs: SCTID: 66937008 Amylo-1,6-glucosidase deficiency SCTID: 124472001 Deficiency of amylo-1,6-glucosidase Thank you in advance for the clarification. @nepijko ---
**Author:** ![alopez](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/alopez/32/157_2.png) [@alopez](https://forums.snomed.org/u/alopez)\ **Post date:** [April 28, 2026, 11:45am UTC](https://forums.snomed.org/t/semantic-duplicates/1253/2 "2026-04-28T11:45:38Z")
Hi! The first one has a different Fully Specified Name: _66937008 |Glycogen storage disease, type III (disorder)|_ This concept represents the clinical syndrome. The second one represents the actual deficiency underlying the syndrome: _124472001 |Deficiency of amylo-1,6-glucosidase (disorder)|_ These are closely related but distinct; one may be more useful than the other in particular contexts. Having the synonym _“Amylo-1,6-glucosidase deficiency”_ in the _“Glycogen storage disease, type III (disorder)”_ concept may require further consideration; it was added in 2017, years after the concept was created, likely in response to user requirements. Best regards Alejandro ---
**Author:** ![jrogers](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@jrogers](https://forums.snomed.org/u/jrogers)\ **Post date:** [April 28, 2026, 2:00pm UTC](https://forums.snomed.org/t/semantic-duplicates/1253/3 "2026-04-28T14:00:36Z")
Yes, this is one of many examples of medical “etiological naming” conventions, wherein a broad (and often variably expressed) downstream phenotype is given the same name as the fixed upstream pathology that ultimately causes it. In this case, a syndrome phenotype carries the same name as the biochemical error that fundamentally causes it. There are MANY other examples, especially now in genetics. Much older examples include “malaria”, which was originally (but mistakenly) named for the “mal (bad) air” that was believed to cause it. More modern pre-genomix examples include heavy metal poisonings, a host of forms of fibrosing alveolitis that are named primarily for their causative agent (Silicosis, Ornithosis etc) and many biochemical states, including of course “hypoglycaemia”. There are some heritable inborn errors of metabolism that cause one distinct phenotype when they occur in isolation, but a different one when they co-occur with another inborn error. HbS, beta-thalassemia and HbS with beta-thalassemia are perhaps the best known such triad. But this example explains why, for ontological consistency, it is necessary for all biochemical errors (such as amylo-1,6-glucosidase deficiency) to be represented separately in SNOMED from the phenotypes that they cause, even when both are by convention often given the same label. ---
**Author:** ![jcase](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@jcase](https://forums.snomed.org/u/jcase)\ **Post date:** [April 28, 2026, 2:12pm UTC](https://forums.snomed.org/t/semantic-duplicates/1253/4 "2026-04-28T14:12:48Z")
This was one of the primary reasons for the addition of the new attribute HAS DEFICIENCY OF, which allows the syndrome caused by the deficiency to have the an explicit releation back to the deficiency itself. Having this new attribute, plus the addition of more specific naming conventions for the FSN will make the distinction between the cause and effect more visible. ---
**Author:** ![echeetham](https://avatars.discourse-cdn.com/v4/letter/e/c0e974/32.png) [@echeetham](https://forums.snomed.org/u/echeetham)\ **Post date:** [May 2, 2026, 7:24am UTC](https://forums.snomed.org/t/semantic-duplicates/1253/5 "2026-05-02T07:24:25Z")
> [@jcase](#): > > …the new attribute HAS DEFICIENCY OF…allows the syndrome caused by the deficiency to have the an explicit releation back to the deficiency itself… Really? If _ **66937008** _ is _‘…the syndrome caused by the deficiency…’_ and _ **124472001** _ is _‘…the deficiency itself…’_ then this quote suggests HAS DEFICIENCY OF will related the former to the latter. However in all briefing notes and discussions I can find we are told that HAS DEFICIENCY OF will take _substances_ in its range. I would therefore expect HAS DEFICIENCY OF to be used to define _124472001 |Deficiency of amylo-1,6-glucosidase (disorder)|_ in terms of _45947007 | Amylo-1,6-glucosidase (substance) |_. Surely it will be DUE TO relationships (Indicative proposal 4a “_Define 410053003 |Clinical manifestation of enzyme deficiency (disorder)| as a 75934005 |Metabolic disease (disorder)|DUE TO 129456006 |Specific enzyme deficiency (disorder)|_”) that will relate the two disorder/finding classes? More generally - and for the record - I still think the ‘ontologically pure’ distinction SI/EAG are attempting to represent here introduces very practical usability and understandability risks that have not yet been addressed. ---
**Author:** ![jcase](https://avatars.discourse-cdn.com/v4/letter/j/57b2e6/32.png) [@jcase](https://forums.snomed.org/u/jcase)\ **Post date:** [May 4, 2026, 4:23pm UTC](https://forums.snomed.org/t/semantic-duplicates/1253/6 "2026-05-04T16:23:04Z")
Your interpretation of the modeling is correct. My apologies for the misunderstanding