Supported Web Service Connection Types

QIE supports a wide range of web service connection types.

Connection Type	Description
DICOMweb	The DICOMweb connection type connects QIE to a DICOMweb server, a PACS, VNA, or archive that supports the DICOM web services. It exposes the standard DICOMweb services as named operations that mapping functions and destination nodes can call: QIDO-RS (query), WADO-RS (retrieve), STOW-RS (store), and UPS-RS (Unified Procedure Step / worklist). See dicomstandard.org/using/dicomweb for more information.
Google Cloud Healthcare API	The Google Cloud Healthcare API connection type is used to establish a connection to and exchange information with Google's Cloud Healthcare API. See cloud.google.com/healthcare for more information on this API.
IHE Web Service Profiles	The IHE Profile connection type allows SOAP based communication with HIE registries and repositories which support the IHE profiles. This profile includes both the XDS.a and XDS.b profiles.
REST (URL Encoded) REST (Content Encoded)	The REST connection type allows QIE to connect to and exchange information with a REST (Representational State Transfer) based web service. REST web services leverage the HTTP GET, POST, PUT and DELETE methods. Content included in REST web services can be transferred using either URL encoding or content encoding.
SOAP Web Service (HTTP)	The SOAP connection type allows QIE to connect to any SOAP (Simple Object Access Protocol) based web service by simply downloading the associated WSDL (Web Service Definition Language) document from the web service endpoint. QIE parses the downloaded WSDL to determine all functions (including parameters and return values) associated with the endpoint. These functions can then be called by QIE mapping functions and destination nodes.
QIE Web Service (Deprecated)	Deprecated. This connection type will be removed in a future QIE release. Use a REST-based connection type instead.