Page tree
Skip to end of metadata
Go to start of metadata

Item

Priority

Requirement description

Cat Type

1

1

The full set of submissions from all parties should ALWAYS be publicly visible in real time. Furthermore, it should not be possible to register a request with limited visibility

Submission

2

1

The tool must provide the ability to search for a particular submission, by text string or identifier, or category of submissions (by submission type or super-type concept) or association with a derivative product (eg Refset or cross-map) or by submitting organisation or user.

Search

3

1

It should be possible to retrieve, group or filter any set of requests by the metadata attached to its individual members and/or the lexical properties of its supporting human-readable information, e.g. to retrieve all 'high priority' reports that mention the word 'vaccine' anywhere in the text and relating to any identifier from Namespace 1000002

Search

4

1

When searching for submissions, the tool should provide features to prevent the user from 'getting lost', or losing previously selected components e.g. use of 'back' button.

Navigation

5

1

The live content of the request repository should be exposed via an API to online authoring and user environments, so that authors interacting with SNOMED content can see it annotated with existing reports in real time.

Reports

6

1

The tool must provide functions to fully support the approvals process as set out in the Content Change Management Process agreed by the IHTSDO

Workflow

11

1

The tool must support the IHTSDO submission appeal process both in respect of process and guiding principles.

Workflow

7

2

The tool must provide control over refining or broadening any search including but not limited to, domain restrictions – e.g. "Procedures only" or "International subset"The tool must allow submissions returned by searches, to be viewed either by individual submission detail (with all supporting information) or in a list of similar submissions.

Search

8

2

The tool should provide the ability to search using wildcards, include/exclude words etc.

Search

9

2

The tool should provide the ability to analyse historical submissions and projected future release data. Further, it should be possible to download the complete set of requests/reports ever made (which should always updated at least daily) in an agreed format (e.g. XML), both for offline study by anybody who cares and also to allow integrating into offline tooling environments.

Reports

10

2

The tool must have the facility to provide links to policies and other documents e.g. Inclusion / exclusion criteria, list of frequently rejected patterns of submissions

User Guide Documentation

  • No labels