{
  "resourceType": "CodeSystem",
  "id": "endpoint-payload-type",
  "meta": {
    "lastUpdated": "2017-04-18T21:44:43.294+00:00",
    "profile": [
      "http://hl7.org/fhir/StructureDefinition/shareablecodesystem"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>Endpoint Payload Type</h2><div><p>This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.</p></div><p><b>Copyright Statement:</b> 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/\r\n            </p><p>This code system http://hl7.org/fhir/endpoint-payload-type defines the following codes:</p><table class=\"codes\"><tr><td><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td>any\r\n                  <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>none\r\n                  <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
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "pa"
    }
  ],
  "url": "http://hl7.org/fhir/endpoint-payload-type",
  "identifier": {
    "system": "urn:ietf:rfc:3986",
    "value": "urn:oid:2.16.840.1.113883.4.642.1.490"
  },
  "version": "3.0.1",
  "name": "Endpoint Payload Type",
  "status": "draft",
  "experimental": true,
  "publisher": "HL7 Patient Administration",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org/fhir"
        }
      ]
    }
  ],
  "description": "This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.",
  "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",
  "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"
    }
  ]
}