The IPD and IMGT/HLA database: allele variant databases

1The Immuno Polymorphism Database (IPD) comprises a set of specialist databases related to the study of polymorphic genes in the immune system. Through the IPD project we collaborate with specialist groups or nomenclature committees that provide and curate individual sections before they are submitted to IPD for online publication. The IPD project stores all the data in a set of related databases. IPD currently consists of five databases: IMGT/HLA, which contains sequences of the human Major Histocompatibility Complex (MHC); IPD-KIR, which contains the allelic sequences of the human Killer-cell Immunoglobulin-like Receptors; IPD-MHC, which is a database of sequences of the MHC of different species; IPD-HPA, which is a database of human platelet antigens; and IPD-ESTDAB, which provides access to the European Searchable Tumour Cell-Line Database, a cell bank of immunologically characterized melanoma cell lines.

2A central function of the IPD project is as a database repository for the sequence data of polymorphic gene sequences. The project connects nomenclature committees for polymorphic gene systems with a core bioinformatics team who develop the tools and infrastructure required to maintain and publish the data. The aim of the project is to facilitate the work of the various nomenclature committees defining and curating the alleles within each gene system. Each allele is defined as a unique nucleotide sequence stored in the database and may cover the full-length of the gene, from UTR to UTR or just a mandatory number of exons. The entries in the database are not a description comparing two sequences. The submissions of a novel sequence must contain the sequence, and details of how this was obtained. A variant cannot not be reported as a Single Nucleotide Polymorphism (SNP) at a single position compared to a reference, without submitting proof of the sequence, the methodology used to obtain the sequence and details of the sample and its source. This ensures that the alleles seen in the databases are restricted to verified sequences and not a dataset of theoretical combinations of SNPs.

3The IMGT/HLA Database was established to provide a locus-specific database (LSDB) for the allelic sequences of the genes in the HLA system, also known as the human MHC. The IMGT/HLA Database was first released in 1998 and subsequently incorporated as a module of IPD in 2012. The MHC is one of the most complex and polymorphic regions of the human genome, with in excess of 220 genes. The core genes of interest in the HLA system are 21 polymorphic HLA genes, found within the 6p21.3 region of the short arm of human chromosome 6, whose protein products mediate human responses to infectious disease and influence the outcome of cell and organ transplants. The level of polymorphism seen in some of the genes is very high, with over 3000 variants seen in HLA-B; this level of variation can be considered hyper-polymorphic when compared to other gene systems. Three distinct regions have been identified within the MHC. The class I region is located at the telomeric end of the MHC and encodes the genes for the HLA class I molecules, HLA-A, -B and -C. These are co-dominantly expressed on the cell surface, and are responsible for presenting intracellularly derived peptides to CD8 positive T cells. The class II region lies at the centromeric end of the MHC and encodes HLA class II genes HLA-DRA, -DRB1, -DRB3, -DRB4, -DRB5, -DQA1, -DQB1, -DPA1 and -DPB1. HLA class II expression is limited to professional antigen presenting cells, where these molecules present extracellularly derived peptides to CD4 positive T cells. Located between the class I and class II regions lies the class III region where a number of non-HLA genes with immune function are located. With a nomenclature covering more than 50 genes and 12 000 alleles, there is an obvious need for a curated LSDB to manage these highly polymorphic variants. The first public release of the IMGT/HLA Database was made on the 16 December 1998. Since then the database has been updated every three months, in a total of 64 releases, (Figure 1), to include all the publicly available sequences officially named by the WHO Nomenclature Committee at the time of release.

4A major driving force behind the development and continued success of the IMGT/HLA Database is its use by the transplantation community. The HLA molecules play a key role in transplantation, with the success of kidney and bone marrow transplantation correlated with the degree to which donors and recipient are HLA matched. It has been shown that HLA matching is a critical determinant of outcome for patients receiving unrelated donor haematopoietic stem cells for haematological disorders. This has led to progressive improvements in the level of resolution achieved by HLA class I and II typing methods. HLA typing now focuses on distinguishing synonymous and non-synonymous differences within the nucleotide sequences that encode the protein domains of HLA class I and II molecules. These are the peptide binding domains that interact with variable lymphocyte receptors. The consequence of these improvements has required the development, for each polymorphic HLA class I and II gene, of a nucleotide sequence database that is both accurate and comprehensive. The use of a generalist sequence database for storing these sequences can be problematic due to inconsistencies in keyword descriptions, erroneous sequences and uncorrected errors.

