HL7 Terminology (THO)
6.0.2 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Active as of 2024-09-23 | Maturity Level: 1 |
{
"resourceType" : "CodeSystem",
"id" : "endpoint-payload-type",
"meta" : {
"lastUpdated" : "2024-04-24T00:00:00+00:00",
"profile" : [
🔗 "http://hl7.org/fhir/StructureDefinition/shareablecodesystem"
]
},
"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><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>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "pa"
},
{
"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.1.1139"
}
],
"version" : "2.0.1",
"name" : "EndpointPayloadType",
"title" : "Endpoint Payload Type",
"status" : "active",
"experimental" : false,
"date" : "2024-09-23T14:11:21+00:00",
"publisher" : "Health Level Seven International",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org"
},
{
"system" : "email",
"value" : "hq@HL7.org"
}
]
}
],
"description" : "This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.",
"copyright" : "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" : 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"
}
]
}