> 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/patients/patient-profile-overview.md). # Patient Profile Overview ## Overview The Patient Profile Overview panel provides a quick-reference summary of the most important information about a patient. It is designed for care team members who need to orient themselves quickly before an encounter or task. ## What the Overview Shows The patient profile overview typically includes: * **Patient name and photo** (if uploaded) * **Date of birth and age** * **Contact information** – primary phone and email * **Care team** – the assigned care team members for this patient * **Program enrollment** – current programs and phases * **Upcoming encounters** – next scheduled visit or call * **Outstanding tasks** – tasks assigned to the care team for this patient * **Recent activity** – last communication, last completed assessment, or last encounter ## Customizing the Overview The fields displayed in the patient overview are configured in Designer using custom profile templates. Your organization may show additional fields such as insurance information, referring provider, or custom patient attributes. Contact your Welkin administrator or Designer user if you need additional fields added to the overview panel. ## Related Pages * [Patient Profile](/care/patients/patient-profile.md) – full patient profile documentation * [Editing Patient Information](/care/patients/editing-patient-information.md) – how to update patient data * [Patient Programs and Phases](/care/patients/care-programs-and-phases.md) – managing program enrollment {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} --- # 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/patients/patient-profile-overview.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.