Partial sequencing analysis of the NS5B region confirmed the predominance of hepatitis C virus genotype 1 infection in Jeddah, Saudi Arabia
Bibliographic record
Abstract
Chronic hepatitis C virus (HCV) infection and its progression are major health problems that many countries including Saudi Arabia are facing. Determination of HCV genotypes and subgenotypes is critical for epidemiological and clinical analysis and aids in the determination of the ideal treatment strategy that needs to be followed and the expected therapy response. Although HCV infection has been identified as the second most predominant type of hepatitis in Saudi Arabia, little is known about the molecular epidemiology and genetic variability of HCV circulating in the Jeddah province of Saudi Arabia. The aim of this study was to determine the dominance of various HCV genotypes and subgenotypes circulating in Jeddah using partial sequencing of the NS5B region. To the best of our knowledge, this is the first study of its kind in Saudi Arabia. To characterize HCV genotypes and subgenotypes, serum samples from 56 patients with chronic HCV infection were collected and subjected to partial NS5B gene amplification and sequence analysis. Phylogenetic analysis of the NS5B partial sequences revealed that HCV/1 was the predominant genotype (73%), followed by HCV/4 (24.49%) and HCV/3 (2.04%). Moreover, pairwise analysis also confirmed these results based on the average specific nucleotide distance identity: ±0.112, ±0.112, and ±0.179 for HCV/1, HCV/4, and HCV/3, respectively, without any interference between genotypes. Notably, the phylogenetic tree of the HCV/1 subgenotypes revealed that all the isolates (100%) from the present study belonged to the HCV/1a subgenotype. Our findings also revealed similarities in the nucleotide sequences between HCV circulating in Saudi Arabia and those circulating in countries such as Morocco, Egypt, Canada, India, Pakistan, and France. These results indicated that determination of HCV genotypes and subgenotypes based on partial sequence analysis of the NS5B region is accurate and reliable for HCV subtype determination.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".