> 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/care/getting-started/new-homepage.md).

# New Homepage

## Overview

The New Homepage enhances daily operations by providing a personalized command center that transforms patient data into actionable insights. It consists of configurable **Widgets** organized into role-based **Dashboards**. Built on the OpenSearch analytics database, the Homepage allows for highly flexible querying while supporting real-time data updates.

> **Note:** The expression-builder interface enables business users to create queries within the Designer. However, users must have an understanding of XOR logic, Welkin entities and their relationships to construct valid queries. Ideally, users should be able to understand and validate the generated OpenSearch query displayed in the Source Code tab.
>
> Customers are responsible for building and testing Widgets. Assistance can be requested from the Welkin team via Professional Services hours if necessary (PSE).

For configuration steps, see:

* [New Homepage Setup (Admin)](https://docs.welkinhealth.com/admin/homepage/new-homepage-setup) – how to activate the New Homepage per environment
* [New Homepage Configuration (Designer)](https://docs.welkinhealth.com/designer/homepage-configuration/new-homepage-designer) – how to create Dashboards and Widgets, including the full reference for date expressions and other condition-building variables

<figure><img src="https://1217226817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQvXoGL7kKvEhUWEGGIAn%2Fuploads%2Fp7FJf2Ym9ICjngYEK36b%2FScreenshot%202026-03-25%20at%2011.12.08.png?alt=media&#x26;token=1ddcf975-dfd0-4c23-b045-3c68e96688dc" alt=""><figcaption></figcaption></figure>

***

## Dashboards

A Dashboard is a set of widgets available on the New Homepage to users with a specific role.

When you log into the Care Portal, a drop-down list on the New Homepage displays the Dashboards available for your role. Selecting a Dashboard displays the list of Widgets added to it.

> **License note:** An environment is limited to **1 Dashboard** under the standard license. This limitation can be unlocked by enabling the **Homepage Plus** feature. Contact your CSM for pricing information.

***

## Widgets

A Widget is a set of rules by which information is selected and displayed. Each Widget queries patient or related entity data and presents it as a filterable, sortable list in the Care Portal.

### Entity Types

Widgets are built around one of the following entity types:

* Patient
* Patient Program
* Assessments
* Encounter
* CDT
* Notification
* Calendar event

The Patient is the parent entity; all others are child entities. Building a Widget from a child entity may introduce limitations (for example, filtering by patient fields is not possible when the widget is built from a child entity).

> **License note:** An environment is limited to **6 Widgets** under the standard license. This limitation can be unlocked by enabling the **Homepage Plus** feature. Contact your CSM for pricing information.

***

## Using Widgets in the Care Portal

Once Widgets are added to a Dashboard, the Care Portal displays a list of patients (or other entities) for whom the specified conditions are met.

Default sorting is applied to each Widget as configured, and column filters can be used to narrow results further.

Clicking on a patient or record in the Widget navigates directly to their profile or the relevant record.

### Filtering by Date

Columns with a **Date** or **DateTime** field type display a **date range picker** instead of a value list. Click the filter icon on a date column to open the picker and choose a preset or custom range.

Available date range presets for widget date filters:

| Preset       | Range                                   |
| ------------ | --------------------------------------- |
| All Time     | No date restriction (clears the filter) |
| Yesterday    | The previous calendar day               |
| Today        | The current calendar day                |
| Tomorrow     | The next calendar day                   |
| This Week    | The current week (Sunday–Saturday)      |
| Next Week    | The following week                      |
| Last 7 Days  | Today and the 6 days before it          |
| Last 30 Days | Today and the 29 days before it         |
| Custom       | Pick a specific start and end date      |

Selecting **All Time** clears the date filter and shows all records regardless of date.

***

## Building Widget Conditions

Widget conditions are configured in the Designer. See [New Homepage Configuration (Designer)](https://docs.welkinhealth.com/designer/homepage-configuration/new-homepage-designer#date-expressions) for the full reference.


---

# 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/care/getting-started/new-homepage.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.
