Complication of surgical 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]/temporally related to/during/after surgical procedure (disorder) | FSN | us:P | gb:P | ci |
[Course] [Periods of life] [Process] [Morphology] of [Body structure] [due to]/temporally related to/during/after surgical procedure | SYN | us:P | gb:P | ci |
Concept model:
Attribute cardinality | Attribute cardinality in role group | Attribute | Value |
|---|---|---|---|
1..1 | 0..0 | {"timestamp":1794272913424,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272913439,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
0..1 | 0..1 | {"timestamp":1794272913443,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272913458,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
0..1 | 0..1 | {"timestamp":1794272913467,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794272913460,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
1..1 | 1..1 | {"timestamp":1794272913439,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} default ( 255234002 |After (attribute)| ) | {"timestamp":1794272913468,"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 | ||
0..1 | 0..1 |
Definition status:
Applies to:
Template language:
JIRA ticket:
Rules for generating descriptions:
Comments
Hi Jim Case, I have added the template language and made the following changes:
Added the domain restriction for this template.
Updated the format for cardinalities by moved the column to the second column.
Updated the cardinality value for finding role group. It should also be optional though role group for disorder or finding should at least be present. However, it cannot be determined for template until at the content authoring stage by template.
The role group for disorders reused the spec at Template for simple disease (disorder) - v2.0 for consistency.
The ranges have been further restricted, e.g. < 260787004 |Physical object (physical object)|, < 363787002 |Observable entity (observable entity)|, < 260245000 |Findings values (qualifier value)| OR < 263714004 |Colors (qualifier value)|
Hi Yongsheng Gao
While you are at it, I created/revised the following templates.They need to be reviewed and the template language updated.
Template name | URL |
Disorder due to/temporally related to [Clinical Finding / Disorder/Event/Procedure] associated with [Physical Object] - revised template - needs review and update of template language | |
Disorder with [Clinical Finding (interprets/has interpretation] - revised template - needs review and update of template language | |
Disorder due to/after [Event] - revised template - needs review and update of template language | |
Disorder due to/following procedure (disorder) | |
Disorder associated with device (disorder) |
Thank you
Hi Bruce Goldberg, thanks for the reminder. Will do.
Yongsheng Gao,
When trying to run this template for compliance using 271984008 |Disorder of prosthetic cardiac valve (disorder)| as the top level concept, the report fails. Any help in debugging would be appreciated
Hi Jim Case, the issue was caused by the default value which is a new feature supported by the WIP template language. [[ +id (<< 726633004 |Temporally related to (attribute)| ) default ( 255234002 |After (attribute)| ]] We will need the enhancement in the reporting platform to support the new template language features. I raised a JIRA ticket for the technical team. https://projects.jira.snomed.org/browse/INFRA-6786
I have changed it to |After| in the query in the reporting platform. The report only identified three concepts that are not aligned with the template.
Yongsheng Gao,
Can we get the template language written for this?