US Public Health Profiles Library
1.0.0-ballot - STU Ballot US

This page is part of the US Public Health Profiles Library (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

ValueSet: US Public Health Supplemental Valueset Example

Official URL: http://hl7.org/fhir/us/ph-library/ValueSet/us-ph-supplemental-valueset-example Version: 1.0.0-ballot
Active as of 2022-06-02 Computable Name: USPublicHealthSupplementalValueSetExample

Usage:Reporting: Supplemental, Clinical Focus: Chlamydia trachomatis infection, Priority: Routine

This valueset is a valueset created for the purposes of demonstrating, by example, the US Public Health Supplemental ValueSet profile.

Define the set of supported endpoint connection types.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 16 concepts

CodeSystemDisplayDefinition
  ihe-xcpdhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XCPDIHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery
  ihe-xcahttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XCAIHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access
  ihe-xdrhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XDRIHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange
  ihe-xdshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XDSIHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing
  ihe-iidhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE IIDIHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display
  dicom-wado-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM WADO-RSDICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
  dicom-qido-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM QIDO-RSDICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
  dicom-stow-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM STOW-RSDICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
  dicom-wado-urihttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM WADO-URIDICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
  hl7-fhir-resthttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 FHIRInteract with the server interface using FHIR's RESTful interface. For details on its version/capabilities you should connect the value in Endpoint.address and retrieve the FHIR CapabilityStatement.
  hl7-fhir-msghttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 FHIR MessagingUse the servers FHIR Messaging interface. Details can be found on the messaging.html page in the FHIR Specification. The FHIR server's base address is specified in the Endpoint.address property.
  hl7v2-mllphttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 v2 MLLPHL7v2 messages over an LLP TCP connection
  secure-emailhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeSecure emailEmail delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content
  direct-projecthttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDirect ProjectDirect Project information - http://wiki.directproject.org/
  hl7-fhir-fileshttp://hl7.org/fhir/us/ph-library/CodeSystem/us-ph-endpoint-connection-type-exampleHL7 FHIR FilesHL7 FHIR Files.
  hl7-cql-fileshttp://hl7.org/fhir/us/ph-library/CodeSystem/us-ph-endpoint-connection-type-exampleHL7 CQL FilesHL7 CQL Files.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The 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
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code