Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case significance |
---|---|---|---|---|
[scale type][property] of [inheres in] to [towards] in [inherent location] by [technique] (observable entity) | FSN | US:PT | GB:PT | CS |
[scale type][property] of [inheres in] to [towards] in [inherent location] by [technique] | PT | US:PT | GB:PT | CS |
Concept model:
Attribute cardinality | Attribute | Value | Role group cardinality |
---|---|---|---|
1..1 | N/A | ||
1..1 | 1..1 | ||
0..1 | 1..1 | ||
1..1 | 1..1 | ||
0..1 | 1..1 | ||
1..1 | 1..1 | ||
1..1 | 1..1 | ||
0..1 | 1..1 |
Definition status:
900000000000073002 |Defined (core metadata concept)|
Applies To:
<< 363787002 |Observable entity (observable entity)| : 704320005 |Towards (attribute)| = << 17386008 |Product containing anti-infective (product)| AND 370130000 |Property (attribute)| = << 118588007 |Susceptibility (property) (qualifier value)| AND 704319004 |Inheres in (attribute)| = < 410607006 |Organism (organism)| AND 370132008 |Scale type (attribute)| = ( 30766002 |Quantitative (qualifier value)| OR 117363000 |Ordinal value (qualifier value)| )
Replaced By:
https://confluence.ihtsdotools.org/x/VzjoBg
Template language:
363787002 |Observable entity (observable entity)|
: [[~1..1]] { [[~1..1]]
704320005 |Towards (attribute)|
= [[ +id (<<
17386008 |Product containing anti-infective (product)|
) @towards]] } , [[~0..1]] { [[~0..1]]
718497002 |Inherent location (attribute)|
= [[ +id (<<
123037004 |Body structure|
OR <<
410607006 |Organism|
OR <<
105590001 |Substance|
OR <<
123038009 |Specimen|
OR <<
260787004 |Physical object|
) @location]]}, [[~1..1]] { [[~1..1]]
370130000 |Property (attribute)|
= [[ +id (<<
118588007 |Susceptibility (property) (qualifier value)|
) @property]] }, [[~0..1]] { [[~0..1]]
704327008 |Direct site (attribute)|
= [[ +id (<<
123038009 |Specimen (specimen)|
) @directsite]] }, [[~1..1]] { [[~1..1]]
704319004 |Inheres in (attribute)|
= [[ +id (<
410607006 |Organism (organism)|
) @inheresIn]] }, [[~1..1]] { [[~1..1]]
370132008 |Scale type (attribute)|
= [[ +id (=
30766002 |Quantitative (qualifier value)|
OR
117363000 |Ordinal value (qualifier value)|
) @scaleType]] }, [[~0..1]] { [[~0..1]]
246501002 |Technique (attribute)|
= [[ +id (<
272394005 |Technique (qualifier value)|
) @technique]] }
Link to the misaligned concept report:
Rules for description generation:
- Apply General rules for generating descriptions for templates;
- Apply Enhancements for the Template Language;
JIRA ticket:
- INFRA-4545Getting issue details... STATUS
- INFRA-8736Getting issue details... STATUS
6 Comments
Yongsheng Gao
Hi Suzanne Santamaria, it looks good to me. We will need to update the role grouping policy for observables. They are self-grouped in the current implementation.
Peter G. Williams
Could the "Applies To" be checked here? I think "AND" has been used in error and there should be commas instead.
I picked this up in the List All Templates report which is currently broken in Production. I've told it to flag up any templates where the domain doesn't match any concepts.
See https://authoring.ihtsdotools.org/template-service/templates/Susceptibility%20Observable
Suzanne Santamaria
Yongsheng Gao , is it acceptable to change from the use of "AND" to commas in the "Applies To" section in this template?
Thanks,
Suzanne
Yongsheng Gao
Hi Suzanne Santamaria , the issue is not about the 'AND' in the syntax because it is the same as the comma. Please see example at 6.4 Conjunction and Disjunction
It looks like that we do not have any concept that is modelled by Property = << Susceptibility (property). Please run the ECL: << 363787002 |Observable entity (observable entity)| : 370130000 |Property (attribute)| = << 118588007 |Susceptibility (property) (qualifier value)|. Therefore, it is correct that this template does not match any concepts.
Cheers,
Yong
cc: Peter G. Williams
Peter G. Williams
Thanks for clarifying that the use of AND is fine here Yong. That's my TIL - today I learned - moment. I've always used commas.
So what's the story for this template that applies to no concepts then?
Suzanne Santamaria
Hi Peter G. Williams, we needed to create a model for the susceptibility LOINC Terms (which align with post-coordinated SNOMED CT expressions using the observable entity model in the LOINC - SNOMED CT Cooperation Project work). SNOMED does not currently contain many susceptibility test concepts, and the ones we have are in the evaluation procedure hierarchy, which as you know may be changed to the observable entity hierarchy at some point and will then use this model.
Thanks Yongsheng Gaofor clarifying the use of "AND."
CC: Farzaneh Ashrafi