11-Locus HLA Typing and 4-Field Resolution

At a glance:

• Quick answer: what does 11-locus HLA typing mean?
• Class I vs Class II HLA loci
• What does 4-field HLA resolution mean?
• Why long-read sequencing can help HLA resolution
• What to specify in a high-resolution HLA typing quote request
• How to interpret an HLA typing report
• Research-use-only limitations
• FAQ
• Next step: request a quote with a locus/resolution specification
• Author

HLA typing quote requests fail more often than they should for one simple reason: the request doesn't define what will be typed and how precisely it should be reported. "HLA typing, high resolution, class I and class II" can mean very different things depending on the loci panel, the reporting target (2-field vs 4-field), and what your downstream analysis needs.

Direct answer (definitions):

• 11-locus HLA typing is a commonly requested panel that spans both classes. It usually means typing HLA-A, HLA-B, HLA-C (class I) plus HLA-DRB1, HLA-DRB3, HLA-DRB4, HLA-DRB5, HLA-DPA1, HLA-DPB1, HLA-DQA1, HLA-DQB1 (class II). Panels can still vary by provider and assay design, so you should list loci explicitly in your quote request.
• 4-field HLA resolution is a reporting format that uses four numeric fields in the allele name (e.g., HLA-A*02:01:01:01). The fields add progressively finer detail: broad allele group → protein-level differences → synonymous coding differences → non-coding differences.

If you're trying to get a quote that's accurate on the first pass, send a single line like this (verbatim example from real inquiry language):

"11-locus including Class I loci HLA-A/B/C and Class II loci HLA-DRB1/3/4/5, DPA1, DPB1, DQA1, DQB1; 4-field resolution."

Then add your sample count, sample type/state, and what you need in the final report.

⚠️ Warning: Even when 4-field is the target, the reportable resolution can vary by sample and locus. It depends on sample quality, assay design, database version, and analysis/QC thresholds.

Quick answer: what does 11-locus HLA typing mean?

In long-read HLA typing discussions, "11-locus" is shorthand for a locus set that covers the most commonly requested classical HLA targets across both classes.

A typical 11-locus set includes:

• Class I: HLA-A, HLA-B, HLA-C
• Class II: HLA-DRB1, HLA-DRB3, HLA-DRB4, HLA-DRB5, HLA-DPA1, HLA-DPB1, HLA-DQA1, HLA-DQB1

Two quote-critical clarifications:

1. "11-locus" is not a universal standard. Labs may implement different amplicon designs or panels. In a quote request, always list the loci to avoid assumptions.
2. DRB3/DRB4/DRB5 presence varies by haplotype. It is still common to request them because they can add class II context, but biologically some samples may not carry all three genes. Listing them separately (and acknowledging variable presence) makes your request unambiguous.

If your downstream work depends on per-locus completeness across a cohort (for example, association studies, subgroup comparisons, or batch-to-batch harmonization), ask upfront how the provider will handle:

• locus dropout due to amplification/coverage
• biological absence vs technical no-call
• ambiguity sets vs single allele assignments
• per-sample QC and rework policy

Class I vs Class II HLA loci

"Class I vs class II" is a real biological distinction, but for a quote request the practical issue is this: class I and class II coverage are different scopes of work.

From a research perspective:

• Class I loci (A/B/C) encode the heavy chain of class I molecules.
• Class II loci in the D region include DR, DQ, and DP genes, which are often discussed as alpha/beta chain pairs in immunology research contexts.

Where quote requests often go wrong is using "class II included" as shorthand without naming loci. A provider cannot reliably infer whether you mean:

• only DRB1
• DRB1 plus DRB3/4/5
• DRB1 plus full DP and DQ alpha/beta genes
• or an even broader set (e.g., additional non-classical loci)

Table 1. Class, loci, and what "coverage" should mean in a quote request

How to interpret the table: "Coverage" should be written as (a) locus coverage (exact genes included) plus (b) resolution coverage (how detailed the reporting target is). If you only write "class I + class II," you're outsourcing the spec to the service team, which usually triggers clarification emails.

A quote-specific clarification: DP/DQ/DR are not interchangeable labels

Quote requests sometimes say "class II (DR/DQ/DP)" and stop there. That's still ambiguous because class II coverage can mean different locus combinations:

