Google Cloud Healthcare API

This mapping function submits data to Google's Cloud Healthcare API, a REST API for writing into a Google Cloud datastore. It exists as its own function type because the API's request shape is fixed and predictable, so QIE can fill in almost all of it for you.

This is one variant of the Web Service mapping function; you get it by selecting a Google Cloud Healthcare API connection in Service. The shared Source, Node Path, Target, Apply Condition and Customize Script settings are described in Working with Mapping Functions.

Datastore

Datastore: The target datastore, chosen from the drop-down.

Selecting it configures the rest of the call. You do not normally need to set the other parameters by hand (this is the whole point of the function type) but it is worth knowing what it sets, both to confirm it is right and because you may need to override one:

Parameter	Value
Method	Post
URL	Set automatically from the selected datastore
Type	Application/json
JSON	Prepopulated with the appropriate template, with a default node path that sends the entire output message as the payload

The default JSON template sends the whole output message. When the datastore expects something narrower, edit the template and set the node path to just the part you mean to send. See Node Tags.

Setting up the connection

The datastore drop-down is populated from the connection, so the connection has to exist and authenticate before this function can be configured. Google Cloud Healthcare connections are created on the Web Service Connections page.

Related

• DICOMweb Sender sends DICOM instances to a DICOMweb endpoint, including Google's
• Google Cloud Healthcare API Sender, the destination-node equivalent, for when the submission is the channel's endpoint rather than a step in a mapping
• FHIR covers QIE's FHIR support, which is usually what a Cloud Healthcare datastore is storing