This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3
Patient Administration Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw JSON (canonical form + also see JSON Format Specification)
Definition for Code System EndpointPayloadType
{ "resourceType" : "CodeSystem", "id" : "endpoint-payload-type", "meta" : { "lastUpdated" : "2019-11-01T09:29:23.356+11:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablecodesystem"] }, "text" : { "status" : "generated", "div" : "<div>!-- Snipped for Brevity --></div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode" : "pa" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "draft" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 1 }], "url" : "http://terminology.hl7.org/CodeSystem/endpoint-payload-type", "identifier" : [{ "system" : "urn:ietf:rfc:3986", "value" : "urn:oid:2.16.840.1.113883.4.642.4.1139" }], "version" : "4.0.1", "name" : "EndpointPayloadType", "title" : "Endpoint Payload Type", "status" : "draft", "experimental" : false, "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, "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" }] }
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.