Page tree

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

Compare with Current View Page History

Version 1 Next »

Target releasen/a
Document statusDRAFT
Document owner

Rory Davidson

Designer
Developers
QA

Goals

  • Provide a tool that enables the management & creation of reference sets (refsets) against the International edition of SNOMED CT and Member extensions.
  • Provide a directory of existing reference sets that can be searched and downloaded to be used by others

Background and strategic fit

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

Assumptions

Requirements

Reference Set Management Epics

#TitleNotes
1

Directory of reference sets

2

Create an extensional simple refset

 
3

Create an intensional simple refset

 
4

Import and host extension simple refsets

 
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 version

 
8

Expert review of refset clinical content

 
9

Create extended-pattern refsets

 
10Edit extended-pattern refsets 

Design Epics (question)

#TitleNotes
1

version management for extensional refsets

 

 

2

version management for intensional refsets

 
3

managing dependencies between refsets and SNOMED versions across extensions

 
4

access to extension content

 
5

management of extension content

 
6

creation of refset identifiers (with namespaces)

 
7

module dependency management

 
8

release process for new/updated refsets

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

Workflow Epics (question)

#TitleNotes
1

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

 
2

management of refsets in the context of product development process

 
3

management of expert review feedback loops

  • during “derived product” development

  • during alignment with dependent SNOMED release
 

User interaction and design

n/a

Questions

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

QuestionOutcome

Not Doing

  • No labels