Aneurysm of [Cardiovascular system structure] (disorder) - v1.0
Status | In PROD |
|---|---|
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance[ |
|---|---|---|---|---|
[Course] [Aneurysm morphology] of [Cardiovascular system structure] (disorder) | FSN | us:P | gb:P | ci |
[Course] [Aneurysm morphology] of [Cardiovascular system structure] | SYN | us:P | gb:P | ci |
Concept model:
Attribute cardinality | Attribute | Value | role group number | Role Group Cardinality |
|---|---|---|---|---|
1..1 | {"timestamp":1791211773555,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1791211773502,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
|
0..1 | {"timestamp":1791211773553,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Course] {"timestamp":1791211773525,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 |
1 .. * @rolegroup |
1..1 | {"timestamp":1791211773496,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1791211773517,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 | |
1..1 | {"timestamp":1791211773502,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1791211773529,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 | |
0..1 |
| 1 |
Definition status:
Applies to:
Template Language:
Rules for description generation:
JIRA tickets:
https://projects.jira.snomed.org/browse/INFRA-3281
Comments
Former user (Deleted) I have made some changes to the template description pattern. Could we clarify the usage for pathological process for this template? Among 30 concepts modelled with course = congenital, 23 concepts are modeled with additional |Pathological process (attribute)| =|Pathological developmental process|, but 7 concepts are not.
Yongsheng Gao and Former user (Deleted) , I have not finished this area as I have been focused on IPs and unused "Congenital" morphologies. The 7 congenital aneurysm concepts without PATH PROCESS are errors of omission and should be corrected. If this is a blocker, I can fix those "quickly"
Yongsheng Gao strange because I had assumed that Jim had completed this section for the congenital aneurysms. I assume the normalisation process would not have picked it up as it is optional. I am happy to review and update.
Is there a way of changing the template to accommodate 'IF |course| = |congenital| THEN |pathological process| = |pathological development process| - probably wishful thinking.
Thanks
Paul
Hi Former user (Deleted) The template language does not support conditional clauses, e.g. if ... then .... There will be false negative by template alignment report. The following ECL query would identify those concepts without pathological process.
<< 432119003 |Aneurysm (disorder)|:
{246454002 |Occurrence (attribute)|=255399007 |Congenital (qualifier value)| AND
[0..0] 370135005 |Pathological process (attribute)|
=<<308490002 |Pathological developmental process (qualifier value)|}
If we change aneurysm to 64572001|Disease (disorder)|, it reveal that 1,410 congenital disorders do not have pathological developmental process. Jim Case I have created a new template to update the one in PROD. The congenital disease template mandates the pathologic process. Could you please review the template Congenital disease v2 - For review