Skip to main content
images/elation.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "credentials": "MD",
    "email_address": "ed.jenner@vaccinesrus.com",
    "first_name": "Edward",
    "id": "214338616987110",
    "is_active": true,
    "last_name": "Jenner",
    "license": "A122123",
    "license_state": "CA",
    "npi": "1619862113",
    "practice_id": "3022123122131",
    "specialty": "Family Medicine",
    "user_id": "582381"
  }
}

{
  "$result_object_key": {
    "credentials": "Physician's credentials, qualifications or post-nominals",
    "email_address": "Physician's email address",
    "first_name": "Physician's first name, given name, or forename.",
    "id": "Unique identifier for the physician in the Elation system.",
    "is_active": "Flag indicating whether the physician is active.",
    "last_name": "Physician's last name, family name, or surname.",
    "license": "Physician's license",
    "license_state": "Physician's license state",
    "npi": "Physician's NPI",
    "practice_id": "Practice ID in Elation",
    "specialty": "Medical specialty",
    "user_id": "User ID in the Elation system."
  }
}

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