Skip to content
naulon

No retraction, correction or concern found when last checked on Oct 21, 2026.

Near real-time monitoring of HIV transmission hotspots from routine HIV genotyping: an implementation case study

Art F Y Poon, Réka Gustafson, Patricia Daly and 10 more

The Lancet HIV · 2016

doi:10.1016/s2352-3018(16)00046-1

Full text

From PubMed Central, U.S. National Library of Medicine, as current on Oct 21, 2026. Paragraph numbers are ours, so an answer can point at one.

Introduction

Phylogenetic clustering uses virus sequence diversity to investigate “hotspots” of rapid transmission. For HIV, this approach has been facilitated by the adoption of routine genotyping for antiretroviral resistance as standard of care for clinical management of HIV infection,. A phylogeny is a tree-based representation of how populations are related through common ancestors. For rapidly-evolving viruses such as HIV, the phylogeny can resemble the transmission history of the virus, although they will not necessarily be congruent because of the extensive genetic diversity of the virus within each host. Thus, a cluster of HIV sequences from different infections that retain a high degree of genetic similarity are likely to be related by recent transmission events. Phylogenetic clusters generated from routine HIV genotype data can be informative even though these sequences tend to target a relatively conserved pol region of the HIV genome that encodes the primary targets of antiretroviral drug regimens, protease and reverse transcriptase (RT). Thus, a number of studies have used phylogenetic clustering for a one-time analysis of HIV pol datasets to retrospectively characterize potential correlates of high transmission rates of HIV, such as treatment history, stage of infection, and routes of transmission-.

Because HIV sequence-based genotypes are constantly accumulating at centers of HIV treatment, there is growing interest in utilizing this resource to inform real-time HIV prevention and control measures-. The BC Centre for Excellence in HIV/AIDS (CFE) is responsible for all HIV genotyping and distribution of antiretroviral therapy (ART) for all BC residents living with HIV, provided at no cost to the patient. Since 2013, the CFE has implemented and utilized an automated system for monitoring HIV transmission hotspots in the province by the phylogenetic clustering analysis of routine HIV genotype data. Combined with a short turn-around for sample processing, this system can provide “near real-time” information on the growth of phylogenetic clusters. We describe our implementation of a phylogenetic monitoring system in BC, and present a case study of an outbreak of transmitted HIV drug resistance detected by the system, which precipitated a formal outbreak investigation and enhanced public health follow-up of the subpopulation affected by the outbreak.

Population database

All data from the BC Drug Treatment Program (DTP) at the CFE is stored on site in a secure Oracle database (enterprise version 11g). The monitoring system was developed around a cached database query that integrates de-identified clinical, demographic, epidemiological and genetic data for all individuals enrolled in the DTP. The clinical data included: the sample collection dates; date of initiating ART; plasma viral loads (HIV RNA copies/mL); and HIV drug resistance levels as predicted by the VircoTYPE algorithm. Dates of HIV seroconversion were imputed using the method described in Poon et al. (Appendix, p.1). Demographic data included gender, birth year, forward sortation area (first three digits of the Canadian postal code) of the physician office that requisitioned the laboratory test, and date of mortality when applicable. Epidemiological data comprised the following risk factors: having ever used injection drugs; males self-identifying as homosexual or bisexual (men who have sex with men, MSM); and having received blood (transfusion) products. As of October 8, 2015, there were n=32505 HIV genotype records produced by the CFE Laboratory Program for 8839 people living with HIV – over half the estimated prevalence of HIV in BC (12981 persons in 2014). The majority (n=27850, 86%) of genotypes covered 1497 bp of HIV pol encoding protease and the first 400 codons of reverse transcriptase (RT); the remaining genotypes were derived from one or more shorter amplicons (Appendix, p.1). Transmitted drug resistance was inferred at the individual level when an HIV genotype sampled prior to initiating ART carried resistance to one or more drug classes; this does not account for people who may have started therapy outside of BC or had participated in clinical trials.

Data analysis

