This page is part of the FHIR Specification (v3.0.2: STU 3). 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
Vocabulary Work Group | Maturity Level: N/A | Ballot Status: Informative |
Definition for Code System Endpoint Payload Type
{ "resourceType": "CodeSystem", "id": "endpoint-payload-type", "meta": { "lastUpdated": "2019-10-24T11:53:00+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-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.2", "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" } ] }
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.