Endpoint Payload Type - HL7 Terminology (THO) v6.5.0

HL7 Terminology (THO)
6.5.0 - Continuous Process Integration (ci build) International flag

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.5.0 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

CodeSystem: Endpoint Payload Type

Official URL: http://terminology.hl7.org/CodeSystem/endpoint-payload-type			Version: 2.0.1
Active as of 2025-07-08	Maturity Level: 1	Responsible: Health Level Seven International	Computable Name: EndpointPayloadType
Other Identifiers: OID:2.16.840.1.113883.4.642.1.1139
Copyright/Legal: 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

This is an example value set defined by the FHIR project, that could be used to represent possible payload document types.

This Code system is referenced in the content logical definition of the following value sets:

EndpointPayloadType

Last updated: 2024-04-24 00:00:00+0000

Profile: Shareable CodeSystem

This case-sensitive code system http://terminology.hl7.org/CodeSystem/endpoint-payload-type defines the following codes:

Code	Display	Definition
any	Any	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
none	None	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