SNOMED CT Refset Management & Translation Tooling

Space shortcuts

Page tree

Versions Compared

Old Version 3

changes.mady.by.user Rory Davidson

Saved on

compared with

New Version 4

changes.mady.by.user Rory Davidson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Reference set management is another part of the authoring and management of SNOMED CT and there is no tool right currently which is sufficient to provide that capability alongside the capability for the community to search for existing reference sets.

...

  • IHTSDO Terminology Server (TS) platform to retrieve the terminology. The TS already provides the backend functionality to manage reference sets but there is currently no REST API for this, nor any front end interface.
  • IHTSDO Identity Management Server (IMS) for user accounts and authentication - IHTSDO Identity Management Service Documentation
  • IHTSDO Component Identifier Service (CIS) for assigning identifiers to new reference sets (within the correct namespace) - ICIS - (this is still in beta/testing)

Requirements

Reference Set Management Epics

#TitleNotes
1

Directory of reference sets

  • The directory solution will contain reference sets that currently exist on the IHTSDO Terminology Server against the SNOMED CT International Release
  • The directory will contain reference sets that are not on the IHTSDO Terminology Server
  • The directory solution will allow a user to search reference sets based on the reference set members
2

Create an extensional simple refset

 
3

Create an intensional simple refset

 
4

Import and host extension simple refsets

  • Import existing RF2 files
5

Visualize the members of simple refset

 
6

Edit the members of simple refsets

 
7

Compute the effect of an update to a dependant SNOMED CT version

 
8

Create extended-pattern refsets

 
9Edit extended-pattern refsets 

Design Epics (question)

#TitleNotes
1

version Version management for extensional refsets

 

 

2

version Version management for intensional refsets

 
3

managing Managing dependencies between refsets and SNOMED CT versions across extensions

 
4

access Access to extension content either by multi-tenancy or other integration strategies

 
5

management Management of extension content within the scope of reference sets

 
6

creation Creation of refset identifiers (with namespaces) using the IHTSDO component identifier service

 
7

module Module dependency management

 
8

release Release process for new /or updated refsets

 
9distribution Distribution of refset products (including documentation, exemplars, links to human-readable versions) 

Workflow/Business Process Epics 

...

#TitleNotes
1

refset identifier concept management (in relation to product & SNOMED releases) 

 
2

management Management of refsets in the context of a product development process

 
3

management Management of expert review feedback loops

  • during “derived product” development

  • during alignment with dependent SNOMED release
 

...

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

...