Members' Public Beta Release Requirements

• free text, multi-line
• required field

As implemented in MVP

•  free text, multi-line
• required field

• drop-down selector, ISO-639 language codes/names
• required field

Could be a subset from a standards list if definition is available. A user-definable subset list preference would be good for UX. Another option, and perhaps slicker UX, would be to make language and country fields auto-complete from entered text, rather than presenting traditional drop-down lists (eg https://www.devbridge.com/sourcery/components/jquery-autocomplete/)?

•  free text, multi-line

• drop-down selector, ISO-3166 country codes/names

Could be a subset from a standards list if definition is available. A user-definable subset list preference would be good for UX. Also see note on "Refset field - Language" above for possible alternative UX approach.

• drop-down selector, SNOMED CT release versions
• required field

• Free text input: SNOMED CT extension names

• date-time, ISO-8601

• free text, multiline

• Number of downloads: integer
• Number of views: integer
• Last modified: date-time, ISO-8601
• Contributor: name 

• drop-down selector, ISO-639 language codes/names

Could be a subset from a standards list if definition is available. A user-definable subset list preference would be good for UX. Also see note on "Refset field - Language" above for possible alternative UX approach.

• free text search query

• drop-down selector, ISO-3166 country codes/names

Could be a subset from a standards list if definition is available. A user-definable subset list preference would be good for UX. Also see note on "Refset field - Language" above for possible alternative UX approach.

• drop-down selector,SNOMED CT release versions

• drop-down selector, SNOMED CT extension codes/names

• free text search query (concept ID pattern matching)

• free text search query (return all Refsets containing the specified term)

• drop-down selector, SNOMED CT clinical domains

Fields for more information display:

• Use case / scope
• Implementation details

• Description field is "view Refset" link anchor
• "View Refset" button is removed from Refset listing entries

• Remove "last updated by" column from Refset listings

To be able to rerun the spec to create new instance e.g. after SNOMED CT changes, to find the differences that need to be managed

Use refset spec to adjust refset content automatically

Needs to be a basic workflow which allows the import/creation of resets, adjusting content to changes to SCT and to producing release files

Needs the ability to import refsets developed outside the tool (including from other member countries) into workbench

Tool should suggest replacements for deprecated content based on historical associations at SCt version change

Include in the Refset display metadata info the SNOMED CT Version used for creation of the refset. Allow for adding a note to remember this is not the latest version when not working with the latest version. Add the refset version as well in each output of the refset: list, file, specification or otherwise.

Allow to build a refset on searching for specific terms additionally to use of other clauses (such as constraint on a hierarchy or sub-hierarchy)

Allow multiple selection of concepts (e.g.: from an imported list) and selection of a clause to apply to those as a group rather than individually (e.g.: list of concepts to exclude + all of their descendants. Add a specification to an imported list where we would apply to all concepts the ‘Kind of’ clause.)

Clauses

o Add Code and children: Does not exist. Can this be created rather than using 2 clauses jointly: Concept is clause + Concept is child of clause.
o With Property: Does not exist. Indicates that the line filters to include codes that have the specified property and/or property value.
o Content Below: Does not exist. Includes the value set nested deeper in the hierarchy appearing directly beneath this one. Allows the unioning or excluding of a complex value set content definition.
o Child Value sets Only: Does not exist. The value set is determined solely by the "child domain" value sets. The tab is included only to define value set metadata such as value set name and OID
o Specializations of Root Concept: Does not exist. Includes all codes in the code system subsumed by the root concept code.

Allow creation of default refset clauses specification templates so we would never start from scratch (for different basic use cases)

Allow different sorting option for the selected descriptions in a specification (alpha, alpha+FSN or alpha+PT, per hierarchy, per sub-hierarchy, etc)

Allow adding a specification to an imported list of concepts created as a refset

When cloning
o all clauses must be cloned as well

o automatically create a name for the Clone o In the cloned refset, mention the original refset this one was cloned from

Activate or not the mandatory date as a user preference and allow flags to inform the user :
o Activate one for the overall refset creation cycle
o Activate and enter date for each user and user role for review and action in the workflow.

When inactivating a concept, make sure all components are being inactivated/cleared and the concept no longer shows in the Taxonomy. Allow creating another refset with same name.

Allow creation of a naming convention template for creation of refse

When adding a comment to a refset, discrepancy between the selected concept and the one where the comment is added. Make sure alignment is 100% effective when selecting a concept and acting on it

Allow to create other than Translation Project where the same concept can be included in many refsets. Allow to display a warning message when a concept (if many, group them in a logical manner if possible) is in many refsets provide metadata as to the refsets name, version, etc.