> 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/home-screen.md). # Home Screen ## Overview The home screen is the first view care team members see upon logging in to the Welkin Care Portal. It provides a summary of your active workload, patients, and upcoming activity. ## Home Screen Layout ### Navigation Bar The left-side navigation bar provides access to all major sections of the Care Portal: * **Patients** – your patient list * **Calendar** – your schedule and encounters * **Messages** – your communication inbox * **Tasks** – assigned tasks * **Reports/Insights** – data views and metrics ### Main Content Area The center of the home screen displays your patient dashboard, task list, and encounter schedule depending on how your organization has configured the home page. ### Search Bar A global search bar at the top allows you to search for patients by name, phone number, email, or patient ID. Results display inline as you type. ### User Menu Click your profile icon in the top right to access your user settings, notification preferences, and logout option. ## Navigating the Care Portal Use the left navigation to move between sections. The breadcrumb trail at the top of each page shows where you are in the portal and allows quick back-navigation. If your organization uses the new widget-based homepage, see [New Homepage](/care/getting-started/new-homepage.md) for details. --- # 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/home-screen.md?ask=&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.