The monitoring system queries the DTP database every hour. Whenever new genotype records are detected, the entire contents of the cached query are downloaded to a secure workstation. Patient identifiers are automatically replaced with random hexadecimal strings with every download to break linkage with the database. HIV genotypes are re-aligned as amino acid sequences against the HXB2 pol reference sequence (K03455) using a pairwise alignment algorithm. Codons associated with the World Health Organization HIV drug resistance mutations surveillance list and insertions relative to HXB2 are excluded from the alignment. 100 replicate “bootstrap” alignments are generated by randomly sampling codons with replacement, and transferred to an in-house computing cluster for phylogenetic reconstruction in parallel by approximate maximum likelihood (Appendix, p.2).

Phylogenetic clusters, defined at a minimum of five members, are assembled from pairs of individuals that fulfill the following clustering criteria in a minimum of 50 out of 100 replicate phylogenies: (1) the total path length separating tips in the phylogeny (patristic distance) is below a cutoff of 0.02 expected nucleotide substitutions per site; (2) the tips correspond to HIV sequences from different individuals, and; (3) at least one of the sequences is derived from the individual's earliest available sample. We use a custom tree traversal algorithm implemented in Python to efficiently extract patristic distances (Appendix, p.3). To recognize clusters between analyses in the absence of fixed patient identifiers, we use the baseline sample collection dates of its first five members to index the cluster against a persistent register (Appendix, p.3-4). Clusters are annotated with clinical and demographic variables, and visualized using a force-directed layout algorithm in GraphViz with forces proportional to the phylogenetic distance between members. Reports are generated by populating a LaTeX template document with cluster statistics and diagrams with the Jinja2 templating engine (http://jinja2.pocoo.org) in Python; a mock-up report is provided in the Appendix (p.7-17).

Role of the funding source

The funders of the study had no role in study design, data collection, data analysis, data interpretation, or writing of the report. The corresponding author had full access to all the data in the study and had final responsibility for the decision to submit for publication.

Results

Since April 1999, the BC DTP population database has consistently accumulated an average of 5.7 HIV genotypes every day from the CFE Laboratory Program (Figure 1). In total, over 32000 genotypes have been produced for over 8800 persons living with HIV in BC. The sample processing time, defined as the number of days between the date of a HIV genotype test requisition and the date that the test result was uploaded into the DTP database, has declined significantly since the inception of program from a median of 14 (interquartile range, IQR 11-19) days prior to 2005, to a median of 6 (IQR 4-7) days from 2010 onwards (Figure 1). Furthermore, current BC treatment guidelines stipulate that an HIV genotype test is automatically performed on the residual blood plasma from the baseline viral load test for every new HIV diagnosis. Based on data from the Seek and Treat for Optimal Prevention of HIV/AIDS (STOP) cohort in BC, the median delay from HIV diagnosis to viral load testing was 26 (IQR 13-104) days.

Monthly and quarterly reports on the growth and characteristics of active clusters being tracked by our monitoring system have been distributed by the CFE since February 2014 to the BC Centre for Disease Control (BCCDC) and medical health officers at the five regional health authorities of British Columbia. A phylogenetic cluster is considered active if one or more new cases associated with the cluster have appeared in the DTP database within the reporting period. These reports were reviewed and discussed at monthly meetings between knowledge users in public health and laboratory staff from the CFE. As of October 8, 2015, a total of 218 phylogenetic clusters, each comprising five or more individuals, have been detected and tracked by the monitoring system. Table 1 summarizes the characteristics of the most active phylogenetic clusters over a 12 month period. These active clusters tended to be predominantly MSM, with substantial variation among clusters in age distributions and prevalence of transmitted drug resistance.

Figures 2 and 3 provide examples of the diagrams automatically generated by the monitoring system for every active cluster within the reporting period, which are designed to inform the prioritization of clusters for public health actions. For example, nodes in the network diagram are scaled to each individual's most recent plasma viral load. This particular set of diagrams correspond to cluster 0, the largest phylogenetic cluster in BC that largely comprises people who use injection drugs in the Vancouver ‘Downtown Eastside’. Cluster 0 has one of the most widespread distributions of all phylogenetic clusters (Figure 3), due in part to the cluster's size (n=414 as of October 8, 2015) and long history of expansion (Figure 2B).

