Request management
Types of requests and suggested fields of each type of request
1. New Concept
| Field Name | Definition | Valid values | Optionality |
| Requestor Internal ID | An alphanumeric value that you can define to uniquely identify this request in your database (or spreadsheet). Note that we may accept your request but assign different terms (FSN, PT, synonyms) than what you suggest. Assigning this ID ensures you can easily track the processed items to your original requests. | An alpha-numeric value | Optional |
| Parent ID | The concept ID of the parent that you are proposing for this new concept. NOTE: If you would like to propose more than one parent for this concept, please identify the other parents in "Notes" column. | Concept IDs in SNOMED CT International | Optional |
| Parent FSN | The FSN (Fully Specified Name) of the parent that you are proposing for this new concept. NOTE: If you would like to propose more than one parent for this concept, please identify the other parents in "Notes" column. | FSNs in SNOMED CT International | Optional |
| FSN | The FSN (Fully Specified Name) that you are proposing for this new concept | Mandatory | |
| PT | The PT (Preferred Term) that you are proposing for this new concept | Mandatory | |
| Synonym | A synonym that you would like to propose for this new concept | Optional | |
| Definition | A text definition for the new concept that you are proposing. Although the FSN should uniquely and adequately describe the term, adding a more elaborate text definition could sometimes help in understanding what exactly the concept represents. For example, here is a text definition added on this FSN: "Eosinophilic pustular folliculitis (disorder)" A dermatosis with pruritic sterile papules and pustules that come together to form plaques with papulovesicular borders, and a tendency toward central clearing and hyperpigmentation, with spontaneous exacerbations and remissions. Histologically variable with folliculitis of follicle sheath and perifollicular dermis and spongiosis of follicular epithelium, sometimes with peripheral leukocytosis and or eosinophilia and or eosinophilic abscesses. | Optional | |
| Reason for Change | The reason why you believe this concept should be added to the Source Terminology | Optional | |
| Notes | Any note pertaining to your request that has not been captured by the previous fields. | Optional | |
| References | References (URLs, Journal articles, etc.) to support and substantiate your request | Optional |
2. New Description
| Field Name | Definition | Valid values | Optionality |
| Requestor Internal ID | An alphanumeric value that you can define to uniquely identify this request in your database (or spreadsheet). Note that the terms that we may accept your request but assign different terms than what you suggest. Assigning this ID ensures you can easily track the processed items to your original requests. | An alpha-numeric value | Optional |
| Concept ID | ID of the concept for which you are proposing a new description | Concept IDs in SNOMED CT International | Mandatory |
| Concept FSN | FSN (Fully Specified Name) of the concept for which you are proposing a new description | FSNs in SNOMED CT International | Mandatory |
| Description | The new description that you are proposing | Mandatory | |
| Description is PT | A flag to indicate whether the new description that you are proposing should be the PT (Preferred Term) of the concept, and the existing PT should become a synonym | Yes (the new description should replace the existing PT) No (the new description should be added as a synonym) | Optional |
| Reason for Change | The reason why you believe this concept should be added to the Source Terminology | Optional | |
| Notes | Any note pertaining to your request that has not been captured by the previous fields | Optional | |
| References | References (URLs, Journal articles, etc.) to support and substantiate your request | Optional |
3. New Relationship
| Field Name | Definition | Valid values | Optionality |
| Requestor Internal ID | An alphanumeric value that you can define to uniquely identify this RFC item in your database (or spreadsheet). Note that the terms that we may accept your request but assign different terms than what you suggest. Assigning this ID ensures you can easily track the processed items to your original requests. | Any alpha-numeric value | Optional |
| Source Concept ID | Each relationship relates two concepts together. Source Concept ID is the ID of the first concept. For example, if you are proposing a new IS-A relationship, this is the concept ID of the proposed child. | Concept IDs in SNOMED CT International | Mandatory |
| Relationship Type | A Relationship contains Identifiers of two logically associated Concepts and the Identifier of another Concept that indicates the Relationship Type by which they are associated. This field is a drop down list for your convenience. | Values in the drop down list | Mandatory |
| Destination Concept ID | Each relationship relates two concepts together. Destination Concept ID is the ID of the first concept. For example, if you are proposing a new IS-A relationship, this is the concept ID of the proposed parent. | Concept IDs in SNOMED CT International | Mandatory |
| Characteristic Type | Characteristic Type identifies whether the relationship is defining (whether a Relationship forms part of the definition of the source concept), qualifying, etc. This field is a drop down list for your convenience. | Defining relationship Qualifying relationship Additional relationship | Optional |
| Refinability | Specifies the refinement requirement of the relationship. For more information and definition of each refinement level please refer to the Technical Implementation Guide. | Not refinable Optional Mandatory | Optional |
| Relationship Group | Groups together relationships that are part of a logically associated relationship group. Multiple attributes and their values can be grouped together into “Relationship groups” to add clarity to concept definitions. A Relationship group combines an attribute-value pair with one or more other attribute-value pairs. All active Relationship records with the same relationshipGroup number and sourceId are grouped in this way. | A numeric value, e.g. 1 | Optional |
| Reason for Change | The reason why you believe this concept should be added to the Source Terminology | Optional | |
| Notes | Any note pertaining to your request that has not been captured by the previous fields | Optional | |
| References | References (URLs, Journal articles, etc.) to support and substantiate your request | Optional |
4. Change or Retire Concept
| Field Name | Definition | Valid values | Optionality |
| Requestor Internal ID | An alphanumeric value that you can define to uniquely identify this request in your database (or spreadsheet). Note that the terms that we may accept your request but assign different terms than what you suggest. Assigning this ID ensures you can easily track the processed items to your original requests. | Any alpha-numeric value | Optional |
| Concept ID | ID of the concept which you are proposing to be changed or retired. | Concept IDs in SNOMED CT International | Mandatory |
| Concept FSN | FSN of the concept which you are proposing to be changed or retired. | Concept FSNs in SNOMED CT International | Mandatory |
| New FSN | The new FSN that you would like to propose for this new concept. Leave this field blank if your proposal does not include a change in FSN | Optional | |
| New Concept Status | The new status that you are proposing for this concept. Leave blank if your proposal does not include a change in concept status. For more details on concept status please refer to the Technical Implementation Guide. | Values from the drop-down list | Optional |
| Concept History Attribute | The new Concept History Attribute that you are proposing for this concept. Leave blank if your proposal does not include a change in Concept History Attribute. For more details on Concept History Attribute please refer to the Technical Implementation Guide. | Values from the drop-down list | Optional |
| Concept History Attribute Value | The new Concept History Attribute Value that you are proposing for this concept. Leave blank if your proposal does not include a change in Concept History Attribute Value. For more details on Concept History Attribute Value please refer to the Technical Implementation Guide. | Optional | |
| Reason for Change | The reason why you believe this concept should be added to the Source Terminology | Optional | |
| Notes | Any note pertaining to your request that has not been captured by the previous fields. | Optional | |
| References | References (URLs, Journal articles, etc.) to support and substantiate your request | Optional |
5. Change or Retire Description
| Field Name | Definition | Valid values | Optionality |
| Requestor Internal ID | An alphanumeric value that you can define to uniquely identify this request in your database (or spreadsheet). Note that the terms that we may accept your request but assign different terms than what you suggest. Assigning this ID ensures you can easily track the processed items to your original requests. | Any alpha-numeric value | Optional |
| Concept ID | ID of the concept that is associated to the description which you are proposing to be changed or retired. | Concept IDs in SNOMED CT International | Mandatory |
| Concept FSN | FSN of the concept that is associated to the description which you are proposing to be changed or retired. | Concept FSNs in in SNOMED CT International | Mandatory |
| Description ID | ID of the description which you are proposing to be changed or retired. | Mandatory | |
| Current Description | Current text of the description which you are proposing to be changed or retired. | Mandatory | |
| Proposed New Description | The new text that you are proposing for this description. Leave blank if your proposal does not include a change in the text of the description. | Optional | |
| Proposed New Case Significance | The new Case significance value that you are proposing for this description. Case significance indicates whether the text of the term can be modified to by switching characters from upper to lower case (or vice-versa). Leave blank if your proposal does not include a change in Case significance. Example of entire term case sensitive: Alzheimer's disease or maladie de Lyme. Example of entire term case insensitive: lung disease. Example of only initial character case insensitive: uGy | Entire term case sensitive Entire term case insensitive Only initial character case insensitive | Optional |
| Proposed New Description Status | The new status that you are proposing for this description. Leave blank if your proposal does not include a change in description status. For more details on description status please refer to the Technical Implementation Guide. | Values from the drop-down list | Optional |
| Reason for Change | The reason why you believe this concept should be added to the Source Terminology | Optional | |
| Notes | Any note pertaining to your request that has not been captured by the previous fields. | Optional | |
| References | References (URLs, Journal articles, etc.) to support and substantiate your request | Optional |
Reference:
Health Infoway. SNOMED CT RFC - InfoRMS. SCT-RFC-Sample-EN.xls Retrieved May 4, 2015.