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

HL7 Terminology (THO)
5.5.0 - Publication International flag

This page is part of the HL7 Terminology (v5.5.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

CodeSystem: Endpoint Payload Type

Official URL: http://terminology.hl7.org/CodeSystem/endpoint-payload-type			Version: 2.0.0
Draft as of 2024-03-09	Maturity Level: 1	Responsible: Health Level Seven International	Computable Name: EndpointPayloadType
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn: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:

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

History

Date

Action

Custodian

Author

Comment

2023-11-14

TSMG

Marc Duteau

Add standard copyright and contact to internal content; up-476