Disorder of [body structure] development (disorder) V2
Status | In progress |
|---|---|
Version | 1.1 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance[ |
|---|---|---|---|---|
[Course] [Periods of life] [Process] [Morphology] of [Body structure] caused by [causative agent] (disorder) | FSN | us:P | gb:P | ci |
[Course] [Periods of life] [Process] [Morphology] of [Body structure] caused by [causative agent] | SYN | us:P | gb:P | ci |
Concept model:
Attribute Cardinality | Attribute | Value | Role Group Cardinality |
|---|---|---|---|
1..1 | {"timestamp":1794273379640,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1794273379682,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | N/A |
0..1 | {"timestamp":1794273379643,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Course] {"timestamp":1794273379662,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0..1 |
1..1 | {"timestamp":1794273379673,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Morphology] {"timestamp":1794273379666,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1..* |
1..1 | {"timestamp":1794273379666,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Body structure] {"timestamp":1794273379645,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | |
0..1 | [Periods of life] | ||
0..1 | [Causative] | ||
1..1 | [Process] | ||
0..1 | OR OR
| 0..1 | |
0..1 |
Definition status:
Applies To:
Template language:
Rules for description generation:
JIRA ticket:
Part of the larger developmental disorders QI topic: https://projects.jira.snomed.org/browse/QI-83
https://projects.jira.snomed.org/browse/INFRA-5277
Reports:
Reports rerun to support finalisation of template. Please see QI ticket for analysis work.
Bone development initial report: https://docs.google.com/spreadsheets/d/1aAjBDBCadWNFKtM5hiBE-KUN1hGL5gabUA6ELSQMHrY/edit?usp=sharing
Bone development misaligned report: https://docs.google.com/spreadsheets/d/1i4mMYJA39RGSryATo6i7UO3DQu98F8VZRJUX-GZq2wI/edit?usp=sharing
Tooth development initial report: https://docs.google.com/spreadsheets/d/1fxCJLeoKDvIWWqKpx6Two0b_bLf9EHOoqfKRm7rNLIU/edit?usp=sharing
Tooth development misaligned report: https://docs.google.com/spreadsheets/d/1WAhMZAwNTq3yFjAuDShD5iAt0YlVaGo1woQRIG2HMP4/edit?usp=sharing
Hi Cathy Richardsonyou asked me to check over the STL here. Looks good. Watch out for consistency in the angle brackets. Like in the table we've got [Morphology] < 49755003 |Morphologically abnormal structure (morphologic abnormality)| which would mean that 49755003 itself would not be acceptable, but in the STL we've got << 49755003 |Morphologically abnormal structure (morphologic abnormality)| so it would be OK there.
The other thing is that a slot is only needed where there is a choice. Where there is no choice, there's no need for a slot. So the pathological process which is sort of "hard coded" can just be written like a normal expression : [[~1..1]] 370135005 |Pathological process (attribute)| = 308490002 |Pathological developmental process (qualifier value)|
The opposite situation occurred for finding values. If you have a choice, you must have a slot! So you want to add in the square slot brackets there and also in that element, I think we're saying you couldn't actually use "Finding values" so the STL is correct to use a single < and the table needs to be in line with that, not << as it is now.