... | @@ -202,8 +202,8 @@ PAYLOAD - `{ |
... | @@ -202,8 +202,8 @@ PAYLOAD - `{ |
|
> }
|
|
> }
|
|
> }`
|
|
> }`
|
|
|
|
|
|
### References and inline citation
|
|
|
|
#### Legacy specification documents.
|
|
### Legacy specification documents.
|
|
As per the ClinGen Variant Curation Working Group recommendation a VCEP should be able to maintain and version specifications for a single gene separately. All specifications that are applicable for multiple genes are to be re-released into separate SVI documents.
|
|
As per the ClinGen Variant Curation Working Group recommendation a VCEP should be able to maintain and version specifications for a single gene separately. All specifications that are applicable for multiple genes are to be re-released into separate SVI documents.
|
|
|
|
|
|
A legacy document with multiple gene specifications will be fully archived when the attribute `legacyReplaced` is set to `true`. This property will be true only AFTER all the linked specification documents are re-released.
|
|
A legacy document with multiple gene specifications will be fully archived when the attribute `legacyReplaced` is set to `true`. This property will be true only AFTER all the linked specification documents are re-released.
|
... | | ... | |