High-Throughput HLA Typing for Cohorts, Whole Blood, and Donor Research Screening

At a glance:

• Quick answer: what information is needed for a high-throughput HLA typing quote?
• Planning HLA typing for 100, 200, or 143 samples
• Whole blood vs extracted DNA for cohort HLA typing
• Choosing loci and resolution for cohort studies
• Data delivery and report management for large projects
• Price, lead time, and feasibility discussions
• Research-use-only limitations
• FAQ
• Next steps: request a high-throughput HLA typing quote
• Author

Large HLA typing projects don't usually stall because the lab can't run the assay—they stall because the quote inputs are incomplete. When you're planning cohort-scale typing (100, 200, or even a "weird number" like 143 samples), you need a plan for sample tracking, batching, loci/resolution, and report consistency before anyone can give you a defensible turnaround time or cost.

This guide is written for research-use-only cohort and donor research screening projects. It focuses on what to send for a quote, how to structure batch manifests, and what to clarify in a feasibility call—without making clinical, diagnostic, or donor eligibility claims.

Key Takeaway: The fastest way to de-risk a 100+ sample HLA typing project is to lock (1) sample type + logistics, (2) locus panel + resolution, and (3) report format + file structure before the first batch ships.

Quick answer: what information is needed for a high-throughput HLA typing quote?

A high-throughput HLA typing quote is only as accurate as your intake packet. For rough quote estimates, providers typically need:

1. Sample count (e.g., 100, 200, 143) and whether delivery is all-at-once or rolling batches
2. Sample type (whole blood vs extracted genomic DNA; also tissue/cell lines if applicable)
3. Requested HLA loci (class I, class II, or an 11-locus panel)
4. Target typing resolution (e.g., two-field vs four-field, and whether ambiguity reporting is acceptable)
5. Data + reporting needs (file formats, table fields, QC notes, ambiguity handling)
6. Logistics constraints (ship-from country, temperature, scheduling, any required documentation)

For project scoping, CD Genomics outlines accepted sample types (including genomic DNA and whole blood) and describes its HLA typing offering as a research service on its HLA typing service page, where the Research Use Only limitation is also stated.

Quote requirements checklist (and why each one matters)

Interpretation: For high-throughput projects, the "lab work" is only one part of the quote. Your batch structure and report expectations are often the real cost and timeline drivers, especially when you need consistent outputs across multiple shipments.

Planning HLA typing for 100, 200, or 143 samples

The core planning challenge is consistency: consistent sample IDs, consistent batch metadata, consistent loci/resolution, and consistent report structure. If those drift between batches, your downstream comparison work becomes a manual cleanup project.

A cohort workflow that prevents quote churn

