FHIR IG analytics

Resources that use this resource

No resources found

Resources that this resource uses

Narrative

Note: links and images are rebased to the (stated) source

Source1

{
  "resourceType": "ValueSet",
  "id": "R2-v2-0299-for-R4B",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "extension": [
        {
          "url": "packageId",
          "valueId": "hl7.fhir.uv.xver-r2.r4b"
        },
        {
          "url": "version",
          "valueString": "0.1.0"
        },
        {
          "url": "uri",
          "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4b"
        }
      ],
      "url": "http://hl7.org/fhir/StructureDefinition/package-source"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4b"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4b"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ValueSet/R2-v2-0299-for-R4B",
  "version": "0.1.0",
  "name": "R2V20299ForR4B",
  "title": "Cross-version ValueSet DSTU2.v2 Encoding for use in FHIR R4B",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T21:02:03.8104715+00:00",
  "publisher": "FHIR Infrastructure",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This cross-version ValueSet represents content from `http://hl7.org/fhir/ValueSet/v2-0299|2.8.2` for use in FHIR R4B.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "purpose": "This value set is part of the cross-version definitions generated to enable use of the\r\nvalue set `http://hl7.org/fhir/ValueSet/v2-0299|2.8.2` as defined in FHIR DSTU2\r\nin FHIR R4B.\r\n\r\nThe source value set is bound to the following FHIR DSTU2 elements:\r\n* \r\n\r\nAcross FHIR versions, the value set has been mapped as:\r\n* `http://hl7.org/fhir/ValueSet/v2-0299|2.8.2`\n* `http://hl7.org/fhir/ValueSet/v2-0299|2.8.2`\n* `http://terminology.hl7.org/ValueSet/v2-0299|2.9`\r\n\r\nNote that all concepts are included in this cross-version definition because no concepts have compatible representations\r\n\r\nFollowing are the generation technical comments:\r\nAll concepts in the comparison are listed as identical.\nThe source and target value sets have the same number of active concepts (3).\nAll concepts in the comparison are listed as identical.\nThe source and target value sets have the same number of active concepts (3).\nFHIR ValueSet `http://hl7.org/fhir/ValueSet/v2-0299|2.8.2`, defined in FHIR DSTU2 does not have any mapping to FHIR R4B",
  "compose": {
    "include": [
      {
        "system": "http://hl7.org/fhir/v2/0299",
        "version": "1.0.2",
        "concept": [
          {
            "code": "A",
            "display": "No encoding - data are displayable ASCII characters."
          },
          {
            "code": "Base64",
            "display": "Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521. Four consecutive ASCII characters represent three consecutive octets of binary data. Base64 utilizes a 65-character subset of US-ASCII, consisting of both the upper and"
          },
          {
            "code": "Hex",
            "display": "Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets."
          }
        ]
      }
    ]
  },
  "expansion": {
    "timestamp": "2026-03-17T21:02:03.8104715+00:00",
    "contains": [
      {
        "system": "http://hl7.org/fhir/v2/0299",
        "version": "1.0.2",
        "code": "A",
        "display": "No encoding - data are displayable ASCII characters."
      },
      {
        "system": "http://hl7.org/fhir/v2/0299",
        "version": "1.0.2",
        "code": "Base64",
        "display": "Encoding as defined by MIME (Multipurpose Internet Mail Extensions) standard RFC 1521. Four consecutive ASCII characters represent three consecutive octets of binary data. Base64 utilizes a 65-character subset of US-ASCII, consisting of both the upper and"
      },
      {
        "system": "http://hl7.org/fhir/v2/0299",
        "version": "1.0.2",
        "code": "Hex",
        "display": "Hexadecimal encoding - consecutive pairs of hexadecimal digits represent consecutive single octets."
      }
    ]
  }
}