Electronic Case Reporting (eCR), published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/case-reporting/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/ecr/ValueSet/valueset-us-ph-supplemental-valueset-example | Version: 3.0.0-ballot | |||
Standards status: Informative | Computable Name: USPublicHealthSupplementalValueSetExample | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.46.48.6 | ||||
Usage:Reporting: Supplemental, Priority: Routine |
This valueset is a simplified duplicate of the eRSD Endpoint Connection Type valueset created for the purposes of demonstraing, 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)
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/endpoint-connection-type
version 📦2.1.1http://hl7.org/fhir/us/ecr/CodeSystem/ersd-endpoint-connection-type
version 📦3.0.0-ballot
Expansion performed internally based on:
This value set contains 17 concepts
Code | System | Display | Definition | status |
dicom-wado-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html | |
dicom-qido-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html | |
dicom-stow-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM STOW-RS | DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html | |
dicom-wado-uri | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html | |
hl7-fhir-rest | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | HL7 FHIR | Interact 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-msg | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | HL7 FHIR Messaging | Use 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-mllp | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection | |
secure-email | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | Secure email | Email delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content | |
direct-project | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | Direct Project | Direct Project information - http://wiki.directproject.org/ | |
cds-hooks-service | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | CDS Hooks Service | A CDS Hooks Service connection. The address will be the base URL of the service as described in the CDS specification https://cds-hooks.hl7.org | |
ihe-xcpd | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | IHE XCPD | IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery | deprecated |
ihe-xca | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | IHE XCA | IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access | deprecated |
ihe-xdr | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | IHE XDR | IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange | deprecated |
ihe-xds | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | IHE XDS | IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing | deprecated |
ihe-iid | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | IHE IID | IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display | deprecated |
hl7-fhir-files | http://hl7.org/fhir/us/ecr/CodeSystem/ersd-endpoint-connection-type | HL7 FHIR Files | HL7 FHIR Files. | |
hl7-cql-files | http://hl7.org/fhir/us/ecr/CodeSystem/ersd-endpoint-connection-type | HL7 CQL Files | HL7 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 |