Planning an HLA typing study is rarely as simple as sending samples for sequencing. Most research teams understand that HLA typing is needed, but they're not always sure how to translate a research objective into a clean, reusable project specification—one that still makes sense when new cohorts are added, when results are merged with other assays, or when a "key" cell line becomes a long-term reference.

This guide is a project-planning checklist. It helps you decide target loci, pick a useful 2-field/3-field/4-field resolution, structure sample groups, define replicate/confirmation logic for decision-critical materials, and prepare the metadata and quote-ready information that keeps HLA results interpretable later. It intentionally avoids deep platform comparison and keeps background to a minimum.

Disclosure and scope: This guide is provided by a sequencing service provider for research-use planning. It does not provide clinical or diagnostic advice.

Key Takeaways for HLA Typing Study Design

A strong HLA typing study design starts with the research decision, then defines loci, resolution, sample groups, metadata, and confirmation rules around that decision.

1. HLA typing study design should begin with the research question, not the sequencing platform.
2. Loci selection should reflect biological context, such as sample annotation, gene editing support, immune assay interpretation, or cohort research.
3. Resolution should be chosen based on how much HLA detail the downstream decision requires.
4. Sample planning should separate screening samples from decision-critical samples.
5. Replicate logic in HLA typing is different from expression studies; confirmation may matter more than biological replication for key samples.
6. Clean metadata makes HLA typing results easier to compare, reuse, and integrate with other research data.

Why HLA Typing Study Design Should Start Before Sequencing

HLA typing study design should begin before samples are submitted because loci, resolution, sample grouping, and metadata determine whether the final results can answer the research question.

The Most Common Planning Mistake

Many projects start with "Can you do HLA typing?" A provider can answer yes—but that doesn't guarantee you'll get the right loci, the right resolution, or a report format that stays reusable.

A more decision-grade way to frame the request is to specify what you need to decide after you receive the results. In practice, that usually means clarifying (1) which loci matter, (2) what resolution is sufficient, (3) which sample groups are being compared or documented, and (4) whether any samples require higher confidence or confirmation before they become references.

What This Guide Helps You Decide

This article helps you define: target loci; a resolution level tied to downstream decisions; sample groups and a way to label decision-critical samples; replicate/confirmation logic; minimum useful sample metadata; ambiguity tolerance; and deliverable expectations.

Define the Research Question Before Choosing Loci

The HLA loci included in a study should be selected according to the biological question, not simply because a panel or workflow can cover them.

Sample Annotation Studies

If the goal is to annotate cell lines, donor-derived materials, small cohorts, or reference samples with an HLA background, many studies begin with a practical core set that stays broadly useful across downstream work: HLA-A, HLA-B, HLA-C, HLA-DRB1, HLA-DQB1, and HLA-DPB1.

