FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

4.4.1.643 ValueSet http://hl7.org/fhir/ValueSet/genomicstudy-dataformat

Clinical Genomics icon Work Group Maturity Level: 1Trial Use Use Context: Country: World, Not yet ready for Production use
Official URL: http://hl7.org/fhir/ValueSet/genomicstudy-dataformat Version: 6.0.0-cibuild
draft as of 2022-08-17 Computable Name: GenomicStudyDataFormat
Flags: Experimental OID: 2.16.840.1.113883.4.642.3.3084

This value set is used in the following places:

The data formats relevant to Genomic Study analysis.


 

This expansion generated 24 Jul 2024


Expansion based on codesystem Genomic Study Data Format v6.0.0-cibuild (CodeSystem)

This value set contains 40 concepts.

CodeSystemDisplay
  bamhttp://hl7.org/fhir/genomicstudy-dataformatBAM
  bedhttp://hl7.org/fhir/genomicstudy-dataformatBED
  bedpehttp://hl7.org/fhir/genomicstudy-dataformatBEDPE
  bedgraphhttp://hl7.org/fhir/genomicstudy-dataformatBedGraph
  bigbedhttp://hl7.org/fhir/genomicstudy-dataformatbigBed
  bigWighttp://hl7.org/fhir/genomicstudy-dataformatbigWig
  birdsuite-fileshttp://hl7.org/fhir/genomicstudy-dataformatBirdsuite-Files
  broadpeakhttp://hl7.org/fhir/genomicstudy-dataformatbroadPeak
  cbshttp://hl7.org/fhir/genomicstudy-dataformatCBS
  chemical-reactivity-probing-profileshttp://hl7.org/fhir/genomicstudy-dataformatChemical-Reactivity-Probing-Profiles
  chrom-sizeshttp://hl7.org/fhir/genomicstudy-dataformatchrom-sizes
  cnhttp://hl7.org/fhir/genomicstudy-dataformatCN
  custom-file-formatshttp://hl7.org/fhir/genomicstudy-dataformatCustom-File-Formats
  cytobandhttp://hl7.org/fhir/genomicstudy-dataformatCytoband
  fastahttp://hl7.org/fhir/genomicstudy-dataformatFASTA
  gcthttp://hl7.org/fhir/genomicstudy-dataformatGCT
  cramhttp://hl7.org/fhir/genomicstudy-dataformatCRAM
  genepredhttp://hl7.org/fhir/genomicstudy-dataformatgenePred
  gff-gtfhttp://hl7.org/fhir/genomicstudy-dataformatGFF/GTF
  gistichttp://hl7.org/fhir/genomicstudy-dataformatGISTIC
  gobyhttp://hl7.org/fhir/genomicstudy-dataformatGoby
  gwashttp://hl7.org/fhir/genomicstudy-dataformatGWAS
  igvhttp://hl7.org/fhir/genomicstudy-dataformatIGV
  lohhttp://hl7.org/fhir/genomicstudy-dataformatLOH
  maf-multiple-alignment-formathttp://hl7.org/fhir/genomicstudy-dataformatMAF-Multiple Alignment Format
  maf-mutation-annotation-formathttp://hl7.org/fhir/genomicstudy-dataformatMAF-Mutation-Annotation-Format
  merged-bam-filehttp://hl7.org/fhir/genomicstudy-dataformatMerged BAM File
  muthttp://hl7.org/fhir/genomicstudy-dataformatMUT
  narrowpeakhttp://hl7.org/fhir/genomicstudy-dataformatnarrowPeak
  pslhttp://hl7.org/fhir/genomicstudy-dataformatPSL
  reshttp://hl7.org/fhir/genomicstudy-dataformatRES
  rna-secondary-structure-formatshttp://hl7.org/fhir/genomicstudy-dataformatRNA-Secondary-Structure-Formats
  samhttp://hl7.org/fhir/genomicstudy-dataformatSAM
  sample-info-attributes-filehttp://hl7.org/fhir/genomicstudy-dataformatSample-Info-Attributes-file
  seghttp://hl7.org/fhir/genomicstudy-dataformatSEG
  tdfhttp://hl7.org/fhir/genomicstudy-dataformatTDF
  track-linehttp://hl7.org/fhir/genomicstudy-dataformatTrack Line
  type-linehttp://hl7.org/fhir/genomicstudy-dataformatType Line
  vcfhttp://hl7.org/fhir/genomicstudy-dataformatVCF
  wighttp://hl7.org/fhir/genomicstudy-dataformatWIG

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code