HL7 Terminology (THO)
6.1.0 - Publication
This page is part of the HL7 Terminology (v6.1.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions
Active as of 2024-11-17 | Maturity Level: 1 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="endpoint-payload-type"/>
<meta>
<lastUpdated value="2024-04-24T00:00:00+00:00"/>
<profile
value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
</meta>
<text>
<status value="generated"/>
<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><a name="endpoint-payload-type-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Last updated: 2024-04-24 00:00:00+0000</p><p style="margin-bottom: 0px">Profile: <a href="http://hl7.org/fhir/R5/shareablecodesystem.html">Shareable CodeSystem</a></p></div><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/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>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="pa"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="1"/>
</extension>
<url value="http://terminology.hl7.org/CodeSystem/endpoint-payload-type"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.1.1139"/>
</identifier>
<version value="2.0.1"/>
<name value="EndpointPayloadType"/>
<title value="Endpoint Payload Type"/>
<status value="active"/>
<experimental value="false"/>
<date value="2024-11-17T12:23:22-07:00"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description
value="This is an example value set defined by the FHIR project, that could be used to represent possible payload document types."/>
<copyright
value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license"/>
<caseSensitive value="true"/>
<content value="complete"/>
<concept>
<code value="any"/>
<display value="Any"/>
<definition
value="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"/>
</concept>
<concept>
<code value="none"/>
<display value="None"/>
<definition
value="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"/>
</concept>
</CodeSystem>