One early decision is whether class I alone is enough (common when you're primarily documenting antigen-presentation context for downstream assays), or whether you need class I plus selected class II loci because the downstream interpretation depends on class II context.

Immunogenetics or Population Studies

For cohort-scale work, your design pressure shifts from "what is enough for one sample?" to "what can we keep consistent across all samples and batches?" If you plan to compare allele frequencies or haplotype patterns across subgroups, consistency in loci and resolution across the entire cohort is usually more important than maximizing the locus count on day one.

Cell Line, iPSC, or Gene Editing Research

If your study includes engineered cell lines, iPSC-derived models, HLA modification, or immune recognition assays, loci selection should be bound to the downstream experiment rather than treated as a generic background add-on. Class I loci are often emphasized when the downstream work depends on T cell recognition and antigen presentation context, while class II loci become more relevant in APC-related models or CD4+ T cell–related interpretation.

Choose Resolution Based on the Decision the Result Must Support

Resolution should be chosen by asking what level of HLA difference matters for the research decision, rather than assuming the highest resolution is always necessary.

What 2-Field, 3-Field, and 4-Field Mean in Practice

Modern HLA nomenclature uses colon-delimited "fields" to describe increasing levels of sequence detail. In practical terms, 2-field typing distinguishes protein-level differences, 3-field adds synonymous coding variation, and 4-field includes non-coding variation. If you need an authoritative summary of how the four-field structure is defined and used, the peer-reviewed IMGT four-field HLA nomenclature tutorial (2023) is a useful reference.

When 2-Field May Be Enough

2-field typing is often a reasonable planning target when the HLA result primarily labels or documents samples rather than driving an allele-specific choice. This is common in basic sample annotation, early exploratory screening, and some cohort overviews where the analysis is not sensitive to fine-grained allele-level distinctions.

The key nuance is that "enough" is defined by the decision, not by the method. If a sample later becomes a reference material, a design that was adequate for labeling may be inadequate for reuse.

When Higher Resolution Is Worth Planning For

Higher-resolution planning is more valuable when results influence model selection, allele-specific research, editing design, rare-allele review, or long-term reference documentation—especially when ambiguity tolerance is low.

A Practical Resolution Rule

If the HLA result only labels a sample, 2-field typing may be sufficient; if the result affects model selection, editing design, rare allele review, or long-term reference documentation, higher-resolution typing should be considered.

Plan Sample Groups Before Counting Samples

Sample planning is not only about how many samples will be sequenced; it is about how samples are grouped, compared, and interpreted.

Define Biological Groups Clearly

Before requesting a quote, define how samples relate to each other for your objective: donor vs cell line, parental vs clone, edited vs unedited, cohort subgroup vs batch, and any control/reference set.

Separate Screening Samples From Decision-Critical Samples

Treat "decision-critical" as an explicit label. Screening/background samples can often tolerate lower resolution because they are not long-lived references. Decision-critical samples (candidate reference cell lines, engineered clones, rare donor-derived materials) typically cannot.

Mini case (de-identified): gene-edited clones need a stricter label

A project typed a parental cell line plus multiple CRISPR-edited clones. Early screening clones were typed at 2-field to document background, but two "winner" clones were later promoted to long-term reference materials used across assays.

Because those reference clones were decision-critical, the team pre-defined a rule: any ambiguity or unexpected divergence vs the parental line triggers a repeat or orthogonal confirmation before the clone is frozen as a reference. This avoided a common failure mode—discovering months later that a key clone's HLA call was not decision-grade for cross-project reuse.

Avoid Mixing Different Project Questions in One Batch

If you're combining donor screening, cohort profiling, and clone confirmation, label each set by research objective in the sample sheet. That single step makes loci, resolution, and deliverable recommendations much cleaner.

Think About Replicates Differently for HLA Typing

Replicates in HLA typing should be planned around sample identity, confidence for critical materials, and workflow control rather than the same logic used for expression or differential analysis studies.

Biological Replicates Are Not Always the Main Question

In RNA-seq and many functional assays, biological replicates are central because you're estimating variability. In HLA typing, a common goal is to establish genotype background for an individual, a cell line, or a donor-derived material. In that use case, the key risk is not "underpowered group comparison," but "a critical sample becomes a reference with insufficient confidence or insufficient documentation."

If your aim is cohort diversity or subgroup-level distribution, sample size and representativeness do become central—just don't import replicate rules from expression studies without checking whether they match your actual decision.

When Technical Repeats or Confirmation May Be Useful

Technical repeats or orthogonal confirmation are most useful when sample quality or interpretability is the risk. Examples include low-input DNA, degraded samples, decision-critical samples with ambiguous calls, suspected rare alleles, engineered clones, inconsistent metadata, and any high-value reference material intended for long-term reuse.

Mini case (de-identified): ambiguity-triggered confirmation keeps edited-clone results reusable

In an edited-clone set, initial typing returned an ambiguous genotype at one locus for a clone selected for downstream immune recognition assays. The team had already defined a confirmation trigger for decision-critical materials, so the sample was re-extracted or re-run (and, if needed, confirmed with an orthogonal approach) before the result was accepted into the project's "reference" dataset.

The practical lesson: confirmation is not a blanket requirement for every sample—it is most valuable when the HLA call will be reused as a stable label across studies, batches, or publications.

How to Mark Replicate Relationships in the Sample Sheet

Rather than relying on naming conventions, capture replicate relationships explicitly with fields such as source/donor ID, clone ID (if relevant), replicate type, extraction batch, passage, edited status, and the expected relationship between samples.

Prepare Metadata That Makes HLA Results Useful Later

Good metadata turns HLA typing results from a one-time report into reusable project information for cell line records, cohort tables, immune assays, and multi-omics analysis.

Minimum Metadata to Prepare Before Submission

At minimum, prepare a stable sample ID, sample type, cell type/tissue source, donor/source ID, any cell line/clone identifiers, edited status (if relevant), extraction batch/date (if you need traceability), target loci, desired resolution, and the downstream use.

If your HLA results will be merged with other assays, check early that your IDs and group labels align with the sample sheet used elsewhere—for example, in Single Cell RNA Sequencing—so that HLA calls can be joined cleanly without rework.

Metadata for Cell Line and Gene Editing Projects

For cell line and gene editing projects, extra traceability fields often pay off: parental line, clone ID, editing target, editing status, passage number, selection round, and intended assay. The goal is not bureaucracy; it's to ensure your HLA results stay interpretable across time and across teams.

Metadata for Cohort or Immunogenetics Projects

For cohorts, governance-aware metadata can include cohort group labels, collection site, batch, relatedness flags (if known), and paired omics availability. Avoid collecting sensitive personal information unless it is clearly approved under your study's governance model.

Mini case (de-identified): cohort expansion fails without versioned deliverables

A cohort began with one batch typed at a consistent set of loci. Months later, the study expanded with additional sites and a second batch. The original results were difficult to compare because the report package did not clearly state the reference database release and did not include a consistent sample ID mapping table for cross-batch joins.

Adding explicit versioning fields (database release, pipeline/report version, report date) and a stable ID map made subsequent batches directly comparable, and it reduced rework when merging HLA calls with other omics sample sheets.

If you want a standards-oriented rationale for why metadata and versioning matter in immunogenetics genotyping reports, MIRING is a relevant reference point—for example, "Challenges for the standardized reporting of NGS HLA genotyping" (2021).

Anticipate Ambiguity Before It Becomes a Reporting Problem

Ambiguity is easier to manage when the study design already identifies which loci, samples, and research decisions cannot tolerate uncertain HLA calls.

Which Samples Are Most Sensitive to Ambiguity?

Ambiguity is most disruptive when one sample's call becomes a long-lived reference. That often includes key reference cell lines, rare donor-derived materials, engineered clones, samples used across multiple assays, subgroup-defining cohort samples, and low-quality or limited-DNA samples.

Which Design Choices Reduce Ambiguity Risk?

Ambiguity management is mostly a design problem. Planning an appropriate resolution, selecting the right loci up front, defining confirmation triggers for decision-critical samples, keeping metadata clean, and documenting reference database versions and analysis approach all reduce the probability that ambiguous calls become a reporting bottleneck.

For additional context on complexity that can contribute to ambiguity (including repeat regions and phasing challenges), see "Repeat-region ambiguity in HLA typing" (2024 commentary).

When to Plan Orthogonal Confirmation

If confirmation might be needed, define the triggers before results arrive. For example: "Any ambiguous call in a decision-critical sample triggers review," and "phasing-sensitive samples follow an additional strategy." Long-read sequencing is often discussed as one approach to reduce cis/trans ambiguity by improving allele phasing across long regions; for a high-level example, see the PubMed-listed 2026 case report on long-read sequencing resolving cis/trans ambiguity.

Match the Sequencing Strategy to the Study Design

Sequencing strategy should be selected after loci, resolution, sample groups, and ambiguity tolerance are defined, not before those design decisions are made.

NGS as a Practical Default for Multi-Loci Research Studies

For many research-use projects, NGS is a practical default when you need multiple loci, a consistent workflow across medium-to-large batches, and standardized reporting. Published studies frequently batch samples and include controls as part of their workflow; as a general example of batched HLA sequencing in practice, see the "Host HLA sequencing and typing" workflow description in a 2022 study: "Deconvoluting complex correlates of COVID-19 severity…" (2022).

Sanger for Targeted Confirmation or Narrow Questions

Sanger sequencing is often used for targeted locus-specific confirmation or narrow follow-up questions. In planning terms, it is typically most useful as part of a pre-defined confirmation strategy for selected decision-critical samples.

Long-Read Sequencing for Phasing or Full-Length Context

Long-read approaches are often considered when ambiguity remains unresolved, when phasing is central to downstream interpretation, or when full-length context supports rare or novel allele review. The planning heuristic is simple: if your decision cannot tolerate ambiguity and phasing is important, plan for how you will address that before the first batch is run.

A Practical Study Design Worksheet for HLA Typing Projects

A study design worksheet helps a project team convert scientific intent into information a sequencing provider can use to recommend loci, resolution, and deliverables.

Use the worksheet to capture: (1) project objective and the decision the result must support; (2) loci and the required resolution; (3) sample groups, counts, and which samples are decision-critical; and (4) confirmation triggers and deliverable expectations.

Copy-ready worksheet template (you can paste into a sample sheet or quote request)

This template is designed to make loci, resolution, confirmation rules, and report requirements explicit before sequencing—so the final HLA calls remain reusable when you add new clones or new cohort batches later.

Example Study Designs for Common Research Scenarios

Example designs make it easier to see how loci, resolution, sample structure, and confirmation logic change with the objective.

What to Share With CD Genomics Before Requesting a Quote

Providing clear study design information helps CD Genomics recommend an HLA typing strategy that fits the project's loci, resolution, sample scale, and downstream research use.

Minimum Information to Include

A clean quote request typically includes: research objective; sample number and sample type; target loci; desired resolution; sample group structure; which samples are decision-critical; whether ambiguity review may be needed; and how results will be used downstream.

If you're ready to discuss execution options, the HLA Typing Sequencing page is a starting point for research use only (RUO) submissions.

When to Ask for Method Guidance

If you're uncertain about loci selection, whether 2-field is enough, whether class II loci are necessary, or whether confirmation should be planned, it's usually more efficient to share your objective and sample categories first, then ask for method guidance based on ambiguity tolerance and decision-critical sample types.

Key Takeaway: The fastest quote process usually starts with a clean sample/metadata sheet, not a platform preference.

Deliverables & Versioning: What to Ask For in Your HLA Typing Report

A planning document is only reusable if the final report can be re-joined to your sample sheet months later. Before you submit samples (or when you request a quote), align on what the report will contain and how versions will be documented.

Minimum deliverables to request

• Sample ID mapping table: the exact sample IDs you provided, plus any provider-side internal IDs.
• Loci and resolution stated explicitly: the loci typed and the intended resolution target (e.g., 2-field vs higher).
• Call format and ambiguity representation: how ambiguous genotypes are represented (e.g., multiple allele pairs, confidence notes) and where to find the "final" call.
• QC summary: key QC signals that help interpret confidence (e.g., coverage/reads summary, failed loci, repeat/confirm flags).
• Methods summary: high-level library/typing approach appropriate for RUO documentation.

Versioning and traceability fields that prevent future rework

• Reference database version used for typing (e.g., IMGT/HLA release version).
• Analysis workflow identifier (pipeline name/version, or report version).
• Report date and change log: what changed if a sample is re-run, re-called, or merged into an updated cohort.

If you expect to expand a cohort over time, ask up front how future batches will be harmonized to keep loci, resolution, and database versions comparable.

FAQ

Which HLA Loci Should I Include in a Research Study?

For many research projects, HLA-A, HLA-B, and HLA-C are common class I loci, while HLA-DRB1, HLA-DQB1, and HLA-DPB1 are often considered when class II context matters. The final loci list should follow the research question and the downstream use of the data.

Is 2-Field HLA Typing Enough?

2-field typing may be enough for basic sample annotation, but higher resolution may be useful when results affect cell line selection, allele-specific research, rare allele investigation, or long-term reference documentation.

How Many Samples Are Needed for an HLA Typing Study?

There is no universal sample number. Small studies may focus on key cell lines or donor-derived materials, while cohort studies require enough samples to support the intended population- or subgroup-level interpretation.

Do HLA Typing Studies Need Biological Replicates?

HLA typing usually determines genotype background rather than expression-level variation, so biological replicate logic differs from RNA-seq or functional assays. For decision-critical samples, technical repeats or orthogonal confirmation may be more useful than biological replication.

What Information Should I Prepare Before Requesting a Quote?

Prepare the research objective, sample type, sample number, target loci, desired resolution, sample group structure, decision-critical samples, and whether ambiguity review or confirmation may be needed so the provider can recommend a fit-for-purpose strategy.