This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon ValueSet http://hl7.org/fhir/ValueSet/endpoint-payload-type

Patient Administration icon Work Group Maturity Level: 1Draft Use Context: Country: World, Not Intended for Production use
Official URL: http://hl7.org/fhir/ValueSet/endpoint-payload-type Version: 6.0.0-cibuild
draft as of 2024-05-14 Computable Name: EndpointPayloadType
Flags: Experimental OID: 2.16.840.1.113883.4.642.3.496

This value set is used in the following places:

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

This value set includes codes based on the following rules:


This expansion generated 14 May 2024

This value set contains 16 concepts.

  any iconhttp://terminology.hl7.org/CodeSystem/endpoint-payload-typeAny

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 iconhttp://terminology.hl7.org/CodeSystem/endpoint-payload-typeNone

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

  urn:hl7-org:sdwg:ccda-structuredBody:1.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-structuredBody:1.1

C-CDA 1.1 constraints using a structured body

  urn:hl7-org:sdwg:ccda-nonXMLBody:1.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-nonXMLBody:1.1

C-CDA 1.1 constraints using a non structured body

  urn:hl7-org:sdwg:ccda-structuredBody:2.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-structuredBody:2.1

C-CDA 2.1 constraints using a structured body

  urn:hl7-org:sdwg:ccda-nonXMLBody:2.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-nonXMLBody:2.1

C-CDA 2.1 constraints using a non structured body

  urn:hl7-org:sdwg:pacp-structuredBody:1.0 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-structuredBody:1.0

PACP 1.0 constraints using a structured body

  urn:hl7-org:sdwg:pacp-nonXMLBody:1.0 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-nonXMLBody:1.0

PACP 1.0 constraints using a non structured body

  urn:hl7-org:sdwg:pacp-structuredBody:1.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-structuredBody:1.1

PACP 1.1 constraints using a structured body

  urn:hl7-org:sdwg:pacp-nonXMLBody:1.1 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-nonXMLBody:1.1

PACP 1.1 constraints using a non structured body

  urn:hl7-org:sdwg:pacp-structuredBody:1.2 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-structuredBody:1.2

PACP 1.2 constraints using a structured body

  urn:hl7-org:sdwg:pacp-nonXMLBody:1.2 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-nonXMLBody:1.2

PACP 1.2 constraints using a non structured body

  urn:hl7-org:sdwg:pacp-structuredBody:1.3 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-structuredBody:1.3

PACP 1.3 constraints using a structured body

  urn:hl7-org:sdwg:pacp-nonXMLBody:1.3 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodespacp-nonXMLBody:1.3

PACP 1.3 constraints using a non structured body

  urn:hl7-org:sdwg:ccda-structuredBody:2.2 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-structuredBody:2.2

C-CDA 2.2 constraints using a structured body

  urn:hl7-org:sdwg:ccda-nonXMLBody:2.2 iconhttp://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodesccda-nonXMLBody:2.2

C-CDA 2.2 constraints using a non structured body


See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code