Skip to main content
images/elation.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "created_at": "2024-01-15T10:30:00Z",
    "deleted_date": "",
    "history_type": "HISTORY_TYPE_PAST",
    "id": "123456789",
    "patient_id": "987654321",
    "rank": 1,
    "text": "Patient has a history of hypertension"
  }
}

{
  "$result_object_key": {
    "created_at": "Timestamp when the history entry was created.",
    "deleted_date": "Timestamp when the history entry was deleted, if applicable.",
    "history_type": "Type of history entry.",
    "id": "Unique identifier for the history entry.",
    "patient_id": "ID of the patient this history belongs to.",
    "rank": "Rank or order of the history entry.",
    "text": "Content of the history entry. Must not be empty."
  }
}

​
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.
​
History
Fetch Action Response Object