{
  "$result_object_key": [
    {
      "code": "F12.34",
      "date": "2024-03-04T14:00:00Z",
      "description": "Adjustment Disorder, With anxiety",
      "end_date": "2025-01-02T14:00:00Z",
      "note_id": "d020aecd-7005-4ef6-b467-9c715017ec17"
    }
  ]
}

{
  "$result_object_key": [
    {
      "code": "Code for the diagnosis",
      "date": "Date when the diagnosis was made",
      "description": "Description of the diagnosis",
      "end_date": "End date of the diagnosis, if applicable",
      "note_id": "ID of the note associated with this diagnosis"
    }
  ]
}

images/intakeq.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": [
    {
      "code": "F12.34",
      "date": "2024-03-04T14:00:00Z",
      "description": "Adjustment Disorder, With anxiety",
      "end_date": "2025-01-02T14:00:00Z",
      "note_id": "d020aecd-7005-4ef6-b467-9c715017ec17"
    }
  ]
}

{
  "$result_object_key": [
    {
      "code": "Code for the diagnosis",
      "date": "Date when the diagnosis was made",
      "description": "Description of the diagnosis",
      "end_date": "End date of the diagnosis, if applicable",
      "note_id": "ID of the note associated with this diagnosis"
    }
  ]
}

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

​
[]Diagnosis
Fetch Action Response Object