Foreign body of [body structure] (disorder) - v1.0
Status | In PROD |
|---|---|
Version | 1.0 |
Interim template to support QI work. Further work required on model. See: https://projects.jira.snomed.org/browse/IHTSDO-848
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
|---|---|---|---|---|
[Morphology] of [Body structure] (disorder) | FSN | us:P | gb:P | ci |
[Morphology] of [Body structure] | SYN | us:P | gb:P | ci |
Concept model:
Attribute Cardinality | Attribute | Value | role group number | Role Group Cardinality |
|---|---|---|---|---|
1..1 | {"timestamp":1792059537350,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | {"timestamp":1792059537347,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 0 |
N/A |
1..1 | {"timestamp":1792059537323,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Morphology] {"timestamp":1792059537337,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 |
1..1 |
0..1 | {"timestamp":1792059537328,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | [Body structure] {"timestamp":1792059537334,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"} | 1 |
Definition status:
{"timestamp":1792059537324,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}
Applies To:
Template Language
Link to the misaligned concept report:
Rules for description generation:
JIRA ticket:
https://projects.jira.snomed.org/browse/INFRA-3464
https://projects.jira.snomed.org/browse/QI-194
Comments
Peter Williams , it may be premature (or not) to do that. We are talking in the ECE and EAG about expanding the PATHOLOGICAL PROCESS range to include new values (such as mechanical trauma) that might be applicable at a later date. However, if we have the ability to modify this template later when these changes come, then I am probably being a bti too cautious.
Hi Jim Case Yes it will be no problem to add a slot name at the same time as the "<<" is added to the attribute value.
Yongsheng Gao Would you please review this template. I have removed the infectious process and causative agent from the template given we have this template: Complication due to disease/procedure(disorder) - for review. In addition many of the current infected foreign body concepts include "without major open wound" and so are slated for movement to situations. Thanks, Cathy.
Cathy Richardson , as discussed, the revision of concept model by causative agent = << |Physical object| needs to be tested. The corespondent physical objects need to be created if they are not covered yet. There are about 417 concepts that are modelled by these subtype of foreign body morphologies. Could you please clarify if this is going to be addressed in this QI task or not?
I think I'd like to take the slot name out of the Pathological Process because it's not a slot - the user has no option about what value goes in there, it's always going to be 441862004 |Infectious process (qualifier value)| - "hard coded" we might say in programming circles. The causative agent could use one however.