In June 2014, the monitoring system determined that cluster 55 had grown by 11 new cases over a period of three months relative to the respective sample collection dates (Figure 4, left panel). A total of eight new cases carried the transmitted drug resistance mutation K103N in HIV RT, which confers resistance to first generation non-nucleotide RT inhibitors, and a median viral load of 4.9 log10 copies/mL. All but one of the individuals had accessed care within Vancouver Coastal Health (VCH) regional health authority. A provisional report on eight of the 11 new cases in cluster 55 was issued on June 24, 2014 (Figure 4, dashed line), a week in advance of the scheduled quarterly report, to the BCCDC and VCH. The baseline samples from the remaining three new cases had not yet been processed by the date of the provisional report. The rapid spread of transmitted drug resistance identified by this provisional report was deemed a sufficient public health concern that the Provincial Health Officer of British Columbia, under the authority of the Public Health Act, issued a formal request to the Chief Medical Health Officer of VCH to perform a public health investigation of all 36 individuals within cluster 55 who had accessed care within VCH. Because HIV is a reportable disease in British Columbia, the corresponding HIV diagnoses were already known to VCH public health. For the eight new cases that appeared to CFE from April to June 2014, the dates of HIV diagnoses ranged from February to June 2014. Of the 36 individuals, 33 unique individuals were identified (three individuals had laboratory tests requisitioned under two different names), of which 27 were already known to VCH public health, including all new cases with transmitted drug resistance, either in the Sexually Transmitted Infection surveillance database or in the Primary Access Regional Information System. All of the known cases were MSM, with a median age at diagnosis of 27 (range 19 to 56) years, of which 12 (44%) had been diagnosed with acute stage disease, as defined by a laboratory testing algorithm and testing history, substantially greater than the average proportion of acute stage diagnoses in the community since 2012.

During this investigation, an additional new case carrying the transmitted drug resistance mutation had appeared in cluster 55. An enhanced public health follow-up was initiated on July 2, 2014 for the nine new cases in cluster 55 (Figure 4, blue highlight). Two additional cases without HIV drug resistance subsequently appeared in cluster 55 (July 2 and 7) that were not included in this follow-up. The objective of the enhanced follow up was to ensure linkage to care and initiation of ART, and to complete any outstanding partner notification, testing and linkage to care (Appendix, p.4). Prior to July 2, only five of the nine individuals were on treatment, of which only one had attained a suppressed viral load; the median viral load was 38109 copies/mL. By September 5, 2014, eight of the individuals had initiated ART and 6 had attained undetectable viral loads, with a median viral load of <40 copies/mL (below the limit of detection; Figure 4). All nine individuals had received partner counseling and referral services (PCRS) at the time of their HIV diagnosis. During the enhanced follow-up, seven individuals were willing to re-engage with public health for further partner counseling and notification. This resulted in 12 additional contacts (five known, seven anonymous) in addition to the 37 contacts (17 known, 20 anonymous) from the initial PCRS. The number of known contacts who were known to be previously HIV positive increased from two to six individuals. Of these four previously positive contacts, one individual who was named as a contact of an acute case of HIV had been disengaged from care and involved in behaviors with high risk of onward HIV transmission. This individual was re-engaged in care as a result of the enhanced follow-up. Subsequent to the start of the enhanced follow-up, cluster 55 was relatively inactive until the end of 2014 with only one additional case (August 14, 2014; Figure 4, centre panel); however, a total of 12 new cases gradually appeared in the following year, of which three carried drug resistance (Figure 4, right panel).

Discussion

The enhanced public health follow-up of the cluster 55 outbreak was followed by the suppression of viral loads in most affected individuals and several months without new cases. It is difficult to attribute a causal effect to this intervention since there was no “control” group undergoing a similar outbreak where public health action was withheld. However, a majority (75%) of the 12 new HIV cases that appeared in cluster 55 since January 2015 were non-resistant strains mapping to parts of the HIV phylogeny that were not targeted by the enhanced public health follow-up. This outcome suggests that the follow-up partially fulfilled its primary objective of preventing the onward transmission of HIV drug resistance, though it was not completely successful in preventing further transmissions in the cluster. Although this follow-up concluded in 2014, cluster 55 has remained a focus of public health actions.

