> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/documents-and-assessments/visual-components-dependencies.md).

# Visual Components Dependencies

Welkin Designer offers a number of different data visualization options for both users and patients. The majority of these items will be found under the Designer section called "Visual Components". The options include:

* Forms
* PFA Folders
* Charts and Graphs
* Data Views
* Program Summary
* Relationship View (Deprecated)

**Forms:** The Forms area is where you can create structured data input visualizations for either patients or users. Some examples include:

* Patient Assessment or Patient Satisfaction surveys
* Standard Medical Forms (PHQ9, GAD7, etc)
* SOAP notes
* Referral Forms

To complete Forms, you must have already completed some [CDT](/designer/documents-and-assessments/visual-components-dependencies.md)s.

To learn more specifics about Forms and form creation, please refer to the Knowledge Base article [here](/designer/documents-and-assessments/visual-components-dependencies.md).

**PFA Folders:** PFA (Patient Facing Assessment) Folders are used to configure the


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.welkinhealth.com/designer/documents-and-assessments/visual-components-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.