# Encounters and Dependencies

## Overview

Encounters in Welkin represent documented interactions between care team members and patients – such as appointments, check-ins, or clinical visits. In the Designer, you configure the structure of encounters, including which assessments and forms are required, and what dependencies exist between encounter components.

***

## Encounter Configuration in the Designer

The Designer controls:

* **Encounter types** – the categories of encounters your organization uses (e.g., "Initial Assessment", "Follow-Up", "Discharge")
* **Required assessments** – which forms must be completed during each encounter type
* **Display order** – how assessments and fields appear within the encounter view
* **Dependencies** – rules that control when encounter components become available

***

## What Are Dependencies?

Dependencies create conditional logic within an encounter. For example:

* A specific assessment only appears after a prerequisite assessment is completed
* A section of the encounter unlocks when a certain field value is set
* A required action must be completed before the encounter can be finalized

***

## Configuring Dependencies

1. In the Designer, open an encounter type.
2. Navigate to the **Dependencies** section.
3. Define the **trigger condition** – the event or field value that activates the dependency.
4. Define the **dependent action** – what becomes available, required, or locked.
5. Save and publish.

***

## Common Dependency Patterns

* **Assessment gating** – completing Assessment A is required before Assessment B appears
* **Conditional required fields** – a field becomes required only if another field has a specific value
* **Encounter completion rules** – all required assessments must be completed before the encounter can be closed

***

## Publishing

Encounter and dependency configuration must be published from the Designer before changes take effect in the Care Portal.

***

## Related Topics

* [Encounters Overview](https://welkin-health-1.gitbook.io/welkin-health-docs/care/feature-overview-encounters) – encounters in Care
* [Create, Modify, Complete Encounters](https://welkin-health-1.gitbook.io/welkin-health-docs/care/encounters-create-modify-complete) – encounter workflow
* [How to Create an Assessment or Form Template](/designer/documents-and-assessments/how-to-create-an-assessment-or-form-template.md) – creating forms
* [Add Conditionality to Assessments](/designer/documents-and-assessments/how-to-add-conditionality-to-assessments.md) – conditional logic


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/designer/notifications-and-communications/encounters-and-dependencies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.