Hospital & Pharmacy Collaboration MOU Template

Partnership Overview & Purpose

A summary of why the hospital and pharmacy are entering the collaboration: the clinical or operational problem it solves, the patient population affected, and the high-level goals both organizations are agreeing to pursue together before any referral or medication activity begins. This section names the specific departments or service lines involved on each side, such as discharge planning, ambulatory care, or a specific pharmacy branch network, so the partnership is never read as a blanket agreement between the two organizations as a whole. It also states the shared outcome both sides are working toward, for example reducing avoidable hospital readmissions tied to medication non-adherence, so every later section can be measured against that stated purpose rather than interpreted in isolation.

Scope of Collaboration

The specific clinical activities covered: patient referrals, medication therapy management, immunization support, discharge medication reconciliation, inventory or formulary access, and any shared clinical programs such as a transitions-of-care or chronic disease management initiative. This section draws an explicit line between what is included in the partnership and what still requires a separate agreement or purchase order, which matters most at renewal time, when one side assumes an activity was always covered and the other assumes it was always a paid add-on. Listing activities individually, rather than describing the partnership in general terms, also makes it far easier to add or remove a service line later without renegotiating the entire MOU from scratch.

Roles & Responsibilities

What the hospital is responsible for, such as referral volume, patient records access, clinical oversight, and discharge planning coordination, versus what the pharmacy is responsible for, such as dispensing, medication counseling, inventory availability, and adherence follow-up calls. Clear ownership here prevents the most common source of hospital-pharmacy friction: both sides assuming the other party is handling a task that, in practice, neither party actually owns. This section should also name a backup contact for each responsibility, so a single staff turnover on either side doesn't quietly stall a referral pathway or a medication reconciliation workflow that patients are depending on. Where a task genuinely sits across both organizations, such as verifying insurance coverage before a referral is finalized, this section should say so explicitly and name which party initiates it, rather than leaving a shared task undocumented and assuming goodwill will cover the gap.

Patient Data Sharing & HIPAA Compliance

The categories of protected health information that will be shared, the systems or channels used to share it, and the safeguards both parties commit to, including access controls, encryption in transit and at rest, minimum-necessary data limits, and audit logging of who accessed what and when. States explicitly that all parties will comply with HIPAA and applicable state privacy law, and notes that where PHI is exchanged for operational purposes beyond direct treatment, such as shared reporting dashboards or joint billing, a separate Business Associate Agreement (BAA) will typically be required alongside this MOU. It also specifies what happens to shared data if the partnership ends: whether records are returned, deleted, or retained under a separate retention schedule.

Financial Terms & Reimbursement

Whether the collaboration involves any exchange of payment: shared program costs, reimbursement for medication therapy management services, grant funding tied to a specific initiative, or a purely no-cost referral relationship built on mutual benefit. Most hospital-pharmacy MOUs are cost-neutral, but this section exists specifically so that assumption is written down in the document rather than discovered for the first time when an invoice arrives. If any costs are shared, this section should also name who approves budget changes and how often the cost-sharing split is revisited, since referral volume and staffing needs on both sides tend to shift well before a 12-month term is up.

Communication, Escalation & Reporting Cadence

The operational cadence that keeps the partnership running day to day: a named point of contact at each organization, a recurring review meeting held monthly or quarterly, a two-tier escalation path that separates clinical concerns (a missed medication reconciliation, an adverse event) from administrative ones (a billing discrepancy, a staffing gap), and the specific metrics each side reports on, such as referral volume, medication adherence rates, and average turnaround time from referral to first fill. Most public-sector MOU toolkits stop at a vague line about parties communicating "as needed." This section replaces that with an actual protocol and named owners for each escalation tier, along with a target response time for each tier, so a routine communication gap doesn't quietly become a patient-safety incident before either side notices it. It also defines how the review meeting's outcomes get documented, so lessons from month one aren't lost by month six.

Term, Renewal & Termination

The MOU's effective period, commonly 12 months, how it renews (automatic renewal unless either party objects in writing, or a required re-signature at each anniversary), and how either party can exit: the notice period required, what happens to shared data and any pending referrals at termination, and whether termination requires cause or can happen for convenience with sufficient notice. This section should also address a wind-down period for active patients already in the middle of a shared program, since an abrupt termination mid-treatment creates real clinical risk that a purely commercial contract wouldn't need to account for. It's worth naming, in advance, who is responsible for notifying affected patients if the partnership ends while they're mid-course on a shared medication management plan, rather than leaving that decision to whichever staff member happens to notice the gap.

Signatures

The signature block: an authorized administrator from the hospital and the pharmacist-in-charge or designated pharmacy representative sign and date the MOU, with space reserved for a witness or notarization if either organization's internal policy requires one before the partnership can go live. Include a line for each organization's compliance or legal reviewer if their internal approval process requires sign-off before an administrator's signature is considered binding.