Disorder due to/following procedure (disorder)
Status | For review |
|---|---|
Version | 0.5 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[Course] [Periods of life] [Process] [Morphology] of [Body structure] due to/following procedure (disorder) | FSN | us:P | gb:P | ci |
[Course] [Periods of life] [Process] [Morphology] of [Body structure] due to/following procedure | SYN | us:P | gb:P | ci |
Concept model:
Attribute cardinality | Attribute cardinality in role group | Attribute | Value |
|---|---|---|---|
1..1 | 0..0 | {"timestamp":1794272915497,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272915478,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
0..1 | 0..1 | {"timestamp":1794272915478,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272915503,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
1..1 | 0..1 | {"timestamp":1794272915515,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272915514,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
0..1 | 0..1 | {"timestamp":1794272915476,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272915504,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
0..1 | 0..1 | ||
0..1 | 0..1 | ||
0..1 | 0..1 | ||
0..1 | 0..1 | ||
0..1 | 0..1 | ||
0..1 | 0..1 | ||
0..1 | 0..1 |
Definition status:
Applies to
< 64572001 |Disease (disorder)| : 42752001 |Due to (attribute)| =< 71388002 |Procedure (procedure)| / 255234002 |After (attribute)| =<< 71388002 |Procedure (procedure)|
Rules for generating descriptions:
Comments
Hi Yongsheng Gao.
This relates to the issue where surgeons do not want to consider sequelae as complications but rather as expected after effects of surgery. Thus, for disease due to and following surgical procedures, sequela is not included as a parent. For non-surgical procedures, we should include sequela as a parent.
Bruce
Hi Bruce Goldberg , if following surgical procedure is not sequelae, should the same logic be applicable to procedure? Sequela is a condition which is the consequence of a previous disease or injury.
cc: Jim Case
Template revised.
Peter G. Williams , please update template language
Hi Bruce Goldberg, can we generalise this template for 'disease due to and following procedure'? Is it necessary to include sequela as it is parent concept? In another template, disease due to and following surgical procedures is complication only. If we need to both complication and sequela, this template can be merged as Disease due to and following disease/procedure.
cc: Jim Case