Use this workflow as your default intake-to-report path (it's intentionally conservative):

• Accessioning + unique IDs: define a single invariant sample identifier (never reused, never reformatted)
• Batch manifest: one spreadsheet per shipment with standardized columns
• Sample-type decision: whole blood vs extracted DNA (including mixed-cohort rules)
• QC gates: define what will be measured and how "pass/flag" is communicated
• Loci + resolution lock: confirm panel and resolution before batch 1 starts
• Analysis + reporting: pre-define file naming, folder structure, and ambiguity representation

Large HLA typing projects require clear sample tracking, loci selection, and reporting requirements before quotation.

Sample tracking and batch metadata: treat it like a LIMS-light

Even if you don't run a full LIMS, you should behave like you do:

• Sample ID invariance: pick one canonical format (e.g., COHORT01-0001) and never change it in later batches.
• Separate "sample ID" from "subject ID": subject-level identifiers may repeat across timepoints; sample IDs must not.
• Record batch lineage: extraction batch, PCR/library batch, sequencing run ID, and analysis run version.

This isn't bureaucracy. In multiplexed HLA workflows, sample-specific tagging/barcoding is foundational to throughput and correct attribution. Classic high-throughput NGS HLA methods used sample tags (MIDs) to pool many individuals while preserving sample identity, and they explicitly discuss how ambiguities can arise when polymorphisms fall outside sequenced regions, requiring either additional sequencing or orthogonal confirmation depending on the study goal.high-resolution, high-throughput HLA genotyping by next-generation sequencing (2009)

Batch planning table (copy/paste template)

Interpretation: This table is the fastest way to align stakeholders. It forces a decision on whether you're running one coherent cohort (same panel + reporting) or several adjacent mini-projects. If you can't fill the "loci panel" and "resolution" columns confidently, schedule a feasibility call before shipping batch 1.

Batch planning checklist (what to prepare before you ship)

Interpretation: If you complete this checklist, you reduce "back-and-forth quoting" and prevent the most common cohort failure mode: a batch 3 report that can't be merged cleanly with batch 1.

Whole blood vs extracted DNA for cohort HLA typing

Whole blood is a common cohort sample type, but "feasible" depends on how the project handles extraction, QC, and logistics. CD Genomics lists blood among accepted sample categories for HLA typing on its CD Genomics "Human Leukocyte Antigen (HLA) Typing" service page (research use only).

The key decision is not "blood or DNA?"—it's whether you want one standardized upstream workflow or you're comfortable with mixed inputs that may complicate batch QC interpretation.

Planning comparison: whole blood vs extracted DNA

Interpretation: Whole blood is workable for cohort-scale studies, but it increases the importance of site metadata (collection tube type, storage time, shipping window). If you need tight batch comparability, extracted DNA prepared under a single SOP can reduce variability—at the cost of moving work upstream.

What to include in a feasibility note for whole blood cohorts

Keep it short, but specific:

• Collection tube type(s) and whether multiple sites use different consumables
• Expected time from draw to shipment
• Expected shipping conditions and any weekend holds
• Whether extraction should be performed by the provider or centrally by the study

For general packaging and submission logistics, link readers to the CD Genomics LongSeq sample submission guideline (and align on the project-specific exceptions on the feasibility call).

Choosing loci and resolution for cohort studies

For cohorts, "what do you want typed?" needs to be decided in a way your downstream analysis can actually use. The two practical levers are:

1. Which loci (class I only vs class I + class II; core loci vs expanded panels)
2. What resolution (what level of allele specificity is required and what ambiguity is acceptable)

Class I and class II: what "coverage" usually means

At a minimum, many cohort projects focus on HLA-A, HLA-B, HLA-C (class I) plus one or more class II loci such as HLA-DRB1, HLA-DQB1, HLA-DPB1. Expanded panels often add DQA1, DPA1, and DRB3/4/5 to capture class II diversity more completely.

Peer-reviewed cohort work explicitly describes 11-locus typing sets such as: HLA-A, -B, -C, -DPA1, -DPB1, -DQA1, -DQB1, -DRB1, -DRB3, -DRB4, and -DRB5.next-generation sequencing of 11 HLA loci in a dengue vaccine cohort (2020)

Two-field vs four-field resolution: what it means (and why it changes quoting)

HLA allele names follow the IMGT/HLA nomenclature system maintained by the IPD-IMGT/HLA database.IPD-IMGT/HLA Database (EBI)

In general:

• Field 1 groups alleles into broad families (historically linked to serologic groups)
• Field 2 distinguishes protein-level differences
• Field 3 distinguishes synonymous coding differences
• Field 4 distinguishes noncoding differences (e.g., introns/UTRs)

A practical explanation of how these fields relate to typical research reporting (and why many associations are captured at two-field resolution) is summarized in a statistical genetics tutorial.tutorial on HLA allele fields and two- vs four-field resolution (2023)

What to clarify before batch 1:

• Are you requesting two-field calls, four-field calls, or "highest supported" calls with transparent ambiguity?
• Do you need full-gene coverage, or is exon-focused typing sufficient for your study question?
• If ambiguity remains, do you want the full ambiguity set reported, or a standardized allele-group representation?

Pro Tip: In large cohorts, it's often better to standardize how ambiguity is represented than to force a single "best" allele call. Ambiguity handling that is consistent across batches is easier to analyze downstream.

Data delivery and report management for large projects

In a cohort context, delivery isn't "a PDF." It's a data package that needs to merge across batches and survive downstream filtering and statistics.

What a cohort-ready deliverable package usually includes

While exact outputs vary by provider and scope, you should expect to align on:

• A master result table (one row per sample, stable columns)
• Locus-level fields (e.g., allele 1 / allele 2 per locus)
• A QC and notes field (flags for low confidence, low coverage, sample issues)
• An ambiguity field or allele-group field when applicable
• Batch identifiers and analysis/software/database version notes

When reporting HLA alleles, be explicit about the string format (two-field vs four-field; whether the "HLA-" prefix is included; whether allele separators are standardized). Use one standard across all batches.

File organization that prevents downstream chaos

A simple convention that works for 100–200+ samples:

• One top-level folder per project
• One subfolder per batch shipment
• One consolidated "merged" folder that is regenerated after each batch completes
• A changelog that records what changed between batch 1 and batch 2 (panel, report schema, software version, etc.)

If you need to justify long-read approaches to stakeholders, you can also link to a technical background resource such as CD Genomics' resource on haplotype phasing to explain why long-range information helps with allele separation in polymorphic regions.

Price, lead time, and feasibility discussions

For high-throughput HLA typing, price and turnaround time can't be responsibly estimated in an article. They depend on project-specific variables that materially change workload and scheduling.

CD Genomics notes that pricing and turnaround time are quote-based and encourages direct discussion on the HLA typing service page.

Cost and lead-time factors checklist (no prices)

Interpretation: Most "surprise delays" come from scope creep in reporting and resolution expectations, not from the sequencing instrument. If you want a predictable timeline, document these factors up front.

Research-use-only limitations

This service and this article are for research use only. CD Genomics explicitly states its HLA typing offering is not for diagnostic procedures or health assessment.

For donor-related work, use terms like donor research screening or research cohort screening. This guide does not provide clinical donor eligibility, transplant matching, patient-care, or regulatory claims.

FAQ

Can CD Genomics provide HLA typing for 100 or 200 samples?

Yes—CD Genomics positions its HLA typing as a scalable research service, and cohort-scale projects are feasible when sample intake, locus panel, and reporting requirements are defined up front. The practical bottleneck for 100–200 samples is rarely "can it be run," but rather whether the project has a consistent batch plan: invariant sample IDs, standardized manifests, and a locked loci/resolution definition before batch 1. For the most accurate quote, prepare a batch table (shipments, sample types, loci, resolution) and confirm deliverables and QC notes for each batch on a feasibility call.

Can whole blood be used for HLA typing?

Often, yes—whole blood is a common research cohort sample type, and CD Genomics lists blood among accepted sample categories for its HLA typing service (research use only). The feasibility questions are operational: collection tubes and site SOPs, time from collection to shipment, shipping conditions, and whether DNA extraction is performed centrally or by the provider. In large cohorts, whole-blood variability can present as batch effects unless you record consistent metadata and keep batch logistics stable across sites.

What information is needed for a rough quote?

A rough quote typically requires (1) sample count and batch schedule, (2) sample type (whole blood vs extracted genomic DNA), (3) requested HLA loci (class I only vs class I+II; core vs expanded panels), (4) target typing resolution (two-field vs four-field, plus ambiguity expectations), and (5) what the deliverable package must include (result tables only vs QC notes, ambiguity fields, and additional files). Price and lead time must be quoted by CD Genomics based on the project's exact scope and logistics, so your goal should be to send a complete intake packet rather than seeking an in-article estimate.

Can I request 11-locus 4-field HLA typing for a cohort?

You can request an expanded multi-locus panel (often referred to as "11-locus" in cohort literature) and a high-resolution reporting target, but you should confirm the exact locus list and what "resolution" means for your study before shipping. Peer-reviewed cohort studies describe 11-locus sets including HLA-A, -B, -C, -DPA1, -DPB1, -DQA1, -DQB1, -DRB1, -DRB3, -DRB4, and -DRB5. Separately, IMGT/HLA nomenclature uses colon-delimited fields where higher-field calls represent more sequence detail. In practice, achievable resolution and ambiguity handling depend on panel design and data support, so align on how ambiguous calls are reported across all batches.

How are results delivered for large sample batches?

For 100+ samples, results are most useful when delivered as a standardized data package rather than ad hoc files. Align in advance on a master results table (one row per sample, fixed columns), allele string format (two-field vs four-field), QC flags, and how ambiguities are represented. Also define a folder and file naming convention so that batch 2 can be merged with batch 1 without manual relabeling. When these decisions are made early, the provider can generate consistent batch reports and you can run downstream statistics without reformatting.

Can this be used for donor matching?

No. This guide is written for research-use-only workflows and uses donor language only in the sense of donor research screening or research cohort screening. It does not provide clinical donor eligibility guidance, transplant matching recommendations, diagnostic interpretation, or patient-care claims. If your project touches any clinical decision-making, discuss the appropriate regulatory and clinical pathways with qualified clinical and regulatory professionals and use services that are explicitly validated and authorized for that purpose.

Next steps: request a high-throughput HLA typing quote

Send your sample count, sample type, requested HLA loci, desired resolution, extraction needs, reporting requirements, and timeline goals to request a high-throughput HLA typing quote.

If you want to speed up the feasibility discussion, include:

• your batch planning table
• your preferred report schema (or a sample table header)
• any logistics constraints (ship-from country, time windows)

Author

Dr. Yang H. — Senior Scientist, CD Genomics

Dr. Yang's work focuses on long-read sequencing workflows, HLA typing, and cohort-scale project planning with an emphasis on QC transparency and reproducibility. Connect on LinkedIn: Dr. Yang H.