• DR is commonly requested as DRB1, and optionally DRB3/DRB4/DRB5.
• DQ is typically requested as the pair DQA1 + DQB1.
• DP is typically requested as the pair DPA1 + DPB1.

If your downstream analysis expects matched alpha/beta locus calls (for example, DP and DQ pair-level interpretation in immunology research), ask the provider to confirm that the reporting includes both alpha and beta loci at the requested resolution, not just one side of the pair.

What does 4-field HLA resolution mean?

HLA allele naming follows official nomenclature rules and is anchored to the curated allele sequence records maintained in IPD‑IMGT/HLA.

A generic allele name looks like:

• HLA-A*02:01:01:01

The official naming rules are updated regularly; a citable primary reference is the NIH-hosted full text of the Nomenclature for Factors of the HLA System, 2026.

HLA field resolution helps define how detailed an HLA typing result is.

Table 2. HLA field level: what it indicates and interpretation cautions

How to interpret the table: "4-field HLA resolution" is best treated as a reporting target, not a guarantee. For quote accuracy, ask what the provider will do when a given locus only supports a lower-field call (e.g., report 2-field, report an ambiguity set, or report a no-call with QC reasoning).

Many teams also run into a second mismatch: they ask for 4-field calls but do not state whether they need phase-resolved haplotypes. In HLA work, "resolution" and "phasing" are related but not identical:

• Resolution is the naming granularity of the allele call you report.
• HLA phasing is whether variants are assigned to the correct haplotype (which matters when a combination of variants defines an allele, or when ambiguity sets remain without phase information).

If your project needs phase-resolved results, specify that in the quote request as a reporting requirement (for example, requesting phase-aware allele assignment and explicit ambiguity representation when phasing is not achieved).

Practical note: 4-field is not the same as "full gene sequencing"

Many researchers conflate these. A 4-field name can imply non-coding differentiation, but whether that is achievable depends on what parts of the locus are actually sequenced and how the analysis assigns alleles.

If your downstream analysis truly needs intronic/UTR differences, clarify in your quote request whether you require:

• full-gene or long-amplicon coverage
• phased haplotype sequences across the locus
• or a 4-field nomenclature label only when evidence supports it

Why long-read sequencing can help HLA resolution

The value of long reads in HLA typing isn't just "more bases." It's that longer molecules can connect variants that are far apart, which supports HLA phasing and can reduce cis/trans ambiguity.

Common failure modes in high-resolution typing occur when:

• two candidate alleles share the same sequence across the interrogated region
• variant positions that disambiguate alleles are not covered (or are covered but not phase-resolved)
• short fragments cannot establish which variants co-occur on the same haplotype

Long-read approaches are often used to:

• span long amplicons or full genes to capture variants across exons and introns
• connect polymorphic sites across the locus for phasing
• reduce ambiguity sets in allele assignment (when the assay and analysis support it)

A concise, open-access overview of why nanopore reads can help immunogenetics workflows is A long road/read to rapid high-resolution HLA typing: the nanopore sequencing perspective (2020).

Primary studies also support long-read HLA typing in high-resolution contexts, including ultrarapid and high-resolution HLA class I typing using transposase-based nanopore sequencing (2023).

From a service planning standpoint, CD Genomics states that its HLA typing service is based on third-generation sequencing technologies including ONT and PacBio (nanopore and SMRT sequencing), and describes a bioinformatics scope including HLA gene assembly and MHC phasing in its CD Genomics service overview.

Key Takeaway: Long reads are most valuable when your study needs phase-aware allele calls or you are trying to reduce ambiguity that comes from stitching together short fragments.

If you need a concrete mental model for why long reads help with phase-aware interpretation, CD Genomics also provides a service overview of haplotype-resolved assemblies in haplotype-resolved T2T sequencing, which uses long-range linkage to separate alleles at scale.

What to specify in a high-resolution HLA typing quote request

A quote request for "11-locus, 4-field" should read like a short specification. If you write it so the provider could copy it into a work order, you'll get a cleaner quote and a clearer expectation of what the report can and cannot say.

Table 3. Quote request checklist for 11-locus, 4-field-target HLA typing

How to interpret the table: The most common mismatch is sending "4-field" as a demand rather than a target, without stating what you want the lab to do when evidence supports only a lower-field call. If 4-field is critical, you need an explicit fallback policy and a plan for how those cases will be handled in downstream analysis.

Batch-scale note (e.g., 143 samples): ask for consistency controls

