End to End Work Flow - Simple Mode

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:

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 a 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 or using type ahead see Using Type Ahead Within CRS

  • 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?

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 or using type ahead see Using Type Ahead Within CRS

  • 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: Search, Taxonomy, and Using Drag and Drop or using type ahead see Using Type Ahead Within CRS

  • 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?

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 or using type ahead see Using Type Ahead Within CRS

  • 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?

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 or using type ahead see Using Type Ahead Within CRS - 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?

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 or using type ahead see Using Type Ahead Within CRS

  • 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?