Only this pageAll pages
Powered by GitBook
1 of 27

CRS Guide

INTRODUCTION

Loading...

Loading...

Loading...

Loading...

Loading...

How to... ?

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

FAQs

Loading...

Loading...

Loading...

Loading...

US GUIDE

Loading...

Content Request Service Terms of Service

PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THIS SNOMED INTERNATIONAL SITE

By continuing to browse and use this website You are agreeing to comply with and be bound by the following terms and conditions of use, which govern our relationship with You in relation to this website.

"We", SNOMED International, operate this site. We are registered in the United Kingdom and have our registered office at 1 Kingdom Street, Paddington London, W2 6BD, United Kingdom. "You" are the user of this website.

TERMS AND CONDITIONS OF USE

We may update our website, including these terms, from time to time, and may change the content at any time, in each case, without notice. Please note that we do not guarantee that our site, or any content or information on it, is complete, up-to-date, error-free or free from inaccuracies or omissions.

The content on our website is provided for general information only. You should not rely on any information provided on our website, and it is your own responsibility to ensure that any products, services or information available through this website meet your specific requirements.

We are the owner or the licensee of all trademarks, copyrights, and other intellectual property rights in our site, and in the material published on it. Those works are protected by copyright laws and treaties around the world. All such rights are reserved.

Our website may include links to other websites. These links are provided for your convenience and do not represent our endorsement of those website(s). We have no responsibility for the content of the linked website(s).

To the extent permitted by law, we exclude all conditions, warranties, representations or other terms which may apply to our website or any information or content on it, whether express or implied.

We will not be liable to You or any other person for any loss or damage, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, arising under or in connection with: (i) Your use of, or inability to use, our website; (ii) Your use of or reliance on any content displayed on our website; or (iii) loss or damage caused by a virus or other technologically harmful material that may infect your computer equipment due to Your use of our website (or any website linked to it).

Your use of this website in breach of these terms may give rise to a claim for damages and/or be a criminal offence.

Provide Feedback

Service Level Agreement for International CRS

Service Level Agreement for International CRS

  • Content Request Service Documentation is here

  • Early visibility for 2025 proposed content changes is here

  • Customer Guidance for requesting content changes via CRS is here

  • Submission dates for CRS are

Previous 2022 Service Level
Target
Current Service Level

\

Request Commitment

A minimum total of 1500 separate requests of the total submitted on or before the published request closure date for submissions shall be considered for inclusion or have an identified content tracker assigned, unless they are marked for clarification, appeal or are rejected or withdrawn.

Requests that are accepted will be considered for inclusion providing that:

  1. The required information as specified in the document ‘Customer Guidance for Requesting Changes to SNOMED CT’ has been supplied with the request.

  2. The request aligns with current editorial guidelines.

90%

UPDATED.

Request Commitment

All requests submitted on or before the published request closure date for the reporting period shall be considered for inclusion or have an identified content tracker assigned, unless they are marked for clarification, appeal or are rejected or withdrawn.

Requests will be considered for inclusion providing that the following criteria are met:

  1. The required information as specified in the document ‘Customer Guidance for Requesting Changes to SNOMED CT’ has been supplied with the request.

All requests marked for clarification will remain open for a period of 60 days, after which the request will be closed without right to appeal.

95%

NO CHANGE.

All requests marked for clarification will remain open for a period of 60 days, after which the request will be closed without right to appeal.

Submitters will receive an acknowledgement of receipt of their submission within 7 working days.

95%

NO CHANGE.

Submitters will receive an acknowledgement of receipt of their submission within 7 working days.

A notice will be published on the website biannually to indicate the submission dates for the CRS.

https://www.snomed.org/snomed-ct/Use-SNOMED-CT/change-or-add

Date of publication for the requested change will be communicated to the submitter via the CRS request at the time it is moved to a status of complete.

100%

here
Provide Feedback

UPDATED.

CRS SLA Reporting Period for Q1 & Q2

Requests submitted between 14th October and 15th April inclusive will be reviewed for inclusion in a monthly release in or before the following July international release.

CRS SLA Reporting Period for Q3 & Q4

