You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Request for Change (RFC)

Implementers can make an RFC to terminology content and subsets. Requests must be made using the Infoway RFC tool, Infoway Request Management System (InfoRMS). In order to submit an RFC, you need to request access to InfoRMS and be logged in. The tool utilizes the users Infoway Account credentials to log in and is located at this URL: https://informs.infoway-inforoute.ca/ 

The tool provides the ability to log an RFC by single entry or by using a template for batch requests. The template should be downloaded each time there is a new request to ensure the current version of the template is used. The template is an Excel file that contains multiple tabs. The “How to Use this spreadsheet” tab describes the various columns and tabs. Users should be familiar with this tab before utilizing any other tab. 

When a request is received, it is evaluated as to its completeness, accuracy, compliance to the editorial guidelines and priority level. Users will be notified of incomplete or inaccurate requests using the workflow status in the tool. An acknowledgement of the request is provided each time a request is submitted. 

All RFCs sent to SNOMED International must follow the SNOMED International Editorial Guidelines to allow better alignment with the international concepts requirements and augment the changes for inclusion in the international terminology. Complying with these guidelines upfront will also reduce the delay in sending the request to SNOMED International and the effort in managing RFC.

When a new concept is added to the Canadian Edition, Infoway will create the following:

  • One description that is the Fully Specified Name (FSN) which includes a sematic tag
  • One description that is the Preferred synonym
  • One additional synonym in English (optional)
  • One additional synonym in French (optional)
  • French translation must be provided to Infoway with references and supporting documentation when appropriate 
  • All synonyms must be semantically equivalent to the concept FSN (not narrower or broader in definition). Word order variants are not accepted.
  • No labels