The use of routinely collected clinical HIV data to inform public health interventions raises important ethical considerations. We have utilized the ethics framework of public health to determine how this information should be collected and used for HIV prevention measures. The guiding principle of this framework is to use the least intrusive but most effective intervention available. As the use of phylogenetics is an emerging area in public health, there are no best practice guidelines for using this information. HIV is a reportable disease in BC. Under the BC Public Health Act Communicable Disease Regulation, a medical health officer may request personally identifying information from a physician when there is reasonable likelihood of HIV transmission. The primary objective of public health management is to prevent onward transmission of HIV by reaching populations at risk – not to ascribe transmission to specific individuals. Accordingly, we have used the phylogenetic cluster defined at a minimum size of five individuals as an operative unit for public health surveillance. When cluster 55 was deemed a significant public health concern, all individuals in the cluster were identified in accordance with the provisions of the Communicable Disease Regulation. Minimal information for all individuals in the cluster was securely transmitted in an encrypted format to VCH Public Health, which was already aware of all persons diagnosed with HIV in the region. The identification of groups to offer counseling, testing and treatment in rapidly growing phylogenetic clusters is consistent with the aims of HIV prevention, and discourages the attribution of fault with any one individual.

One of the general limitations to monitoring HIV transmission hotspots from routine genotyping is that it is restricted to populations with members who present for HIV testing and have a plasma viral load test. Under current provincial guidelines, a genotype test is automatically performed using the residual blood plasma from the baseline viral load tests for all new HIV diagnoses. We estimate that over half of all residents of BC living with HIV have HIV genotype test records in the DTP database. This sampling density is well within recommended levels for the reproducible identification of clusters. However, individuals who are untested or disengaged from care are likely underrepresented in the database population. A recent meta-analysis suggested that the undiagnosed population may contribute disproportionately to the onward transmission of HIV; hence, the impact of realtime monitoring may be contingent on optimizing all stages in the cascade of HIV care. Furthermore, the time between HIV infection and diagnosis inevitably varies substantially among individuals. Despite these unavoidable limitations, we have demonstrated that phylogenetic monitoring can supplement standard epidemiological methods and inform public health actions on a time scale that is sufficient to potentially alter the course of a localized outbreak.

Another challenge for the implementation of HIV phylogenetic monitoring is finding the balance between protecting an individual's right to privacy and right to refuse medical care, and the public health responsibility to prevent the onward transmission of HIV. This dilemma is exacerbated by the criminalization of HIV exposure or transmission, since the same phylogenetic methods used for characterizing transmission hotspots have also been misused to prosecute individuals for the transmission of HIV. It is further compounded by the widespread use of the terms “transmission network” or “transmission cluster” to refer to genetically-similar virus populations, which implicitly equates a phylogenetic relationship with a transmission event. On the contrary, a molecular phylogeny cannot establish whether the virus was transmitted directly from one individual to another, due to the extensive diversity of HIV within hosts and the potential for transmissions through unknown third parties. Furthermore, a phylogeny cannot determine the directionality of HIV transmission without extensive clonal sequencing of the virus populations.

The ubiquity of routine HIV genotyping in developed settings, where the comparably low but highly heterogeneous prevalence of HIV poses significant challenges for the cost-effective deployment of HIV prevention resources, is strong motivation for near real-time monitoring through the secondary analysis of data already being collected as standard of care. We have presented a case where our monitoring system prioritized a specific outbreak of transmitted HIV drug resistance for public health intervention. Such actions will ultimately become important for supporting targeted HIV prevention efforts and preserving treatment options for the population, and may translate to other areas of infectious disease.

References 32

  1. 1.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  2. 2.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  3. 3.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  4. 4.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  5. 5.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  6. 6.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  7. 7.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  8. 8.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  9. 9.
  10. 10.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  11. 11.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  12. 12.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  13. 13.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  14. 14.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  15. 15.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  16. 16.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  17. 17.
  18. 18.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  19. 19.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  20. 20.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  21. 21.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  22. 22.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  23. 23.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  24. 24.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  25. 25.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  26. 26.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  27. 27.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  28. 28.
  29. 29.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  30. 30.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  31. 31.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

  32. 32.

    This reference’s wording can’t be shown under the paper’s licence.

    Not in our library

Cited by papers we hold 7

Reads

Read by people on this page

None yet.

Checked or read by AI through naulon

None yet.

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.

Are you an author?

Is this your paper?

Claim it to add your note and be paid when agents cite it. Free.