FHIR Specification (v0.0.82: DSTU CI-Build
1). The current version which supercedes this version

This is 5.0.0 . For a full list the Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Extension-geneticsgenomicreferencesequenceid.xml

Example ValueSet/variable-role (JSON)

Responsible Owner: Terminology Infrastructure Work Group Standards Status : Informative

Raw XML JSON ( canonical form + also see JSON Format Specification )

GenomicRefSeqID Raw XML Definition for Value SetEvidence Variable Role

The genomic reference sequence identifier is included, to support testing using alternative reference sequences. The genomic reference sequence identifier is included, to support testing using alternative reference sequences. May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #. Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list). The genomic reference sequence identifier is included, to support testing using alternative reference sequences. </StructureDefinition> 
{
  "resourceType" : "ValueSet",
  "id" : "variable-role",
  "meta" : {
    "lastUpdated" : "2025-12-17T09:50:17.012+00:00"
  },
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet variable-role</b></p><a name=\"variable-role\"> </a><a name=\"hcvariable-role\"> </a><ul><li>Include all codes defined in <a href=\"codesystem-variable-role.html\"><code>http://hl7.org/fhir/variable-role</code></a><span title=\"Version is not explicitly stated, which means it is fixed to the version provided in this specification\"> version &#x1F4E6;6.0.0-ballot3</span></li></ul></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "cds"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "normative"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 1
  }],
  "url" : "http://hl7.org/fhir/ValueSet/variable-role",
  "identifier" : [{
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:oid:2.16.840.1.113883.4.642.3.3048"
  }],
  "version" : "6.0.0-ballot3",
  "name" : "EvidenceVariableRole",
  "title" : "Evidence Variable Role",
  "status" : "active",
  "experimental" : false,
  "date" : "2020-12-28T16:55:11+11:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "The role that the variable plays.",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
      "code" : "001",
      "display" : "World"
    }]
  }],
  "immutable" : true,
  "compose" : {
    "include" : [{
      "system" : "http://hl7.org/fhir/variable-role"
    }]
  }
}

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.