{
  "$result_object_key": [
    {
      "id": "4894",
      "is_duplicate": false,
      "relationships": "Mother",
      "snomed_term": {
        "concept_id": "12345",
        "term": "Diabetes"
      }
    }
  ]
}

{
  "$result_object_key": [
    {
      "id": "The unique identifier of the family history condition",
      "is_duplicate": "Is the condition a duplicate",
      "relationships": "Enum field for family relationships",
      "snomed_term": {
        "concept_id": "ID for snomed term",
        "term": "Snomed term name"
      }
    }
  ]
}

images/healthie.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": [
    {
      "id": "4894",
      "is_duplicate": false,
      "relationships": "Mother",
      "snomed_term": {
        "concept_id": "12345",
        "term": "Diabetes"
      }
    }
  ]
}

{
  "$result_object_key": [
    {
      "id": "The unique identifier of the family history condition",
      "is_duplicate": "Is the condition a duplicate",
      "relationships": "Enum field for family relationships",
      "snomed_term": {
        "concept_id": "ID for snomed term",
        "term": "Snomed term name"
      }
    }
  ]
}

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

​
[]FamilyHistoryCondition
Fetch Action Response Object