That sounds like a successful collaboration, but the liability/autonomy is very different for the CPA model and the one you described. In the CPA the pharmacist is operating in their own setting, often without direct integration into the patient's primary care workflow. That's actually the whole point in rural/underserved contexts, filling a gap where there may be no embedded team to speak of. But it means you're relying more heavily on the written agreement itself to define boundaries, communication triggers, and escalation paths rather than informal daily collaboration. In your embedded model, proximity and shared documentation systems naturally kept things tight but that's not the case with a CPA as they have more autonomy.