Elevate Pango lineage BA.2.75 to Nextstrain clade 22D #984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This elevates the Pango lineage BA.2.75 to Nextstrain clade 22D with the label
22D (Omicron)
as impactful Omicron sub-lineages BA.2, BA.4, BA.5, etc... are still labelled as Omicron by the WHO.Critically, BA.2.75 has been increasing in frequency rapidly in India with a consistent logistic growth rate of 0.13 per day, compared to a logistic growth rate of BA.5 of 0.01 per day.
BA.2.75 was at 15% frequency directly estimated from GISAID data at the beginning of July. This increase of 0.13 per day is comparable to observed increase of BA.5 in the US and the UK in May.
Observing this similar trajectory of BA.2.75 in India as observed for BA.5 in multiple geographies strongly suggests that this will be a globally competitive clade, especially as we're seeing BA.2.75 directly outcompete BA.5 in India.
Additionally, there are nine spike substitutions observed in BA.2.75, including reversion of 493 to wild type, which is greater than the three substitutions observed in BA.4/5.
These mutations include G446S which is shown to escape from existing immunity to BA.2 viruses in DMS assays.
Previous Omicron-derived clades 22A (Pango lineage BA.4), 22B (lineage BA.5) and 22C (lineage BA.2.12.1) have driven sizable epidemics across the globe due to a combination of antigenic drift and increased intrinsic transmissibility.
Our primary rationale for labeling Nextstrain clades remains one of circulation and being able to discuss circulating viruses that are driving epidemics.
Our existing 4 point rationale includes:
as a mechanism to identify a clade early on that is expected to circulate widely. However, this threshold has not been reached for BA.2.75 due to how we calculate "regional" frequency, in this case, frequency in Asia. Our regional frequency estimates subsample viruses within a region equally across countries within a region. However, India is a huge country and observing 15% frequency in India is perhaps 3X the global prevalence of observing 15% frequency in South America.
To be able to call clades at an appropriate time, we propose to add an additional criteria to our existing four, namely:
This gives a higher bar for country-level threshold in terms of variant spread and also restricts to larger countries to reduce stochastic impacts. Here, the observation of >25% frequency requires some extrapolation from samples collected in June to frequency in mid-July, but I think is justified.