Meridian is a living document, not a static policy. This page describes how provider feedback flows from the point of care into reviewed, agreed-upon updates. The system works at whatever tier of infrastructure is currently available — starting functional today and evolving toward a continuously improving clinical intelligence platform.
Each item in Meridian has a speech bubble icon. Tapping it opens a pre-addressed email with the module name and item pre-filled in the subject line. You add your comment and send. Emails route to a dedicated Meridian Feedback folder via Outlook rule. An administrator reviews the folder periodically and consolidates feedback manually.
Write your comment. Hit send. That's it.
The module owner reviews submissions on a defined cadence (target: monthly). Accepted changes are incorporated into the next version of the relevant module. You will see a version number update in the footer of each module.
Power Automate access (typically included in M365 license). Low IT lift — may be self-service.
Speech bubble emails continue as in Tier 1, but a Power Automate flow monitors the Meridian Feedback inbox and automatically parses each submission. Module name and item are extracted from the subject line. A structured row is appended to a shared Excel file or SharePoint List with columns for: timestamp, submitter, module, item reference, and comment body. A notification is posted to a designated Teams channel so the review team sees submissions in real time.
A shared spreadsheet or SharePoint List, filterable by module, date, and review status. Designated reviewers have read access at all times. No manual aggregation required.
One Power Automate flow connecting Outlook to SharePoint. Estimated setup time with IT support: half a day.
IT involvement. Standard M365 stack. Recommended architecture for enterprise deployment.
Speech bubble opens a Microsoft Form (not an email) with structured fields: module name (pre-filled), item reference (pre-filled), comment type (factual correction / clinical disagreement / suggested addition / other), comment text, and optional submitter name. Submission triggers a Power Automate flow that creates a SharePoint List item, creates a Planner task in the Meridian Feedback plan, and posts a Teams notification.
A Planner kanban board with one column per module. Each piece of feedback is a card that moves across columns: Submitted, Under Review, Accepted, Incorporated, Deferred. Reviewers can comment on cards, assign them, set due dates, and track resolution without leaving Teams.
A Power Automate flow generates a Word document from all Accepted items in the SharePoint List, structured by module with item-level comments. This document is the update spec passed to the development workflow. Version history is maintained in SharePoint.
Replace mailto links with Microsoft Forms links. Add Planner integration to existing Power Automate flow. Estimated additional setup time: half a day.
Requires development investment and IT partnership. This tier represents the full platform vision for Meridian.
Speech bubbles write directly to a structured database. Submissions are timestamped, tagged to content versions, and visible to submitters with status indicators. High-frequency feedback on a specific item surfaces automatically as a priority signal. Review cycles shift from periodic to rolling.
A conversational interface grounded exclusively in Meridian content plus a curated clinical corpus. Answers questions about institutional approach — not general medical questions. Cites specific modules and items. Explicitly declares when a question falls outside scope.
Each module item carries optional reference links maintained by the module owner: guidelines (KDIGO, CDC, APA), key evidence (SPRINT, CDC 2022), tools (CKD-EPI calculator, MME calculator), and patient resources. Links are versioned and reviewed before each module version publishes.
For questions at the edge of the curated corpus, the chatbot fetches current information from pre-approved external sources — society guidelines, FDA drug safety communications, CDC clinical guidance — combining institutional policy with the latest external evidence. Never fetches from unapproved sources.
Every content change tracked with author, date, source feedback, reviewer approval, and prior version preserved. Providers see when any item was last reviewed and what changed. Transforms Meridian into an auditable clinical governance artifact.
Aggregate, de-identified data on module access, feedback volume, FAQ usage, and chatbot queries. Answers which clinical areas have provider uncertainty, which items generate disagreement, and whether Meridian is used at point of care or only during onboarding.