AU Provider Directory Implementation Guide
2.1.0-ci-build - Draft Australia flag

AU Provider Directory Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 2.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-pd/ and changes regularly. See the Directory of published versions

ValueSet: Australian Service Interfaces

Official URL: http://hl7.org.au/fhir/pd/ValueSet/service-interfaces Version: 2.1.0-ci-build
Standards status: Draft Maturity Level: 0 Computable Name: AustralianServiceInterfaces

Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.

The Australian Service Interfaces value set enumerates well known service interfaces that can be used for specifying a connection type.

References

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 20 concepts

SystemCodeDisplay (en)DefinitionstatusJSONXML
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  dicom-wado-rsDICOM WADO-RSDICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  dicom-qido-rsDICOM QIDO-RSDICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  dicom-stow-rsDICOM STOW-RSDICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  dicom-wado-uriDICOM WADO-URIDICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  hl7-fhir-restHL7 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.
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  hl7-fhir-msgHL7 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.
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  hl7v2-mllpHL7 v2 MLLPHL7v2 messages over an LLP TCP connection
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  secure-emailSecure emailEmail delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  direct-projectDirect ProjectDirect Project information - http://wiki.directproject.org/
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  cds-hooks-serviceCDS Hooks ServiceA 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
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  ihe-xcpdIHE XCPDIHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discoverydeprecated
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  ihe-xcaIHE XCAIHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Accessdeprecated
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  ihe-xdrIHE XDRIHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchangedeprecated
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  ihe-xdsIHE XDSIHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharingdeprecated
http://terminology.hl7.org/CodeSystem/endpoint-connection-type  ihe-iidIHE IIDIHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Displaydeprecated
http://hl7.org.au/fhir/CodeSystem/smd-interfaces  http://ns.electronichealth.net.au/smd/intf/SealedImmediateMessageDelivery/TLS/2010Sealed Immediate Message DeliveryService interface for secure message delivery (immediate mode)
http://hl7.org.au/fhir/CodeSystem/smd-interfaces  http://ns.electronichealth.net.au/smd/intf/SealedMessageDelivery/TLS/2010Sealed Message DeliveryService interface for secure message delivery (deferred mode)
http://hl7.org.au/fhir/CodeSystem/smd-interfaces  http://ns.electronichealth.net.au/smd/intf/SealedMessageRetrieval/TLS/2010Sealed Message RetrievalService interface for secure message delivery (retrieval in deferred mode)
http://hl7.org.au/fhir/CodeSystem/smd-interfaces  http://ns.electronichealth.net.au/smd/intf/TransportResponseDelivery/TLS/2010Transport Response DeliveryService interface for secure message delivery (deliver acknowledgement)
http://hl7.org.au/fhir/CodeSystem/smd-interfaces  http://ns.electronichealth.net.au/smd/intf/TransportResponseRetrieval/TLS/2010Transport Response RetrievalService interface for secure message delivery (retrieve acknowledgement)

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