5The outcome and success of a transplant could be affected by a single SNP between the recipient and the donor. It is therefore vital for any repository storing HLA sequences to have high standards of both quality control and curation. To this end all sequences submitted to the IMGT/HLA Database are expected to meet a minimum set of agreed criteria. These criteria have been defined to ensure that both the quality of sequence submitted and the clinically relevant data are of the highest standard. Sequences that do not meet these standards are not accepted, although they may be found in other databases. Following initial checks on the data quality, the submissions are further checked to ensure that appropriate steps have been taken to correctly identify novel polymorphisms. The process uses in-house pipelines, which utilize Basic Local Alignment Search Tool (BLAST) and Clustal, to both search and align the sequence submission, against both known and unnamed but submitted sequences, at the amino-acid, coding DNA sequence (CDS) and genomic level. The results of these searches highlight discrepancies against existing sequences, as well as providing detail analysis used in the provisional assignment of a name. In addition to automated analysis, curators analyse each sequence to ensure their validity and understand their mechanism of generation. Finally, no sequence is accepted into the database until it is formally named by experts within the field. The IMGT/HLA Database utilizes modern bioinformatics techniques to curate, annotate and analyse all submitted sequences, but in addition all sequences are checked by several experts at various stages of the submission process to ensure accuracy. To ensure the dissemination of these curated sequences to the wider community, once named, the alleles are added to the next nomenclature update. At this point, all named and publically available alleles are added to the public copy of the IMGT/HLA Database, the online resources are updated, and the wider community is notified of the release. At this point the users of the database are able to download the most recent version of the database to update their own local resources, ensuring that clinical testing is performed on the most recent data available.

6In recent years there has been a demand to increase the accuracy and length of sequences, while where possible lowering the cost of sequencing. This has led to the development of ‘Next Generation Sequencing’ (NGS) techniques which have enabled affordable, routine high-throughput sequencing approaches. High-throughput sequencing generates billions of sequence bases through parallel sequencing such that the same molecule(s) is sequenced multiple times in the same experiment leading, in turn, to vast amounts of new data being made available. Within immunogenetics, this has led to new approaches to sequencing the HLA genes, potentially providing greater accuracy and coverage. These developments have far-reaching implications for both immunogenetics research and clinical applications of Haematopoietic Stem Cell Transplantation (HSCT). HSCT uses DNA sequences to identify potential transplant donors with patients, as HLA matching is a critical factor when considering potential donors for patients receiving allogeneic transplants for haematological disorders.

7These recent developments in NGS methods have seen the user base of the IMGT/HLA Database expand with the additional interest in the highly curated datasets that are needed for analysis of data produced using the next generation of technology. The IMGT/HLA Database has historically been populated with data produced by a number of techniques that have focussed specifically on the more variable regions of the HLA molecule, specifically exons 2 and 3 of class I and exon 2 of class II. This has meant that whilst the database holds a large number of polymorphic sequences, these sequences can be limited to particular regions of the DNA. Figure 2 shows two coverage plots for HLA-B, the most polymorphic locus, detailing the amino-acid sequence, the CDS and the genomic DNA (gDNA) sequence. The concentration of coverage around exons 2 and 3 can be clearly seen, particularly as sequencing of these exons has been the minimum requirement for acceptance. The coverage of the flanking exons is much lower with <25% of the sequences containing data on exon 1 and <35% containing data on exon 4. The average coverage for gDNA is <10% of the alleles at a given gene.

8The generation of long-read length sequences will see an increased number of sequences deposited into the database. Whilst some of these sequences will extend existing entries, and fill out missing sequence, it is expected that many of the entries will provide novel sequences. The impact of this deluge of data in the clinical setting and its utility has yet to be measured. Under current practices, the influx of genomic data will have little effect on matching algorithms that are based solely on exon 2 and exon 3 sequence for class I or the exon 2 sequence for class II. However, with this increase in data, comes the need to analyse the impact of polymorphisms outside of these regions and assess these positions for their clinical relevance. While the expected influx of sequences also raises questions regarding the suitability of both the database and the nomenclature for the task, the HLA nomenclature was updated in 2010, and the changes implemented should ensure that even with a tsunami of new sequences, the nomenclature is fit for purpose. The underlying infrastructure used to maintain the IMGT/HLA Database is currently been reviewed and new tools and analysis pipelines are being developed to assist in the curation of sequences generated by NGS techniques.

