...
To build a single concept authoring tool that supported by release management featuresprovides basic functions for creating and editing a single concept.
Scope
Using the new authoring tool to release SNOMED CT without the Workbench.
...
# | Title | User Story | Priority | Notes | JIRA Ticket | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | creating Creating a new concept starting with a concrete model in SNOMED CT | As an author, I want to create a new concept by using an existing model so that I can reuse the relationships in an existing concept model to create my new concept model. | |||||||||
2 | representing Representing the searched concept model | As an author, I want to see the concept model I searched from taxonomy so that I can know if it is the concept model in a diagramI wan to use to create a new one. | |||||||||
3 | editing Editing to the logical model | As an author, I want to edit the concept logical model by drag and drop the | |||||||||
4 | editing Editing the description (FSN, PT, etc.) | As an author, I want to edit the description in text fields | |||||||||
5 | accessing Accessing to more descriptions | As an author, I want to be able to add more descriptions of the concept | |||||||||
6 | manipulating languages accessibilityDefining language | As an author, I want to be able to add languagesdefine the type of language | |||||||||
7 | handling Handling multiple instances of single concept editing by using list management (being able to handle lists of a number of different concept changes, but each applied to a single concept) | As an author, I want to manage many different single concept changes in one list/webpage | |||||||||
8 | adding Adding more than one new concept editing in a single window | As an author, I want to add more than one concept change in the same webpage | |||||||||
9 | crossing boundary from one concept to another in a single window | As an author, I want to see each model related to the the description and a boundary from one concept to another | 10 | displaying Displaying the SNOMED CT taxonomy | As an author, I want to see the SNOMED CT taxonomy | ||||||
1110 | searching Searching the existing concept model in taxonomy | As an author, I want to search the existing concept model in taxonomy, which is the one I want to use as a start point | |||||||||
12 | displaying Displaying the searched existing concept model in logical model | As an author, I want to see the diagram of my selected concept model | |||||||||
13 | saving Saving the concepts just created in single concept editing tool | As an author, I want to save all edits of the concepts | |||||||||
14 | validating Validating each concept editing individually | As an author, I want to validate each concept I edited | |||||||||
15 | classifying Classifying concepts in the list | As an author, I want to classify concepts I edited | |||||||||
16 | moving Moving forward to the next step (review) | As an author, I want to move the completed editing task to the review stage | |||||||||
17 | grouping Grouping and ungrouping the relationship group | As an author, I want to be able to group and ungroup the relationship groups | |||||||||
18 | reviewing Reviewing the searched model and editing model side by side in the same window | As an author, I want to see both logical model I searched in taxonomy for reference and the model I am editing so that I can compare them easily. | |||||||||
19 | deleting Deleting the new editing description/attribute/value/concept from the editing panel if concept is unreleased | As an author, I want to be able to delete the descriptions, attributes-values, relationship group so that I can delete the wrong one before I commit my editing | |||||||||
20 | modifying Modifying relationship group by drag & drop a attribute-value pair into different relationship group | As an author, I want to drag & drop a attribute-value pair from one relationship group to another instead of changing the relationship number |
...
# | Title | User Story | Notes | JIRA Ticket |
---|---|---|---|---|
1 | each Each concept has at least one FSN | As an author, I want to define at least one FSN | ||
2 | only Only one of FSN can be marked as preferred in a given language | As an author, I want to mark only one of FSN as preferred in a given language | ||
3 | using Using a language reference set to specify which FSN descriptions is preferred in each language or dialects | As an author, I want to use a language reference set to specify FSN description is preferred in each language | ||
4 | each Each FSN term ends with a semantic tag, which indicates the semantic category to which the concept belongs (e.g. clinical finding, disorder, procedure, etc.) | As an author, I want to indicate the semantic category to which the concept belongs by using semantic tags | ||
5 | each Each concept can have one or more descriptions of type synonym in each a given language | As an author, I want to define more than one description of type synonym in each a given language |
| |
6 | populating Populating default preferred term in US when FSN is imported | As an author, I want the FSN to be populated into the preferred term (synonym) | ||
7 | specifying Specifying the language reference set of the preferred term | As an author, I want to specify the language reference set of each preferred term (US/GB) so that I can know the preferred term for which language | ||
8 | populating Populating default synonym when PT is defined | As an author, I want the PT to be populated into the synonym as the default synonym | ||
9 | distinguishing Distinguishing different relationship groups | As an author, I want to distinguish different relationship groups by different background colour of each relationship group instead of labeling the number of relationship group. | ||
10 | defining Defining the definition status | As an author, I want to define the definition status of each concept, either fully defined or primitive | ||
11 | defining Defining the status of concept | As an author, I want to define the status of each concept, either active or inactive |
...