|
|
This page provides tutorials and illustrations on how to use the CSpec Editor UI and its features.
|
|
This page provides tutorials and illustrations on how to use the CSpec Editor UI and its features.
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
## Introduction to CSpec Editor
|
|
## Introduction to CSpec Editor
|
|
|
|
|
|
|
|
ClinGen Criteria Specification Editor is an application which is designed primarily to allow users with appropriate access and permissions to do the following:
|
|
ClinGen Criteria Specification Editor is an application which is designed primarily to allow users with appropriate access and permissions to do the following:
|
|
|
|
|
|
|
1. **Create new** criteria specification document
|
|
1. **Create new** criteria specification document
|
|
|
2. **Edit** previously existing specification documents
|
|
2. **Edit** previously existing specification documents
|
|
|
3. **Reopen**, **submit** specification documents for approval and **release** approved criteria specification documents
|
|
3. **Reopen**, **submit** specification documents for approval and **release** approved criteria specification documents
|
|
|
|
|
|
|
|
The Editor in general will also allow to
|
|
The Editor in general will also allow to
|
|
|
|
|
|
|
1. Track the specification approval process and versioning of these documents
|
|
1. Track the specification approval process and versioning of these documents
|
|
|
2. Transfer content to external applications _via_ ClinGen Data Exchange
|
|
2. Transfer content to external applications _via_ ClinGen Data Exchange
|
|
|
|
|
|
|
|
The beta version of the Editor is available here [https://cspec.genome.network/cspec/ed/svi](https://cspec.genome.network/cspec/ed/svi)
|
|
The beta version of the Editor is available here <https://cspec.genome.network/cspec/ed/svi>
|
|
|
|
|
|
|
|
## User Management
|
|
## User Management
|
|
|
|
|
|
|
|
All users must be logged in to the cspec editor to gain access to the documents that are affiliated to their vceps. One can access the login form here - <https://cspec.genome.network/cspec/ed/svi>. Type in your credentials in the form shown below:
|
|
All users must be logged in to the cspec editor to gain access to the documents that are affiliated to their vceps. One can access the login form here - <https://cspec.genome.network/cspec/ed/svi>. Type in your credentials in the form shown below: 
|
|
|
<img src="uploads/7ff89af5710e66b78d5362f2fb6e42d1/login.png" width="500" height="200">
|
|
|
|
|
|
|
|
|
|
### First time users
|
|
### First time users
|
|
|
|
|
|
|
|
First time users must register to gain access to our system. Please use your email registered in the Group and Personnel Management System to register. One can access the Registration form by clicking the _Register_ button shown in the login form - <https://cspec.genome.network/cspec/ed/svi>. That link will lead you to the form as shown below:
|
|
First time users must register to gain access to our system. Please use your email registered in the Group and Personnel Management System to register. One can access the Registration form by clicking the _Register_ button shown in the login form - <https://cspec.genome.network/cspec/ed/svi>. That link will lead you to the form as shown below:
|
|
|
|
|
|
|
|
<kbd>
|
|
<kbd></kbd>
|
|
|
<img src="uploads/1d87f36975dd8774a6e5cb08bf1a5394/register.png" width="450" height="400">
|
|
|
|
|
</kbd>
|
|
|
|
|
|
|
|
|
|
### Requesting Access
|
|
### Requesting Access
|
|
|
- Log in to the Editor - https://cspec.genome.network/cspec/ed/svi once you are [registered](#First-time-users).
|
|
|
|
|
The CSpec Editor ideally should match the vcep membership with GPM as soon as a registered user logs in. However, GPM integration to the CSpec and autoregistration feature will be available ONLY for the future releases of the Editor.
|
|
|
|
|
First time users with no affiliation will see a message as shown below:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Log in to the Editor - <https://cspec.genome.network/cspec/ed/svi> once you are [registered](#First-time-users). The CSpec Editor ideally should match the vcep membership with GPM as soon as a registered user logs in. However, GPM integration to the CSpec and autoregistration feature will be available ONLY for the future releases of the Editor. First time users with no affiliation will see a message as shown below: 
|
|
|
- Users can request access to a VCEP by using the _Request Access_ feature at the top right hand side (below your account name) as shown below:
|
|
- Users can request access to a VCEP by using the _Request Access_ feature at the top right hand side (below your account name) as shown below:
|
|
|
<kbd>
|
|
|
|
|
<img src="uploads/c68e18234f0e5081ec802d5fe43ece2c/rAccess.png" width="100" height="70">
|
|
<kbd></kbd>
|
|
|
</kbd>
|
|
|
|
|
|
|
|
|
|
#### Request Access As a VCEP Coordinator/Member or SVI approver
|
|
#### Request Access As a VCEP Coordinator/Member or SVI approver
|
|
|
A user can request for a specific role (defined within the scope of CSpec Editor) to gain access to a specific VCEP.
|
|
|
|
|
|
|
|
|
|
<kbd>
|
|
A user can request for a specific role (defined within the scope of CSpec Editor) to gain access to a specific VCEP.
|
|
|
<img src="uploads/04d52244091491fc6840d7d92a7356f2/requestAccesscoordinator.png" width="350" height="150">
|
|
|
|
|
</kbd>
|
|
<kbd></kbd>
|
|
|
|
|
|
|
|
1. Choose the VCEP of interest
|
|
1. Choose the VCEP of interest
|
|
|
2. Choose the Role from the three available options:
|
|
2. Choose the Role from the three available options: a) **VCEP Coordinator** - VCEP Coordinator can create, edit, submit and release Criteria Specification documents. A VCEP coordinator can add a registered user as a coordinator or a member to their respective VCEPs. b) **VCEP Member** - VCEP member can create, edit Criteria Specification documents. c) **SVI approver** - Approves/reviews submitted specifications. Choose _All VCEPs_ if you are requesting for this role.
|
|
|
a) **VCEP Coordinator** - VCEP Coordinator can create, edit, submit and release Criteria Specification documents. A VCEP coordinator can add a registered user as a coordinator or a member to their respective VCEPs. b) **VCEP Member** - VCEP member can create, edit Criteria Specification documents. c) **SVI approver** - Approves/reviews submitted specifications. Choose _All VCEPs_ if you are requesting for this role.
|
|
|
|
|
|
|
|
|
|
## Entry Page
|
|
## Entry Page
|
|
|
Entry page shows a tabular view of all the specifications that a user has access to. The specification documents are grouped with respect to the VCEPs. Given below is an example of an entry page view for a test user who is a coordintor for multiple VCEPs.
|
|
|
|
|
|
|
Entry page shows a tabular view of all the specifications that a user has access to. The specification documents are grouped with respect to the VCEPs. Given below is an example of an entry page view for a test user who is a coordintor for multiple VCEPs.  The table is:
|
|
|
The table is:
|
|
|
|
|
- By default sorted alphabetically by the VCEP name
|
|
- By default sorted alphabetically by the VCEP name
|
|
|
- Each column is sortable individually.
|
|
- Each column is sortable individually.
|
|
|
- Pagination can be adjusted using the page controls on the top left hand side.
|
|
- Pagination can be adjusted using the page controls on the top left hand side.
|
|
|
- Search field allows filtering specification document by gene, disease, status, etc.
|
|
- Search field allows filtering specification document by gene, disease, status, etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
## Creating a new specification document
|
|
## Creating a new specification document
|
|
|
Click the _Create New_ item in the Tools menu at the top right hand side of the Entry page as shown below:
|
|
|
|
|
|
|
|
|
|
Submit the create new form. The form _Submit_ button will be disabled until all the required fields are selected or filled in:
|
|
|
|
|
|
|
|
|
|
<kbd>
|
|
Click the _Create New_ item in the Tools menu at the top right hand side of the Entry page as shown below:  Submit the create new form. The form _Submit_ button will be disabled until all the required fields are selected or filled in:
|
|
|
<img src="uploads/efc5180b9ce9b8fcd3b86fe9d3942954/createNew.png" width="350" height="300">
|
|
|
|
|
</kbd>
|
|
<kbd></kbd>
|
|
|
|
|
|
|
|
Once a new document has been successfully created the success message will guide you to the new document like so:
|
|
Once a new document has been successfully created the success message will guide you to the new document like so:
|
|
|
|
|
|
|
|
<kbd>
|
|
<kbd></kbd>
|
|
|
<img src="uploads/a31925b5413f8b1ef63c8c8ba0198c53/success.png" width="200" height="70">
|
|
|
|
|
</kbd>
|
|
|
|
|
|
|
|
|
|
## Detailed view of a specification document
|
|
## Detailed view of a specification document
|
|
|
One can access the specification document page by clicking the pencil icon at the end of each row in the entry table.
|
|
|
|
|
Sections of a specification document are:
|
|
One can access the specification document page by clicking the pencil icon at the end of each row in the entry table. Sections of a specification document are:
|
|
|
|
|
|
|
### General Metadata
|
|
### General Metadata
|
|
|
Metadata about the specification include the title, version, current status, etc,.
|
|
|
|
|
A specification document goes through a series of stages, right from when a new document is created. These stage transitions are displayed at this section as breadcrumbs and an example is shown below.
|
|
Metadata about the specification include the title, version, current status, etc,. A specification document goes through a series of stages, right from when a new document is created. These stage transitions are displayed at this section as breadcrumbs and an example is shown below. 
|
|
|
|
|
|
|
|
|
|
|
|
|
### Changing the status of the document
|
|
### Changing the status of the document
|
|
|
One can change the status of the document using the tool option at the top right hand side and this feature is designed to respond based on the permissions a user has.
|
|
|
|
|
<kbd>
|
|
One can change the status of the document using the tool option at the top right hand side and this feature is designed to respond based on the permissions a user has. <kbd> </kbd>For instance a _VCEP coordinator_ can submit the document in _Classification Rules In Prep_ stage for approval (_Classification Rules Submitted_). <kbd> </kbd>Once submitted, a coordinator can no longer make edits to that document. To make further edits the submission has to be either a) withdrawn - choosing the option _Withdraw Classification Rules Submitted_ or b) must be formally approved by the SVI approver. Similarly, an _SVI approver_ can approve OR review ( document returned without approval ) the submitted document to move the status of a document to the next stage, _Pilot Rules In Prep_ or _Classification Rules In Prep_ respectively.
|
|
|
|
|
|
|
|
</kbd>
|
|
### Change (update) the disease information
|
|
|
For instance a _VCEP coordinator_ can submit the document in _Classification Rules In Prep_ stage for approval (_Classification Rules Submitted_).
|
|
|
|
|
<kbd>
|
|
A VCEP coordinator can change the following properties which are defined as the scope of the document in either of the _Prep_ stages (Classification Rules In Prep, Pilot Rules In Prep). Use the Edit Scope tool as shown here.
|
|
|
|
|
|
|
|
</kbd>
|
|
|
|
|
Once submitted, a coordinator can no longer make edits to that document. To make further edits the submission has to be either a) withdrawn - choosing the option _Withdraw Classification Rules Submitted_ or b) must be formally approved by the SVI approver. Similarly, an _SVI approver_ can approve OR review ( document returned without approval ) the submitted document to move the status of a document to the next stage, _Pilot Rules In Prep_ or _Classification Rules In Prep_ respectively.
|
|
|
|
|
|
|
|
|
|
### Change (update) the disease information
|
|
|
|
|
A VCEP coordinator can change the following properties which are defined as the scope of the document in either of the _Prep_ stages (Classification Rules In Prep, Pilot Rules In Prep)
|
|
|
|
|
Use the Edit Scope tool as shown here.
|
|
|
|
|
Fill the _Edit Scope_ form and hit _Submit_ to make the following changes:
|
|
Fill the _Edit Scope_ form and hit _Submit_ to make the following changes:
|
|
|
|
|
|
|
1. Transcript
|
|
1. Transcript
|
|
|
2. Add new diseases
|
|
2. Add new diseases
|
|
|
3. Remove previously existing diseases
|
|
3. Remove previously existing diseases
|
|
|
4. Update the mode of inheritance
|
|
4. Update the mode of inheritance
|
|
|
|
|
|
|
|
|
|
|
|
|
### Criteria & Strength Specifications
|
|
### Criteria & Strength Specifications
|
|
|
|
|
|
|
A VCEP coordinator or a member can edit the _Criteria & Strength Specifications_ table. Details can be found [here](/Criteria-And-Strength-Specifications)
|
|
A VCEP coordinator or a member can edit the _Criteria & Strength Specifications_ table. Details can be found [here](/Criteria-And-Strength-Specifications)
|
|
|
|
|
|
|
## Reopen a previously released/existing specification document
|
|
## Reopen a previously released/existing specification document
|
|
|
A _Released_ specification document must be reopened in order to make further edits. The document then must be versioned and submitted for approval. To reopen the document use the tool option on the top right hand side of the specification document. Once reopened the document status will be _Pilot Rules In Prep_
|
|
|
|
|
<kbd>
|
|
|
|
|
|
|
|
|
|
</kbd>
|
|
|
|
|
|
|
|
|
|
### Re-submit the reopened document.
|
|
A _Released_ specification document must be reopened in order to make further edits. The document then must be versioned and submitted for approval. To reopen the document use the tool option on the top right hand side of the specification document. Once reopened the document status will be _Pilot Rules In Prep_ <kbd></kbd>
|
|
|
|
|
|
|
|
### Re-submit the reopened document.
|
|
|
|
|
|
|
|
Once a reopened document has been edited, it must be submitted for approval by submitting the document. Click the tool option, as shown below at the top right hand side of the document to _submit_ your document.
|
|
Once a reopened document has been edited, it must be submitted for approval by submitting the document. Click the tool option, as shown below at the top right hand side of the document to _submit_ your document. 
|
|
|
|
|
|
|
|
|
|
|
|
|
This tool will launch a modal as show below. Please mark the following:
|
|
This tool will launch a modal as show below. Please mark the following:
|
|
|
|
|
|
|
1. Correct version (minor or major with respect to the changes made)
|
|
1. Correct version (minor or major with respect to the changes made)
|
|
|
2. Release notes
|
|
2. Release notes
|
|
|
3. Click the submit button which will place the document in _Pilot Rules Submitted_
|
|
3. Click the submit button which will place the document in _Pilot Rules Submitted_
|
| ... | @@ -125,23 +108,17 @@ This tool will launch a modal as show below. Please mark the following: |
... | @@ -125,23 +108,17 @@ This tool will launch a modal as show below. Please mark the following: |
|
|
|
|
|
|
|
|
|
|
|
|
#### Change the version of a submitted document
|
|
#### Change the version of a submitted document
|
|
|
Once submitted one can alter the version of the document by using the overwrite version feature. Withdraw the submission or if a submitted document is returned without approval this feature will be enabled. Use the tool option to see this feature. By default this is set to _No_.
|
|
|
|
|
|
|
Once submitted one can alter the version of the document by using the overwrite version feature. Withdraw the submission or if a submitted document is returned without approval this feature will be enabled. Use the tool option to see this feature. By default this is set to _No_.  If the _Yes_ button is clicked for the _Change version?_ field an additional input field will appear. Fill in the new version here which will overwrite the running version of the document. Make sure to add all the three places in your version, that is it must be of the form - _1.0.0_  Submit your document once you have the correct version entered as shown in the example below: 
|
|
|
If the _Yes_ button is clicked for the _Change version?_ field an additional input field will appear. Fill in the new version here which will overwrite the running version of the document.
|
|
|
|
|
Make sure to add all the three places in your version, that is it must be of the form - _1.0.0_
|
|
|
|
|
|
|
|
|
|
Submit your document once you have the correct version entered as shown in the example below:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Release an approved document
|
|
## Release an approved document
|
|
|
Releasing a document will publish all the content of the approved document to
|
|
|
|
|
|
Releasing a document will publish all the content of the approved document to
|
|
|
|
|
|
|
1. The CSpec Registry
|
|
1. The CSpec Registry
|
|
|
2. The Data Exchange Kafka service, thereby making it available for VCI and other applications.
|
|
2. The Data Exchange Kafka service, thereby making it available for VCI and other applications.
|
|
|
|
|
|
|
|
Follow the steps below to release a document. To release a document, the submitted document must be **approved** and placed in _Approved For Release_ state as shown below. Review the content and make all the required changes before a document is released.
|
|
Follow the steps below to release a document. To release a document, the submitted document must be **approved** and placed in _Approved For Release_ state as shown below. Review the content and make all the required changes before a document is released.
|
|
|
|
|
|
|
|
1. Change the status of the document by clicking the top right hand side tool option.
|
|
1. Change the status of the document by clicking the top right hand side tool option.
|
|
|
2. This will launch a release option and submit the form.
|
|
2. This will launch a release option and submit the form.  |
|
|
|
|
\ No newline at end of file |
|
|
|
|
|
|
|
|
|
|
|
\ No newline at end of file |
|
|
