Organization Stamp

[arpaddanos]

This is a feature request for organizations to be able to add an organization tag or digital "stamp" to evidence items and assertions. This would aid in searches and ultimately in submissions to databases like ClinVar for attribution and rating issues. Also this feature might be extended to expert editor-type stamps.

related to #811

[susannasiebert]

This might be needed for #998

[susannasiebert]

Proposal (this is in regards to assertions but can probably be applied to evidence items as well):

We will add two new actions to the interface:

• Submit an endorsement: Any curator or editor can submit an accepted assertion for endorsement for any organization they are a member of. If the curator/editor is a member of multiple organizations, they will get a dropdown to pick the organization they want to submit the assertion under. The assertion now has a pending endorsement.
• Accept an endorsement: Any editor that is a member of the same organization as an assertion with a pending endorsement can accept the assertion's pending endorsement.

If a suggested change to an assertion is accepted, the endorsement will go back into pending state. An editor in the same organization would need to re-approve the endorsement.

Given the above this is applied as follows to create a FDA-approved "database" within CIViC:

• Organizations will be able to be marked as being a VCEP
• VCEP organizations will have a status of either not FDA-approved (stage I-III) or FDA-approved (stage IV). Once a VCEP reaches stage IV we will be informed by ClinGen of this status change and change the corresponding VCEP organization to FDA-approved in our database.
• Any VCEP organization (irregardless of FDA approval status) can now go through the endorsement process for accepted assertions as described above, i.e., any member of a VCEP organization can submit an endorsement for an approved assertion and any editor of the same VCEP can accept these endorsements (side note: at one point we discussed that any VCEP editor can accept endorsements but this stricter protocol will be easier to implement since it matches the more general endorsement logic above).
• We will create a secondary FDA-approved assertions table in the CIViC database. This will have all of the fields of the main assertions table plus a field for version and a field for the VCEP organization that endorsed the assertion. Once an assertion endorsement has been accepted the endorsed assertion will be copied to the FDA-approved assertions table with a version stamp and the endorsing organization field filled in.
• When an VCEP-endorsed assertion has an accepted suggested change, the endorsement will go back into pending state. Once it is approved by a VCEP editor of the matching organization, the assertion will be copied into the FDA-approved assertions table with an updated version stamp. The assertion is now in the FDA-approved assertions table multiple times with unique version stamps and the entries reflect the state of the assertion at the point in time that they were copied.
• There will be a page in the UI to display the "gold star" FDA-approved assertions. These are assertions that were endorsed by VCEPs that themselves are FDA-approved. Effectively, a VCEP can be not FDA-approved but still submit endorsements. Once the VCEP reaches FDA-approval status their endorsed assertions will be displayed on this page.