Complication [Disease] due to [diabetes mellitus] - In Progress
Status | In Progress |
|---|---|
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[Disease] due to [diabetes mellitus] (disorder) | FSN | us:P | gb:P | ci |
[Disease] due to [diabetes mellitus] (disorder) | SYN | us:P | gb:P | ci |
Concept model:
Attribute Cardinality | Attribute | Value | role group number | Attribute Group Cardinality |
|---|---|---|---|---|
1..1 |
{"timestamp":1794273606906,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1794273606885,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 | N/A |
0..1 | {"timestamp":1794273606888,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794273606884,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794273606896,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794273606879,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
1..1 | {"timestamp":1794273606881,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794273606896,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 | 1.1 |
0..1 | 2 | 0..1 | ||
0..1 | 3 | 0..1 | ||
0..1 | ||||
0..1 | 4 | 0..1 | ||
0..1 |
Definition status:
Applies To:
<< 74627003 | Diabetic complication (disorder) |
Template language:
Link to the misaligned concept report:
Link to the report which include all complex patterns: https://docs.google.com/spreadsheets/d/1RgqkUUaXMRCgC7YlbTWBO2gfebZ5zFZFC1CU-sssjHY/edit#gid=0
Rules for description generation:
Remove the semantic tag, e.g. (body structure)
Add a synonym of the form [Disease] due to [diabetes mellitus]
Comments
Hi Yongsheng Gao, I had wondered whether that was the case. Lets remove it and see what happens.
Thanks Former user (Deleted), I have removed the endocrine system and added the template language. The report should return some misalignments, but it did not. Peter Williams Could you please have a look at the template query. The example for the expected misalignment, e.g. 399866003 |Retinal venous beading co-occurrent and due to diabetes mellitus (disorder)|.
Will do yes, could you raise an Infra ticket please? I've got a lot to prioritise and that'll help ensure it doesn't get missed. Thanks Yongsheng Gao
Cheers Peter Williams, The INFRA ticket is added
Former user (Deleted) , if this is a true "due to" association, the complication due to diabetes is not a subconcept of diabetes. Should the finding site of endocrine system be removed?