9The analysis of the data produced by NGS techniques, whether it is the long reads associated with the Pacific Biosciences SMRT technology or shorter tiled reads associated with Roche 454, Illumina and ION-PGM, Ion-Torrent, still require an accurate reference database in order to assess the quality of the sequences produced. The hyper-polymorphic nature of HLA means that it can be difficult to accurately phase and implement sequencing analysis when a reference sequence is either unavailable or highly variable. The IMGT/HLA Database is currently focusing on addressing the challenge posed by this lack of reference data. With over 12 000 known alleles, it may not be possible to source material for all of these to obtain the full genomic sequence. Instead, the expected influx of NGS data will begin to populate the missing areas of the database. The IMGT/HLA Database will currently only accept full-length genomic sequences where the phasing of all of the tiled reads can be proven. The concern is that without accurate phasing the inferred full-length sequences produced by assembling fragments may be inaccurate. Assemblies produced based on regions that miss information or with low coverage in the reference database, may be of low accuracy or incorrectly phased. Due to the hyper-polymorphic nature of the key genes sequenced for HSCT, SNPs that may be key to assembling full-length sequences may not be available from the database, suggesting it is not just coverage but depth of coverage that is essential for accurate assembly. The IMGT/HLA Database contains genomic sequences for all the main serological groups for class I (HLA-A, -B and -C) but the coverage for class II is much lower, which may effect the accuracy of any assembled sequence.

10The IMGT/HLA Database displays allelic variation against a reference sequence for each gene. The differences can be seen visually in the sequence alignment tool. The Human Genome Variation Society (HGVS) reporting system, is another method for reporting alleles. The HGVS description compares each allele to a reference sequence and describes the change, rather than providing separate sequences for both alleles. In 2014, the IMGT/HLA Database has introduced HGVS reporting for all alleles, as part of the allele report page on the main website, see Figure 3. This report lists the variation seen in each allele against both the WHO Nomenclature Committee for Factors of the HLA System approved Reference Sequence, and the GRC Reference Sequence (GRCh38/hg38). It should be noted that these references often refer to different sequences, and for some genes the GRC reference sequences do not match existing sequences within the IMGT/HLA Database. The hyper-polymorphic nature of the HLA system is emphasized when using the HGVS reporting methods. HLA-B currently has over 3500 known variant sequences that differ by at least a SNP within the gDNA sequence. The HGVS report for HLA-B needs to list over 113 629 descriptors to cover this polymorphism just at the CDS level. Using an alternative reference sequence, B*15:01:01:01 compared to B*07:02:01, reduces the number of descriptors by 23%. This suggests that the HGVS descriptors are less reliable indices of the levels of variation as they can be easily influenced by the choice of reference sequence. Further development of these descriptors, their use, and publication will allow for linking the descriptors catalogued in the IMGT/HLA Database to other reference databases. This is of particular interest for NGS analysis, for example, the establishment of cross references between the IMGT/HLA HGVS descriptors and the rs# used in dbSNP, which is an increasingly common request from the new users of the database.

11The IMGT/HLA Database provides a diversity of tools for the analysis of HLA sequences. Some of these tools were custom written for the IMGT/HLA Database, whereas others were incorporated from the existing set of tools described on the EBI website. The website includes tools for producing user-defined sequence alignments at the protein, cDNA and gDNA level. The user is also able to perform queries for specific HLA alleles; the output provides access to detailed information on any HLA allele, including information on the ethnic origin of the source material, database cross-references and seminal publications. This information is also available through integration with European Bioinformatic Institute (EBI) EB-Eye search engine.

12Sequence data, both nucleotide and protein, from IPD is incorporated into the EBI suite of search tools including the FASTA suite of programmes and the BLAST and are downloadable from the EBI's File Transfer Protocol (FTP) directory in a variety of commonly used formats such as FASTA, MSF and PIR.

13The HLA Nomenclature and its publication through the IMGT/HLA Database has been taken as a model by other groups working on curating MHC sequence variation. The MHC sequences of many different species have been reported, often in different formats and with different nomenclature systems used in the naming and identification of new genes and alleles in each species. This disparate approach has led to many individual studies, often unrelated, with the potential for conflicting nomenclature. The nomenclature for MHC genes and alleles in species other than humans and mice has historically been overseen either informally by groups generating sequences, or by formal nomenclature committees set up by the International Society for Animal Genetics (ISAG). This work is now overseen by the Comparative MHC Nomenclature Committee and is supported by ISAG and the Veterinary Immunology Committee (VIC) of the International Union of Immunological Societies (IUIS). With the high degree of similarity seen in the sequences of the MHC from a number of different species a consistent methodology for the curation, naming and publication of these sequences is recommended. By bringing the work of different nomenclature committees together a central resource that facilitates further research on the MHC of each can be developed. The first version of the IPD-MHC database involved the work of groups specializing in non-human primates (NHP), canines (DLA) and felines (FLA) and incorporated all data previously available in the IMGT/MHC Database. Further developments have been able to add sequences from cattle (BoLA), teleost fish, rats (RT1), sheep (OLA) and swine (SLA). In 2012 the nomenclature used to describe the alleles of non-human primates was extensively revised and updated. This was accompanied by updating the NHP section of IPD-MHC, which currently contains over 4000 alleles covering 47 species of apes, old world and new world monkeys. The management of the sequences within IPD-MHC and the provision of an online submission tool has enabled these databases to grow. The number of sequences deposited in IPD-MHC has increased by at least 10% each year. This has resulted in regular publications reporting updates or changes to the nomenclature.

