{ "$result_object_key": [ { "custom_module_form_id": "RequestedFormCompletion's custom module form ID", "custom_module_form_name": "RequestedFormCompletion's custom module form name", "dietician_organization_id": "Organization ID for the User's (Patient's) registered dietitian", "dietitian_email_address": "Email address of the User's (Patient's) registered dietitian", "dietitian_first_name": "First name of the User's (Patient's) registered dietitian", "dietitian_id": "ID of the User's (Patient's) registered dietitian", "dietitian_last_name": "Last name of the User's (Patient's) registered dietitian", "dietitian_organization_id": "Organization ID for the User's (Patient's) registered dietitian", "id": "RequestedFormCompletion object ID", "patient_id": "Patient's ID" } ]}
v1
List Requested Form Completion
Documentation for the List Requested Form Completion action for Healthie
{ "$result_object_key": [ { "custom_module_form_id": "RequestedFormCompletion's custom module form ID", "custom_module_form_name": "RequestedFormCompletion's custom module form name", "dietician_organization_id": "Organization ID for the User's (Patient's) registered dietitian", "dietitian_email_address": "Email address of the User's (Patient's) registered dietitian", "dietitian_first_name": "First name of the User's (Patient's) registered dietitian", "dietitian_id": "ID of the User's (Patient's) registered dietitian", "dietitian_last_name": "Last name of the User's (Patient's) registered dietitian", "dietitian_organization_id": "Organization ID for the User's (Patient's) registered dietitian", "id": "RequestedFormCompletion object ID", "patient_id": "Patient's ID" } ]}
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.