Hematoma of [body structure] due to [disorder] (disorder) - v1.0
Status | In PROD |
|---|---|
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[Periods of life][Morphology] of [Body structure] due to [disorder] (disorder) | FSN | us:P | gb:P | ci |
[Periods of life][Morphology] of [Body structure] due to [disorder] | SYN | us:P | gb:P | ci |
Concept model:
Attribute Cardinality | Attribute | Value | Role Group Cardinality |
|---|---|---|---|
1..1 | {"timestamp":1792063051081,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1792063051084,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
N/A |
0..1 | {"timestamp":1792063051069,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1792063051180,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
|
1..1 | {"timestamp":1792063051295,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Morphology] {"timestamp":1792063051183,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
1..1 |
0..1 | {"timestamp":1792063051091,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Body structure] {"timestamp":1792063051039,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | |
0..1 |
Definition status:
Applies To:
Template language:
Link to the misaligned concept report
Complex - https://docs.google.com/spreadsheets/d/1y28A5_qD8ukAnbekxizkZy_xe6gGYDhOsLgVNhBd6Q0/edit#gid=0
Rules for description generation:
JIRA ticket:
https://projects.jira.snomed.org/browse/QI-189
https://projects.jira.snomed.org/browse/INFRA-3457
Comments
Cathy Richardson , Should this template also include clinical course, occurrence ?
Yongsheng Gao There are 206 hematoma disorder concepts. Only 2 of these concepts use a clinical course attribute so I'd suggest we not include that attribute. It would be better to check on concepts that need that attribute for validity. 10 hematoma concepts use the occurrence attribute and 5 of these relate to birth trauma for which we have a template in draft. I'll add occurrence given the overall numbers.
At some point it would be good to look at the templates in relation to areas in which they overlap e.g. the birth trauma one and hematoma, fracture ones etc..to check our consistency - naming conventions, modelling.
Cathy Richardson I agree that those occasionally used attribute should be reviewed before they are included in the template. I have updated the cardinality for associated morphology as mandated. The template language and link to the report are added. This template is ready for implementation.
The first step is to build a library of templates. Then, we will need to consolidate and refine the templates in the library. The domains for templates and descriptions patterns will need to be refined over time.