NameFlagsCard.TypeDescription & Constraintsdoco
.. SubstanceNucleicAcid TUDomainResourceNucleic acids are defined by three distinct elements: the base, sugar and linkage. Individual substance/moiety IDs will be created for each of these elements. The nucleotide sequence will be always entered in the 5’-3’ direction

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... sequenceType Σ0..1CodeableConceptThe type of the sequence shall be specified based on a controlled vocabulary
... numberOfSubunits Σ0..1integerThe number of linear sequences of nucleotides linked through phosphodiester bonds shall be described. Subunits would be strands of nucleic acids that are tightly associated typically through Watson-Crick base pairing. NOTE: If not specified in the reference source, the assumption is that there is 1 subunit
... areaOfHybridisation Σ0..1stringThe area of hybridisation shall be described if applicable for double stranded RNA or DNA. The number associated with the subunit followed by the number associated to the residue shall be specified in increasing order. The underscore “” shall be used as separator as follows: “Subunitnumber Residue”
... oligoNucleotideType Σ0..1CodeableConcept(TBC)
... subunit Σ0..*BackboneElementSubunits are listed in order of decreasing length; sequences of the same length will be ordered by molecular weight; subunits that have identical sequences will be repeated multiple times

.... subunit Σ0..1integerIndex of linear sequences of nucleic acids in order of decreasing length. Sequences of the same length will be ordered by molecular weight. Subunits that have identical sequences will be repeated and have sequential subscripts
.... sequence Σ0..1stringActual nucleotide sequence notation from 5' to 3' end using standard single letter codes. In addition to the base sequence, sugar and type of phosphate or non-phosphate linkage should also be captured
.... length Σ0..1integerThe length of the sequence shall be captured
.... sequenceAttachment Σ0..1Attachment(TBC)
.... fivePrime Σ0..1CodeableConceptThe nucleotide present at the 5’ terminal shall be specified based on a controlled vocabulary. Since the sequence is represented from the 5' to the 3' end, the 5’ prime nucleotide is the letter at the first position in the sequence. A separate representation would be redundant
.... threePrime Σ0..1CodeableConceptThe nucleotide present at the 3’ terminal shall be specified based on a controlled vocabulary. Since the sequence is represented from the 5' to the 3' end, the 5’ prime nucleotide is the letter at the last position in the sequence. A separate representation would be redundant
.... linkage Σ0..*BackboneElementThe linkages between sugar residues will also be captured

..... connectivity Σ0..1stringThe entity that links the sugar residues together should also be captured for nearly all naturally occurring nucleic acid the linkage is a phosphate group. For many synthetic oligonucleotides phosphorothioate linkages are often seen. Linkage connectivity is assumed to be 3’-5’. If the linkage is either 3’-3’ or 5’-5’ this should be specified
..... identifier Σ0..1IdentifierEach linkage will be registered as a fragment and have an ID
..... name Σ0..1stringEach linkage will be registered as a fragment and have at least one name. A single name shall be assigned to each linkage
..... residueSite Σ0..1stringResidues shall be captured as described in 5.3.6.8.3
.... sugar Σ0..*BackboneElement5.3.6.8.1 Sugar ID (Mandatory)

..... identifier Σ0..1IdentifierThe Substance ID of the sugar or sugar-like component that make up the nucleotide
..... name Σ0..1stringThe name of the sugar or sugar-like component that make up the nucleotide
..... residueSite Σ0..1stringThe residues that contain a given sugar will be captured. The order of given residues will be captured in the 5‘-3‘direction consistent with the base sequences listed above

doco Documentation for this format