Requests submitted between 16th April and 13th October inclusive will be reviewed for inclusion in a monthly release in or before the following January international release.

  • The submitter has not exceeded the maximum of 150 changes of the same type.

  • Complex requests that impact a large area of content or require additional input from resources other than the manager of the request may exceed this time period.

    Request Balance

    SNOMED International reserves the right to assess the number of submissions made per country per release to create balance of submissions and fairness in equal resolution of requests.

    Any set of requests from the same member country/submitter may not exceed 150 of the same type during a 6 month period. Examples of the same type of requests would be: 150+ requests for new concepts all in the same hierarchy (i.e. procedure, body structure, substance etc), 150+ requests for changes to existing content such as new descriptions, modeling changes such as to stated relationships or attributes, concept or description inactivation, changes to descriptions or questions about existing content.

    The 150 total may be submitted as a large submission or smaller submissions, however once the total of 150 has been reached no further requests of the same type will be accepted during that 6 month period. Further requests above the 150 total will be marked as rejected.

    Slight overages of the 150 will be considered on a case by case basis for submission and must be approved prior to submission by contacting Maria Braithwaite (mbr@). Requests must follow the customer guidance documentation and must:

    • Meet an International use case.

    • Meet

    Any set of requests exceeding 150 of the same type must be referred to the Customer and Stakeholder Relationship Management lead before being submitted to the CRS system.

    Bulk Submissions

    Must be submitted to the , they will coordinate the best path for inclusion, either a bulk submission or a Member Priority project, including feedback timeline within available resources and priorities.

    The request aligns with current editorial guidelines.
  • The submitter has not exceeded the maximum of 150 changes of the same type.

  • Complex requests that impact a large area of content or require additional input from resources other than the manager of the request may exceed this time period.

    Request Balance

    SNOMED International reserves the right to assess the number of submissions made per country per release to create balance of submissions and fairness in equal resolution of requests.

    Any set of requests from the same member country/submitter may not exceed 150 of the same type during the same SLA reporting period. Examples of the same type of requests would be: 150+ requests for new concepts all in the same hierarchy (i.e. procedure, body structure, substance etc), 150+ requests for changes to existing content such as new descriptions, modeling changes such as to stated relationships or attributes, concept or description inactivation, changes to descriptions or questions about existing content.

    The 150 total may be submitted as a large submission or smaller submissions, however once the total of 150 has been reached no further requests of the same type will be accepted during that SLA reporting period. Further requests above the 150 total will be marked as rejected.

    Any set of requests exceeding 150 of the same type must be referred to the Customer and Stakeholder Relationship Management lead before being submitted to the CRS system to discuss options for inclusion into the international release.

    Bulk Submissions

    Must be submitted to the Customer & Stakeholder Relationship Executive, they will coordinate the best path for inclusion, either a bulk submission or a Member Priority project, including feedback timeline within available resources and priorities.

    Requirements for new content/content changes that exceed 150 changes of the same type will not usually be accepted via the CRS without prior discussion.

    snomed.org
    SNOMED International Editorial Guidelines
    Customer & Stakeholder Relationship Representative

    Content Request Glossary

    Term
    Explanation

    Local SNOMED CT code

    Local SNOMED CT extension code - optional

    Local code

    Local non-SNOMED CT reference code - optional

    \

    Accessing CRS

    The International SNOMED CT Content Request Service (CRS) is located here: http://snomed.org/crs.

    The US SNOMED CT Content Request Service (USCRS) guide is located in the last pages of this guide: https://github.com/SNOMED-Documents/snomed-crs-guide/blob/main/how-to.../broken-reference/README.md

    System requirements for using CRS & USCRS

    In order to use both CRS and USCRS, it is strongly recommended to use Google Chrome and a reliable internet connection. No other software needs to be installed on your computer in order to use CRS.

    Who May Access International CRS?

    An authorized requester to the International CRS is usually a named individual from a national release center, a user from a member country who does not have access to a national release center or individuals from international groups who have been identified as providing specialist content.

    How to get into CRS & USCRS?

    Both CRS & USCRS uses the Identity Management Service (IMS) to manage credentials. You can use your existing login name and password that you use for Confluence (if applicable). If you do not have account, please follow the instructions below.

    If you already have an account to access SNOMED International's Confluence, you will be able to access CRS with your existing account credentials, although you will still need to request access to be able to log in to CRS.

    If you do not have an account, or find that you do not have access, please fill in the following form to request access: Confluence User Accounts.

    Should you still have any difficulty, please contact us by sending an email to .

    Figure 1a. Once logged in through IMS, you are automatically logged in to the CRS. Choose the CRS from the list of IHTSDO tools and you will be redirected to your CRS dashboard.

    Figure 1a

    Managing Submitted Requests Screen

    Audience

    Applicable to users responsible for managing content requests. See also: for task status meaning

    From CRS Dashboard , in Submitted Requests (1) , select a request which has status is New (2) to go to request details page.|

    Figure 1: The Submitted Requests screen select Accept Request (1) button to accept a request, then you will be redirected to CRS Dashboard

    From CRS Dashboard , in Submitted Requests

    Notifications

    If there is any change which related to your submitted requests such as status changed, new comment added, batch importing completed, then CRS will inform you via its notification feature.

    from any page of CRS you will see the icon

    __**

    CRS will only notify a user about new comments/feedback/questions/answers added if it provided in CRS. For comments which come from out side of CRS such as JIRA, theuser will not get any notification. Please note this is in addition to email notifications. The system will also send an email notification for new comments, feedback, and Q&A.

    Topic

    What category the request falls under - required

    Summary

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

    Proposed Use Case

    It is very important to incorporate a clear use case 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: 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.

    Provide Feedback
    techsupport@snomed.org
    Provide Feedback

    Notes:

    Provide Feedback
    at the very top right of the page, the number of new notifications shall be displayed as number which next to the icon. you can click on the icon (1)to see the list of notifications (2) and click on each message (3) to go to request details or batch details.
    **__
    (Figure 1), select a request which has status is
    New
    to go to request details page.select
    Reject Request
    (1) button and provide a reason and select Confirm button
    in Reject Request dialog (2)
    to reject a request, you will be redirected to
    CRS Dashboard.
    |

    From CRS Dashboard , in Submitted Requests (Figure 1), select a request which has status is New to go to request details page.Select Pending Clarification (1), to launch the , Pending Clarification dialog (2). Enter a Reason (what clarification is desired on) and select Confirm , you will be redirected to CRS Dashboard.|

    From CRS Dashboard , in My Requests , select a rejected request to go to request details page.select Appeal Rejection (1) button to appeal a request, then provide a reason and select Confirm button in the Appeal Request Rejection (2) you will be redirected to CRS Dashboard.|

    From CRS Dashboard , in My Requests , select a Accepted request to go to request details pageSelect Withdraw Request (1), to launch the Withdraw Request dialog (2). Provide a reason and select Confirm , then you will be redirected to CRS Dashboard.|

    \

    Provide Feedback

    Accept Request

    Reject Request

    SIRS to CRS Status Map

    Clarification Requested

    Appeal Rejected Request

    Withdraw Request

    CRS Workflow

    Provide Feedback

    How do I get to CRS?

    Please go to , where you will be asked to log in.

    https://request.ihtsdotools.org
    Provide Feedback

    Creating Requests

    What mode should I use?

    Task
    Simple
    Batch Import

    Modify, retire, or, create a single Concept

    x

    x

    Make more than one change to an existing Concept

    In Simple Mode , a user can create a request to perform a single action on one concept:

    • create a new Concept

    • Add a new Description to an existing concept

    • Add a new Relationship to an existing concept

    • Modify an existing Description of an existing concept

    In Batch Mode , a user can create a request to perform a multiple (typically) related actions

    In each of the Simple and Direct modes, there are certain fields which are mandatory and need to be completed on each request:

    Field
    Description
    Mandatory
    Notes

    Summary| Provide a short summary which will help staff identify and triage the request| Y| Please note this field has a 255 character limit Proposed Use Case| Provide justification on why the content should be added or changed| Y|

    Reference| Provide references which can be verified to confirm the need to add or change the content| Y|

    Local SNOMED CT Code| Add the local valid SNOMED CT identifier of the content to be added if one exists| |

    Local Code| Add any other local code identifiers for your own reference| |

    Definition| Precise meaning of the requested content addition or change| |

    Notes| Any extra notes which will help the triage of the request| |

    Namespace| Add the namespace of the content, if applicable| |

    UMLS CUI| Add the UMLS Concept Unique Identifier if one exists| |

    Originating Organization| Choose the organization from the drop down that is requesting the change or addition| Y| International CRS only Collaboration Agreement| If relevant, select the collaboration agreement under which the request is being made| | International CRS only

  • Change a Relationship of an existing concept

  • Retire a Description of an existing concept

  • Retire Relationship of an existing concept

  • Change or Retire an existing Concept

  • Other - all requests not covered by the above types

  • n/a

    x

    Retire more than one more component to an existing Concept

    n/a

    Topic

    From the dropdown, choose the relevant area/domain for the request

    Y

    What is Simple mode used for?

    What is Batch mode used for?

    Form Fields

    Provide Feedback

    Reassign Request

    Audience

    Applicable to internal users responsible for managing content requests.

    Assign Request to Authoring

    • Assign request from the Accepted Requests

    From CRS Dashboard, click on Accepted Requests (1) from the left panel, tick to select accepted request from the list (2) then click on Assign requests to Authoring button (3) to show assignment dialog |

    ---|---

    Select a project from Project drop-down list, type assignee name in Assignee text box to get suggestions and pick one in list, provide summary for authoring task and click Assign Requests button to create task.|

    From CRS Dashboard, click on Submitted Requests from the left panel, click on a Accepted request in list then click on Assign requests button (1) to show Assign Requests to Authoring Task (2) dialog Select a project from Project drop-down list, type assignee name in Assignee text box to get suggestions and pick one in list, provide summary for authoring task and click Assign Requests button to create task.|

    • Assign request from the Accepted Requests

    From CRS Dashboard, click on Accepted Requests (1) from the left panel, tick to select accepted request from the list (2) then click on Assign requests to Staff button (3) to show assignment dialog |

    Type assignee name in Assignee text box to get suggestions and pick one in list, and then click Assign Requests button to create task.|

    From CRS Dashboard, click on Submitted Requests (1) from the left panel, click on a accepted request from the list and then click on Assign to Staff button (1) to showAssign Requests to Staff (2) dialog Type assignee name in Assignee text box to get suggestions and pick one in list, and then click Assign Requests button to create task.|

    How do I obtain a CRS Account?

    What types of Content Requests are supported?

    Before making any request, please read the guidance on submitting content -

    Version 15.0 Customer Guidance for Requesting Changes to SNOMED CT 20240723.pdf

    The new CRS tool features a variety of templates and two request entry modes to appeal to most users. These Include:

    • Create a new Concept(s)

    A request for a new concept must take into account existing content and align with the existing Editorial Guidance

    • Add New Synonym(s)

    A new synonym may be added to an existing concept if the request aligns with existing Editorial Guidance and has a clear justification.

    • Add or Modify Parent(s)

    A new parent may be added to an existing concept (or changed) if the request aligns with existing Editorial Guidance and has a clear justification.

    • Add or Modify Description(s)

    A new description may be added to an existing concept (or changed) if the request aligns with existing Editorial Guidance and has a clear justification.

    • Inactivate Concept(s), Description(s), or Relationship(s)

    Concepts or their components may be inactivated if the request aligns with existing Editorial Guidance and has a clear justification.

    • Modify and Create New Relationship(s)

    New relationships or modification to existing concepts may be made if the request aligns with existing Editorial Guidance and has a clear justification.

    Withdrawing a Submitted Request

    Steps
    Reference

    Provide Feedback

    Assign Request to Staff

    Provide Feedback
    * Assign request from the Submitted Requests
    ---|---
    * Assign request from the Submitted Requests

    1 - Select a request from the dashboard to load theEdit Request screen.2 - To withdraw the request select Withdraw Request (A) from the Request Info panel. This will load the Withdraw Request dialog.

    3 - From the Withdraw request dialog, enter a reason for withdrawing the request and select Confirm. The system will indicate that it is processing the request. Once completed you will be redirected to the dashboard and the status will be in the Withdrawn status and the request will be considered closed.

    Provide Feedback

    Navigating CRS from the Sidebar

    What are My Requests?

    These are the requests that the current user has submitted. From this dashboard as user may view their own requests and track their progress through evaluation and, if accepted, eventual inclusion into SNOMED CT.|

    What are My Assigned Requests?

    These are the requests that the current user has been assigned. From this dashboard as user can view their assigned requests and update request in to CRS and SNOMED CT.|

    What are Submitted Requests ?

    Users may search requests from other users to identify similar or identical requests.|

    What are Accepted Requests? :

    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.|

    What are My Batch Requests?

    Refers to Content Requests for a large scale addition of new content/ and or large scale modifications to existing content.|

    Allows a user to create a Content Request in simple or direct mode|

    Allows a user to create a request for large numbers of new content adaptations or modifications by uploading content.|

    _

    ** **

    What is Create New Request?

    What is New Batch Import?

    Provide Feedback
    _

    Create a Batch Request

    Summary

    The batch Import function allow to create many requests of all request types through importing file from PC. The imported file will be checked validation before it added into system. All requests in batch is set status to 'Draft' as default.

    The information below will give you more details on the operation of this function. Also you can refer and download batch template at link below.

    Where is the Batch Import template located?

    The template can be downloaded by selecting the Download batch template link from the Batch Import screen. The template can also be found here. The template is identical to the template you may have previously used on SIRS in order to make transition between the systems as smooth as possible, so you will be able to use any batch requests you have already prepared.

    Importing a New Batch

    From CRS Dashboard, select the New Batch Import from the left panel to navigate to the Batch Import screen.

    Files may be uploaded one of two ways:

    1. By dragging a file on top of the Drop Batch File Here area (Figure 2)

    2. Click on area 'Select or Drop Batch File Here ' (1) tobrowsing batch file(2) from PC. Then click on button 'Open' (3) in dialog to adding the selected file into Uploaded Files list (Figure 3)

    The file will be uploaded to the server (1) and notify user once it completed (2) (3) , you can select on each tab (4) to review your uploaded requests. once you are happy with the file. Move scrollbar (5) to the right to view more information of batchSelect Import Request (6) button to show import statistic (figure 5), and then select on Import button to import it to the system. Otherwise, you can delete it if you want.| _

    _Figure 4 - Review Batch File and Import &#xNAN;Deleting Batch If a batch has been uploaded to CRS but not yet imported, users can delete it in batch uploading screen by following the below instructions:From the Batch Import page, select item in the Uploaded Files list (1) and click on button 'Remove Request' (2). Then a dialog with confirmation message(3) is populated at the top page, click on button 'OK' in dialog to delete batch.| _

    _Figure 6: Deleting batch

    From CRS Dashboard, select on My Batch Requests (1) from the left panel to navigate to the My batches page (2).Click on button 'Import Batch' (3) to navigate to Batch Import page (Figure 1).|

    |--- Select on a batch row to go to batch request details, with Batch Details (1), Statistics (2), Batch Requests (3), Searching batch (4) and Number of requests (5) in batch as shown in the screenshot below.|

    Figure 8 - Batch Details page

    From My Batches page, select a New Batch in list to navigate to batch details. The batch status set to 'New' (1) when all requests in batch is in Draft status (2)| From Batch Details page, try to submit a request in list. And then refresh this page, Submitted request is changed to 'New' status (1) and the batch status is changed from 'New' to 'In Progress'(2). Status 'In Progress' is displayed only when a request in list is submitted.| From Batch Details page, change status all requests in list to Completed or Withdrawn or Reject or all three (1). And then refresh this page , thebatch status is changed from 'In-Progress' to 'Completed' (2).|\

    _Figure 11.2 - Batch in status 'Completed'\

    _Figure 11.3 - Batch in status 'Completed'\

    Batch Statistics

    From Batch Details page, Submitted Requests number (1) is updated after requests are changed status to 'New' (2). .

    Figure 12 - Submitted Requests Number From Batch Details page, Accepted Requests number (1) is updated after requests are changed status to 'Accepted' (2).

    Figure 13 - Accepted Requests Number From Batch Details page, Rejected Requests number (1) is updated after requests are changed status to 'Rejected' (2).

    Figure 13 - Rejected Requests Number

    From My Batches page, select a New Batch in list to navigate to batch details. And click on button 'Delete Batch' (1) button, the confirmation dialog (2) is populated at the top, then click on button 'OK' to confirm deleting batch.

    Viewing Batches

    Batch status

    Deleting in Batch Details

    Provide Feedback
    ___Figure 3 - Browse File to Import
    ---|---

    Customizing the list view screen

    Steps
    Reference

    To hide/show any column on a list view screen select the, Columns button on the upper right portion of the screen.

    The UI will indicate that the columns have been saved.

    Provide Feedback

    Search, Taxonomy, and Using Drag and Drop

    In many cases you will want to search for one or more concepts for the purposes of editing or reference. The search tab allows you to search SNOMED by typing text in the search field. After pressed Enter key, it will lists all concepts that match your query. The search tab contains a number of features:

    • View search results by matching terms or grouped by concept

    • Distinguish between primitive and fully defined concepts in a set of search results

    A drop down list of all table columns will appear. From this list select (or unselect to hide) to hide show / the desired columns. Select the Save button to confirm your selections.
    Distinguish between active and inactive concepts in a set of search results
  • View more details about a concept in a set of search results

  • Add concepts from a set of search results to a saved list for future use

  • You can use wildcards in the search term to find partial matches. Asterisk ( * ) matches all subsequent characters regardless of word length. Question mark ( ? ) matches a single character. For example:

  • punc* would find all words stemmed with "punc" eg punch, punched, punctum, puncture etc punc? would find punch punc??? would find punched and punctum punc?u? would find punctum but not punched

    Steps
    Reference

    If desired a single concept id can be used to locate a specific concept. This is useful for newly created concepts.Concepts from search can be dragged and dropped by selecting the concept by pressing and holding on the FSN.The UI will then highlight the areas that are "drop zones" (A)

    Drag the concept to the desired form field and let go to populate the field with this concept.

    Steps
    Reference

    From the search tab, you may type a query into the search field and the search widget will begin to locate results. You can toggle your results view between matching terms or grouped by concept by selecting the checkbox next to the search field.

    View Matching TermsThis search query returns all cases of a query. Eg. If i search for Diabetes mellitus excluded I may recieved 2 search results for this concept since my word "diabetes " is used three times when defining this concept.

    Grouped By ConceptFor this same search query, if I select Grouped By Concept, I will only receive one search result for each concept, narrowing my search result to one.

    • In a set of search results a primitive concept is identified by a

    Primitive icon and a fully defined concept is identified by a
    Fully Defined icon.
    • In a set of search results an inactive concept is identified by a

    icon.
    If desired search results can be filtered to active concepts only by selecting the Active Only button

    From a set of search results you may want to view more details about a concept before adding it to your saved list or selecting it for editing. To do so click either the

    or
    icon within the concept that you wish to display the details of and a modal will appear.

    If you want to save a concept into the Saved List from the search results, you can click the 'add' button

    to add the concept into the Saved List. After the concept is added, the 'add' button is disabled
    , so you can't add the same concept into the Saved List twice.

    From various components of the CRS tool a

    View in Taxonomy button can be used to show a concept's position in the taxonomy. Selecting the View in Taxonomy button will load the concept in the Taxonomy pane.

    Note: only one concept can be viewed at a time and selecting a different concept will replace the Taxonomy tree with that of the newly selected concept.

    Concepts from search can be dragged and dropped by selecting the concept by pressing and holding on the FSN.

    The UI will then highlight the areas that are "drop zones"

    Drag the concept to the desired form field and let go to populate the field with this concept.

    Provide Feedback

    Search Terms

    Search by Concept Id and drag and drop to fields in a request

    View search results by matching terms or grouped by concept

    Distinguish and filter between active, inactive, primitive and fully defined concepts in a set of search results

    View more details about a concept in a set of search results, and its position in the taxonomy

    Add Concepts From Search Results to the Saved List

    Viewing a concept in the taxonomy within CRS and use it in a drag and drop scenario

    CRS Quickstart User Guide

    What is the SNOMED CT Content Request Service (CRS)?

    This tool allows users to request modify or make additions to SNOMED CT.

    How do I get to CRS?

    Please go to https://request.ihtsdotools.org or http://snomed.org/crs, where you will be asked to log in.

    How do I obtain a CRS Account?

    Please see, Accessing CRS.

    Is there any quick introduction?

    Yes. (and the screen is purposefully blank for a few minutes..)

    What type of content requests can I make?

    Before making any request, please read the guidance on submitting content -

    Version 15.0 Customer Guidance for Requesting Changes to SNOMED CT 20240723.pdf

    Users are able to create requests to add, modify or retire information in SNOMED CT, including:

    • Creating a new Concept(s)

    • New Synonym(s)

    • Add Parent(s)

    • Modify Description(s)

    • Modify Parent(s)

    • Modify Relationship(s)

    • New Relationship(s)

    • Retire Concept(s)

    • Retire Description(s)

    • Retire Relationship(s)

    • Other:

      • Request for new attributes to be introduced

      • Request for existing attributes to be removed

    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 prioritized for investigation.

    There are two methods of creating requests for SNOMED Content: and . To learn more about these modes and help choosing the correct one see: .

    Users may exit the system for later completion, validation, and submission.

    As an requester you can do a number of things on each request - .

    CRS Status
    Description
    PreviousSIRS Status

    Request for existing Refsets to be amended (new members or changes)
  • Request for enhancement (clean-up) of areas of SNOMED CT

  • Request for changes to the concept model

  • Changes to editorial policy statements

  • Changes to text definitions (e.g. "surgical procedure")

  • Request for Quality initiative to address specific quality issues within the Terminology

  • Accepted

    Following initial review, each request is assigned to a member of the Content Team. A change to a status of ‘Accepted’ does not mean that the request will be approved for inclusion in SNOMED CT.

    Approved & Accepted In Scope

    Under Authoring

    A member of the Content Team is actively evaluating the request.

    Construction

    In Inception

    Where a new request aligns with an ongoing content project, the request will be placed into this status 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.

    Awaiting policy

    Clarification Needed

    Where insufficient information is provided to proceed with a request, a member of the Content Team will incorporate questions to be resolved and change the status of the request to ‘Clarification Needed’. This will generate an email to the original requester. Where a request for clarification to a customer is not answered within 60 days from the date the clarification is generated, the request will be marked as rejected.

    Clarification requested

    Forwarded

    Where a request is received that is not in scope for the International Edition of SNOMED CT, it may be suitable for a specific extension. The request may be marked as forwarded to denote that it has been handed over to another extension manager or National Release Center.

    Forwarded

    Withdrawn

    Once submitted, a request cannot be deleted but can be "Withdrawn" by the original requestor.

    Withdrawn

    In Appeal

    Where a request has been “Not Accepted”, the submitter may request a further review of the decision. The submitter can then place the request in “In Appeal” status. In these circumstances the decision will be reviewed and if necessary referred to the Head of Terminology for final disposition.

    Appeal

    Appeal Rejected

    After conclusion of the appropriate appeal process, where the outcome remains unchanged, this status will be applied.

    Appeal Rejected

    Rejected

    Where a request has had a full review and is not considered to be in scope for SNOMED CT, or does not meet the criteria outlined in the Editorial Guide, or clarification about the request has not been received within 60 days it will be rejected.

    Rejected

    Ready For Release

    The requested change has been made and approved, however this status does not assure that the requested change will be included in the final release data.

    Construction

    Completed

    A request status will be changed to "Completed" once the SNOMED CT International Edition, in which the request has been addressed, has been released.

    Completed

    Draft

    A request that has been started and saved but not yet submitted.

    Draft

    New

    All submissions (excluding draft) are initially assigned a status of New. A preliminary check will be carried out to ensure that the new request falls within the inclusion criteria and scope for the International Edition of SNOMED CT before the request will be progressed.

    New

    How are Requests Prioritized?

    How do I submit a request?

    Can I save my Content Request and return to it later for completion?

    Can I modify my Request once it is submitted?

    Request Status Glossary

    Create A Request in Simple Mode
    Create a Batch Request
    Creating Requests
    Managing Submitted Requests Screen
    Provide Feedback

    End to End Work Flow - Simple Mode

    Steps
    Reference
    Steps
    Reference

    Create A Request in Simple Mode

    In Simple mode , user can create more types request as 'New Concept' , 'New Description' , 'New Relationship' , 'Change Description' , 'Change Relationship' , 'Retire Description' , 'Retire Relationship' , 'Change or Retire Concept' or 'Other' . In this mode, user is provided an easy user interface to use. As well as Direct mode, new request will be added into the My Request list in status Draft orNew after user saved or submitted request.

    From CRS Dashboard (Figure 1), click on Create New Request (1), select Simple (2) from Input Mode|

    Figure 2 - Select Simple Mode

    1. The system will load the New Request screen; fill out the request details:

      1. Local SNOMED CT code (6) - Local SNOMED CT extension code - _optional_

    • Originating Organization (7) - The source of the request ex: Organization Name Donation - required

    Steps
    Reference

    3. The system will load the New Request screen; fill out the request details:

    • * Local SNOMED CT code (6) - Local SNOMED CT extension code - _optional_
      • Originating Organization (7) - The source of the request ex: Organization Name Donation - required

      • Collaboration Agreement (8) - CMT or LOINC - optional

      • Topic (9) - What category the request falls under - required

      • Summary (10) - Usually the FSN that is the subject of the request - required

      • Proposed Use Case (11) - Describe the usage scenario - required

      • Destination Terminology (19) - SNOMED CT International or New Concept Requests - optional

      • Reference (12) - Supporting notes as to why the content request should be completed

      • Notes (13) - Any additional comments desired to be made about the request

      • Namespace (14) - optional

    4. To change a relationship, fill out the following fields:

    • * Concept (15) \- 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](31033178.html) or using type ahead see [Using Type Ahead Within CRS](Using-Type-Ahead-Within-CRS_31033205.html)
      • Relationship (20) - Select which of the descriptions from the selected concept should be changed

      • Select Show Stated Relationship or Show Inferred Relationship (21)

      • Proposed RelationshipType (22)

      • Proposed Destination Concept (23) - For more info on populating this field via search or taxonomy see: or using type ahead see

      • Proposed CharacteristicType (24)

      • Proposed Refinability (25)

      • Proposed Relationship Group(26)

    5. Press Save Request (4) to save your work or press Submit Request (5) to submit it. The request will have a status of New and you will be redirected to the dashboard.6. Jump to: What happens after my Request has been submitted?|

    Steps
    Reference

    3. The system will load the New Request screen; fill out the request details:

    • * Local SNOMED CT code (6) - Local SNOMED CT extension code - _optional_
      • Originating Organization (7) - The source of the request ex: Organization Name Donation - required

      • Collaboration Agreement (8) - CMT or LOINC - optional

      • Topic (9) - What category the request falls under - required

      • Summary (10) - Usually the FSN that is the subject of the request - required

      • Proposed Use Case (11) - Describe the usage scenario - required

      • Reference (12) - Supporting notes as to why the content request should be completed

      • Notes (13) - Any additional comments desired to be made about the request

      • Namespace (14) - optional

    4. To change or inactivate a concept, fill out the following fields:

    • * Concept (15) - 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](31033178.html) or using type ahead see [Using Type Ahead Within CRS](Using-Type-Ahead-Within-CRS_31033205.html)
      • New Concept FSN (27)

      • Inactivation Reason (28)

      • Duplicated Concept (29)

      • Historical Association (30)

      • Historical Association Value (31)

    5. Press Save Request (4) to save your work or press Submit Request (5) to submit it. The request will have a status of New and you will be redirected to the dashboard. 6. Jump to: What happens after my Request has been submitted?|

    Steps
    Reference

    3. The system will load the New Request screen; fill out the request details:

    • * Local SNOMED CT code (6) - Local SNOMED CT extension code - _optional_
      • Local code (32) - Local non-SNOMED CT reference code - optional

      • Originating Organization (7) - The source of the request ex: Organization Name Donation - required

      • Collaboration Agreement (8) - CMT or LOINC - optional

      • Topic (9) - What category the request falls under - required

      • Summary (10) - Usually the FSN that is the subject of the request - required

      • Proposed Use Case (11) - Describe the usage scenario - required

      • Reference (12) - Supporting notes as to why the content request should be completed

      • Definition(s) (33) - optional

      • Notes (13) - Any additional comments desired to be made about the request

      • Namespace (14) - optional

      • UMLS CUI (34) - optional

    4. To create a new Concept, fill out the following fields:

    • * Parent Concept (35) _-_ For more info on populating this field via search or taxonomy see: [Search, Taxonomy, and Using Drag and Drop](31033178.html) or using type ahead see [Using Type Ahead Within CRS](Using-Type-Ahead-Within-CRS_31033205.html) _\- optional_
      • New Concept FSN (36)

      • Semantic Tag (37)

      • Preferred Term (38)

      • Synonym(s) (39)

    5. Press Save Request (4) to save your work or press Submit Request (5) to submit it. The request will have a status of New and you will be redirected to the dashboard. 6. Jump to: What happens after my Request has been submitted?|

    Steps
    Reference

    3. The system will load the New Request screen; fill out the request details:

    • * Local SNOMED CT code (6) - Local SNOMED CT extension code - _optional_
      • Originating Organization (7) - The source of the request ex: Organization Name Donation - required

      • Collaboration Agreement (8) - CMT or LOINC - optional

      • Topic (9) - What category the request falls under - required

      • Summary (10) - Usually the FSN that is the subject of the request - required

      • Proposed Use Case (11) - Describe the usage scenario - required

      • Reference (12) - Supporting notes as to why the content request should be completed

      • Notes (13) - Any additional comments desired to be made about the request

      • Namespace (14) - optional

    4. To create a new Description, fill out the following fields:

    • * Concept (15) - 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](31033178.html) or using type ahead see [Using Type Ahead Within CRS](Using-Type-Ahead-Within-CRS_31033205.html)
      • Description (40) - Create New Description Here - required

      • New Case Significance (41) - optional

      • Checkbox for Description is PT (42) - optional

    5. Press Save Request (4) to save your work or press Submit Request (5) to submit it. The request will have a status of New and you will be redirected to the dashboard. 6. Jump to: What happens after my Request has been submitted?|

    Request Form Glossary
    Term
    Explanation

    Local SNOMED CT code

    Local SNOMED CT extension code -optional

    Local code

    Local non-SNOMED CT reference code - optional

    Topic

    What category the request falls under - required

    Proposed Use Case| It is very important to incorporate a clear use case 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: 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.

    ** **

    Please refer to PDF document Customer Guidance for Requesting Changes to SNOMED CT , Section 7 Request Status.

    This can also be accessed through https://www.snomed.org/change-or-add.

    Provide Feedback

    1. Press "Create New Request" in the left sidebar (1).

    2. The system will load the create New Request dialog box; select an input mode (2) (direct or simple) and a desired Request Type template (3), then press Create Request in the dialogue box.

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

    Getting Started - Create Request

    Simple mode - Change Description

    Simple mode - Change Relationship

    Simple mode - Change or Inactivate Concept

    Simple mode - Create New Concept

    Simple mode - Create New Description

    What happens after my request is submitted?

    SelectNew Concept** (3) from drop-down list Request Type and click Create Request (4) |

    ---|---

    Figure 3 - Select New Concept Type Select tab Taxonomy (1), Search or Saved List from the left panel to select a desire concept to drag & drop to Parent Concept (3) field. And then Source Terminology(4) is set automatically to SNOMED CT. But if this request is opened from Batch Requests, Terminology Suggestion(4) is set toCurrent Batch.**|

    Figure 4 - Compose a New Concept If you want to add more Parent Concept, click on the plus icon

    on each Parent Concept (1) to add.If you want to remove a Parent Concept, click on the minus icon

    on each Parent Concept (1) to remove.|

    Figure 4.1 - Add/Remove Parent Concept If you want to add more Synonyms , click on the plus icon

    on each synonym (1) to add. if you want to remove a synonym, click on

    button on each synonym to remove. do the same with Definition(2).| _

    _Figure 5 - Add More Synonyms and Definitions Select tab Request Info (1) to save(2) the request with Draft status which allows you to edit request details before submit, or submit (3) the request to manager/staff. Request details editing is locked after submitted.| _

    _Figure 6 - Save or Submit Request

    Select New Description from Request Type drop-down list and click Create Request button (Figure 7)|

    ---|---

    Figure 7 - Select New Description Search or browse for a desire concept from the left panel (1) to drag & drop it into Concept field (2), enter request details to Save or Submit the request (Figure 6).|

    Figure 8 - Compose a New Description

    Select New Relationship from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Source Concept, Relationship Type, and Destination Concept from the left panel (1) to drag & drop it into each corresponding fields (2), enter request details to Save or Submit the request (Figure 6).|

    |---

    Select Change or Retire Concept from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Concept from the left panel (1) to drag & drop into each corresponding fields (2), select a New Concept Status (3) and History Attribute (4), and then enter request details to Save or Submit the request.e|

    |---

    Select Change Description from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Concept from the left panel (1) to drag & drop into Concept field (2), select Active Description(3) and New Case Significance (4) that you want to change, and then enter request details to Save or Submit the request.|

    |---

    Select Change Description from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Concept from the left panel (1) to drag & drop into Concept field (2), select Active Description(3) and New Case Significance (4) that you want to change, and then enter request details to Save or Submit the request.|

    |---

    Select Change Relationship from Request Type drop-down list and click Create Request button (Figure 3)

    Search or browse for a desire Concept from the left panel (1) to drag & drop it into corresponding fields (2), select a Relationship (3) , Proposed RelationshipType (4), Proposed CharacteristicType (5), Proposed Refinability(6) that you want to change and then enter request details to Save or Submit the request.

    Select Retire Description from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Concept from the left panel (1) to drag & drop it into Concept field (2), select a Active Description(3) and New Description Status(4), that you want to retire and then enter request details to Save or Submit the request.|

    ---|---

    Figure 12 - Compose a Change Relationship |

    Figure 13 - Compose a Retire Description

    Select Retire Relationship from Request Type drop-down list and click Create Request button (Figure 3)Search or browse for a desire Concept from the left panel (1) to drag & drop it into Concept field (2), select a Relationship(3) , Relationship****Status(4) and Destination Terminology (5) that you want to retire and then enter request details to Save or Submit the request.

    Select Other from Request Type drop-down list and click Create Request button (Figure 3)Enter request details to Save or Submit the request.|

    ---|---

    Figure 14 - Compose a Other request

    Provide Feedback

    Summary

    Dashboard

    New Concept

    ---|---

    New Description

    New Relationship

    Change or Retire Concept

    Change Description

    Change Relationship

    Retire Description

    Retire Relationship

    Other

    Figure 14 - Compose a Retire Relationship

    Collaboration Agreement (8) - CMT or LOINC - optional

  • Topic (9) - What category the request falls under - required

  • Summary (10) - Usually the FSN that is the subject of the request - required

  • Proposed Use Case (11) - Describe the usage scenario - required

  • Reference (12) - Supporting notes as to why the content request should be completed

  • Notes (13) - Any additional comments desired to be made about the request

  • Namespace (14) - optional

  • 4. To change a description, fill out the following fields:

      • Active Description (16) - Select which of the descriptions from the selected concept should be changed

      • Proposed New Description (17) - Type the new description term

      • New Case Significance (18) - Set the Case Significance of the New Description

      5. Press Save Request (4) to save your work or press Submit Request (5) to submit it. The request will have a status of New and you will be redirected to the dashboard.6. Jump to: What happens after my Request has been submitted?

    Summary

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

    Search, Taxonomy, and Using Drag and Drop
    Using Type Ahead Within CRS
    * Concept (15) - 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](31033178.html) or using type ahead see [Using Type Ahead Within CRS](Using-Type-Ahead-Within-CRS_31033205.html)

    What happens after my request is submitted?

    Please refer to PDF document .

    This can also be accessed through .

    Customer Guidance for Requesting Changes to SNOMED CT , Section 7 Request Status
    https://www.snomed.org/change-or-add
    Provide Feedback

    Using Type Ahead Within CRS

    Using Type Ahead to Locate Concepts or Relationships

    Steps
    Reference

    Within CRS there may be times where you need to enter in a Concept or Relationship manually. The system will attempt to guess the concept you are looking for by using typeahead. To use, simply enter more then 3 characters to begin searching. Narrow the search results by entering more characters.

    This is also applicable for concepts and relationships in Direct Mode

    Provide Feedback

    US CRS User Guide

    What is the US SNOMED CT Content Request Service (USCRS)?

    This tool allows users to request, modify, or make additions to SNOMED CT. The USCRS is the SNOMED International content request system specific for user content requests for the US Edition of SNOMED CT.

    The USCRS tool is important in the effort to support the development, enhancement, and distribution of clinically specific vocabularies to facilitate the exchange of clinical data and improve retrieval of health information. SNOMED CT is one of a suite of designated standards for use in U.S. Federal Government systems for the electronic exchange of clinical health information and is also a required standard in interoperability specifications of the U.S. Healthcare Information Technology Standards Panel.

    How do I get to USCRS?

    Please go to US Edition SNOMED CT Content Request System (https://us-request.ihtsdotools.org/), which will then open the Welcome to SNOMED International page to enable log in. Once your login details are authenticated, the login process will automatically open your USCRS dashboard at the original address.

    Please Note: The application is optimized for the Google Chrome browser - please do NOT use another browser (such as IE).

    How do I obtain a USCRS Account?

    A SNOMED International account is needed to access CRS.

    If you do not have an account, or find that your existing account does not have access to USCRS, please follow the instructions on our . The form on this page can be used to request a new account for USCRS access, and also to (including USCRS) if not yet granted to an existing account.

    To request USCRS access, check (tick) the "US Content Request Service (USCRS)" option in the form section entitled "(Optional) In addition to a SNOMED International account, you may request access to specific SNOMED International tools & services", and also include an explanation of why you need USCRS and any additional qualifying information in the sections immediately after that.

    Should you still have any difficulty, please contact us by sending an email to .

    Yes. (and the screen is purposefully blank for a few minutes..)

    Users are able to create requests to add, modify or retire information in SNOMED CT including:

    • Creating a new Concept(s)

    • New Synonym(s)

    • Add Parent(s)

    • Modify Description(s)

    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 prioritized for investigation.

    There are three methods of creating requests for SNOMED Content: Simple Mode, Direct Mode, and Batch Mode. To learn more about these modes and help choosing the correct one see: Creating Requests.

    A basic understanding of SNOMED CT content and structure is required, and each request must include a justification, or practical use case. Every request must also include an identifier that links to the current version of either International Edition of SNOMED CT or US Edition of SNOMED CT. Both are available from the National Library of Medicine to users with a UMLS Metathesaurus License.

    Users may exist the system for later completion, validation, and submission.

    As an requestor you can do a number of things on each request - Managing Submitted Requests Screen

    CRS Status
    Description
    Previous SIRS Status

    Modify Parent(s)

  • Modify Relationship(s)

  • New Relationship(s)

  • Retire Concept(s)

  • Retire Description(s)

  • Retire Relationship(s)

  • Other:

    • Request for new attributes to be introduced

    • Request for existing attributes to be removed

    • Request for existing Refsets to be amended (new members or changes)

    • Request for enhancement (clean-up) of areas of SNOMED CT

    • Request for changes to the concept model

    • Changes to editorial policy statements

    • Changes to text definitions (e.g. "surgical procedure")

    • Request for Quality initiative to address specific quality issues within the Terminology

  • Accepted

    Following initial review, each request is assigned to a member of the Content Team. A change to a status of ‘Accepted’ does not mean that the request will be approved for inclusion in SNOMED CT.

    Approved & Accepted In Scope

    Under Authoring

    A member of the Content Team is actively evaluating the request.

    Construction

    In Inception

    Where a new request aligns with an ongoing content project, the request will be placed into this status 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.

    Awaiting policy

    Clarification Needed

    Where insufficient information is provided to proceed with a request, a member of the Content Team will incorporate questions to be resolved and change the status of the request to ‘Clarification Needed’. This will generate an email to the original requester. Where a request for clarification to a customer is not answered within 60 days from the date the clarification is generated, the request will be marked as rejected.

    Clarification requested

    Forwarded

    Where a request is received that is not in scope for the International Edition of SNOMED CT, it may be suitable for a specific extension. The request may be marked as forwarded to denote that it has been handed over to another extension manager or National Release Center.

    Forwarded

    Withdrawn

    Once submitted, a request cannot be deleted but can be "Withdrawn" by the original requestor.

    Withdrawn

    In Appeal

    Where a request has been “Not Accepted”, the submitter may request a further review of the decision. The submitter can then place the request in “In Appeal” status. In these circumstances the decision will be reviewed and if necessary referred to the Head of Terminology for final disposition.

    Appeal

    Appeal Rejected

    After conclusion of the appropriate appeal process, where the outcome remains unchanged, this status will be applied.

    Appeal Rejected

    Rejected

    Where a request has had a full review and is not considered to be in scope for SNOMED CT, or does not meet the criteria outlined in the Editorial Guide, or clarification about the request has not been received within 60 days it will be rejected.

    Rejected

    Ready For Release

    The requested change has been made and approved, however this status does not assure that the requested change will be included in the final release data.

    Construction

    Completed

    A request status will be changed to "Completed" once the SNOMED CT International Edition, in which the request has been addressed, has been released.

    Completed

    Draft

    A request that has been started and saved but not yet submitted.

    Draft

    New

    All submissions (excluding draft) are initially assigned a status of New. A preliminary check will be carried out to ensure that the new request falls within the inclusion criteria and scope for the International Edition of SNOMED CT before the request will be progressed.

    New

    Is there any quick introduction?

    What type of content requests can I make?

    How are Requests Prioritized?

    How do I submit a request?

    Can I save my Content Request and return to it later for completion?

    Can I modify my Request once it is submitted?

    Request Status Glossary

    SNOMED International User Accounts page
    request access to particular tools
    uscrs@snomed.org
    International and US Editions
    Provide Feedback

    SNOMED CT Content Request Service (CRS) Guide

    The document provides a comprehensive overview of the features and usage guidelines of the software application. It begins with an introduction that outlines the primary objectives and target audience. Subsequent sections detail installation procedures, basic and advanced functionalities, and customization options. The document also includes troubleshooting tips, frequently asked questions, and contact information for support. Each section is designed to ensure users can effectively utilize the application to meet their specific needs.



    © Copyright 2026 International Health Terminology Standards Development Organisation, all rights reserved.

    This document is a publication of International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED International owns and maintains SNOMED CT®.

    Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of SNOMED International. This document may be subject to updates. Always use the latest version of this document published by SNOMED International. This can be viewed online and downloaded by following the links on the front page or cover of this document.

    SNOMED®, SNOMED CT® and IHTSDO® are registered trademarks of International Health Terminology Standards Development Organisation. SNOMED CT® licensing information is available at

    Provide Feedback

    . For more information about SNOMED International and SNOMED International Membership, please refer to
    or contact us at
    .
    CRS Quickstart User Guide
    Content Request Service Terms of Service
    Service Level Agreement for International CRS
    CRS Workflow
    http://snomed.org/licensing
    http://www.snomed.org
    info@snomed.org