For large batches, you should ask two extra questions that rarely matter for single samples:

• Will the same IPD‑IMGT/HLA database version and the same analysis pipeline be applied across the entire cohort? This supports reproducibility and avoids version-driven differences between batches.
• Will you receive both a per-sample report and a cohort-level summary table? Cohort summaries make it easier to track locus dropout rates, ambiguity frequency, and batch-to-batch comparability.

If you expect staged shipments, clarify whether each shipment will be processed independently or whether results will be harmonized in a single consolidated deliverable.

Common quote failure modes (and how to avoid them)

These are the patterns that trigger the most follow-up questions during feasibility review:

1. Loci are implied, not listed. Writing "class I + class II" without naming loci forces the provider to guess. Fix: list all requested loci explicitly.
2. "4-field" is stated without a fallback policy. When certain loci/samples do not support 4-field reporting, teams argue later about what should have happened. Fix: write "4-field where reportable; 2-field minimum otherwise" (or your own rule).
3. Batch size is large, but reporting expectations are not. In cohorts (like 143 samples), you often need consistent file formats, consistent database versions, and a predictable no-call/ambiguity policy. Fix: request a cohort summary table plus per-sample details.
4. Sample state is unclear. "We have blood" or "we have DNA" can hide extraction needs, storage history, and QC risk. Fix: specify whether you will submit extracted gDNA, and what you know about integrity.
5. The request reads clinical. Mentioning donor matching or transplant eligibility can stop a RUO workflow immediately. Fix: state RUO explicitly and keep language research-focused.

A quote-ready email template (copy/paste)

Subject: Quote request — 11-locus HLA typing, 4-field target, 143 samples (RUO)

Body:

• Project scope: Human HLA typing (research use only)
• Requested loci: HLA-A, HLA-B, HLA-C, HLA-DRB1, HLA-DRB3, HLA-DRB4, HLA-DRB5, HLA-DPA1, HLA-DPB1, HLA-DQA1, HLA-DQB1
• Target resolution: 4-field where reportable; please confirm expected reportable resolution per locus and how ambiguous/no-call cases are reported
• Sample count: 143
• Sample type/state: [extracted gDNA / whole blood / tissue / cell line] + whether DNA extraction is needed
• Reporting needs: per-sample QC summary; IPD‑IMGT/HLA database version used for allele assignment; deliverables format
• Timeline: [desired start + internal milestone]

CTA (verbatim): Send your requested HLA loci, resolution target, sample type, sample number, and reporting needs to request an 11-locus long-read HLA typing quote.

For general submission logistics, you can also link internal stakeholders to CD Genomics' sample submission guideline.

How to interpret an HLA typing report

A report is only useful if you can tell what the lab is asserting at each locus and how conservative the pipeline was.

At minimum, a research-ready report should let you answer:

1. What allele call was assigned at each locus, and at what field level?
2. Is the call phase-resolved, ambiguous, or a no-call?
3. Which database and database version were used for allele assignment?
4. What QC notes explain any limitations (low input, locus dropout, etc.)?

Symbols and suffixes you may see in reports

Even when two reports both claim "high resolution," the notation can differ. A few conventions are common in HLA reporting and are worth aligning on before you scale to a large cohort:

• A slash (for example, A*02:01/02:05) usually indicates an ambiguity set: more than one allele remains consistent with the data and the model.
• A suffix letter can indicate expression status (for example, N for null alleles).
• Some reporting styles include G or P group designations that collapse alleles sharing a defined sequence region.

If your downstream pipeline requires a single allele string per locus, ask the provider how they will represent ambiguity sets and how you should handle them computationally. For cohort-scale studies, this is not a formatting detail; it changes how you compute frequencies and associations.

On CD Genomics' side, the internal educational guide A Practical Guide to HLA Typing and Result Interpretation summarizes common symbols and pitfalls in a way that's useful for onboarding non-specialist collaborators.

Resolution level vs ambiguity vs no-call

• A lower-field call (for example, 2-field) can be the correct, conservative answer when the data doesn't justify further subdivision.
• An ambiguity set usually means multiple allele candidates remain consistent with the observed data given the locus, the sequenced region, and the analysis model.
• A no-call typically means the data did not pass the lab's QC threshold for that locus at the required confidence.

