Page tree

StatusIn PROD
Version

1.0

New versionTemplate for simple disease (disorder) - v2.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance[
[Course] [Periods of life] [Process] [Morphology] of [Body structure] caused by [Substance] (disorder)FSNus:Pgb:Pci
[Course] [Periods of life] [Process] [Morphology] of [Body structure] caused by [agent]SYNus:Pgb:Pci


Concept model:

Definition status:  


900000000000073002 |Defined|

Applies To:

64572001 | Disease (disorder)|

Template language:

Link to the misaligned concept report:

https://docs.google.com/spreadsheets/d/13d7TmcAyhn6bg8j635aBmbkTi-wndcXmUkYuMgD6MV0/edit#gid=0

Rules for description generation: 

  1. Apply General rules for generating descriptions for templates;
  2. Apply Enhancements for the Template Language;

JIRA ticket:



2 Comments

  1. The authoring platform and terminology serve can support axioms in OWL representation now. The self-grouped attributes need to be placed in a role group that is greater than 0. For example, the attribute |Clinical course| was in role group 0 in the stated relationship file. Now, it should be in role group 1 or greater.

    The alternative approach is to represent role groups by fill in different colors as shown in above without role group numbers. This will be similar to dash lines used for indicating role group. 

    Please note the template language is also updated for role grouping.

  2. Updated the format for both the concept model table and template language. The key changes include:

    1. Moved role group attribute to the first column and changed the name to 'Attribute cardinality to align with the MRCM specification. The value in the first 'attribute cardinality' column specifies the number of an attribute can be present in a concept model. This template is a generic template for conditions that should only be modeled by a single role group. Therefore, the attribute cardinality is 1..1.   
    2. The second column 'attribute cardinality' is renamed as 'Cardinality cardinality within role group'. The general principle is that an attribute should not be present more than once in a role group. Note, some existing content has two finding sites in a role group that do not conform to this template. 
    3. The values in the concept model table should be represented in the following format in the template language section:
             [[ Attribute cardinality ]] {[[ Attribute cardinality in role group ]]  Attribute = [[ +id ( Value ) @slotName ]] }
    4. Each row should be present a pair of attribute/value in the template language and align with each row in the concept table. Note, the new line break will be ignored in the template alignment report query after the March deployment of the reporting platform.