Decision support

Compare standards by the job they do

Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.

Working set

Choose profiles

1 of 3 selected

htsgetStandard

Add a profile

Decision lens

Compare roles before choosing an implementation.

The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”

Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
Test the boundary
Read what each option leaves unresolved before judging maturity or implementation fit.

Assessment

Review lifecycle coverage and practical fit.

Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.

01 · Lifecycle reach

Where each profile contributes directly

Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.

Readiness-stage coverage for GA4GH htsget
Profile	Plan	Acquire	Harmonize	Exchange	Learn + reuse
htsgetStandard	GA4GH htsget has no direct role recorded in Plan.	GA4GH htsget has no direct role recorded in Acquire.	GA4GH htsget has no direct role recorded in Harmonize.	GA4GH htsget has a direct role in Exchange.	GA4GH htsget has a direct role in Learn + reuse.

Direct role recordedNo direct role recorded

02 · Boundaries

What each option does not cover

These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.

htsget

Stage boundary: No direct role is recorded for Plan, Acquire, Harmonize.
Known limitation: The API does not define source-file semantics, consent, authorization policy, reference aliases, or QC. Servers may transcode data, and bearer tokens or returned ticket URLs require careful handling.

03 · Detailed assessment

Check the fit and source behind the map

Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.

Detailed comparison of GA4GH htsget
Assessment	htsgetGA4GH htsget
Purpose & coverage	Ticket-based retrieval of complete or region-scoped read and variant data in BAM, CRAM, VCF, and BCF formats through GET or POST requests and service metadata. Best fitRemote genomic analysis and visualization that need selected genomic regions or full datasets without copying an entire source object first.
Readiness stages	ExchangeLearn + reuse
AI-ready contribution	Enables efficient retrieval of genomic slices for analysis, while region selection can create sampling bias and still requires provenance, reference, cohort, and QC controls.
First limitation to test	The API does not define source-file semantics, consent, authorization policy, reference aliases, or QC. Servers may transcode data, and bearer tokens or returned ticket URLs require careful handling.
Maturity	Scaling Current GA4GH Support Ready API with multiple production implementations
Sources & links	htsget retrieval API v1.3.0 (opens in a new tab)Read full profile