Molecular Definition Implementation Guide for Molecular Data Types
1.0.0-ballot1 - ci-build
Molecular Definition Implementation Guide for Molecular Data Types
1.0.0-ballot1 - ci-build
Molecular Definition Implementation Guide for Molecular Data Types, published by HL7 International / Clinical Genomics. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/molecular-definition-data-types/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/molecular-definition-data-types/ValueSet/nucleotide-dna-1letter-ambiguous | Version: 1.0.0-ballot1 | |||
| Standards status: Draft | Maturity Level: 0 | Computable Name: NucleotideDNA1LetterAmbiguous | ||
Single-letter ambiguous symbols for DNA residues.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna| Code | Display | Definition |
| G | Guanine | G |
| A | Adenine | A |
| T | Thymine | T |
| C | Cytosine | C |
| R | Purine | G or A |
| Y | Pyrimidine | T or C |
| M | Amino | A or C |
| K | Keto | G or T |
| S | Strong interaction (3 H bonds) | G or C |
| W | Weak interaction (2 H bonds) | A or T |
| H | not-G, H follows G in the alphabet | A or C or T |
| B | not-A, B follows A | G or T or C |
| V | not-T (not-U), V follows U | G or C or A |
| D | not-C, D follows C | G or A or T |
| N | Any nucleotide | G or A or T or C |
Expansion performed internally based on codesystem Nucleotide DNA Symbols v1.0.0-ballot1 (CodeSystem)
This value set contains 15 concepts
| Code | System | Display | Definition |
| G | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Guanine | G |
| A | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Adenine | A |
| T | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Thymine | T |
| C | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Cytosine | C |
| R | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Purine | G or A |
| Y | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Pyrimidine | T or C |
| M | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Amino | A or C |
| K | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Keto | G or T |
| S | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Strong interaction (3 H bonds) | G or C |
| W | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Weak interaction (2 H bonds) | A or T |
| H | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | not-G, H follows G in the alphabet | A or C or T |
| B | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | not-A, B follows A | G or T or C |
| V | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | not-T (not-U), V follows U | G or C or A |
| D | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | not-C, D follows C | G or A or T |
| N | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/nucleotide-dna | Any nucleotide | G or A or T or C |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The 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 |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |