Page tree
Skip to end of metadata
Go to start of metadata

Getting Started - Create Request

StepsReference
  1. User selects "Create New Request" button from left sidebar (A).
  2. The system will load the create New Request dialog box, and the user selects an input mode (B) (direct or simple) and then selects the desired Request Type template (C) and select Create Request.

To jump to the next steps please select the desired request combination:

Simple mode - Change Description

StepsReference

3. The system will load the New Request screen. From this screen a user must fill out the New Request Details:

  • Local code (D) - Local extension code - optional
  • Topic (E) - What category the request falls under - required
  • Summary (F) - Usually the FSN that is the subject of the request - required
  • Justification (G) - The source of the request ex: Organization Name Donation - required
  • Reference (H) - Supporting notes as to why the content request should be completed
  • Notes (I) - Any additional comments desired to be made about the request
  • Namespace (J) - optional

 

4. To change a description a user must fill out the following fields

    • Concept (K) - The concept containing the description which is desired to be changed. For more info on populating this field via search or taxonomy see: Search, Taxonomy, and Using Drag and Drop or using type ahead see Using Type Ahead Within CRS
    • Active Description (L) - Select which of the descriptions from the selected concept should be changed
    • Proposed New Description (M) - Type the new description term
    • New Case Significance (N) - Set the Case Significance of the New Description

5. Select Save Request (O) to save your work or select Submit Request (P) to Submit the Request. The request will have a status of New.

6. Jump to: What happens after my Request has been submitted?

 

Simple mode - Change Relationship

StepsReference

3. The system will load the New Request screen. From this screen a user must fill out the New Request Details:

  • Local code   (D) - Local extension code - optional
  • Topic  (E) - What category the request falls under - required
  • Summary  (F) - Usually the FSN that is the subject of the request - required
  • Justification (G) - The source of the request ex: Organization Name Donation - required
  • Reference  (H) - Supporting notes as to why the content request should be completed
  • Notes (I) - Any additional comments desired to be made about the request
  • Namespace (J) - optional

4. To change a relationship a user must fill out the following fields

5. Select Save Request (R) to save your work or select Submit Request (S) to Submit the Request. Once the request has been submitted it will have a status of New and the user will be redirected to the dashboard. 

6. Jump to: What happens after my Request has been submitted?

Simple mode - Change or Retire Concept

StepsReference

3. The system will load the New Request screen. From this screen a user must fill out the New Request Details:

  • Local code   (D) - Local extension code - optional
  • Topic  (E) - What category the request falls under - required
  • Summary  (F) - Usually the FSN that is the subject of the request - required
  • Justification (G) - The source of the request ex: Organization Name Donation - required
  • Reference  (H) - Supporting notes as to why the content request should be completed
  • Notes (I) - Any additional comments desired to be made about the request
  • Namespace (J) - optional

4. To change or retire a concept a user must fill out the following fields

  • New Concept FSN (L)
  • New Concept Status (M)
  • Duplicated Concept (N)
  • History Attribute (O)
  • History Attribute Value (P)

5. Select Save Request (Q) to save your work or select Submit Request (R) to Submit the Request. Once the request has been submitted it will have a status of New and the user will be redirected to the dashboard.

6. Jump to: What happens after my Request has been submitted?

Simple mode - Create New Concept

StepsReference

3. The system will load the New Request screen. From this screen a user must fill out the New Request Details:

4. To create a new Concept a user must fill out the following fields

5. Select Save Request (S) to save your work or select Submit Request (T) to Submit the Request. Once the request has been submitted it will have a status of New and the user will be redirected to the dashboard.

6. Jump to: What happens after my Request has been submitted?

Simple mode - Create New Description

StepsReference

3. The system will load the New Request screen. From this screen a user must fill out the New Request Details:

  • Local code (D) - Local extension code - optional
  • Topic (E) - What category the request falls under - required
  • Summary (F) - Usually the FSN that is the subject of the request - required
  • Justification (G) - The source of the request ex: Organization Name Donation - required
  • Reference (H) - Supporting notes as to why the content request should be completed
  • Notes (I) - Any additional comments desired to be made about the request
  • Namespace (J) - optional
  • 4. To create a new Description a user must fill out the following fields

      • Concept (K) - The concept that you would like to add the description to. For more info on populating this field via search or taxonomy see: Search, Taxonomy, and Using Drag and Drop or using type ahead see Using Type Ahead Within CRS - required
      • Description (L) - Create New Description Here - required
      • New Case Significance (M) - optional
      • Is the new Description the Preferred Term? (N)- optional

    5. Select Save Request (O) to save your work or select Submit Request (P) to Submit the Request. Once the request has been submitted it will have a status of New and the user will be redirected to the dashboard. 

    6. Jump to: What happens after my Request has been submitted?

 

 

Request Form Glossary

Term

Explanation

Local code

Local extension code - optional

Topic

What category the request falls under - required

Summary

Usually the FSN that is the subject of the request - required

 

Justification