14The IMGT/HLA Database model can also be applied outside the MHC, as is seen in the IPD-KIR Database. The KIR genes are members of the immunoglobulin super family (IgSF) formerly called Killer-cell Inhibitory Receptors. KIRs are highly polymorphic both at the allelic and haplotypic levels. They are composed of two or three Ig-domains, a transmembrane region and cytoplasmic tail, which can in turn be short (activatory) or long (inhibitory). Due to the complexity in the KIR region and KIR sequences, a KIR Nomenclature Committee was established in 2002 to undertake the naming of human KIR allele sequences. The first KIR Nomenclature report was published in 2003, which coincided with the first release of the IPD-KIR database. The number of officially named human KIR alleles has increased since the initial release, which contained 89 alleles. As of January 2014, there are now over 600 alleles, which code for over 320 unique protein sequences. Table 1 provides further information on the content of the various projects.

15The IPD-HPA and IPD-ESTDAB projects are housed within IPD but do not share the same structure and tools as the other projects. The IPD-HPA Database provides a centralized repository for the data, which define the human platelet antigens (HPA). Alloantibodies against human platelet antigens are involved in neonatal alloimmune thrombocytopenia, post-transfusion purpura and refractoriness to random donor platelets. The HPA nomenclature system was adopted in 1990 to overcome problems with the previous nomenclature. Since then, more antigens have been described and the molecular basis of many have been resolved, and the nomenclature was revised in 2003. The European Searchable Tumour Line Database (ESTDAB) Database and Cell Bank provide a service enabling investigators to search online for HLA typed immunologically characterized tumour cells as part of the European Commission Fifth Framework Infrastructures Program.

16A major challenge for the developers and the curators of the databases is to keep up with the increasing number of allele sequences that are being submitted. In recent years the number of sequences in the database increased on average by 29% each year. The database must develop new tools for the visualization of sequences whilst maintaining the high standards set in the presentation and quality of the HLA sequences and nomenclature to the research community. The techniques behind NGS offer the potential to phase polymorphisms across genes, rather than within the individual genes. The database will need to consider how this type of data can be made available and whether a nomenclature for these haplotypes needs implementing or whether existing reporting formats can be utilized to present this data, using the HLA Nomenclature and allele designations as core components in reporting these new variants. The database aims to continually develop new tools and refine existing tools to meet this challenge. These challenges must be met by all IPD projects.

17The IPD provides a centralized resource for everybody interested, clinically or scientifically, in the MHC system. The database and accompanying tools allow the study of these alleles from a single site on the World Wide Web. It aids in the management and development of nomenclature, providing a continuing and updated resource for the Nomenclature Committees. The challenges for the database are to keep up with the increase in submitted sequences, keep pace with the increasing difficulties in performing analyses on larger datasets and develop new tools for the visualization of sequences whilst maintaining the high standards set in the presentation and quality of the sequences and nomenclature to the research community.

18The IMGT/HLA database is covered by the Creative Commons Attribution-NoDerivs Licence, which is applicable to all copyrightable parts of the database, which includes the sequence alignments. This means that users are free to copy, distribute, display and make commercial use of the databases in all jurisdictions provided they give the appropriate credit. Support for the database is requested from commercial users of the database resources. If users intend to distribute a modified version of the data in any form, then they must ask for permission; this can be done by contacting hla@alleles.org for further details of how modified data can be reproduced.

19IPD Homepage: http://www.ebi.ac.uk/ipd/IPD FTP Site: ftp://ftp.ebi.ac.uk/pub/databases/ipd/IMGT/HLA Homepage: http://www.ebi.ac.uk/ipd/imgt/hla/IMGT/HLA FTP Site: ftp://ftp.ebi.ac.uk/pub/databases/ipd/imgt/hla/Contact: hla@alleles.org

20IPD Homepage: http://www.ebi.ac.uk/ipd/

21IPD FTP Site: ftp://ftp.ebi.ac.uk/pub/databases/ipd/

22IMGT/HLA Homepage: http://www.ebi.ac.uk/ipd/imgt/hla/

23IMGT/HLA FTP Site: ftp://ftp.ebi.ac.uk/pub/databases/ipd/imgt/hla/

24Contact: hla@alleles.org