Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions

: Endpoint Payload Type - JSON Representation

Page standards status: Informative Maturity Level: 1

Raw json | Download

{
  "resourceType" : "CodeSystem",
  "id" : "endpoint-payload-type",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: CodeSystem endpoint-payload-type</b></p><a name=\"endpoint-payload-type\"> </a><a name=\"hcendpoint-payload-type\"> </a><p>This case-sensitive code system <code>http://hl7.org/fhir/endpoint-payload-type</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">any<a name=\"endpoint-payload-type-any\"> </a></td><td>Any</td><td>Any payload type can be used with this endpoint, it is either a payload agnostic infrastructure (such as a storage repository), or some other type of endpoint where payload considerations are internally handled, and not available</td></tr><tr><td style=\"white-space:nowrap\">none<a name=\"endpoint-payload-type-none\"> </a></td><td>None</td><td>This endpoint does not require any content to be sent, simply connecting to the endpoint is enough notification. This can be used as a 'ping' to wakeup a service to retrieve content, which could be to ensure security considerations are correctly handled</td></tr></table></div>"
  },
  "extension" : [
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status",
      "valueString" : "Informative"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger" : 1
    },
    {
      "extension" : [
        {
          "url" : "packageId",
          "valueId" : "hl7.fhir.uv.xver-r3.r4"
        },
        {
          "url" : "version",
          "valueString" : "0.1.0"
        },
        {
          "url" : "uri",
          "valueUri" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"
        }
      ],
      "url" : "http://hl7.org/fhir/StructureDefinition/package-source"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode" : "pa"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode" : "informative",
      "_valueCode" : {
        "extension" : [
          {
            "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"
          }
        ]
      }
    }
  ],
  "url" : "http://hl7.org/fhir/endpoint-payload-type",
  "version" : "3.0.2",
  "name" : "Endpoint Payload Type",
  "status" : "draft",
  "experimental" : true,
  "date" : "2026-03-20T11:58:40+11:00",
  "publisher" : "Patient Administration",
  "contact" : [
    {
      "name" : "Patient Administration",
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://www.hl7.org/Special/committees/pafm"
        }
      ]
    }
  ],
  "description" : "This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "copyright" : "Some content from IHE® Copyright © 2015 IHE International, Inc.    This content is from the IHE Technical Frameworks and Supplements,    available for free download and use at http://www.ihe.net/Technical_Frameworks/",
  "caseSensitive" : true,
  "valueSet" : "http://hl7.org/fhir/ValueSet/endpoint-payload-type|4.0.1",
  "content" : "complete",
  "concept" : [
    {
      "code" : "any",
      "display" : "Any",
      "definition" : "Any payload type can be used with this endpoint, it is either a payload agnostic infrastructure (such as a storage repository), or some other type of endpoint where payload considerations are internally handled, and not available"
    },
    {
      "code" : "none",
      "display" : "None",
      "definition" : "This endpoint does not require any content to be sent, simply connecting to the endpoint is enough notification. This can be used as a 'ping' to wakeup a service to retrieve content, which could be to ensure security considerations are correctly handled"
    }
  ]
}