bio-clinical-databases-hla-typing

Identify HLA-A/B/C four-field alleles from WES/WGS or RNA-seq using OptiType, HLA-HD, arcasHLA outputs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stellaromics/fast-bioinfo --skill bio-clinical-databases-hla-typing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bio-clinical-databases-hla-typing
Source: https://github.com/stellaromics/fast-bioinfo/tree/main/.claude/agents/spatial-analysis/skills/bio-clinical-databases-hla-typing
Command: npx skills add https://github.com/stellaromics/fast-bioinfo --skill bio-clinical-databases-hla-typing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HLA typing from NGS data is essential for transplant matching and pharmacogenomic screening, but many clinicians and researchers lack integrated workflows to call and interpret HLA alleles across data types.

Core Features & Use Cases

  • End-to-end HLA typing: call HLA-A, HLA-B, HLA-C (and optionally Class II loci with other tools) from WES/WGS or RNA-seq data.
  • Tool-agnostic parsing: parse OptiType, HLA-HD, or arcasHLA outputs into standardized four-field alleles.
  • Use Case: A transplant team can quickly generate a report showing patient HLA alleles for matching and drug-response screening.

Quick Start

Run OptiType on a WES or RNA-seq dataset to obtain four-field HLA-A, B, and C calls.

Frequently Asked Questions about bio-clinical-databases-hla-typing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform HLA typing from NGS data for transplant matching?

HLA typing from NGS data uses tools like OptiType, HLA-HD, or arcasHLA to call HLA-A, HLA-B, and HLA-C alleles from WES, WGS, or RNA-seq datasets. The parsed results provide standardized four-field alleles to support clinical transplant matching and pharmacogenomic screening.

What is the best way to parse OptiType and arcasHLA outputs into clinical reporting formats?

Parsing OptiType and arcasHLA outputs involves standardizing raw allele calls into four-field HLA alleles. This tool-agnostic parsing workflow extracts HLA-A, HLA-B, and HLA-C results to generate standardized clinical reports for patient matching and drug-response screening.

Can I use RNA-seq data for HLA typing with OptiType?

HLA typing with OptiType fully supports RNA-seq data alongside WES and WGS datasets. You can run the workflow directly on RNA-seq reads to obtain accurate four-field HLA-A, HLA-B, and HLA-C calls for clinical reporting.

Does this HLA typing workflow support Class II loci calling?

HLA typing workflows primarily call Class I loci (HLA-A, HLA-B, HLA-C) using OptiType. Calling Class II loci requires applying other specific tools like HLA-HD or arcasHLA to your WES, WGS, or RNA-seq data for broader immunogenomic profiling.

Why do I need four-field HLA alleles for pharmacogenomic screening?

Four-field HLA alleles provide the high-resolution specificity required for accurate pharmacogenomic screening and transplant matching. Standardizing NGS calls to this resolution ensures precise identification of patient HLA types, minimizing graft rejection risks and adverse drug responses.