VCV Statement Extensions¶
Overview¶
Schema Reference
For the canonical extension reference tables (extension names, value types, and descriptions), see VCV Statements — Extensions.
VCV aggregate statement records contain extensions arrays at two structural levels — on the top-level Statement and on the classification object. Extensions carry aggregate review status information and classification context that are not part of the GA4GH VA-Spec statement model but are essential for interpreting the aggregation outcome.
All extensions follow the structure { "name": "<extension_name>", "value": <value> }.
Statement Extensions¶
Extensions on the top-level VCV Statement record.
| Extension | Type | Description |
|---|---|---|
clinvarReviewStatus |
string | The aggregate review status derived from the submission level and aggregation outcome. See Aggregate Review Status for the complete value table. Always present. |
Example¶
[
{ "name": "clinvarReviewStatus", "value": "criteria provided, multiple submitters, no conflicts" }
]
Review status values:
practice guideline— PGreviewed by expert panel— EPcriteria provided, single submitter— CP with one submittercriteria provided, multiple submitters, no conflicts— CP concordantcriteria provided, conflicting classifications— CP conflictingno assertion criteria provided— NOCPno classification provided— NOCLflagged submission— FLAG
Classification Extensions¶
Extensions on the classification MappableConcept within the Statement.
| Extension | Type | Description |
|---|---|---|
conflictingExplanation |
string | A formatted breakdown of conflicting classification counts. Present only when the classification is conflicting. |
Example¶
A conflicting CP classification:
{
"conceptType": "Classification",
"name": "Conflicting classifications of pathogenicity",
"extensions": [
{ "name": "conflictingExplanation", "value": "Pathogenic(3); Likely pathogenic(2)" }
]
}
Note
The conflictingExplanation extension is only present when multiple distinct significance values exist for a conflict-detectable proposition type. Non-conflicting classifications and single-submitter aggregations do not include this extension.
A non-conflicting classification has no extensions on the classification object: