> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List requested form completion

***

title: "List Requested Form Completion"
description: "Documentation for the List Requested Form Completion action for Healthie"
sidebarTitle: "List Requested Form Completion"
----------------------------------------------

![images/healthie.svg](https://mintcdn.com/morfhealth/EU2WCxuXGIUQcziR/images/healthie.svg?fit=max\&auto=format\&n=EU2WCxuXGIUQcziR\&q=85\&s=d168a24dbae69f2202ca63dd7aa2e1f3)

# Parameters

**Action** `Parameters`

**parameters**

**Keywords** `string`

This field maps to the destination API `keywords` field.

Optional search text passed to Healthie to narrow the requests returned.

**Status** `string`

This field maps to the destination API `status` field.

Set to `Open` to return only requests the patient hasn't completed yet. Completed requests drop out of the list, so an empty result means nothing is outstanding.

## Checking whether a patient has completed a form

The result doesn't include a status field. To check completion, filter the request with **Status** set to `Open` and look for the form in the result:

```js Form still outstanding theme={null}
open_requests.exists(r, r.custom_module_form_id == "1252974")
```

```js Form completed (or never requested) theme={null}
!open_requests.exists(r, r.custom_module_form_id == "1252974")
```

Replace `open_requests` with this node's result object key and `1252974` with the Healthie form ID. A form that was never requested also has no open request, so the second check can't tell "completed" from "never sent"; make sure the form is requested (for example, automatically when the appointment is booked) before relying on it.

```json Result Object Example theme={null}
{
  "$result_object_key": [
    {
      "custom_module_form_id": "72028",
      "custom_module_form_name": "Intake Questionnaire",
      "dietician_organization_id": "123450",
      "dietitian_email_address": "drfleming@example.com",
      "dietitian_first_name": "Alexander",
      "dietitian_id": "100070",
      "dietitian_last_name": "Fleming",
      "dietitian_organization_id": "123450",
      "id": "57211",
      "patient_id": "121250"
    }
  ]
}
```

```json Result Object Description theme={null}
{
  "$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"
    }
  ]
}
```

### Result Object Field Details

You can use the result of the action's data as inputs to downstream workflow actions.

Each fetch action requires an object name, which nests the action's result data inside the downstream data context in the workflow. See [Passing Data Between Actions](https://docs.morf.health/docs/knowledge_base/passing_data_between_actions.md) for how to set it and reference the result from downstream nodes.

Here we demonstrate how to refer to this data using the prefix `$result_object_key`.

**\[]RequestedFormCompletion** `Fetch Action Response Object`

**fields**

**id** `string` *required*

RequestedFormCompletion object ID

```json CEL theme={null}
$result_object_key[*].id
```

```json Example theme={null}
"57211"
```

**patient\_id** `string` *required*

`ID` Patient's ID

```json CEL theme={null}
$result_object_key[*].patient_id
```

```json Example theme={null}
"121250"
```

**dietician\_organization\_id** `string`

Organization ID for the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietician_organization_id
```

```json Example theme={null}
"123450"
```

**dietitian\_organization\_id** `string`

Organization ID for the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietitian_organization_id
```

```json Example theme={null}
"123450"
```

**dietitian\_first\_name** `string`

First name of the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietitian_first_name
```

```json Example theme={null}
"Alexander"
```

**dietitian\_last\_name** `string`

Last name of the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietitian_last_name
```

```json Example theme={null}
"Fleming"
```

**dietitian\_email\_address** `string`

Email address of the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietitian_email_address
```

```json Example theme={null}
"drfleming@example.com"
```

**dietitian\_id** `string`

ID of the User's (Patient's) registered dietitian

```json CEL theme={null}
$result_object_key[*].dietitian_id
```

```json Example theme={null}
"100070"
```

**custom\_module\_form\_id** `string`

RequestedFormCompletion's custom module form ID

```json CEL theme={null}
$result_object_key[*].custom_module_form_id
```

```json Example theme={null}
"72028"
```

**custom\_module\_form\_name** `string`

RequestedFormCompletion's custom module form name

```json CEL theme={null}
$result_object_key[*].custom_module_form_name
```

```json Example theme={null}
"Intake Questionnaire"
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.