For ClinGen/CGC/VICC Codes, AMP/ASCO/CAP Category, and ACMG Codes we want to have the ability to support versions of the curation protocols.
We can continue to display the appropriate code type based on the assertion type, but now the user will need to select the specific version of the protocol they are curating under and be presented with the appropriate code options based on that protocol.
Broadly, we will need a table for "Protocol" or "Code Sets" which will have a name, a version string, a brief descriptive text, and a link to a document describing the protocol. This will be associated with a set of codes allowable under that protocol (ex: Tier I - Level A or OS2, OS3, OP1, OP4). These protocols can also optionally be associated with CIVIC orgs so they can be displayed on the appropriate page
We'll want to build some basic admin functionality to manage these protocols.
The team believes it will be possible to backfill existing assertions.
For ClinGen/CGC/VICC Codes, AMP/ASCO/CAP Category, and ACMG Codes we want to have the ability to support versions of the curation protocols.
We can continue to display the appropriate code type based on the assertion type, but now the user will need to select the specific version of the protocol they are curating under and be presented with the appropriate code options based on that protocol.
Broadly, we will need a table for "Protocol" or "Code Sets" which will have a name, a version string, a brief descriptive text, and a link to a document describing the protocol. This will be associated with a set of codes allowable under that protocol (ex: Tier I - Level A or OS2, OS3, OP1, OP4). These protocols can also optionally be associated with CIVIC orgs so they can be displayed on the appropriate page
We'll want to build some basic admin functionality to manage these protocols.
The team believes it will be possible to backfill existing assertions.