It is very important to incorporate a clear justification for any change request for the International Edition of SNOMED CT. For example “Used as a member of a value set in support of the provider occupation field.” This level of detail will assist the Content Team in understanding the nature and context of the requirement. The justification will also aid in assessing the risks and benefits that are associated with making the change. Please remember that change requests that are country specific are not suitable for the International Edition. This type of change request will not be accepted. Please note that Justification is a mandatory field when making a submission. Copy and paste of generic text such as “gap in terminology” does not supply adequate justification for a change and may result in further clarification (which will delay the inclusion of the request) or a status change to “Not accepted.”

Semantic Tag

It is important to consider where the requested concept will sit within the SNOMED CT hierarchy. The requester must take into account the nature of their requirement along with how it will be implemented in clinical systems. When making a request for a new concept the desired semantic tag for the new addition is required as part of the submission. This will assist the Content Team in understanding the nature of the requirement and also help in ensuring that the original requirements are met. The requester should verify that the requested semantic tag aligns with the requested parent term. For example a request for a new concept in the finding hierarchy must be a descendant of the concept 404684003|Clinical finding (finding). Further information about the semantic tag can be found in the Editorial Guide (Section 7.1.1 Fully Specified Name).

Reference

 

Submissions for a change to the International Edition of SNOMED CT should be supported by at least one reference. The reference can be added to the justification field in the request template. Please remember that requests for change need to be of international relevance and not confined to one member country. The supporting information submitted with the request is required to be recent and from an authoritative source such as a scientific or professional journal, OMIM, PubMed, Orphanet or a professional society. References to Wikipedia are not sufficient. Literature intended for patient education purposes should not be used in support of a request; it frequently includes generalizations that are not always true but may be true in the context of the topic being addressed.

Notes

Any additional comments desired to be made about the request

Namespace

When submitted with a request, the extension concept ID will be retained when the concept is added to the International edition of SNOMED CT. Where retention of the extension concept ID is not required the concept ID must NOT be submitted with the request.

Definition

Where a new concept is being requested, a text definition that identifies the exact nature of the request must be included. This is especially important where the request is for an obscure disease or a new procedure or is unusual in its nature. Please note that restating the requested descriptions is not considered to be sufficient as a definition.


What happens after my request is submitted? 

Following an initial review, each request is assigned a manager who is a member of the Content Team. A request is Accepted, Rejected, or ,  change to a status of “Accepted” does not mean that the request will be approved for inclusion in SNOMED CT.
  1. Following initial review, each request is assigned a manager who is a member of the IHTSDO Content Team. A change to a status of “Accepted in scope” does not mean that the request will be approved for inclusion in SNOMED CT. All requests are treated as normal priority with the exception of data errors. Where a request points towards a possible error in SNOMED CT, the request will be prioritised 
    for investigation.
  2. The next step in a request cycle will be a status change of  “In process” which indicates that the Content Team is actively evaluating the request. The following outcomes are possible. 
    • Inception/ Elaboration : When request aligns with an ongoing content project, the request will be placed on hold until editorial policy is available to support the requested change or addition. Content projects are intended to investigate issues or enhancements to both existing and future content for SNOMED CT. A process for understanding the problem and elaboration of a solution is undertaken in order to make improvements to existing content and clarify how content of a similar nature will be incorporated into SNOMED CT in the future. Depending upon the nature of the content project, this may be a longterm large scale content project or a smaller project with a shorter timescale. The project  id will be included in CRS to facilitate future management of these requests. Customers may review the content project to which the request 
    • Clarification Requested: Where insufficient information is provided to proceed with a request, the request manager will incorporate questions to be resolved into the comments text field and change the status of the request to Clarification Requested. This will generate an email to the original requester. To receive email notification, the setting must be enabled: Where a request for clarification to a customer is not answered within two months (60 days) from the date the clarification is generated, the request will be closed with a status of Not Accepted along with a note that the request was closed due to a lack of response by the submitter. After this no further action will be taken with the request, if the change is still required a new request must be submitted. The resubmitted request must include additional information related to the request for clarification. Failure to provide additional information will lead to a rejection of the request
    • Not Accepted: Where a request has had a full review and is not considered to be either in scope for SNOMED CT or does not meet the criteria outlined in the Editorial Guide, it will be declined using “Not Accepted.”
    • After conclusion of the appropriate appeal process, where the outcome remains unchanged, this status will be applied.

3. Construction -  When the request manager has carried out the requested/clarified change, the associated request is placed in “Construction” phase. This does not assure that the requested change will be approved and included in the final release data. There are a considerable number of technical processes undertaken after editing for a particular release has closed. This can on occasion result in a change that has been made being reverted or a concept removed from the release.

4. Withdrawn - A submitter may choose to withdraw their request at any time up to the point the status is assigned as “Construction”. However, a submitter may not unilaterally prevent the addition of content to SNOMED CT, or cause it to be retired through this mechanism if it is believed to be a valid request and of value to stakeholders

5. Completed - A request status will be changed to “Completed” once the edit has been made and approved and the data files are ready for release. Prior to this time, inclusion in the release cannot be guaranteed. 


Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'Managing Submitted Requests Screen'.