Contusion of [body structure] (disorder) - v1.0
Status | In PROD |
|---|---|
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[Course] contusion of [X body structure] (disorder) | FSN | us:P | gb:P | ci |
[Course] contusion of [X body structure] | SYN | us:P | gb:P | ci |
[Course] bruise of [X body structure] | SYN | us:A | gb:A | ci |
Concept model:
Attribute cardinality | Attribute | Value | Role group cardinality |
|---|---|---|---|
1..1 | {"timestamp":1789550627586,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1789550627563,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | N/A |
0..1 | {"timestamp":1789550627585,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1789550627608,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0..1 |
1..1 | {"timestamp":1789550627624,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1789550627617,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1..1 |
1..1 | {"timestamp":1789550627604,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1789550627589,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1..1 |
0..1 | [body structure] | ||
0..1 | 0..* | ||
0..1 |
Definition status:
Applies to
Template language:
Link to the misaligned concept report:
https://docs.google.com/spreadsheets/d/1-SX7NzyUUEltjYmDvIO56t408wbYfOIDBqGNt66ZXR8/edit#gid=0
Rules for generating descriptions:
JIRA tickets:
https://projects.jira.snomed.org/browse/INFRA-5278
Comments
Many thanks @Peter Williams for the quick action. I will get right on it. Looks like the template may need to be updated to reflect the second morphology, which would not be a subtype of contusion. Would that be the right approach?
Yes I think so, a 2nd optional role group where the morphology is << 49755003 |Morphologically abnormal structure (morphologic abnormality)| MINUS << 308492005 |Contusion - lesion (morphologic abnormality)| to ensure that the 2nd role group contains a different morphology from the 1st. Would we want the 2nd role group to always use the same finding site as the 1st role group? We'd give that 2nd slot the same name as the 1st (eg @fsite) in that case to indicate they're expected to contain the same value - they're effectively the same thing in two different places.
@Peter Williams, no, the finding site could be different.
See the proposed edits to make sure I got the cardinalities correct
Hi @Jim Case, I have updated the template language and included the clinical course in the description pattern. The term pattern for additional morphology and site would not be easy. It could be improved in future. The cardinality for the additional morphology is changed to optional to align with the role group cardinality. If you do not have any further changes, this template is ready for implementation.
Hi @Jim CaseI said I'd check out contusion for you and I assume this was the one since you've been in here recently. I filled in the report above. 46 misaligned and it seems to be nearly all concepts which have some secondary morphology - a wound, fracture or focal damage - as well as the contusion in another role group.