# Translation of causation and co-occurrence in FSN **URL:** \ **Category:** Translation User Group\ **Tags:** tug-under-discussion\ **Created:** [November 5, 2026, 4:32pm UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722 "2026-11-05T16:32:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ovage](https://avatars.discourse-cdn.com/v4/letter/o/bc8723/32.png) [@ovage](https://forums.snomed.org/u/ovage)\ **Post date:** [November 5, 2026, 4:32pm UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/1 "2026-11-05T16:32:03Z")
SNOMED CT contains a certain amount of FSNs expressing causatin and co-occurrence, for example 8161000119106 |Arthritis co-occurrent and due to Crohn’s disease (disorder)| and 15993551000119100 |Disorder of eye co-occurrent and due to Marfan syndrome (disorder)|. According to the Editorial Guide, no new concepts should be modelled wtih this description. However, there are still some legacy concepts: “There are approximately 300 legacy concepts with _co-occurrent and due_ _to_ in the description. Do not add new concepts with the terming _co-occurrent and due to;_ instead use co-occurrence modeling (both conditions are represented in a supertype) in addition to the _Due to_ (attribute) if warranted by the clinical condition.” ([Disorder Combination Modeling | Specifications SNOMED CT Editorial Guide | SNOMED International Documents](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/disorder-combination-modeling#naming-pattern-1)) Translating FSNs of combined disorders which are related by two phrases are challenging, especially when a natural and clinical friendly language is the ideal. In Norway, we will change these translation, omitting the “co-occurrent” element. This also is in alignment with the description of new concepts in the international editions. Have other countries considered similar approaches? ---
**Author:** ![klindve2025](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/klindve2025/32/823_2.png) [@klindve2025](https://forums.snomed.org/u/klindve2025)\ **Post date:** [November 6, 2026, 1:52pm UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/2 "2026-11-06T13:52:58Z")
Hi! We started to look at these last year and I agree that co-current can be omitted in the translation. It will make the preferred term easier to understand as well. ---
**Author:** ![cdanielsen](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/cdanielsen/32/251_2.png) [@cdanielsen](https://forums.snomed.org/u/cdanielsen)\ **Post date:** [November 6, 2026, 2:17pm UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/3 "2026-11-06T14:17:55Z")
This sounds like a solution that DK might adopt too, but is SI not still working on these descriptions and could the result in some cases be something different than what you expect? ---
**Author:** ![klindve2025](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/klindve2025/32/823_2.png) [@klindve2025](https://forums.snomed.org/u/klindve2025)\ **Post date:** [November 9, 2026, 10:47am UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/4 "2026-11-09T10:47:15Z")
I also noted that “due to” is often an occurring part of the co-current concepts (like the issue we are discussing here), but we also have co-current without due to (and due to without co-current). So… need to look at our current translations an see if anything changes if we omit co-current. ---
**Author:** ![annatina](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@annatina](https://forums.snomed.org/u/annatina)\ **Post date:** [November 10, 2026, 9:23am UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/5 "2026-11-10T09:23:46Z")
Hi @ovage and all, this is the excerpt form our translation guideline [https://conf.spaces.snomed.org/wiki/spaces/GTG/pages/132539391/SNOMED+CT+D-A-CH-+bersetzungsrichtlinie:](https://conf.spaces.snomed.org/wiki/spaces/GTG/pages/132539391/SNOMED+CT+D-A-CH-+bersetzungsrichtlinie:) ![image](https://europe1.discourse-cdn.com/flex014/uploads/snomed/original/1X/c1d1f97db66f7f835ad411d3f567b9c8f2dc42e0.png) =\> we decided to translate “co-occurrent and due to” into “_mit und durch_ = with and due to”, which is sufficiently short so it was accepted. Regarding the co-occurrence topic I had an exchange on CRS, see [https://prod-request.ihtsdotools.org/#/requests/preview/967214?kb](https://prod-request.ihtsdotools.org/#/requests/preview/967214?kb) . Best regards from Austria, Annatina ---
**Author:** ![mcordell](https://dub1.discourse-cdn.com/flex014/user_avatar/forums.snomed.org/mcordell/32/325_2.png) [@mcordell](https://forums.snomed.org/u/mcordell)\ **Post date:** [November 10, 2026, 7:19pm UTC](https://forums.snomed.org/t/translation-of-causation-and-co-occurrence-in-fsn/1722/6 "2026-11-10T19:19:14Z")
Your approach seems to align with the latest editorial advice for the terms. Where the “co-occurrent” element is implied (unless it is explicitly “following”). Though you’ve also highlighted a general frustration of mine with how the editorial changes are managed: > [@ovage](#): > > “There are approximately 300 legacy concepts with _co-occurrent and due_ _to_ in the description. Do not add new concepts with the terming _co-occurrent and due to;_ instead use co-occurrence modeling (both conditions are represented in a supertype) in addition to the _Due to_ (attribute) if warranted by the clinical condition.” Not updating legacy content to reflect updated editorial rules, is arguably worse than not updating the editorial rules. It introduces more inconsistency and confusion. It’s also much easier for authors to create new content based on the precedent of existing content.