If you need a durable, citable reference point for how allele definitions are curated and updated, use the European Bioinformatics Institute's IPD‑IMGT/HLA database.

For internal training (especially when multiple stakeholders will read the report), CD Genomics also provides an internal educational guide, A Practical Guide to HLA Typing and Result Interpretation, that summarizes field structure and common report symbols.

Why database version belongs in the deliverables

HLA catalogs evolve. New alleles are added, and naming conventions receive updates. If you are comparing across timepoints, cohorts, or sites, "same sample, different database version" can become a real source of disagreement.

From a reproducibility standpoint, it is reasonable to request that the report states:

• reference database name and version
• the general approach used for allele assignment (e.g., assembly- or consensus-based), at least at a descriptive level
• how the lab handles ambiguous calls and no-calls

If your organization cares about traceability, this is not administrative overhead. It is what makes the report usable later.

Research-use-only limitations

This service is for research use only and is not for use in diagnostic procedures.

Do not treat research HLA typing outputs as transplant eligibility decisions, donor matching determinations, or patient-care guidance. If your research program intersects with regulated workflows, align downstream use with your institution's compliance and review requirements.

FAQ

What loci are included in 11-locus HLA typing?

An "11-locus" request usually refers to three class I loci (HLA-A, HLA-B, HLA-C) plus eight class II loci (HLA-DRB1, DRB3, DRB4, DRB5, DPA1, DPB1, DQA1, DQB1). Some providers group DRB3/4/5 or treat them as optional because gene presence varies by haplotype. For quote accuracy, list the loci explicitly and ask the provider to confirm the assay panel and how biological absence vs technical no-call will be represented in deliverables.

Does HLA typing cover class II loci beyond class I?

It can, but you should not assume it does. Many "HLA typing" requests default to class I loci (A/B/C) unless class II is specified. If you want class II coverage, name the loci (for example, DRB1 plus DRB3/4/5, and DP/DQ alpha and beta loci). This is one reason it helps to include the phrase HLA class I vs class II loci in your quote request: it signals both scope and the need for explicit locus listing.

What is 4-field HLA resolution?

4-field resolution reports an allele name with four numeric fields (for example, HLA-A*02:01:01:01). In common interpretation, the fields add detail from allele group to protein differences, then synonymous coding differences, then non-coding differences. The official naming conventions are captured in periodic nomenclature reports; a strong primary reference is the NIH-hosted Nomenclature for Factors of the HLA System (2026). In quotes, treat 4-field as a target and specify a fallback rule for loci/samples where only lower-field calls are reportable.

Can long-read sequencing reduce HLA ambiguity?

Often, yes. The mechanism is that long reads can connect distant variants on the same molecule, supporting phasing and reducing cis/trans ambiguity that can occur when shorter fragments are stitched together. The degree of ambiguity reduction still depends on assay design, read accuracy, and sample quality. If you want to set expectations, request that the provider reports ambiguity sets explicitly and notes where results are phase-resolved.

Is 4-field resolution always guaranteed?

No. Even when a provider targets 4-field reporting, reportable resolution can vary by sample and locus due to DNA integrity, locus-specific amplification performance, sequencing error profiles, reference database and version, and conservative QC thresholds. If 4-field is required for your analysis, put it in the quote request as "4-field where reportable" and ask for locus-by-locus reporting expectations and a plan for ambiguous or no-call outcomes.

What should I include in a quote request for 143 samples?

Start with: (1) an explicit locus list (don't just write "class I + class II"), (2) a resolution target with an acceptable fallback rule, (3) the sample count (143) and whether the work is one batch or staged, and (4) sample type/state (extracted gDNA versus blood/tissue/cell lines, plus whether extraction is needed). Then add reporting requirements that support reproducibility: per-sample QC summary, ambiguity/no-call representation, and the IPD‑IMGT/HLA database version used for allele assignment.

Next step: request a quote with a locus/resolution specification

If you only take one thing from this guide, make it this: write the quote request so it can be copied into a work order without interpretation.

Send your requested HLA loci, resolution target, sample type, sample number, and reporting needs to request an 11-locus long-read HLA typing quote.

Author

Dr. Yang H., Senior Scientist at CD Genomics

Dr. Yang focuses on long-read sequencing study design and analysis for complex genomic regions, with an emphasis on reproducible reporting and QC-transparent bioinformatics deliverables.

LinkedIn: Dr. Yang H. on LinkedIn