{
  "$result_object_key":  {
    "id":  "4894"
  }
}

{
  "$result_object_key":  {
    "id":  "The unique identifier of the allergy sensitivity"
  }
}

​
Parameters

​
Action
Parameters
​
Category
string
required

This field maps to the destination API category field.

​
Category Type
string

This field maps to the destination API category_type field.

​
Custom Name
string

This field maps to the destination API custom_name field.

​
Custom Reaction
string

This field maps to the destination API custom_reaction field.

​
Name
string
required

This field maps to the destination API name field.

​
Onset Date
values.v1.Date

This field maps to the destination API onset_date field.

​
Reaction
string
required

This field maps to the destination API reaction field.

​
Reaction Type
string

This field maps to the destination API reaction_type field.

​
Severity
string

This field maps to the destination API severity field.

​
Status
string

This field maps to the destination API status field.

​
Patient ID
string

This field maps to the destination API user_id field.

​
Drug Allergen ID
string

This field maps to the destination API drug_allergen_id field.

{
  "$result_object_key":  {
    "id":  "4894"
  }
}

{
  "$result_object_key":  {
    "id":  "The unique identifier of the allergy sensitivity"
  }
}

​
Result Object Field Details

You can use the result of the action’s data as inputs to downstream workflow actions.

Each fetch action requires a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow.

Here we demonstrate how to refer to this data using the prefix $result_object_key.

​
AllergySensitivity
Fetch Action Response Object
​
id
string
required

The unique identifier of the allergy sensitivity

CEL
$result_object_key.id
Example
"4894"