> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/changelog/2026/next-generation-clinicians-portal-and-pharmacy-integrations-beta.md). # Next-Generation Clinicians Portal & Pharmacy Integrations Beta *Released February 9, 2026* **Next-Generation Clinicians Portal**: a new design language and feature set for managing the entire patient lifecycle within the platform — new analytics dashboards, a new Orders page, voucher and intake form management, customer/patient management, a redesigned Settings page, an improved large-display experience, and a more cohesive mobile experience. **Pharmacy Integrations (major milestone, closed beta)**: MDI now connects directly with selected pharmacy partners for more efficient prescription delivery, bringing the entire order workflow into the platform. This release is effectively the origin of what's now documented as Direct to Pharmacy (DTP). ## \[Clinicians App] * Ability to hide PHI on mobile * Improved labeling for forwarded messages * Improved encounter rejection modal * Redesigned partner details modal (including partner offerings) * Support for two new labs when parsing results ## \[Patients] * Improvements to camera access permissions * Fixed demo vouchers requesting patient phone number twice * New message sender type ("Partner") for API-created messages * New digital signature question type ## \[Web] * New automation for generating PDFs for standard prescriptions * Fixed bold text in intake form questions not reflecting in the Patient App * Tags added to encounters export * New automation steps to support pharmacy integrations * Improvements to invoicing ## \[API] * Daily email notifications for failed webhooks * New webhook for clinician license updates * Improvements to the WooCommerce extension * Fixed security emails displaying incorrect location * Fixed incorrect counts in flagged encounter emails --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mdintegrations.com/changelog/2026/next-generation-clinicians-portal-and-pharmacy-integrations-beta.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.