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/strand-orientation | Version: 1.0.0-ballot1 | |||
Standards status: Informative | Computable Name: StrandOrientationVS |
Strand orientation terms of various molecular sequences.
References
http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/strand-orientation
Expansion performed internally based on codesystem Strand Orientation v1.0.0-ballot1 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
forward | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/strand-orientation | Forward strand | 5' to 3' for nucleotides or N-to-C for amino acids; also known as positive/plus strand. Single stranded sequences are conventionally represented in forward direction. |
reverse | http://hl7.org/fhir/uv/molecular-definition-data-types/CodeSystem/strand-orientation | Reverse strand | 3' to 5' orientation; also known as negative/minus strand. Applicable only to double stranded sequences. |
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 |