HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: Endpoint Payload Type - TTL Representation

Draft as of 2023-07-17 Maturity Level: 1

Raw ttl | Download


@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

 a fhir:CodeSystem ;
  fhir:nodeRole fhir:treeRoot ;
  fhir:id [ fhir:v "endpoint-payload-type"] ; # 
  fhir:meta [
fhir:lastUpdated [ fhir:v "2020-04-09T21:10:28.568+00:00"^^xsd:dateTime ] ;
    ( fhir:profile [
fhir:v "http://hl7.org/fhir/StructureDefinition/shareablecodesystem"^^xsd:anyURI ;
fhir:link <http://hl7.org/fhir/StructureDefinition/shareablecodesystem>     ] )
  ] ; # 
  fhir:text [
fhir:status [ fhir:v "generated" ] ;
fhir:div "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>This 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>"
  ] ; # 
  fhir:extension ( [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"^^xsd:anyURI ] ;
fhir:value [ fhir:v "pa" ]
  ] [
fhir:url [ fhir:v "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"^^xsd:anyURI ] ;
fhir:value [ fhir:v "1"^^xsd:integer ]
  ] ) ; # 
  fhir:url [ fhir:v "http://terminology.hl7.org/CodeSystem/endpoint-payload-type"^^xsd:anyURI] ; # 
  fhir:identifier ( [
fhir:system [ fhir:v "urn:ietf:rfc:3986"^^xsd:anyURI ] ;
fhir:value [ fhir:v "urn:oid:2.16.840.1.113883.4.642.1.1139" ]
  ] ) ; # 
  fhir:version [ fhir:v "1.0.0"] ; # 
  fhir:name [ fhir:v "EndpointPayloadType"] ; # 
  fhir:title [ fhir:v "Endpoint Payload Type"] ; # 
  fhir:status [ fhir:v "draft"] ; # 
  fhir:experimental [ fhir:v "false"^^xsd:boolean] ; # 
  fhir:date [ fhir:v "2023-07-17T22:16:15-06:00"^^xsd:dateTime] ; # 
  fhir:publisher [ fhir:v "HL7 Patient Administration"] ; # 
  fhir:contact ( [
    ( fhir:telecom [
fhir:system [ fhir:v "url" ] ;
fhir:value [ fhir:v "http://hl7.org/fhir" ]     ] )
  ] ) ; # 
  fhir:description [ fhir:v "This is an example value set defined by the FHIR project, that could be used to represent possible payload document types."] ; # 
  fhir:caseSensitive [ fhir:v "true"^^xsd:boolean] ; # 
  fhir:content [ fhir:v "complete"] ; # 
  fhir:concept ( [
fhir:code [ fhir:v "any" ] ;
fhir:display [ fhir:v "Any" ] ;
fhir:definition [ fhir:v "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" ]
  ] [
fhir:code [ fhir:v "none" ] ;
fhir:display [ fhir:v "None" ] ;
fhir:definition [ fhir:v "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" ]
  ] ) . #