# Brand Terminology Flexibility

## Overview

Welkin allows organizations to customize the names of core platform objects to match their own brand language and clinical terminology. Instead of showing generic labels like "Patient" or "Program", you can configure the platform to display your organization's preferred terms throughout the Care Portal.

***

## What Can Be Renamed

The following objects support custom terminology:

* **Patient** – rename to "Member", "Client", "Resident", or any term your organization uses
* **Program** – rename to "Care Plan", "Pathway", "Track", etc.
* **Phase** – rename to "Stage", "Step", "Level", etc.
* **Encounter** – rename to "Visit", "Appointment", "Session", etc.
* **Assessment** – rename to "Form", "Survey", "Questionnaire", etc.
* **Goal** – rename to "Objective", "Target", etc.

***

## How to Configure

1. In the Designer, navigate to **Terminology** or **Brand Settings**.
2. Locate the object you want to rename.
3. Enter the **singular** and **plural** forms of your preferred term.
4. Save and publish the changes.

The new terminology appears throughout the Care Portal UI, including navigation labels, headings, buttons, and notifications.

***

## Notes

* Terminology changes are display-only. They do not affect underlying data, API field names, or exports.
* Custom terminology is applied consistently across all roles and views in the Care Portal.
* If your organization uses the API, API field names (such as `patient`, `program`) remain unchanged regardless of display terminology.

***

## Publishing

Create a draft in the Designer and publish to apply terminology changes to the live Care Portal.


---

# 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/terminology-and-help/brand-terminology-flexibility.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.