> 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/2025/uat-environment-no-code-automations-and-carepair-launch.md). # UAT Environment, No-Code Automations & CarePair Launch *Released August 19, 2025* **New UAT Environment**: a staging/User Acceptance Testing environment, separate from production, receives release candidates 2+ weeks before production. Partner/admin accounts were migrated (no offerings/intake forms were migrated, to avoid data-sync issues). Sandbox remains the primary environment for new integration/development work; UAT is for stress-testing and compatibility validation, not ongoing development. It's accessible at the API URL `api.mdintegrations.xyz` and the Partner Admin Panel `mdintegrations.xyz` — use "Forgot Password" to reset migrated account access. **Updated Partner Onboarding Process**: new tools and content help you integrate, including a way to indicate partnered pharmacies and a centralized offerings library with pre-approved treatments you can import directly into your account. **Automations (launch)**: a no-code workflow builder with multiple triggers and step-by-step logic flows. It starts with automated NPS campaign submission; the roadmap includes automating patient communication (including AI chatbot messaging), automated follow-up visit flows, custom pharmacy order integrations, and triage/escalation of inbound messages. **NPS Campaigns (launch)**: custom Net Promoter Score campaigns to gather patient feedback about their provider/treatment experience. ## \[Clinicians App] * Added a walkthrough video * App settings now sync across devices * Improved AI algorithms; AI reply suggestions now offer up to 4 variations * New Smart View for questionnaires * Messaging a patient with multiple open encounters now asks which encounter to move to Waiting * New contextual onboarding tour; deep-links persist after login * Clinicians can opt out of certain offering assignments * Updates to the assignment/reassignment algorithm * Doctors now receive treatment-opportunity suggestions when approving encounters (CarePair) — this is CarePair's origin/launch ## \[Patients] * Blank loading screen while partner theming loads (previously the default theme flashed) * Integrated NPS collection workflow * Improvements to the Stripe checkout experience * Fixed session issues with account switching * Pregnancy question shown only for patients over 8 years old * Tracking of abandonment for custom questions ## \[Web Platform] * Redesigned onboarding flow * New sections for Automations and NPS Campaigns * Option to exclude or prioritize clinicians for specific offerings * Image and Store URL can now be added to offerings for customization (CarePair-related e-commerce metadata) ## \[API] * New email notifications for flagged/pinned encounters * Automatic refunds for expired, unused vouchers * Enhanced AI and lab result parsing * New email alerts for pending uploads (e.g. driver's license, AV) * UAT environment support * WooCommerce integration enhancements --- # 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/2025/uat-environment-no-code-automations-and-carepair-launch.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.