Deformity of [body structure] (disorder) - v1.0
Status | Archived |
|---|---|
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[course] [morphology] of [body structure] caused by [agent] (disorder) | FSN | us:P | gb:P | ci |
[course] [morphology] of [body structure] caused by [agent] | SYN | us:P | gb:P | ci |
Concept model:
Attribute cardinality | Attribute | Value | Role group number | Role group cardinality |
|---|---|---|---|---|
1..1 |
{"timestamp":1792060543232,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1792060543222,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 | N/A |
0..1 | {"timestamp":1792060543219,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Course] {"timestamp":1792060543215,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
| 0 | N/A |
0..1 |
{"timestamp":1792060543237,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1792060543241,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 | 1..1 |
1..1 |
{"timestamp":1792060543260,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} |
{"timestamp":1792060543275,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 | |
0..1 |
|
| 1 | |
0..1 | 1 | |||
0..1 | [agent] | 1 |
Definition status:
Applies to:
Template Language:
Link to the misaligned concept report
https://docs.google.com/spreadsheets/d/1QGAnnSbAKdloO2QtsPbN7Y6oK27EY3taGTWmnE-gmdU/edit#gid=2
Simple - https://docs.google.com/spreadsheets/d/16vB8OozMuqIp_Z5rc0Wb7uyzFhWwHUT49m8gk1B2sKI/edit
Rules for description generation:
JIRA ticket:
Comments
Hi Yongsheng Gao, thank you for the feedback. I have updated the template to include physical force and removed the interprets attribute.
Thanks Suzanne Santamaria The template is ready for implementation. The link to the report is added. Cheers, Yong
Yongsheng Gao I just updated the attribute cardinally for Occurrence. It had been 1..1 and I just changed it to 0..1. Please confirm this change is what we want.
Suzanne Santamaria Yes, the occurrence should be optional as 0..1.
I wonder if there's a case for splitting this into two templates, as much for the sake of the semantic tag as anything Suzanne Santamaria
I use the focus concept to indicate the PPP when I come to normalize, and I believe for the (finding) concepts I'll be setting that to Clinical Finding rather than Disease?
Hi Peter Williams, I'm not sure if your comment is still current. We already have two templates for deformities. The other one is here: https://snomed.atlassian.net/wiki/x/Rp-8Bw.
Thanks Suzanne Santamaria, having 417893002 |Deformity (finding)| as the applicable range for this template threw me. Yes, the other template is what I needed to be using.
Hi
Suzanne Santamaria, |physical force| has been modelled for some concepts. You might want to include it as allowed range. If you were intended to review them, it is fine to leave the template as it is.
Regarding attribute |interprets|, the |Contracture of joint| template provides a model that mandates |interprets|. If we include this attribute as optional in this template, it might have less non-conformance report. However, it does not provide any guidance that what condition would require |interprets|. If we remove this attribute, it would help us to identify subdomains that need additional attributes. So, we can develop more templates that is similar to Contracture of joint to help authoring. If you prefer to include |interprets|, we also need to include |has interpretation| as optional. Both |interprets| and |has interpretation| need to be placed in a separate role group. Thought?