{
  "$result_object_key": {
    "id": "57211",
    "metadata": {
      "priority": "High",
      "referral_department": "Cardiology"
    },
    "patient_id": "67890",
    "referral_reason": "Follow-up care",
    "referring_physician_id": "12345"
  }
}

{
  "$result_object_key": {
    "id": "The unique identifier of the referral",
    "metadata": "Metadata",
    "patient_id": "ID of the referred patient",
    "referral_reason": "The reason the client was referred to the physician",
    "referring_physician_id": "ID of the referring physician"
  }
}

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "id": "57211",
    "metadata": {
      "priority": "High",
      "referral_department": "Cardiology"
    },
    "patient_id": "67890",
    "referral_reason": "Follow-up care",
    "referring_physician_id": "12345"
  }
}

{
  "$result_object_key": {
    "id": "The unique identifier of the referral",
    "metadata": "Metadata",
    "patient_id": "ID of the referred patient",
    "referral_reason": "The reason the client was referred to the physician",
    "referring_physician_id": "ID of the referring physician"
  }
}

​
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.

​
Referral
Fetch Action Response Object
{
  "$result_object_key": {
    "id": "57211",
    "metadata": {
      "priority": "High",
      "referral_department": "Cardiology"
    },
    "patient_id": "67890",
    "referral_reason": "Follow-up care",
    "referring_physician_id": "12345"
  }
}

{
  "$result_object_key": {
    "id": "The unique identifier of the referral",
    "metadata": "Metadata",
    "patient_id": "ID of the referred patient",
    "referral_reason": "The reason the client was referred to the physician",
    "referring_physician_id": "ID of the referring physician"
  }
}

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "id": "57211",
    "metadata": {
      "priority": "High",
      "referral_department": "Cardiology"
    },
    "patient_id": "67890",
    "referral_reason": "Follow-up care",
    "referring_physician_id": "12345"
  }
}

{
  "$result_object_key": {
    "id": "The unique identifier of the referral",
    "metadata": "Metadata",
    "patient_id": "ID of the referred patient",
    "referral_reason": "The reason the client was referred to the physician",
    "referring_physician_id": "ID of the referring physician"
  }
}

​
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.

​
Referral
Fetch Action Response Object